snazy opened a new issue, #774:
URL: https://github.com/apache/polaris/issues/774
### Describe the bug
Polaris uses some asynchronously executed tasks to run operations for table
and manifest file cleanup. Those tasks are potentially executed in a separate
thread in the same JVM. There is however no guarantee that those tasks will
eventually run for multiple reasons:
* Tasks (e.g. via
`org.apache.polaris.service.catalog.BasePolarisCatalog#dropTable`) are
triggered _after_ the fact.
* Although tasks are persisted, there is no mechanism to pick up tasks that
did not start or did not finish ("long lasting" failures, JVM terminates).
Overall this means that for example a "drop table with purge" returns a
successful result to the user, the actual purge may never ever happen.
### To Reproduce
_No response_
### Actual Behavior
_No response_
### Expected Behavior
_No response_
### Additional context
_No response_
### System information
_No response_
--
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]
