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

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

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

    https://github.com/apache/flink/pull/1437#discussion_r46836934
  
    --- Diff: 
flink-streaming-connectors/flink-connector-kafka/src/main/java/org/apache/flink/streaming/connectors/kafka/FlinkKafkaConsumer.java
 ---
    @@ -563,37 +559,44 @@ public void notifyCheckpointComplete(long 
checkpointId) throws Exception {
                                        LOG.warn("Received confirmation for 
unknown checkpoint id {}", checkpointId);
                                        return;
                                }
    -   
    -                           checkpointOffsets = (long[]) 
pendingCheckpoints.remove(posInMap);
    +
    +                           //noinspection unchecked
    +                           checkpointOffsets = 
(HashMap<KafkaTopicPartition, Long>) pendingCheckpoints.remove(posInMap);
    +
                                
                                // remove older checkpoints in map
                                for (int i = 0; i < posInMap; i++) {
                                        pendingCheckpoints.remove(0);
                                }
                        }
    -   
    -                   if (LOG.isInfoEnabled()) {
    -                           LOG.info("Committing offsets {} to offset 
store: {}", Arrays.toString(checkpointOffsets), offsetStore);
    +                   if(checkpointOffsets.size() == 0) {
    --- End diff --
    
    I think this is a bug. If the list is empty after you remove the checkpoint 
to commit, it only means that no pending checkpoint was subsumed. It should 
still commit the offsets to Kafka.


> Allow reading from multiple topics with one FlinkKafkaConsumer
> --------------------------------------------------------------
>
>                 Key: FLINK-3102
>                 URL: https://issues.apache.org/jira/browse/FLINK-3102
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kafka Connector
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>
> Currently, a Kafka consumer allows to read from only one topic.
> For cases where multiple topics contain messages with the same schema, it is 
> useful to allow to subscribe to many topics using one FlinkKafkaConsumer 
> instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to