DomGarguilo commented on code in PR #4115:
URL: https://github.com/apache/accumulo/pull/4115#discussion_r1442192268
##########
test/src/main/java/org/apache/accumulo/test/ImportExportIT.java:
##########
@@ -294,6 +295,7 @@ public void testExportImportOffline() throws Exception {
// verify the new table is offline
assertFalse(client.tableOperations().isOnline(destTable), "Table should
have been offline.");
+ assertEquals(getServerContext().getTableState(TableId.of(tableId)),
TableState.OFFLINE);
Review Comment:
Yea I think you are understanding things correctly.
I think it could make sense to be more strict about transition states but
could that cause issues if a similar situation arises where a table is stuck in
a state and we want to manually transition it but if the tableOp does not allow
for it, then it would be really stuck without being able to manually
transition. For example if for some reason a table is stuck in NEW and we want
to online it but that is not an allowed transition, then it would remain stuck
in that state.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
