nsivabalan commented on issue #17077:
URL: https://github.com/apache/hudi/issues/17077#issuecomment-4800756417
This appears to be fixed in master by PR #14052 (commit `4f80914b2030`,
*fix: Allow INSERT INTO sql to preserve duplicates values by default*). After
that change, `INSERT INTO` defaults to preserving duplicates, so the `Auto
upgrade/downgrade drops secondary index` test was updated to explicitly set
`hoodie.spark.sql.insert.into.operation=upsert` so the secondary-update on id=1
actually upserts. The current test in
`hudi-spark-datasource/hudi-spark/src/test/scala/org/apache/spark/sql/hudi/feature/index/TestSecondaryIndex.scala`
(around line 268) wraps the v8 secondary-index scenario with
`withSQLConf("hoodie.spark.sql.insert.into.operation" -> "upsert", ...)`. Could
you re-run the test on latest master and close this issue if it now passes? If
you are still seeing the insert failure, please share the exact stack/log so we
can re-open with a concrete repro.
--
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]
