[jira] [Updated] (FLINK-6199) Single outstanding Async I/O operation per key

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-6199:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> Single outstanding Async I/O operation per key
> ----------------------------------------------
>
>                 Key: FLINK-6199
>                 URL: https://issues.apache.org/jira/browse/FLINK-6199
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Jamie Grier
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> I would like to propose we extend the Async I/O semantics a bit such that a user can guarantee a single outstanding async request per key.
> This would allow a user to order async requests per key while still achieving the throughput benefits of using Async I/O in the first place.
> This is essential for operations where stream order is important but we still need to use Async operations to interact with an external system in a performant way.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)