Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/89#issuecomment-37554932
@mridulm and @puravaggarwal Thanks for doing this. As a general direction,
however, we are actually moving away from MetadataCleaner in the long run -
PR#126 is the first step, which cleans up state explicitly once it is out of
scope of the application. Periodically cleaning up is really a somewhat hacky
mechanism because surprisingly often we end up removing what the application
actually still needs, especially in streaming.
Therefore, I am not sure if we actually want to expose these fields to the
user, since doing so encourages them to use this feature that is not
technically correct and intended to be deprecated in the future.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
