[
https://issues.apache.org/jira/browse/HBASE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gray updated HBASE-1804:
---------------------------------
Attachment: HBASE-1804-v1.patch
Removes usage of FAMILY_COMPARATOR. Replaces with straight binary compare,
Bytes.BYTES_COMPARATOR.
Needs to be tested and discussed. I don't see why or where we expect or need
to be tolerant of a family with a colon. It should be stripped from old api
stuff, and is not even part of the equation of the new api.
This does fix the original bug. If you run a new API put with family: it will
throw no such column family exception.
> Puts are permitted (and stored) when including an appended colon
> ----------------------------------------------------------------
>
> Key: HBASE-1804
> URL: https://issues.apache.org/jira/browse/HBASE-1804
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Fix For: 0.20.0, 0.21.0
>
> Attachments: HBASE-1804-v1.patch
>
>
> If I have a table with family "testFamily", currently I can do Puts using the
> new API by specifying the family name with or without a colon. The KV is
> then stored w/ or w/o depending on how the Put was done.
> If you try to Put.add("testFamily:", "qualifier", "value") this should throw
> a NoSuchColumnFamilyException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
