[
https://issues.apache.org/jira/browse/BEAM-9855?focusedWorklogId=501835&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-501835
]
ASF GitHub Bot logged work on BEAM-9855:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Oct/20 21:58
Start Date: 17/Oct/20 21:58
Worklog Time Spent: 10m
Work Description: tweise commented on a change in pull request #13116:
URL: https://github.com/apache/beam/pull/13116#discussion_r506988274
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkExecutionEnvironments.java
##########
@@ -259,28 +278,44 @@ static StreamExecutionEnvironment
createStreamExecutionEnvironment(
options.setShutdownSourcesAfterIdleMs(0L);
}
}
+ }
- applyLatencyTrackingInterval(flinkStreamEnv.getConfig(), options);
-
- if (options.getAutoWatermarkInterval() != null) {
-
flinkStreamEnv.getConfig().setAutoWatermarkInterval(options.getAutoWatermarkInterval());
- }
-
- // State backend
- if (options.getStateBackendFactory() != null) {
+ private static void configureStateBackend(
Review comment:
Flink is headed in the direction where everything that is set on an
environment becomes configurable (including the executor, FLIP-73). This change
kind of goes in the opposite direction, increasing the amount of Flink pipeline
options further. Should we look into the generic configuration mechanism
instead, where it is really easy for the user to supply the Flink configuration
(optionally inline, instead of via a separate file)?
##########
File path: runners/flink/flink_runner.gradle
##########
@@ -148,6 +148,8 @@ dependencies {
compile "org.apache.flink:flink-java:$flink_version"
compile "org.apache.flink:flink-runtime_2.11:$flink_version"
compile "org.apache.flink:flink-streaming-java_2.11:$flink_version"
+ // RocksDB state backend
+ compile "org.apache.flink:flink-statebackend-rocksdb_2.11:$flink_version"
Review comment:
Just wanted to confirm that dependency won't be baked into the job
server as it is already part of the Flink dist.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 501835)
Time Spent: 40m (was: 0.5h)
> Make it easier to configure a Flink state backend
> -------------------------------------------------
>
> Key: BEAM-9855
> URL: https://issues.apache.org/jira/browse/BEAM-9855
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: P3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We should make it easier to configure a Flink state backend. At the moment,
> users have to either (1) configure the default state backend in their Flink
> cluster, or make sure (2a) they include the dependency in their Gradle/Maven
> project (e.g.
> {{"org.apache.flink:flink-statebackend-rocksdb_2.11:$flink_version"}} for
> RocksDB) (2b) set the state backend factory in the {{FlinkPipelineOptions}.
> The drawback of option (2) is that it only works in Java due to the factory
> specification being in Java.
> We can make it easier by simple adding pipeline options for the state backend
> name and the checkpoint directory which will be enough for configuring the
> state backend. We can add the RocksDB state backend as a default dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
