[
https://issues.apache.org/jira/browse/JENA-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974558#comment-15974558
]
Osma Suominen commented on JENA-1305:
-------------------------------------
[~anujkumar] The ES documentation should be integrated with the rest of the
jena-text documentation, meaning this page:
https://jena.apache.org/documentation/query/text-query.html
As [~ajs6f] said, you can either use the "Improve this Page" link at the top,
or check out the SVN tree, make changes, and send a patch (i.e. attach it to
this issue).
Currently the jena-text documentation still talks about Solr. I figured it
would be easiest to do a search-and-replace from Solr to Elasticsearch (after
all, they are both similar external indexes) and then fix the remainder of the
text so that it applies properly to Elasticsearch.
Most of the jena-text features documented on that page work only with the
Lucene backend and those don't have to be changed (though it would be good to
somehow state which features are supported by each backend, perhaps as a table).
> 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
>
> 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)
