[
https://issues.apache.org/jira/browse/FLINK-13792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13792:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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.
> source and sink support manual rate limit
> -----------------------------------------
>
> Key: FLINK-13792
> URL: https://issues.apache.org/jira/browse/FLINK-13792
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Affects Versions: 1.8.1
> Reporter: zzsmdfj
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> in current flink implement automatic flow control by back pressure, it is
> efficient for the most scene, but in some special scenario, do we need
> fine-grained flow control to avoid impact on other systems? For example: if i
> have window with days(a lot of datas), then do call ProcessWindowFunction
> when trigger, this will produce a lot of data to sink, if sink to message
> queue, it can have a huge impact to message queue. so if there is sink rate
> limiter, it is friendly to external system. for source rate limiter, it is
> appropriate for having window operator and accumulating a large amount of
> historical data.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
