You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
When closing SFTPInputStream after SFTP read/write completion, the SFTPInputStream.close method is not properly closing the file stream. This can lead to resource leaks.
1.Terminal shows that the SFTP connection is not released.
2.Debugging reveals that the file stream is not closed when the SFTPInputStream.close method is triggered.
Zeta or Flink or Spark Version
No response
Java or Scala Version
jdk8
Screenshots
1.The initialization of SFTPInputStream.class does not pass the file stream to the parent class FSInputStream.class
2.the SFTPInputStream.close method only triggers the FSInputStream.close method, which is unable to close the file stream actually held by SFTPInputStream.
Search before asking
What happened
When closing SFTPInputStream after SFTP read/write completion, the SFTPInputStream.close method is not properly closing the file stream. This can lead to resource leaks.
SeaTunnel Version
2.3.2
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
jdk8
Screenshots
1.The initialization of SFTPInputStream.class does not pass the file stream to the parent class FSInputStream.class
2.the SFTPInputStream.close method only triggers the FSInputStream.close method, which is unable to close the file stream actually held by SFTPInputStream.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: