You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 03:38:09 UTC

Re: [I] AnalysisException thrown when executing SQL time travel query using TIMESTAMP AS OF [hudi]

nsivabalan commented on issue #16362:
URL: https://github.com/apache/hudi/issues/16362#issuecomment-4795592936

   This issue appears to be fixed on `master`. The stack trace points at `HoodieResolveReferences` in `HoodieAnalysis.scala`, which calls `HoodieSpark3CatalystPlanUtils.toTableIdentifier` and chokes on 3-part identifiers like `spark_catalog.db.table`. That entire rule (and the `toTableIdentifier` helper) was removed in commit [`812950bc`](https://github.com/apache/hudi/commit/812950bc9ead4c28763b907dc5a1840162f35337) (PR #7871, [HUDI-4690][HUDI-4503] *Cleaning up Hudi custom Spark `Rule`s*, Feb 2023, released in 0.13.0+). The current code delegates resolution to Spark and applies Hudi-specific transforms post-hoc, so 3-part identifiers no longer flow through `toTableIdentifier`. Time travel via `TIMESTAMP AS OF` is exercised in `hudi-spark-datasource/hudi-spark/src/test/scala/org/apache/spark/sql/hudi/dml/others/TestTimeTravelTable.scala`.
   
   Could you confirm which Hudi version you were running? If it was pre-0.13.0, please upgrade and re-test. If the issue still reproduces on 0.14.x / 1.x, please reopen with the new stack trace and we can take another look. Closing as resolved otherwise.


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org