Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3198
I think we can keep from having to close the `AbstractStateBackend` by not
caching the `dbOptions` and `columnOptions` and instead giving new ones to the
`RocksDBKeyedStateBackend`. The keyed backend is not meant to be stateless and
already has a lifecycle and will be disposed. It would simply take ownership of
these options as well which would make responsibilities more clear.
Sorry for being annoying about this but I would really like to keep the
"state backend factory" as a factory and not add lifecycle stuff to it as well.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
