wombatu-kun commented on code in PR #12772: URL: https://github.com/apache/hudi/pull/12772#discussion_r2103820263
########## hudi-client/hudi-spark-client/src/main/scala/org/apache/hudi/HoodiePartitionValues.scala: ########## @@ -0,0 +1,24 @@ +/* + * 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.hudi + +import org.apache.spark.sql.catalyst.InternalRow + +trait HoodiePartitionValues extends InternalRow { Review Comment: Yes, it's because of breaking change in basic data structure `InterenalRow`: brand new abstract method `VariantVal getVariant(int ordinal)` is added to Spark's `InternalRow`. So we have to implement it in `InternalRow`'s subclasses only for Spark 4 env. As `HoodiePartitionValues extends InternalRow` and `HoodiePartitionCDCFileGroupMapping extends HoodiePartitionValues` and `HoodiePartitionFileSliceMapping extends HoodiePartitionValues`, we must provide different implementations of this class hierarchy for Spark 3 and Spark 4, and construct instances of these classes through additional APIs in SparkAdapter. -- 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]
