[
https://issues.apache.org/jira/browse/JENA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019424#comment-16019424
]
Anuj Kumar commented on JENA-1305:
----------------------------------
Hey [~andy.seaborne] [~ajs6f] Sorry for the delayed response. The CMS Content
update was only meant to replace Solr with ElasticSearch and do some cleaning.
It was not a complete representation of ElasticSearch Text Indexing within Jena.
That I captured solely in the Word Doc i attached.
I believe the idea was to separate out the Documentation for ElasticSearch in a
separate CMS Doc and link it from [this
page](https://jena.apache.org/documentation/query/text-query.html)
I believe it would be very important to provide the attached documentation to
the end user, else they will be left clueless as to what exactly ES does and
how to configure it.
Thanks.
> 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
> Fix For: Jena 3.3.0
>
> Attachments: Elastic Search Implementation of Jena Text Index.docx
>
> 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)
