jackylee-ch commented on PR #10199:
URL: https://github.com/apache/paimon/pull/10199#issuecomment-5954922281

   Fixed in ab2a2d2f9. The procedure now refreshes Spark's cached plans even 
when the rollback fails after entering the commit — `rollback_to_as_latest` can 
publish the rollback snapshot and then throw (e.g. a post-commit callback), so 
the state is already durable and the shared success-only refresh left `CACHE 
TABLE` serving pre-rollback data. A small wrapper runs `refreshSparkCache` in 
both the success and failure paths; the original failure is preserved and a 
refresh error is only added as suppressed.
   
   Verified locally in `paimon-spark-ut` (spark3, 4 passed): the new test 
caches the table, injects a post-commit callback failure during the rollback, 
and asserts `SELECT` returns the rolled-back row rather than the stale cached 
one. Reverting to the plain wrapper fails it with `[1,original]` vs 
`[2,replacement]`. spotless and `git diff --check` clean.
   


-- 
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]

Reply via email to