[ 
https://issues.apache.org/jira/browse/FLINK-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320327#comment-16320327
 ] 

ASF GitHub Bot commented on FLINK-8306:
---------------------------------------

Github user pnowojski commented on a diff in the pull request:

    https://github.com/apache/flink/pull/5200#discussion_r160692827
  
    --- Diff: 
flink-connectors/flink-connector-kafka-base/src/main/java/org/apache/flink/streaming/connectors/kafka/internals/AbstractFetcher.java
 ---
    @@ -51,7 +50,7 @@
      *            the Flink data streams.
      * @param <KPH> The type of topic/partition identifier used by Kafka in 
the specific version.
      */
    -public abstract class AbstractFetcher<T, KPH> {
    +public abstract class AbstractFetcher<T, KPH> implements 
KafkaOffsetCommitter {
    --- End diff --
    
    Probably you are right, however I haven't thought this through, but if you 
had and you feel that's a good opportunity to make some larger refactor I'm 
fine with that :)
    
    Anyway, as we discussed offline, such refactor could be made in separate PR 
and here you could just implement 
`AbstractFetcher#doCommitInternalOffsetsToKafka` for the testing purposes. 
    
    I don't mind if you choose one over the other approach :)


> FlinkKafkaConsumerBaseTest has invalid mocks on final methods
> -------------------------------------------------------------
>
>                 Key: FLINK-8306
>                 URL: https://issues.apache.org/jira/browse/FLINK-8306
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector, Tests
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Critical
>             Fix For: 1.5.0, 1.4.1
>
>
> The {{FlinkKafkaConsumerBaseTest}} has invalid mocks on a final 
> {{AbstractFetcher::commitInternalOffsetsToKafka(...)}} method. While an easy 
> fix would be to simply make that method non-final, that is not ideal since it 
> would be best that the method is left final to prevent overrides in 
> subclasses.
> This suggests that offset committing functionality is too tightly coupled 
> with the {{AbstractFetcher}}, making it hard to perform concise tests to 
> verify offset committing.
> I suggest that we decouple record fetching and offset committing as separate 
> services behind different interfaces. We should introduce a new interface, 
> say {{KafkaOffsetCommitter}}, and test against that instead. Initially, we 
> can simply let {{AbstractFetcher}} implement {{KafkaOffsetCommitter}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to