[
https://issues.apache.org/jira/browse/JENA-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921228#comment-16921228
]
Brian McBride commented on JENA-1749:
-------------------------------------
I understand you are not able to work on this until 24 Sept. I'm not sure
whether that is "can't fiddle with the code" till then or would like to put off
discussions till then. I won't expect a reply to this until you are back,
though I am concerned about whether this issue will be addressed before or
after the upcoming 3.13.0 release? I would like to use the release so I would
like it fixed before or JENA-1723 pulled from the release - but its not a do
or die thing.
Yes - my use case is limited to the query form you mention - we are just
looking up subjects. However, I may not be the only user of this
functionality. Is asking your users to change the best approach here?
JENA-1723 is prioritised as MINOR.
The issue with more complex queries e.g.
{{(?s ?score ?lit) text:query (" field: "foo" )}}
exists in the current code base. The JENA-1723 changes make that no worse.
Support for these more complex queries where the document is multi-fielded
could be treated as a separate issue and addressed in the next release. So if
restoring the functionality I use can be done by making the 'fix' you first
suggested and also not binding ?lit if it would bind null, we would be done and
dusted - at least for now.
Whereas the faux property is a bit of a carbuncle on the face of an old friend.
In the longer term would you be open to exploring more general support for
multi-fielded documents? It may well be in our interest here to make a
contribution that would enable our apps to rely only on core JenaText features?
> 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
> Priority: Major
> Attachments: stacktrace.txt
>
>
> 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:
> {quote}PREFIX xsd:
> [<http://www.w3.org/2001/XMLSchema#>|http://www.w3.org/2001/XMLSchema#]
> PREFIX text: [<http://jena.apache.org/text#>|http://jena.apache.org/text#]
> PREFIX ppd:
> [<http://landregistry.data.gov.uk/def/ppi/>|http://landregistry.data.gov.uk/def/ppi/]
>
> PREFIX lrcommon:
> [<http://landregistry.data.gov.uk/def/common/>|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.
> {quote}
> This is a simplifed 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.2#803003)
