You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/12/01 00:45:17 UTC

[GitHub] [druid] himanshug commented on pull request #10551: Remove hard limitation that druid(after 0.15.0) only can consume Kafka version 0.11.x or better

himanshug commented on pull request #10551:
URL: https://github.com/apache/druid/pull/10551#issuecomment-736143481


   @zhangyue19921010 I think making Druid flexible to work with older versions of Kafka is good, so +1 on that.
   
   regarding the specific implementation here --
   does the problem happen if `isolation.level=read_uncommitted` ? if no, then all that is needed is to make "isolation.level" overridable via the `ioConfig` instead of introducing another configuration `consumeTransactionally`.
   That can be achieved by removing `props.put("isolation.level", "read_committed");` from `KafkaConsumerConfigs.getConsumerProperties()` and making that a default in `KafkaIndexTaskIOConfig` if `isolation.level=read_committed` is not explicitly supplied by the user.
   
   does that make sense?


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



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org