user  

Messages by Thread

• • Re: Python 3 avro v.1.9.2 is not pip installable Ismaël Mejía
  • Re: Python 3 avro v.1.9.2 is not pip installable Cris Ewing
• How to serialize & deserialize contiguous block of GenericRecords Pedro Cardoso
  • Re: How to serialize & deserialize contiguous block of GenericRecords Ryan Skraba
  • Re: How to serialize & deserialize contiguous block of GenericRecords Pedro Cardoso
  • Re: How to serialize & deserialize contiguous block of GenericRecords Ryan Skraba
• Call for presentations for ApacheCon North America 2020 now open Rich Bowen
• avro-c error: "Datum too large for file block size" Titouan Christophe
  • Re: avro-c error: "Datum too large for file block size" Dan Schmitt
  • Re: avro-c error: "Datum too large for file block size" Titouan Christophe
• avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Driesprong, Fokko
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Ryan Skraba
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Ryan Skraba
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Driesprong, Fokko
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Ryan Skraba
  • Re: avro-tools illegal reflective access warnings roger peppe
  • Re: avro-tools illegal reflective access warnings Driesprong, Fokko
  • Re: avro-tools illegal reflective access warnings roger peppe
• Schema modification with 1.9.1 Java api Dan Schmitt
• How best to handle JSON decoding for nullable fields Cary Young
• More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions zoly farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Driesprong, Fokko
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions Sean Busbey
  • Re: More idiomatic JSON encoding for unions Driesprong, Fokko
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
  • Re: More idiomatic JSON encoding for unions roger peppe
  • Re: More idiomatic JSON encoding for unions Zoltan Farkas
• Recomended naming of types to support for schema evolution Martin Mucha
  • Re: Recomended naming of types to support for schema evolution Lee Hambley
  • Re: Recomended naming of types to support for schema evolution Martin Mucha
  • Re: Recomended naming of types to support for schema evolution Lee Hambley
  • Re: Recomended naming of types to support for schema evolution Martin Mucha
  • Re: Recomended naming of types to support for schema evolution Lee Hambley
  • Re: Recomended naming of types to support for schema evolution Vance Duncan
• name-agnostic schema resolution (a.k.a. structural subtyping?) roger peppe
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) Ryan Skraba
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) roger peppe
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) Zoltan Farkas
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) roger peppe
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) roger peppe
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) Vance Duncan
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) roger peppe
  • Re: name-agnostic schema resolution (a.k.a. structural subtyping?) Michael Burr
• New Committer: Ryan Skraba Driesprong, Fokko
  • Re: New Committer: Ryan Skraba Nandor Kollar
  • Re: New Committer: Ryan Skraba Ismaël Mejía
  • Re: New Committer: Ryan Skraba Michael Burr
  • Re: New Committer: Ryan Skraba Austin Cawley-Edwards
  • Re: New Committer: Ryan Skraba Ryan Skraba
  • Re: New Committer: Ryan Skraba Niels Basjes
  • Re: New Committer: Ryan Skraba Brian Lachniet
  • Unsubscribe Dee Inguva
  • Re: New Committer: Ryan Skraba fady
• records with without fields? roger peppe
  • Re: records with without fields? Vance Duncan
  • Re: records with without fields? Ryan Skraba
  • Re: records with without fields? roger peppe
  • Re: records with without fields? Jonah H. Harris
  • Re: records with without fields? roger peppe
  • Re: records with without fields? roger peppe
  • Re: records with without fields? Vance Duncan
  • Re: records with without fields? roger peppe
  • Re: records with without fields? Vance Duncan
  • Re: records with without fields? roger peppe
  • Re: records with without fields? Vance Duncan
  • Re: records with without fields? Ryan Skraba
• Resolving a possible specification inconsistency pertaining to the doc attribute Jonah H. Harris
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute Ryan Skraba
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute Jonah H. Harris
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute roger peppe
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute Ryan Skraba
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute roger peppe
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute Jonah H. Harris
  • Re: Resolving a possible specification inconsistency pertaining to the doc attribute Jonah H. Harris
• recursive types roger peppe
  • Re: recursive types Lee Hambley
  • defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Lee Hambley
  • Re: defaults for complex types (was Re: recursive types) Ryan Skraba
  • Re: defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Lee Hambley
  • Re: defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Andy Le
  • Re: defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Andy Le
  • Re: defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Andy Le
  • Re: defaults for complex types (was Re: recursive types) roger peppe
  • Re: defaults for complex types (was Re: recursive types) Doug Cutting
  • Re: defaults for complex types (was Re: recursive types) Andy Le
• "class org.apache.avro.util.Utf8 cannot be cast to class java.lang.String" error Javier Holguera
• Deserialize list of JSON-encoded records with evolved Schema Austin Cawley-Edwards
  • Re: Deserialize list of JSON-encoded records with evolved Schema Zoltan Farkas
  • Re: Deserialize list of JSON-encoded records with evolved Schema Austin Cawley-Edwards
• Non-Deterministic avsc Directory Compilation Austin Cawley-Edwards
  • Re: Non-Deterministic avsc Directory Compilation Ryan Skraba
  • Re: Non-Deterministic avsc Directory Compilation Michael A. Smith
  • Re: Non-Deterministic avsc Directory Compilation Lee Hambley
  • Re: Non-Deterministic avsc Directory Compilation Austin Cawley-Edwards
• Accessing default value in schema Mark Petronic
  • Re: Accessing default value in schema Dan Schmitt
  • Re: Accessing default value in schema Mark Petronic
• schema evolution with top-level union. Martin Mucha
• How to build up a record datum and validate in C++ Mark Petronic
• avro.java.string property being ignored during deserialization when nested inside unions Priit Danelson
• File created with c++ can not be read with Python alopez
  • Re: File created with c++ can not be read with Python Arne Vogel
• Re: Announcement: Avro Schema Viewer Robin Trietsch
  • Re: Announcement: Avro Schema Viewer Driesprong, Fokko
• it's still there is not workaround on 1.9.1 to handle missing field in json ? Yanna elina
• AvroTypeException with "Expected" case : field name is not provided Yanna elina
  • Re: AvroTypeException with "Expected" case : field name is not provided fady
• Can I run Avro IPC on Android? Suman Bhunia
• Release notes for Avro 1.9.1 Javier Holguera
  • Re: Release notes for Avro 1.9.1 Driesprong, Fokko
• Avro at Apachecon US 2019 Ismaël Mejía
  • Re: Avro at Apachecon US 2019 Brian Lachniet
  • Re: Avro at Apachecon US 2019 Ismaël Mejía
• [Announce] Please welcome Nándor Kollár to the Apache Avro PMC Sean Busbey
  • Re: [Announce] Please welcome Nándor Kollár to the Apache Avro PMC Brian Lachniet
  • Re: [Announce] Please welcome Nándor Kollár to the Apache Avro PMC Niels Basjes
  • Re: [Announce] Please welcome Nándor Kollár to the Apache Avro PMC Driesprong, Fokko
• Reg : Avro Secondary Sorting using AvroJob Api SB M
• Avro schema having Map of Records Edgar H
  • Re: Avro schema having Map of Records Ryan Skraba
  • Re: Avro schema having Map of Records Edgar H
  • Re: Avro schema having Map of Records Ryan Skraba
  • Re: Avro schema having Map of Records Edgar H
• AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Ryan Skraba
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Ryan Skraba
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Svante Karlsson
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Svante Karlsson
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Martin Mucha
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Svante Karlsson
  • Re: AVRO schema evolution: adding optional column with default fails deserialization Ryan Skraba
  • Re: Schema parses in C# Avro lib but not in Kafka Schema registry (assume that it is the java lib) Patrick Farry
• Reg: Avrojob schema validation option. SB M
  • Re: Reg: Avrojob schema validation option. Ryan Skraba
  • Re: Reg: Avrojob schema validation option. SB M
  • Re: Reg: Avrojob schema validation option. Ryan Skraba
  • Re: Reg: Avrojob schema validation option. SB M
• Returning errors from IPC responders Lee Hambley
• Deserialize only a subset of the avro message Vishwas Siravara
  • Re: Deserialize only a subset of the avro message David Carlton
• union schema evolution KV 59
  • Re: union schema evolution Driesprong, Fokko
  • Re: union schema evolution KV 59
• Should a Schema be serializable in Java? Ryan Skraba
  • Re: Should a Schema be serializable in Java? Ismaël Mejía
  • Re: Should a Schema be serializable in Java? Doug Cutting
  • Re: Should a Schema be serializable in Java? Driesprong, Fokko
  • Re: Should a Schema be serializable in Java? Ismaël Mejía
  • Re: Should a Schema be serializable in Java? Ryan Skraba
  • Re: Should a Schema be serializable in Java? Ismaël Mejía
  • Re: Should a Schema be serializable in Java? Ryan Skraba
  • Re: Should a Schema be serializable in Java? Driesprong, Fokko
  • Re: Should a Schema be serializable in Java? Zoltan Farkas
  • Re: Should a Schema be serializable in Java? Driesprong, Fokko
• Avro C++: How to serialize data as Data Object File to send in Kafka? steinio
  • Re: Avro C++: How to serialize data as Data Object File to send in Kafka? Svante Karlsson
• Python 3: AssertionError on reading empty file David Beswick
  • Re: Python 3: AssertionError on reading empty file Michael A. Smith
  • RE: Python 3: AssertionError on reading empty file David Beswick
• Aliases with Forward Compatibility Aaron Dixon
  • Re: Aliases with Forward Compatibility Zoltan Farkas
  • Re: Aliases with Forward Compatibility Aaron Dixon
  • Re: Aliases with Forward Compatibility Zoltan Farkas
• ApacheCon North America 2019 Schedule Now Live! Rich Bowen
• [ANNOUNCE] Please welcome Ismaël Mejía to the Apache Avro PMC Sean Busbey
  • Re: [ANNOUNCE] Please welcome Ismaël Mejía to the Apache Avro PMC Jesse Anderson
  • Re: [ANNOUNCE] Please welcome Ismaël Mejía to the Apache Avro PMC Brian Lachniet
  • Re: [ANNOUNCE] Please welcome Ismaël Mejía to the Apache Avro PMC Niels Basjes
  • Re: [ANNOUNCE] Please welcome Ismaël Mejía to the Apache Avro PMC Driesprong, Fokko
• does avro 1.9.0 include support for forward declarations in IDL files? David Carlton
  • Re: does avro 1.9.0 include support for forward declarations in IDL files? Bridger Howell

• Earlier messages
• Later messages