[
https://issues.apache.org/jira/browse/JENA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907306#comment-15907306
]
Anuj Kumar commented on JENA-1305:
----------------------------------
Hi [~osma]
I have been able to at-least handle multi valued predicates. I now only do an
append of the data and not replace. So far so good. This is the first
implementation, that may need to be changed for handling cases where we need to
delete subset of data instead of entire data. This is your point 3 above.
And for that, I want to get some clarity on different scenarios that I need to
handle. Will multi value occur of language field or for any field? This will
derive my design and implementation.
Any insights into this aspect will help greatly for me developing a generic
solution.
Thanks,
Anuj Kumar
> 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)
