hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1249) Rearchitecting of server, client, API, key format, etc for 0.20
Date Mon, 16 Mar 2009 16:23:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682353#action_12682353

Jim Kellerman commented on HBASE-1249:

> Erik Holstad added a comment - 10/Mar/09 01:14 PM
> 2. I think that the setting of the timestamp should not be exposed to the user but, be
set by HBase at all times. This limitation
> simplifies a lot when reasoning about the order across storefiles and client formats,
to make it as fast, early outs and simple, 
> list instead of map, as possible.

-1 Unless there is another "version" field. We have an application that makes extensive use
of timestamp at Powerset.

> Rearchitecting of server, client, API, key format, etc for 0.20
> ---------------------------------------------------------------
>                 Key: HBASE-1249
>                 URL: https://issues.apache.org/jira/browse/HBASE-1249
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Jonathan Gray
>            Priority: Blocker
>             Fix For: 0.20.0
> To discuss all the new and potential issues coming out of the change in key format (HBASE-1234):
zero-copy reads, client binary protocol, update of API (HBASE-880), server optimizations,

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

View raw message