[
https://issues.apache.org/jira/browse/JENA-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920992#comment-16920992
]
Code Ferret commented on JENA-1749:
-----------------------------------
So your use case is limited to:
{code}
?s text:query ( "query with fields" LUCENE_LIMIT )
{code}
with no use of `highlight:` or `lang` object args?
If so, so then one possibility is to add a _faux_ property,
{{text:withFields}}, to be used like so:
{code}
?s text:query ( text:withFields "query with fields" LUCENE_LIMIT )
{code}
This would make clear the use case and provide straightforward setup of the
query and handling of the results.
As I said I can't get to fiddling with the code and adding new unit tests and
so on until after 24 Sept. I expect it to take a couple of days.
> 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)
