Skip to content

Commit 0f5d756

Browse files
committed
Changing WriteBatcher logging to debug
This is seeming to be too low-level for a user - i.e. user doesn't need to know about a "batcher". The info-level logging we already have that confirms the number of partitions and thread count is of much more value.
1 parent a2d8b14 commit 0f5d756

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/main/java/com/marklogic/spark/writer/WriteContext.java

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,9 @@ WriteBatcher newWriteBatcher(DataMovementManager dataMovementManager) {
113113
final int threadCount = getUserDefinedThreadCountPerPartition() > 0 ?
114114
getUserDefinedThreadCountPerPartition() : getCalculatedThreadCountPerPartition();
115115

116-
Util.MAIN_LOGGER.info("Creating new batcher with thread count of {} and batch size of {}.", threadCount, batchSize);
116+
if (Util.MAIN_LOGGER.isDebugEnabled()) {
117+
Util.MAIN_LOGGER.debug("Creating new batcher with thread count of {} and batch size of {}.", threadCount, batchSize);
118+
}
117119
WriteBatcher writeBatcher = dataMovementManager
118120
.newWriteBatcher()
119121
.withBatchSize(batchSize)

0 commit comments

Comments
 (0)