[
https://issues.apache.org/jira/browse/FLINK-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532961#comment-16532961
]
Ted Yu commented on FLINK-9735:
-------------------------------
I currently don't see what is wrong with the code in {{RocksDBResource}} - it
only cares about SSD optimization.
Even if you fix it to align with javadoc, I wonder why opt is assigned to again
- if new attributes are added on top of existing opt, there is no need to
assign again with the same reference.
> Potential resource leak in RocksDBStateBackend#getDbOptions
> -----------------------------------------------------------
>
> Key: FLINK-9735
> URL: https://issues.apache.org/jira/browse/FLINK-9735
> Project: Flink
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: vinoyang
> Priority: Minor
>
> Here is related code:
> {code}
> if (optionsFactory != null) {
> opt = optionsFactory.createDBOptions(opt);
> }
> {code}
> opt, an DBOptions instance, should be closed before being rewritten.
> getColumnOptions has similar issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)