[
https://issues.apache.org/jira/browse/HBASE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629911#action_12629911
]
stack commented on HBASE-859:
-----------------------------
Text had same problem as binary keys. If keys were URLs and URL included any of
below characters, then we had same problem:
{code}
0 nul 1 soh 2 stx 3 etx 4 eot 5 enq 6 ack 7 bel
8 bs 9 ht 10 nl 11 vt 12 np 13 cr 14 so 15 si
16 dle 17 dc1 18 dc2 19 dc3 20 dc4 21 nak 22 syn 23 etb
24 can 25 em 26 sub 27 esc 28 fs 29 gs 30 rs 31 us
32 sp 33 ! 34 " 35 # 36 $ 37 % 38 & 39 '
40 ( 41 ) 42 * 43 +
{code}
> HStoreKey needs a reworking
> ---------------------------
>
> Key: HBASE-859
> URL: https://issues.apache.org/jira/browse/HBASE-859
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Critical
>
> HBASE-832 had to make an ugly hack to address fact that rows that included
> the delimiter -- or a byte < delimiter -- messed up sorting in .META. Fix
> the ugly hack, and while we're at it, add a byte for flags to the HSK so can
> mark if key is a meta key, a delete key (cell/family/row), etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
