vinothchandar commented on a change in pull request #4888:
URL: https://github.com/apache/hudi/pull/4888#discussion_r831616177
##########
File path:
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieBaseRelation.scala
##########
@@ -54,8 +55,12 @@ trait HoodieFileSplit {}
case class HoodieTableSchema(structTypeSchema: StructType, avroSchemaStr:
String)
-case class HoodieTableState(recordKeyField: String,
- preCombineFieldOpt: Option[String])
+case class HoodieTableState(tablePath: String,
+ latestCommit: String,
Review comment:
latestCommitTime
##########
File path:
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/BaseFileOnlyRelation.scala
##########
@@ -52,6 +53,14 @@ class BaseFileOnlyRelation(sqlContext: SQLContext,
override type FileSplit = HoodieBaseFileSplit
+ override lazy val mandatoryColumns: Seq[String] = {
+ if (isMetadataTable(metaClient)) {
Review comment:
lets remove this special casing for metadata table? It's dealing with an
abstraction few layers deeper than here.
##########
File path:
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieBaseRelation.scala
##########
@@ -79,13 +84,30 @@ abstract class HoodieBaseRelation(val sqlContext:
SQLContext,
protected lazy val basePath: String = metaClient.getBasePath
- // If meta fields are enabled, always prefer key from the meta field as
opposed to user-specified one
- // NOTE: This is historical behavior which is preserved as is
+ // NOTE: Record key-field is assumed singular here due to the either of
Review comment:
same. can we avoid references to metadata table from this layer
--
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]
