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

ASF GitHub Bot commented on JENA-1305:
--------------------------------------

Github user osma commented on the issue:

    https://github.com/apache/jena/pull/227
  
    Regarding merging, I would like to merge PR #226 first which changes the 
`TextIndex.query` method, breaking out the `lang` and `graph` information into 
separate parameters. The effect on this code should be that the `parse` method 
becomes unnecessary, but all the calls to the `query` method in the integration 
tests need to be changed slightly. I can do that myself, as I don't want to 
burden @anujgandharv anymore with extra work, but if you like you can switch 
your code on top of that branch already.
    
    Do people have opinions about whether to squash these (currently) 29 
commits into a single commit for `master`, or leave them as they are? It's a 
trade-off between historical accuracy and clarity. There have been quite a few 
back-and-forth changes in this branch. I would be inclined to squash and rebase 
before merging, making it clear what has actually changed in the jena-text 
code. The original commits should still be available in this PR in case anyone 
is interested in those. Opinions? @ajs6f? @afs?


> 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