[ 
https://issues.apache.org/jira/browse/FLINK-22389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-22389:
-----------------------------------
    Labels: stale-assigned  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it. If the "warning_label" label is not removed in 7 days, the 
issue will be automatically unassigned.


> 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
>            Assignee: Igal Shilman
>            Priority: Major
>              Labels: stale-assigned
>             Fix For: statefun-3.1.0
>
>
> 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.3.4#803005)

Reply via email to