[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703721#action_12703721
]
Erik Holstad commented on HBASE-1249:
-------------------------------------
@Stack
+ TimeRange might be like the CellBounds, just a class with 2 timestamp, upper
and lower bound for the getFetch.
+ About the Fmaily object, I think I need to do some testing, cause I didn't
know that an object was that big while sending it over the wire, but we all
want the same thing here, to make it as fast as possible, so it that turns out
top be the case, we will absolutely change the format. and I guess if you
wanted to send extra params along with the family and columns we can put them
before. Just seems more complicated to have a non object approach, but will
have a look at the sizes.
+ The version code is now handled inside of the compareTo(KeyValue) and if we
would lift it out of there we would have to add some extra logic outside,
nothing major. The biggest reason for not doing this is the fact that the
GetRow/GetFamilies calls will have to do this compare too, even thought they
can never early out, so those calls are going to have to carry some extra
weight.
+ GetXServer is different from GetX by the compareTo(KeyValue) method and some
other smaller helper methods that are related to that one, but that is the only
thing.
+ For now I only have the RowFilterInterface in my code, so that is the same
for now.
> 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
>
> Attachments: HBASE-1249-Example-v1.pdf, HBASE-1249-Example-v2.pdf,
> HBASE-1249-GetQuery-v1.pdf, HBASE-1249-GetQuery-v2.pdf,
> HBASE-1249-GetQuery-v3.pdf, HBASE-1249-GetQuery-v4.pdf,
> HBASE-1249-StoreFile-v1.pdf, HBASE-1249-StoreFile-v4.pdf
>
>
> 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, etc...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
