[
https://issues.apache.org/jira/browse/HBASE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708362#action_12708362
]
Jonathan Gray commented on HBASE-1304:
--------------------------------------
I'm about 2/3 done with scanners. The last bit is the hardest to deal with
because of the multi-leveled complexity. A scan is opened, and then nexted one
row at a time. Each query uses one region at a time, and for that region, has
a scanner per store (family) and for each store, a scanner for memcache and one
for the storefiles. Within the storefiles, there is a scanner for each hfile.
This has to be all be intelligently and efficiently merged.
The primary issue I'm dealing with now is that Memcache is not immutable, so
the "next" row can change between calls. For that reason, it doesn't seem to
make sense to actually make them stateful. Rather, it uses tailSet() on every
next call.
Should have a patch up for Scans tomorrow. I've done some stuff for Puts and
Deletes but not patch-ready yet, should be tomorrow or wednesday depending on
scanner testing goes.
> New client server implementation of how gets and puts are handled.
> -------------------------------------------------------------------
>
> Key: HBASE-1304
> URL: https://issues.apache.org/jira/browse/HBASE-1304
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Erik Holstad
> Assignee: Jonathan Gray
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: hbase-1304-v1.patch, HBASE-1304-v2.patch,
> HBASE-1304-v3.patch, HBASE-1304-v4.patch
>
>
> Creating an issue where the implementation of the new client and server will
> go. Leaving HBASE-1249 as a discussion forum and will put code and patches
> here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
