[
https://issues.apache.org/jira/browse/FLINK-22389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22389:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Expose Message Batches to SDKs
> ------------------------------
>
> Key: FLINK-22389
> URL: https://issues.apache.org/jira/browse/FLINK-22389
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Reporter: Konstantin Knauf
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> Stateful Functions always invokes a functions with a batch of messages. Under
> normal operations the batch size=1 (no batching).
> If a function is slow and backpressure arises, the batch size grows, though.
> From an SDK perspective, this batching is not visible. The function is always
> invoked with a single message. This makes it impossible to efficiently
> evaluate the whole batch at once (e.g. with pandas).
> This issue was requested in
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-Statefun-Python-Batch-tp43022.html.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
