danny0405 commented on issue #17512: URL: https://github.com/apache/hudi/issues/17512#issuecomment-4504962424
> 3. Add upstream propagation as a second source (the only genuinely new piece). When eventTimeFieldName is not set but the writer is reading from another Hudi table (e.g., HoodieIncrSource, Spark SQL on a Hudi source), inherit the upstream commit's per-partition min/max as the downstream commit's watermark for the same destination partitions. Order of precedence: Let's hold on and clarify before pushing any changes, when you san the eventTimeFieldName is not set for downstream table, can we have the declaration that the table already lost the event time tracing abilities? For e.g, the downstream table might have some filtering logic that drop part of the data set, then the event time from upstream table does not make sense anymore. More proper way from my understanding is that we suggest the user to always keep the eventTimeFieldName in their table schema if they want a meaningful event time tracking in business. -- 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]
