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/07/10 04:50:26 UTC

[GitHub] [flink] freezhan commented on pull request #12157: [FLINK-17691][Connectors/Kafka] fix the bug FlinkKafkaProducer011 transactional.id too long when use Semantic.EXACTLY_ONCE mode

freezhan commented on pull request #12157:
URL: https://github.com/apache/flink/pull/12157#issuecomment-656480710


   @aljoscha  How about letting the user pass this prefix parameter, then then also add a check inside the generator to verify that we really obey the length cap.
   
   Transaction.id should have a business meaning.
   
   I don't think the following lengthy context makes any sense, it's not readable if it's too long, right
   ```java
    getRuntimeContext().getTaskName() + "-" + ((StreamingRuntimeContext) getRuntimeContext()).getOperatorUniqueID()
   ```
   
   


----------------------------------------------------------------
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