You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (Jira)" <ji...@apache.org> on 2020/01/24 13:57:00 UTC

[jira] [Commented] (FLINK-15747) Enable setting RocksDB log level from configuration

    [ https://issues.apache.org/jira/browse/FLINK-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022958#comment-17022958 ] 

Nico Kruber commented on FLINK-15747:
-------------------------------------

I'm not so sure about making this configurable as the use cases are quite slim, especially as long as you do not have control over the location of the LOG or the ability to pipe this into log4j via configuration. Plus, I guess, when you get to the point of needing this log, you probably also know how to add an {{OptionsFactory}}. At this point, it is already advanced debugging...

> Enable setting RocksDB log level from configuration
> ---------------------------------------------------
>
>                 Key: FLINK-15747
>                 URL: https://issues.apache.org/jira/browse/FLINK-15747
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>            Reporter: Yu Li
>            Priority: Major
>             Fix For: 1.11.0
>
>
> Currently to open the RocksDB local log, one has to create a customized {{OptionsFactory}}, which is not quite convenient. This JIRA proposes to enable setting it from configuration in flink-conf.yaml.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)