Github user osma commented on the pull request:
https://github.com/apache/jena/pull/52#issuecomment-101232751
> But how to change correctly the existent code to target Lucene taking
that extra language into account ?
You are currently already parsing the property function arguments in
TextQueryPF.build() to switch to the the correct text index.
If you want to instead have a single index with an extra lang field like I
suggested (note that this is just a suggestion - I think this would be cleaner
than having many separate indexes, but you or others may of course disagree!),
then you probably need to move that logic instead to the objectToStruct()
method in the same class, which also has access to the property function
arguments and already does a lot of parsing. objectToStruct() creates the query
string for Lucene, so you should be able to add an extra parameter there (look
at the query function which [adds a graph
parameter](https://github.com/LICEF/jena/blob/upstream/jena-text-multilingual/jena-text/src/main/java/org/apache/jena/query/text/TextQueryPF.java#L218)
for an example).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
