[
https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762096#comment-13762096
]
Jonathan Hsieh commented on HBASE-9334:
---------------------------------------
The main goal here is to do the onerous but necessary task of narrowing the
API. Today we expose too many internals that will hinder our ability to do
optimizations (like pushing encodings data out the client for them to interpret
instead of having the rs interpret and then re-encode ship and then having the
client interpret again).
[~nkeywal] The concerns here are seem to be on the HBASE-9359 parts? I think
the release notes for filter part is accurate when the filter part was a
standalone patch (I ended up committing it together with HBASE-9359 because it
had a compile problem.).
Let's move this to HBASE-9359?
> Convert KeyValue to Cell in hbase-client module - Filters
> ---------------------------------------------------------
>
> Key: HBASE-9334
> URL: https://issues.apache.org/jira/browse/HBASE-9334
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 0.95.2
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-9334.patch, hbase-9334.v2.patch,
> hbase-9334.v3.patch, hbase-9334.v4.patch, hbase-9334.v6.patch
>
>
> The goal is is to remove KeyValue from the publicly exposed API and require
> clients to use the cleaner mroe encapsulated Cell API instead. For filters,
> this affects #filterKeyValue, #transform, #filterrow, and #getNextKeyHint.
> Since Cell is a base interface for KeyValue, changing these means that 0.94
> apps may need a recompile but probably no modifications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
