[jira] [Created] (HBASE-5534) HBase shell's return value is almost always 0
HBase shell's return value is almost always 0 - Key: HBASE-5534 URL: https://issues.apache.org/jira/browse/HBASE-5534 Project: HBase Issue Type: Improvement Reporter: Alex Newman Assignee: Alex Newman So I was trying to write some simple scripts to verify client connections to HBase using the shell and I noticed that the HBase shell always returns 0 even when it can't connect to an HBase server. I'm not sure if this is the best option. What would be neat is if you had some capability to run commands like hbase shell --command='disable table;\ndrop table;' and it would error out if any of the commands fail to succeed. echo disable table | hbase shell could continue to work as it does now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5240) HBase internalscanner.next javadoc doesn't imply whether or not results are appended or not
HBase internalscanner.next javadoc doesn't imply whether or not results are appended or not --- Key: HBASE-5240 URL: https://issues.apache.org/jira/browse/HBASE-5240 Project: HBase Issue Type: Bug Reporter: Alex Newman Assignee: Alex Newman Just looking at http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/InternalScanner.html. We don't know whether or not the results are appended to results list, or if we always clear it first. boolean next(ListKeyValue results) Grab the next row's worth of values. booleannext(ListKeyValue result, int limit) Grab the next row's worth of values with a limit on the number of values to return. Method Detail next boolean next(ListKeyValue results) throws IOException Grab the next row's worth of values. Parameters: results - return output array Returns: true if more rows exist after this one, false if scanner is done Throws: IOException - e next boolean next(ListKeyValue result, int limit) throws IOException Grab the next row's worth of values with a limit on the number of values to return. Parameters: result - return output array limit - limit on row count to get Returns: true if more rows exist after this one, false if scanner is done Throws: IOException - e -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5217) Reenable the thrift tests, and add a new one for getRegionInfo
Reenable the thrift tests, and add a new one for getRegionInfo -- Key: HBASE-5217 URL: https://issues.apache.org/jira/browse/HBASE-5217 Project: HBase Issue Type: Improvement Reporter: Alex Newman Assignee: Alex Newman At some point we disabled tests for the thrift server. In addition, it looks like the getRegionInfo no longer functions. I'd like to reenable the tests and add one for getRegionInfo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5211) org.apache.hadoop.hbase.replication.TestMultiSlaveReplication#testMultiSlaveReplication is flakey
org.apache.hadoop.hbase.replication.TestMultiSlaveReplication#testMultiSlaveReplication is flakey - Key: HBASE-5211 URL: https://issues.apache.org/jira/browse/HBASE-5211 Project: HBase Issue Type: Bug Reporter: Alex Newman Attachments: trunk.txt I can't seem to get this test to pass consistently on my laptop. Also my hudson occasionally tripps up on it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4895) Change tablename format in meta to be the UUID of the tablename rather than the tablename.
Change tablename format in meta to be the UUID of the tablename rather than the tablename. -- Key: HBASE-4895 URL: https://issues.apache.org/jira/browse/HBASE-4895 Project: HBase Issue Type: Sub-task Reporter: Alex Newman Assignee: Alex Newman This is something stack and I discussed at hadoop world. Overall I think it cleans thing up significantly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4840) If I call split fast enough, while inserting, rows disappear.
If I call split fast enough, while inserting, rows disappear. -- Key: HBASE-4840 URL: https://issues.apache.org/jira/browse/HBASE-4840 Project: HBase Issue Type: Bug Reporter: Alex Newman I'll attach a unit test for this. Basically if you call split, while inserting data you can get to the point to where the cluster becomes unstable, or rows will disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4841) If I call split fast enough, while inserting, rows disappear.
If I call split fast enough, while inserting, rows disappear. -- Key: HBASE-4841 URL: https://issues.apache.org/jira/browse/HBASE-4841 Project: HBase Issue Type: Bug Reporter: Alex Newman I'll attach a unit test for this. Basically if you call split, while inserting data you can get to the point to where the cluster becomes unstable, or rows will disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4616) Update hregion encoded name to reduce logic and prevent region collisions in META
Update hregion encoded name to reduce logic and prevent region collisions in META - Key: HBASE-4616 URL: https://issues.apache.org/jira/browse/HBASE-4616 Project: HBase Issue Type: Umbrella Reporter: Alex Newman Assignee: Alex Newman -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4617) META migration
META migration -- Key: HBASE-4617 URL: https://issues.apache.org/jira/browse/HBASE-4617 Project: HBase Issue Type: Sub-task Reporter: Alex Newman -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
