[
https://issues.apache.org/jira/browse/BEAM-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329091#comment-16329091
]
Luke Cwik commented on BEAM-3488:
---------------------------------
Its strange that it happens so many times since it should only happen once. I'm
wondering whether a feature that was added like date sharded files is making it
so that we output so much. How is your sink configured?
> Reduce log noise coming from File sink
> --------------------------------------
>
> Key: BEAM-3488
> URL: https://issues.apache.org/jira/browse/BEAM-3488
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Affects Versions: 2.2.0
> Reporter: Pawel Bartoszek
> Assignee: Kenneth Knowles
> Priority: Minor
>
> After switching to Beam 2.2 I noticed that File sink related classes generate
> lots of lines likes this:
> {code:java}
> 2018-01-16 01:37:37,080 INFO org.apache.beam.sdk.io.FileBasedSink - No output
> files to write.
> 2018-01-16 01:37:37,104 INFO org.apache.beam.sdk.io.WriteFiles - Will
> finalize 0 files{code}
>
> I did some counts and it looks like this lines account for 82% of all lines
> in the log yet not giving much information.
> I am happy to raise a PR to make "No output files to write." and "Will
> finalize {} files" logged at DEBUG level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
