[
https://issues.apache.org/jira/browse/JENA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902955#comment-15902955
]
Osma Suominen commented on JENA-1305:
-------------------------------------
Hi [~anujkumar],
If the tests run from {{mvn test}} then everything is fine, sorry for the
confusion.
I think your plan for having a single document per entity is reasonable. If you
can use ES features to maintain a list of values for a single field, then that
should work. However, it's possible that you also need to store the language
tag together with the value - think about the scenario point 3 above, where one
of the "Berlin" labels gets removed but not all of them.
An alternative that I used in the reimplementation of the Lucene multilingual
analyzer for jena-text is to split the fields by language, so that no the
Lucene index level you have language-specific fields, e.g. {{label_en}},
{{label_fr}}, {{label_de}} etc. This way you don't have to mix values having
different language tags.
> Elastic Search Support for Apache Jena Text
> --------------------------------------------
>
> Key: JENA-1305
> URL: https://issues.apache.org/jira/browse/JENA-1305
> Project: Apache Jena
> Issue Type: New Feature
> Components: Text
> Affects Versions: Jena 3.2.0
> Reporter: Anuj Kumar
> Assignee: Osma Suominen
> Labels: elasticsearch
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> This Jira tracks the development of Jena Text ElasticSearch Implementation.
> The goal is to extend Jena Text capability to index, at scale, in
> ElasticSearch. This implementation would be similar to the Lucene and Solr
> implementations.
> We will use ES version 5.2.1 for the implementation.
> The following functionalities would be supported:
> * Indexing Literal values
> * Updating indexed values
> * Deleting Indexed values
> * Custom Analyzer Support
> * Configuration using Assembler as well as Java techniques.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
