Fix logging for closing partition channels - partition and topic misp…

…laced (#977)
snowflakedb · Oct 28, 2024 · ad49fe6 · ad49fe6
1 parent 8a7a305
commit ad49fe6
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/src/main/java/com/snowflake/kafka/connector/internal/streaming/SnowflakeSinkServiceV2.java b/src/main/java/com/snowflake/kafka/connector/internal/streaming/SnowflakeSinkServiceV2.java
@@ -518,8 +518,8 @@ private void closeSequentially(Collection<TopicPartition> partitions) {
           LOGGER.info(
               "Closing partitionChannel:{}, partition:{}, topic:{}",
               topicPartitionChannel == null ? null : topicPartitionChannel.getChannelNameFormatV1(),
-              topicPartition.topic(),
-              topicPartition.partition());
+              topicPartition.partition(),
+              topicPartition.topic());
           partitionsToChannel.remove(partitionChannelKey);
         });
   }
@@ -539,8 +539,8 @@ private CompletableFuture<Void> closeTopicPartition(TopicPartition topicPartitio
     LOGGER.info(
         "Closing partitionChannel:{}, partition:{}, topic:{}",
         topicPartitionChannel == null ? null : topicPartitionChannel.getChannelNameFormatV1(),
-        topicPartition.topic(),
-        topicPartition.partition());
+        topicPartition.partition(),
+        topicPartition.topic());
 
     // It's possible that some partitions can be unassigned before their respective channels are
     // even created.