[jira] Updated: (HBASE-847) new API: HTable.getRow with numVersion specified

["Doğacan Güney (JIRA)" <ji...@apache.org>]

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

Doğacan Güney updated HBASE-847:
--------------------------------

    Attachment: HBASE-847_v2.patch

New version of patch. Same as the last one except

- Added a new test case (TestGetMultipleVersions)
- Changed Cell to keep a reverse sorted map of timestamp->value. This way, a cell is guaranteed to return latest timestamp at the top.
- Also changed iteration. Cell now iterates over Entry<Long, byte[]>'s. Nothing in hbase code uses cell iteration anyway (and it didn't work just a while back:). Still, I am open to suggestions.
- Added javadoc for new overloads

There is a small bug. If, say, your table is configured to keep last 3 versions and you have just written code that makes 5 updates to a row/column (with timestamps, t1, t2, t3, t4, t5.) Now if you try asking for 5 versions, you will only get t5, t4 and t3. But if you ask for 5 versions starting from t4, you will get t4, t3, -t2- (at least until table is compacted). I don't know if this will be too much of a problem. I also should note that HTable#get also behaves like this.

About subtasks: I think HBASE-857 and HBASE-44 are covered. I am not sure about HBASE-31. Is it useful to get just timestamps and not values?


> new API: HTable.getRow with numVersion specified
> ------------------------------------------------
>
>                 Key: HBASE-847
>                 URL: https://issues.apache.org/jira/browse/HBASE-847
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: 0.2.0
>            Reporter: Michael Bieniosek
>            Assignee: Doğacan Güney
>             Fix For: 0.19.0
>
>         Attachments: HBASE-847_v2.patch, HBASE_847.patch
>
>
> I'd like to be able to call HTable.getRow with numVersions, and get multiple versions for each column.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.