[ 
https://issues.apache.org/jira/browse/BEAM-6285?focusedWorklogId=190022&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-190022
 ]

ASF GitHub Bot logged work on BEAM-6285:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jan/19 14:34
            Start Date: 25/Jan/19 14:34
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on issue #7598: [BEAM-6285] 
add parameters for offsetConsumer in KafkaIO.read()
URL: https://github.com/apache/beam/pull/7598#issuecomment-457591311
 
 
   @XuMingmin Yes, I agree that there is no reason to test Kafka behaviour. On 
the other hand, it would make sense, at least, to test that offset consumer 
options were properly overridden by using `withOffsetConsumerConfigOverrides()`.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 190022)
    Time Spent: 1h 50m  (was: 1h 40m)

> add parameters for offsetConsumer in KafkaIO.read()
> ---------------------------------------------------
>
>                 Key: BEAM-6285
>                 URL: https://issues.apache.org/jira/browse/BEAM-6285
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-kafka
>            Reporter: Xu Mingmin
>            Assignee: Xu Mingmin
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Add an option in KafkaIO.read() to avoid using `offsetConsumer`. 
> *What's the problem:*
> When security is enabled, function 
> `KafkaUnboundedReader.updateLatestOffsets()` always fails with lots of WARN 
> log.
> *What's the cause:*
> `offsetConsumer` uses a mocked `ConsumerConfig.GROUP_ID_CONFIG`, and it 
> doesn't work as expected when security is enabled. In our case, 
> `ConsumerConfig.GROUP_ID_CONFIG` is the key to validate whether this consumer 
> is approved.
> *What's the solution:*
> Add an option to disable `offsetConsumer` by developers;
> *What's the side effect:*
> With `offsetConsumer` disabled, backlog is unknown.
>  
> [~rangadi] any comments?
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to