Github user amiara514 commented on the pull request:
https://github.com/apache/jena/pull/64#issuecomment-103635153
Languages can now be stored in the index by providing a langField param to
EntityDefinition (assembler and java code). So you can use a TexIndexLucene
with your own analyzer and target language of localized literals.
3 cases on Sparql clauses :
```?s text:query (rdfs:label 'word' 'lang:en' )``` will target english
literals
```?s text:query (rdfs:label 'word' 'lang:none')``` will target unlocalized
literals
```?s text:query (rdfs:label 'word')``` will ignore language
NOTE: in Sparql queries, ```lang``` is a predefined keyword and the Lucene
query will be mapped with the right langField name.
Moreover, TextIndexConfig class has been introduced and EntityDefinition
refactored to simplify TextDatasetFactory as desired.
LuceneUtil has moved as Util class in analyzer package. It still used with
the LocalizedAnalyzerAssembler
---
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.
---
