MurderWind commented on issue #6455: URL: https://github.com/apache/iceberg/issues/6455#issuecomment-1359687357
> // Ideally, operatorId should be used as the threadPoolName as Flink guarantees its uniqueness > // within a job. SplitEnumeratorContext doesn't expose the OperatorCoordinator.Context, which > // would contain the OperatorID. Need to discuss with Flink community whether it is ok to expose > // a public API like the protected method "OperatorCoordinator.Context getCoordinatorContext()" > // from SourceCoordinatorContext implementation. For now, <table name>-<random UUID> is used as > // the unique thread pool name. actually. i i found the bug when org.apache.iceberg.jdbc.JdbcTableOperations#connections connections properties closed turn true ,it is happened. but i don't find why closed turns true. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
