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

Osma Suominen commented on JENA-1305:
-------------------------------------

Also, you asked about the graph field in GitHub comments. My point was that if 
you want to have a single ES document per entity, then working with multiple 
graphs quickly gets tricky. I would suggest that you keep the ES index 
graph-agnostic for now: don't store the graph in the index at all and 
consequently don't filter by graph at query time. This is how jena-text/Lucene 
used to work before I added the graph-specific indexing feature.

If you really want to do graph-aware indexing, then you have two options:

# Make one ES document per (entity URI + graph URI) combination
# Make one ES document per entity, but for every indexed value, store also the 
graph(s) in which this value is asserted. I think this would quickly get messy, 
but in theory it would be possible.

Anyway my recommendation is not to worry about graphs in the initial 
implementation.

> 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