sanpwc commented on a change in pull request #105:
URL: https://github.com/apache/ignite-3/pull/105#discussion_r619284270



##########
File path: 
modules/vault/src/main/java/org/apache/ignite/internal/vault/common/Entry.java
##########
@@ -0,0 +1,45 @@
+/*
+ * 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.ignite.internal.vault.common;
+
+import org.apache.ignite.lang.ByteArray;
+import org.jetbrains.annotations.NotNull;
+import org.jetbrains.annotations.Nullable;
+
+/**
+ * Represents a vault unit as entry with key and value, where
+ * <ul>
+ *     <li>key - an unique entry's key. Keys are comparable in lexicographic 
manner and represented as an {@link ByteArray}.</li>
+ *     <li>value - a data which is associated with a key and represented as an 
array of bytes.</ul>
+ * </ul>
+ */
+public interface Entry {

Review comment:
       It seems that we should have Entry interface that will be extended with 
MetaStorageEntry with extra revision logic. Please consider doing this in 
separate ticket. Same is about UpdateListener<T>




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


Reply via email to