[
https://issues.apache.org/jira/browse/HBASE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clint Morgan updated HBASE-583:
-------------------------------
Attachment: hbase-583-v2.patch
This is a newer version (requires HBASE-583) renamings.
I was playing around with our serialization methods to try and make comparison
for EG longs work as lexicographic comparison on the serialized byte array. I
don' t think this approach will work very will for complex types, it was a PITA
to get serialized longs to compare correctly. And the resulting serialization
was less efficient.
So this approach allows the Range filter to take a WritableByteArrayComparable.
This guy can do the deserialization of the byte array and compare it with the
range limit value.
Sorry for lack of tests, but I've tested this in our layer above hbase and it
seems to work.
> RangeRowFilter, allow to choose rows based on a (lexicographic) comparison to
> column's values
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-583
> URL: https://issues.apache.org/jira/browse/HBASE-583
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: filters
> Reporter: Clint Morgan
> Priority: Minor
> Attachments: hbase-583-v2.patch, hbase-583.patch
>
>
> This allows one to do equal, greater than, etc comparisons on column values.
> Only rows with columns which pass comparison get through.
> Its cleaner and more powerful than the "columnFilter" in RegExpRowFilter
> which only provides equals. I think this functionality should be deprecated
> in RegExpRowFilter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
