Hi,
I saw a minor thing during working on meta table related stuff.
Not sure if I should open a Jira issue for this kind of minor change.
(Please let me know if so) See the patch in attachment.
I ran the unit test for this, looks good:
"[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running
org.apache.hadoop.hbase.coprocessor.TestCoprocessorServiceBackwardCompatibility
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
15.651 s - in
org.apache.hadoop.hbase.coprocessor.TestCoprocessorServiceBackwardCompatibility
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
"
Thanks,
Xu
diff --git
a/hbase-endpoint/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorServiceBackwardCompatibility.java
b/hbase-endpoint/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorServiceBackwardCompatibility.java
index e7181bb..edb217f 100644
---
a/hbase-endpoint/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorServiceBackwardCompatibility.java
+++
b/hbase-endpoint/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorServiceBackwardCompatibility.java
@@ -118,7 +118,7 @@ public class TestCoprocessorServiceBackwardCompatibility {
DummyResponse.getDefaultInstance());
assertEquals(REGIONSERVER, DummyCoprocessorService.numRegionServer);
-
TEST_UTIL.getConnection().getTable(TableName.valueOf("hbase:meta")).batchCoprocessorService(
+
TEST_UTIL.getConnection().getTable(TableName.META_TABLE_NAME).batchCoprocessorService(
DummyCoprocessorService.getDescriptor().findMethodByName("dummyCall"),
DummyRequest.newBuilder().setValue(REGION).build(), Bytes.toBytes(""),
Bytes.toBytes(""),
DummyResponse.getDefaultInstance());