gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alfonso Nishikawa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-510) Conform Query.setEndKey to inclusive query for HBaseStore
Date Sun, 28 May 2017 11:21:04 GMT

     [ https://issues.apache.org/jira/browse/GORA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alfonso Nishikawa updated GORA-510:
    Summary: Conform Query.setEndKey to inclusive query for HBaseStore  (was: Conform Query.setEndKey
to inclusive query in HBaseStore)

> Conform Query.setEndKey to inclusive query for HBaseStore
> ---------------------------------------------------------
>                 Key: GORA-510
>                 URL: https://issues.apache.org/jira/browse/GORA-510
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: gora-hbase
>    Affects Versions: 0.6, 0.7, 0.8
>            Reporter: Alfonso Nishikawa
>            Assignee: Alfonso Nishikawa
>            Priority: Minor
>              Labels: query
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> The endKey query option does not work properly in HBase: Gora's query inteface defines
it as 'inclusive' while HBase behaves 'exclusive'.
> The tests have been @ignored temporarily (since 2014! "nothing is more permanent than
a temporary solution" ;) as shown at TestHBaseStore ([1]).
> There is a "TODO" with the message "raise an issue for HBase to allow us to specify if
the endRow will be inclusive or exclusive", but HBase documentation states:
> "Note: In order to make stopRow inclusive add a trailing 0 byte"
> So: I propose to update HBaseStore to conform Gora's interface based on HBase's solution.
> [1] https://github.com/apache/gora/blob/apache-gora-0.7/gora-hbase/src/test/java/org/apache/gora/hbase/store/TestHBaseStore.java#L248

This message was sent by Atlassian JIRA

View raw message