Doesn't work, unfortunately. Looks like the warning is emitted in hadoop fs api -- perhaps the java properties aren't propogated.
In any case, isn't this a bug in the avro-tools jar? -Isaac PS. The hadoop fs api has other counter-intuitive behavior, causing issues like: $ avro-tools cat *.avro /dev/null Exception in thread "main" java.io.FileNotFoundException: /dev/.null.crc (Permission denied) (which would have been useful to count records) On Oct 12, 2016, at 11:11 PM, radai <radai.rosenbl...@gmail.com<mailto:radai.rosenbl...@gmail.com>> wrote: reading the doc page (http://logging.apache.org/log4j/1.2/faq.html#noconfig), there's a log4j.defaultInitOverride property. have you tried adding -Dlog4j.defaultInitOverride=true to your command line ? On Wed, Oct 12, 2016 at 11:29 AM, Isaac Levy <isaac.l...@coxautoinc.com<mailto:isaac.l...@coxautoinc.com>> wrote: Is there any way to silence these? $ java -jar avro-tools-1.8.1.jar tojson foo log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Looks like avro-tools used to include<https://issues.apache. org/jira/browse/AVRO-758> log4j config. -Isaac Levy OS X el cap, java 1.8.0_92
