Re: stand alone avro-tools prints log4j warning

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 wrote: > Is there any

[jira] [Updated] (AVRO-1887) set up precommit checks via Apache Yetus

[ https://issues.apache.org/jira/browse/AVRO-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Acharya updated AVRO-1887: Attachment: AVRO-1887-1.patch Updated some incorrect comment. Also tagging [~aw] to do some code

stand alone avro-tools prints log4j warning

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

[jira] [Comment Edited] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568638#comment-15568638 ] Anders Sundelin edited comment on AVRO-1933 at 10/12/16 2:56 PM: - Patch set

[jira] [Commented] (AVRO-1927) If a default value is set, Avro allows null values in non-nullable fields.

[ https://issues.apache.org/jira/browse/AVRO-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568879#comment-15568879 ] Andreas Maier commented on AVRO-1927: - So I had a look at the generated Java code. And strangely

[jira] [Commented] (AVRO-1927) If a default value is set, Avro allows null values in non-nullable fields.

[ https://issues.apache.org/jira/browse/AVRO-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568867#comment-15568867 ] Andreas Maier commented on AVRO-1927: - Sorry for the long delay. I was on vacation. I tried the code

[jira] [Updated] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Sundelin updated AVRO-1933: -- Attachment: AVRO-1933-compatible-with-AVRO-1931.patch Patch set compatible with AVRO-1931 patch

[jira] [Updated] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Sundelin updated AVRO-1933: -- Attachment: AVRO-1933.patch Patch set adding more error details to SchemaCompatibility. Also

[jira] [Created] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

Anders Sundelin created AVRO-1933: - Summary: SchemaCompatibility class could be more user-friendly about incompatibilities Key: AVRO-1933 URL: https://issues.apache.org/jira/browse/AVRO-1933 Project:

[jira] [Commented] (AVRO-1340) use default to allow old readers to specify default enum value when encountering new enum symbols

[ https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15568443#comment-15568443 ] Zoltan Ivanfi commented on AVRO-1340: - I like the mechanism suggested by Matthieu, but I think

[jira] [Commented] (AVRO-1605) Remove Jackson classes from public API

[ https://issues.apache.org/jira/browse/AVRO-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15567956#comment-15567956 ] Gabor Szadovszky commented on AVRO-1605: Thanks for the response, Ryan. Sure, it is reasonable.