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

Yun Gao updated FLINK-20888:
----------------------------
    Description: 
Currently ContinuousFileReaderOperator would close the output on close(), if it 
is chained with more operators, it would also close the following operators 
before their endOfInput() is called (by default, we would call op1.endInput(), 
op1.close(), op2.endInput(), op2.close()... in order). This might cause some 
problems like in 

[https://lists.apache.org/thread.html/r50a94aaea4fe25f3927a4274ea8272e6b76ecec8f3fe48d2566689bd%40%3Cuser.flink.apache.org%3E]

  was:
Currently ContinuousFileReaderOperator would close the output on close(), if it 
is chained with more operators, it would close the following operators before 
their endOfInput() is called (by default, we would call op1.endInput(), 
op1.close(), op2.endInput(), op2.close()... in order). This might cause some 
problems like in 

https://lists.apache.org/thread.html/r50a94aaea4fe25f3927a4274ea8272e6b76ecec8f3fe48d2566689bd%40%3Cuser.flink.apache.org%3E


> ContinuousFileReaderOperator should not close the output on close()
> -------------------------------------------------------------------
>
>                 Key: FLINK-20888
>                 URL: https://issues.apache.org/jira/browse/FLINK-20888
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / FileSystem
>    Affects Versions: 1.12.0
>            Reporter: Yun Gao
>            Priority: Major
>
> Currently ContinuousFileReaderOperator would close the output on close(), if 
> it is chained with more operators, it would also close the following 
> operators before their endOfInput() is called (by default, we would call 
> op1.endInput(), op1.close(), op2.endInput(), op2.close()... in order). This 
> might cause some problems like in 
> [https://lists.apache.org/thread.html/r50a94aaea4fe25f3927a4274ea8272e6b76ecec8f3fe48d2566689bd%40%3Cuser.flink.apache.org%3E]



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

Reply via email to