[
https://issues.apache.org/jira/browse/JENA-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274554#comment-16274554
]
ASF GitHub Bot commented on JENA-1438:
--------------------------------------
Github user xristy commented on a diff in the pull request:
https://github.com/apache/jena/pull/320#discussion_r154380929
--- Diff:
jena-text/src/main/java/org/apache/jena/query/text/TextQueryPF.java ---
@@ -347,11 +352,15 @@ private StrMatch objectToStruct(PropFuncArg
argObject, boolean executionTime) {
log.warn("Text query string is not a literal " + list) ;
return null ;
}
-
- if (x.getLiteralDatatype() != null &&
!x.getLiteralDatatype().equals(XSDDatatype.XSDstring)) {
--- End diff --
Thank you for the tips. I tried to avoid changing code that was present. I
plan to raise another issue or two in jena-text and will be glad to visit some
of these cases to try and use RDF functionality rather than bare Java
functionality. It certainly will make the code clearer.
> rdf:langString argument to text:query silently ignored
> ------------------------------------------------------
>
> Key: JENA-1438
> URL: https://issues.apache.org/jira/browse/JENA-1438
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
> Affects Versions: Jena 3.5.0
> Environment: N/A
> Reporter: Code Ferret
> Priority: Minor
>
> Queries of the form:
> {{?s text:query "some string"@lang-code}}
> return no results even when there are matches found by the _equivalent_:
> {{?s text:query ("some string" "lang:lang-code")}}
> {quote}
> Note the above _equivalent_ form is currently valid only if
> {{text:multilingualSupport false}}.
> {quote} See [JENA-1437|https://issues.apache.org/jira/browse/JENA-1437]
> A reasonable fix is to recognize the {{rdf:langString}} case and treat it as
> the _equivalent_ form referring to the {{text:defautlField}}; otherwise, at
> least an error should be indicated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
