HeartSaVioR commented on a change in pull request #25811: [SPARK-29111][CORE] 
Support snapshot/restore on KVStore
URL: https://github.com/apache/spark/pull/25811#discussion_r326876649
 
 

 ##########
 File path: 
common/kvstore/src/main/java/org/apache/spark/util/kvstore/KVStoreSnapshotter.java
 ##########
 @@ -0,0 +1,152 @@
+/*
+ * 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
+ *
+ *    http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * 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.spark.util.kvstore;
+
+import com.google.common.io.ByteStreams;
+
+import java.io.DataInputStream;
+import java.io.DataOutputStream;
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.io.IOException;
+import java.nio.charset.StandardCharsets;
+import java.util.Set;
+
+public class KVStoreSnapshotter {
+  private static final int MARKER_END_OF_TYPE = -2;
+  private static final int MARKER_END_OF_FILE = -1;
+
+  private final KVStoreSerializer serializer;
+
+  public KVStoreSnapshotter(KVStoreSerializer serializer) {
+    this.serializer = serializer;
+  }
+
+  public void dump(KVStore store, File snapshotFile) throws Exception {
 
 Review comment:
   > Well, InputStream/OutputStream could work around this case. But I'm afraid 
it brings troublesome usage for the caller, as they needs to prepare their own 
streams(local or HDFS, in or out). And I believe, currently, KVStore is only 
designed to persist in filesystems and underlying streams should always be file 
streams. So, exposing InputStream/OutputStream seems an overkill here.
   
   Sorry I totally disagree this is an workaround - especially the parameter 
here depending on is pure Java API, which any Java developers must know and 
familiar with how to deal with.
   
   
https://github.com/apache/spark/blob/c7c6b642dccb3fbd5f82b81cff7f88a776976c7d/core/src/main/scala/org/apache/spark/scheduler/ReplayListenerBus.scala#L52-L59
   
   Just look at ReplayListenerBus. What exactly it requires caller to prepare? 
InputStream. Does it use something other than file except some case of UT? 
Well, no. That's consideration on API level to open extension.
   
   I'll leave the decision to the committers.
   
   Even if we turn out to agree directly depend on Hadoop, I would just move 
this to core module and rewrite this as Scala. Writing this to Java was the 
intentional effort to put this along with other classes in common/kvstore, and 
I don't think modules in common depend on hadoop - except network-yarn which 
even define Hadoop dependency as provided. common modules are trying to avoid 
depending on Hadoop.

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


With regards,
Apache Git Services

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

Reply via email to