[ 
https://issues.apache.org/jira/browse/JENA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902818#comment-15902818
 ] 

Anuj Kumar commented on JENA-1305:
----------------------------------

Hi [~osma]
 The tests will work just fine when run with mvn test because the test 
framework takes care of instantiating the embedded ES.

Thanks for clarifying the multiple value scenario. I think I can still make it 
work by using a single document in ElasticSearch. 
So this is what I will do:
* There will be a single Document for any given Entity. 
* If there are multiple values for the same predicate, instead of replacing 
them, I will append to the existing list of values. I know there is a way to do 
it in ES, I just have to test it.
* If there are multiple fields that needs to be indexed for the same Entity, 
all of them will be indexed in the same ES Document. This is working already.

Does this sound reasonable?


> 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)

Reply via email to