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

jocean.shi updated FLINK-15343:
-------------------------------
    Description: 
  Currently, The "TwoInputStreamOperator" such as 
"CoBroadcastWithKeyedOperator" "KeyedCoProcessOperator" and the
 (Co)stream such as "ConnectedStreams" "BroadcastConnectedStream" only support 
compute watermark by two stream.
 but user just need one stream to compute watermark in some case.
      For example: one stream is only rule data or control command, it
 don't hava event time.
 I think user has right to choose which stream to compute watermark.

  was:
  Currently, The "TwoInputStreamOperator" such as 
"CoBroadcastWithKeyedOperator" "KeyedCoProcessOperator" and the
(Co)stream such as "ConnectedStreams" "BroadcastConnectedStream" only support 
compute watermark by two stream.
but user just need one stream to compute watermark in some case.
     For example: one stream is only rule data or control command, it
don't hava event time.
I think user has right to choose which stream to compute watermark.


> Add Watermarks options for TwoInputStreamOperator
> -------------------------------------------------
>
>                 Key: FLINK-15343
>                 URL: https://issues.apache.org/jira/browse/FLINK-15343
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: jocean.shi
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>   Currently, The "TwoInputStreamOperator" such as 
> "CoBroadcastWithKeyedOperator" "KeyedCoProcessOperator" and the
>  (Co)stream such as "ConnectedStreams" "BroadcastConnectedStream" only 
> support compute watermark by two stream.
>  but user just need one stream to compute watermark in some case.
>       For example: one stream is only rule data or control command, it
>  don't hava event time.
>  I think user has right to choose which stream to compute watermark.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to