[
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454646#comment-13454646
]
Elliott Clark commented on HBASE-6769:
--------------------------------------
Yes I totally forgot to git add the FailedSanityCheckException.
I just spun up a local 0.94 build and a 0.92.1 hbase shell. resulting in:
{code}
1.9.3-p194 :001 > list
TABLE
0 row(s) in 0.7450 seconds
1.9.3-p194 :002 > create 'test_table', 'd'
0 row(s) in 0.1560 seconds
1.9.3-p194 :003 > put 'test_table', 'rk', 'b:1', '0'
ERROR: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action:
org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException: Column family
b does not exist in region
test_table,,1347513173188.d9d026b9ac9c899bd21cff52682905bd. in table {NAME =>
'test_table', FAMILIES => [{NAME => 'd', BLOOMFILTER => 'NONE',
REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '3', TTL =>
'2147483647', MIN_VERSIONS => '0', BLOCKSIZE => '65536', IN_MEMORY => 'false',
BLOCKCACHE => 'true'}]}
at
org.apache.hadoop.hbase.regionserver.HRegionServer.multi(HRegionServer.java:3470)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1400)
: 1 time, servers with issues: android-c6740ac93630ee19:57140,
Here is some help for this command:
Put a cell 'value' at specified table/row/column and optionally
timestamp coordinates. To put a cell value into table 't1' at
row 'r1' under column 'c1' marked with the time 'ts1', do:
hbase> put 't1', 'r1', 'c1', 'value', ts1
{code}
So it looks like everything works well.
> HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
> -----------------------------------------------------------
>
> Key: HBASE-6769
> URL: https://issues.apache.org/jira/browse/HBASE-6769
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0, 0.94.1
> Reporter: Jean-Daniel Cryans
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6769-0.94-0.patch, HBASE-6769-0.patch
>
>
> I think this is a pretty major usability regression, since HBASE-5021 this is
> what you get in the client when using a wrong family:
> {noformat}
> 2012-09-11 09:45:29,634 WARN
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1
> action: DoNotRetryIOException: 1 time, servers with issues: sfor3s44:10304,
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1601)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1377)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:916)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:772)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:747)
> {noformat}
> Then you have to log on the server to understand what failed.
> Since everything is now a multi call, even single puts in the shell fail like
> this.
> This is present since 0.94.0
> Assigning to Elliott because he asked.
--
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
