[
https://issues.apache.org/jira/browse/FLINK-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen updated FLINK-22741:
---------------------------------
Description:
This is an umbrella issue for various issues to hide and reduce the complexity
and surface area (and configuration space) of Apache Flink when using Stateful
Functions.
The goal of this is to create a setup and configuration that works robustly in
the vast majority of settings. Users should not be required to configure
anything Flink-specific, but only general parameters (like for example total
memory size) and StateFun specific parameters (like request timeouts and
batching).
If this happens at the cost of some minor regression in peak stream throughput,
we can most likely stomach that in StateFun, because the performance cost is
commonly dominated by the interaction between StateFun cluster and remote
function deployments.
was:
This is an umbrella issue for various issues to hide and reduce the complexity
and surface area (and configuration space) of Apache Flink when using Stateful
Functions.
The goal of this is to create a setup and configuration that works robustly in
the vast majority of settings. Users should not be required to configure
anything Flink-specific, other than
If this happens at the cost of some minor regression in peak stream throughput,
we can most likely stomach that in StateFun, because the performance cost is
commonly dominated by the interaction between StateFun cluster and remote
function deployments.
> Hide Flink complexity from Stateful Functions
> ---------------------------------------------
>
> Key: FLINK-22741
> URL: https://issues.apache.org/jira/browse/FLINK-22741
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Affects Versions: statefun-3.0.0
> Reporter: Stephan Ewen
> Priority: Major
>
> This is an umbrella issue for various issues to hide and reduce the
> complexity and surface area (and configuration space) of Apache Flink when
> using Stateful Functions.
> The goal of this is to create a setup and configuration that works robustly
> in the vast majority of settings. Users should not be required to configure
> anything Flink-specific, but only general parameters (like for example total
> memory size) and StateFun specific parameters (like request timeouts and
> batching).
> If this happens at the cost of some minor regression in peak stream
> throughput, we can most likely stomach that in StateFun, because the
> performance cost is commonly dominated by the interaction between StateFun
> cluster and remote function deployments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
