majian1998 opened a new pull request, #11224:
URL: https://github.com/apache/hudi/pull/11224
In Hudi, the Spark3_5Adapter calls v2.v1Table which in turn invokes the
logic within Delta. When executed on a Delta table, this may result in an
error. Therefore, the logic to determine whether it is a Hudi operation has
been altered to class name checks to prevent errors during Delta Lake
executions.
When executing the delta test of spark3.5, the error is reported as follows:
`[DELTA_INVALID_V1_TABLE_CALL] v1Table call is not expected with path based
DeltaTableV2
org.apache.spark.sql.delta.DeltaIllegalStateException:
[DELTA_INVALID_V1_TABLE_CALL] v1Table call is not expected with path based
DeltaTableV2
at
org.apache.spark.sql.delta.DeltaErrorsBase.invalidV1TableCall(DeltaErrors.scala:1801)
at
org.apache.spark.sql.delta.DeltaErrorsBase.invalidV1TableCall$(DeltaErrors.scala:1800)
at
org.apache.spark.sql.delta.DeltaErrors$.invalidV1TableCall(DeltaErrors.scala:3203)
at
org.apache.spark.sql.delta.catalog.DeltaTableV2.$anonfun$v1Table$1(DeltaTableV2.scala:320)
at scala.Option.getOrElse(Option.scala:189)
at
org.apache.spark.sql.delta.catalog.DeltaTableV2.v1Table(DeltaTableV2.scala:320)
at
org.apache.spark.sql.adapter.Spark3_5Adapter.$anonfun$resolveHoodieTable$1(Spark3_5Adapter.scala:57)
at scala.Option.orElse(Option.scala:447)
at
org.apache.spark.sql.adapter.Spark3_5Adapter.resolveHoodieTable(Spark3_5Adapter.scala:52)
at
org.apache.spark.sql.hudi.analysis.HoodieAnalysis$ResolvesToHudiTable$.unapply(HoodieAnalysis.scala:362)
`
### Change Logs
none
### Impact
none
### Risk level (write none, low medium or high below)
none
### Documentation Update
None
### Contributor's checklist
- [ ] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
--
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]
