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

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

Github user anujgandharv commented on the issue:

    https://github.com/apache/jena/pull/226
  
    
    Thanks @osma . I learned from you that: _It's always good to have Unit 
Tests for the changes to make sure we are not missing any corner cases :)_
    
    So just to clarify, if the Sparql query string is:
    
    ```
    SELECT ?s
    { ?s text:query (rdfs:label 'word' 10) ; 
         rdfs:label ?label 
    }
    ```
    then the query method will receive the following attributes: 
`RDFS.label.asNode(), "word", null, null, 10`
    
    And if the query string is: `?s text:query (rdfs:label 'word' 'lang:en' )`, 
then the query method will receive the following attributes: 
`RDFS.label.asNode(), "word", null, "en"`
    
    And finally if the query string is: `?s text:query ('word' 'lang:en' )`, 
then the query method will receive the following attributes: 
`RDFS.label.asNode(), "word", null, "en"` , where the Node property is the 
default Node defined at the configuration time. 
    
    Can you confirm all the scenarios above please. I will modify my test cases 
and logic accordingly.
    
    NOTE: I say NULL for graph attribute, mainly because I don't care about it 
in the ES 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