amaliujia commented on a change in pull request #1725:
URL: https://github.com/apache/ozone/pull/1725#discussion_r553765849



##########
File path: 
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/ha/SCMTransactionInfo.java
##########
@@ -0,0 +1,111 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with this
+ * work for additional information regarding copyright ownership. The ASF
+ * licenses this file to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * <p>
+ * <p>http://www.apache.org/licenses/LICENSE-2.0
+ * <p>
+ * <p>Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations 
under
+ * the License.
+ */
+package org.apache.hadoop.hdds.scm.ha;
+
+import com.google.common.base.Preconditions;
+import org.apache.hadoop.hdds.StringUtils;
+
+import java.util.Objects;
+
+import static org.apache.hadoop.ozone.OzoneConsts.TRANSACTION_INFO_SPLIT_KEY;
+
+final public class SCMTransactionInfo {

Review comment:
       I think we are better to reuse `OMTransactionInfo` after merge HDDS-2823 
back to master.
   
   Not reusing `OMTransactionInfo` is to try to reduce the risk that have 
conflicts after syncing master int HDDS-2823. Also, to reuse 
`OMTransactionInfo`, I think we'd better to update the name to 
`TransactionInfo`, which will be a source of conflicts , unless we can change 
it in the master branch first. And I also add some more functions in 
`SCMTransactionInfo`, if we reuse `OMTransactionInfo`, those new functions will 
also become source of conflicts. 
   
   To conclude a bit, we can reuse it after merging SCM HA back to master, the 
goal is try to reduce potential conflicts if there could be any.
   
   SCM HA is in developing branch anyway and I am sure we will need to clean up 
lots of stuff eventually. As long as we have JIRAs to not lose track of such 
work. 




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to