ctubbsii commented on code in PR #5334:
URL: https://github.com/apache/accumulo/pull/5334#discussion_r1956554019
##########
server/manager/src/main/java/org/apache/accumulo/manager/tableOps/clone/CloneZookeeper.java:
##########
@@ -37,20 +35,12 @@ class CloneZookeeper extends ManagerRepo {
public CloneZookeeper(CloneInfo cloneInfo, ClientContext context)
throws NamespaceNotFoundException {
this.cloneInfo = cloneInfo;
- this.cloneInfo.namespaceId = Namespaces.getNamespaceId(context,
Review Comment:
I'm not sure exactly what to expect when the serialization of the fate
operation's classes are changed, but if a clonetable operation was serialized
with 2.1.3, and then interrupted, and then resumed after upgrading to 2.1.4,
the deserialization in order to resume the operation will probably fail in some
way. I'm not sure if you need to do anything to check it in the code... maybe
just warn users that they should make sure there's no outstanding clone
operations before doing an upgrade.
--
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]
