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

ASF GitHub Bot commented on S2GRAPH-209:
----------------------------------------

GitHub user daewon opened a pull request:

    https://github.com/apache/incubator-s2graph/pull/160

    [S2GRAPH-209] GlobalIndex supports field data types such as Numeric to 
enable Range Query.

    First implemented a range query in 'elasticsearch' and applied 
VertexQueryParam(offset, limit).


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/daewon/incubator-s2graph S2GRAPH-209

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-s2graph/pull/160.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #160
    
----
commit 70da15004ebf33a8590b89d9e916ba2d1e70da1f
Author: daewon <daewon@...>
Date:   2018-04-23T09:02:51Z

    refactoring

commit 37b4a45bb47db48d05cfbcdafb8f0867c1d33cca
Author: daewon <daewon@...>
Date:   2018-04-23T09:42:13Z

    add vertexQueryParam on esIndexProvider

----


> GlobalIndex supports field data types such as Numeric to enable Range Query.
> ----------------------------------------------------------------------------
>
>                 Key: S2GRAPH-209
>                 URL: https://issues.apache.org/jira/browse/S2GRAPH-209
>             Project: S2Graph
>          Issue Type: Improvement
>          Components: s2core
>            Reporter: Daewon Jeong
>            Assignee: Daewon Jeong
>            Priority: Minor
>
> h1. GlobalIndex supports field data types such as Numeric to enable Range 
> Query.
> The provided GlobalIndex expects all stored fields as String values.
> For the above reason, even if the property type of the vertex/edge is 
> Numeric, the following Range Query can not be performed.
> {noformat}
> age: [50 TO 100]
> {noformat}
>  
> Change it to support it.
> The 'lucene' being implemented as a reference supports the field types listed 
> below.
> {noformat}
>  {TextField}: {@link Reader} or {@link String} indexed for full-text search
>  {StringField}: {@link String} indexed verbatim as a single token
>  {IntPoint}: {@code int} indexed for exact/range queries.
>  {LongPoint}: {@code long} indexed for exact/range queries.
>  {FloatPoint}: {@code float} indexed for exact/range queries.
>  {DoublePoint}: {@code double} indexed for exact/range queries.
>  {SortedDocValuesField}: {@code byte[]} indexed column-wise for 
> sorting/faceting
>  {SortedSetDocValuesField}: {@code SortedSet<byte[]>} indexed column-wise for 
> sorting/faceting
>  {NumericDocValuesField}: {@code long} indexed column-wise for 
> sorting/faceting
>  {SortedNumericDocValuesField}: {@code SortedSet<long>} indexed column-wise 
> for sorting/faceting
>  {StoredField}: Stored-only value for retrieving in summary results
>  {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to