[
https://issues.apache.org/jira/browse/JENA-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945007#comment-16945007
]
Brian McBride edited comment on JENA-1749 at 10/5/19 7:53 AM:
--------------------------------------------------------------
I suggest some clarification of the documentation is needed before this issue
is fully resolved.
I don't think this needs to be addressed for 3.13.1. Perhaps I should register
it as a new Jira rather than reopening this one.
The documentation states that multiple fields in text queries are not
supported. That should be amended to say something along this lines of:
- normally multiple fields in a text query won't have the effect that you might
expect because each triple is indexed as a separate document
- multiple fields in a text query are accepted and may be useful, e.g. where
the text index has not been created by the provided Jena text mechanisms but
provided by other means
- an explanation of limitations on the bound values should there be multiple
fields in a returned document
I would be happy to suggest some words if that would be helpful.
was (Author: bwm):
I suggest some clarification of the documentation is needed before this issue
is fully resolved.
I don't think this needs to be addressed for 3.13.1. Perhaps I should register
it as a new Jira rather than reopening this one.
The documentation states that multiple fields in text queries are not
supported. That should be amended to say something along this lines of:
- normally multiple fields in a text query won't have the effect that you might
expect because each triple is indexed as a separate document
- multiple fields in a text query are accepted and may be useful, e.g. where
the text index has not been created by the provided Jena text mechanisms but
provided by other means
- an explanation of limitations on the bound values should there be multiple
fields in a returned document
> Support lucene field names in jena text queries
> -----------------------------------------------
>
> Key: JENA-1749
> URL: https://issues.apache.org/jira/browse/JENA-1749
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
> Affects Versions: Jena 3.13.0
> Reporter: Brian McBride
> Assignee: Code Ferret
> Priority: Major
> Fix For: Jena 3.14.0
>
> Attachments: stacktrace.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Until recent changes made during implementation of JENA-1723, it was possible
> to have a Lucene text query that used Lucene field names. With the
> implementation of JENA-1723 such queries result in a exception
> For example:
> {noformat}
> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
> PREFIX text: <http://jena.apache.org/text#>
> PREFIX ppd: <http://landregistry.data.gov.uk/def/ppi/>
> PREFIX lrcommon: <http://landregistry.data.gov.uk/def/common/>
> SELECT *
> { ?ppd_propertyAddress
> text:query ( "street: the" 3000000 ) .
> } LIMIT 1
> Cannot parse 'text:street: the ': Encountered " ":" ": "" at line 1, column
> 11.
> {noformat}
> This is a simplified query from a running production system that works in
> 3.12.0 but is failing in 3.13.0-SNAPSHOT.
> Some discussion and analysis of this issue has occurred in email:
> [https://lists.apache.org/thread.html/ccc1d5c5eaebcddafc2dbae85f3b5901396e3ab203df6bb4014e8270@%3Cusers.jena.apache.org%3E]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
