timoninmaxim commented on a change in pull request #8490:
URL: https://github.com/apache/ignite/pull/8490#discussion_r569490636



##########
File path: 
modules/core/src/main/java/org/apache/ignite/cache/query/index/sorted/IndexKey.java
##########
@@ -0,0 +1,36 @@
+/*
+ * 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.cache.query.index.sorted;
+
+import org.apache.ignite.internal.processors.cache.persistence.CacheDataRow;
+import org.jetbrains.annotations.Nullable;
+
+/**
+ * Represents a complex index key.
+ */
+public interface IndexKey {

Review comment:
       Yes, I agree, this is wrong. As IndexKey expected to be used by user 
queries and it definitely should not contain info about CacheDataRow.
   
   I've reworked a hierarchy of classes related to IndexKey, IndexRow. Now 
InlineIndexTree is generic of IndexRow, and not of IndexSearchRow (it was 
confusing, IMHO). IndexRow now extends IndexKey. As a result, I simplified a 
couple of places in the code.




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