You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "A. Soroka (JIRA)" <ji...@apache.org> on 2017/05/21 11:50:04 UTC

[jira] [Comment Edited] (JENA-1305) Elastic Search Support for Apache Jena Text

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

A. Soroka edited comment on JENA-1305 at 5/21/17 11:49 AM:
-----------------------------------------------------------

I've finally had a chance to review these docs, and while they are very complete (thank you [~anujkumar]!) they are not actually a patch on the current documentation. They are a standalone Microsoft Word document. I can do the format translation as needed, but [~anujkumar] (or perhaps [~osma]?), would it be possible for you to indicate how you expect the new docs to be integrated with the old ones, perhaps with headings in the text that match those there now and a list of Solr-related headings to eliminate?

I will try to do this alone if I have to, but I worry a bit because I am not very familiar with the text indexing machinery. (Perhaps I should work on that for the future...) For example, the Elasticsearch docs do not explain how to configure different analysis pipelines, and I don't know if that is a gap in docs or just because ES doesn't have that ability.


was (Author: ajs6f):
I've finally had a chance to review these docs, and while they are very complete (thank you [~anujkumar]!) they are not actually a patch on the current documentation. They are a standalone Microsoft Word document. I can do the format translation as needed, but [~anujkumar] (or perhaps [~osma]?), would it be possible for you to indicate how you expect the new docs to be integrated with the old ones, perhaps with headings in the text that match those there now and a list of Solr-related headers to eliminate?

I will try to do this alone if I have to, but I worry a bit because I am not very familiar with the text indexing machinery. (Perhaps I should work on that for the future...) For example, the Elasticsearch docs do not explain how to configure different analysis pipelines, and I don't know if that is a gap in docs or just because ES doesn't have that ability.

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