You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/02/28 14:55:11 UTC

[GitHub] [flink] guoweiM edited a comment on issue #11196: [FLINK-16246][connector kinesis] Exclude AWS SDK MBean registry from Kinesis build

guoweiM edited a comment on issue #11196: [FLINK-16246][connector kinesis] Exclude AWS SDK MBean registry from Kinesis build
URL: https://github.com/apache/flink/pull/11196#issuecomment-592548023
 
 
   In response to this problem, I think there are two ideas. One is the idea of cleaning up. Everyone has said it in more detail, and I have n’t added anything. There is another idea is to keep the singleton. Some third-party libraries have the design philosophy. There must be individual singleton objects, and these objects are consistent with the life cycle of the JVM. In this case, if we can guarantee that these singleton objects in a TM do not increase with the increase of Task, is it acceptable? In this way, we can also avoid case-by-case resolution.  @StephanEwen What do you think?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services