You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by GitBox <gi...@apache.org> on 2022/11/18 06:33:45 UTC

[GitHub] [avro] yurybubnov opened a new pull request, #1970: Avro-3313: [Java] use default enum when reading with old schema

yurybubnov opened a new pull request, #1970:
URL: https://github.com/apache/avro/pull/1970

   ## What is the purpose of the change
   According to [Avro documentation](https://avro.apache.org/docs/1.11.1/specification/#enums) for default value for Enums:
   ```
   default: A default value for this enumeration, used during resolution when the reader encounters a symbol from the writer that isn’t defined in the reader’s schema (optional). The value provided here must be a JSON string that’s a member of the symbols array. See the documentation on schema resolution for how this gets used.
   ```
   And in [Schema Resolution](https://avro.apache.org/docs/1.11.1/specification/#schema-resolution)
   ```
   if both are enums: if the writer’s symbol is not present in the reader’s enum and the reader has a default value, then that value is used, otherwise an error is signalled.
   ```
   
   This is not the case at the moment in Java implementation.
   In the [TestSchemaCompatibilityEnumDefaults](https://github.com/apache/avro/blob/master/lang/java/avro/src/test/java/org/apache/avro/TestSchemaCompatibilityEnumDefaults.java), both writer and reader schemas are required for successful decoding object serialized with new schema into old schema. 
   It should be possible, to decode Enums with just the old schema, without the new one present, as in specified in the documentation.
   
   
   ## Verifying this change
   
   
   This change added tests and can be verified as follows:
   * New test is added to TestSchemaCompatibilityEnumDefaults to verify the change
   
   
   ## Documentation
   
   - Does this pull request introduces a new feature? No
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] KalleOlaviNiemitalo commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
KalleOlaviNiemitalo commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1027249970


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   Is this executed during the tests?
   
   AFAICT this is for the case where the decoded enum ordinal is out of range for the schema with which it was supposedly written.  Does the spec really say that the enum default should matter in that situation?



##########
lang/java/avro/src/main/java/org/apache/avro/io/FastReaderBuilder.java:
##########
@@ -488,8 +488,18 @@ private FieldReader createArrayReader(Schema readerSchema, Container action) thr
 
   private FieldReader createEnumReader(EnumAdjust action) {
     return reusingReader((reuse, decoder) -> {
+      Object resultObject;
       int index = decoder.readEnum();
-      Object resultObject = action.values[index];
+      if (index >= action.values.length) {

Review Comment:
   Could check index \< 0 too.



##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {

Review Comment:
   Could check ordinal \< 0 too.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1035006757


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   The requirement to have the correct writer's schema during the read operation makes Avro unusable in real-world production scenarios. 
   If this requirement is enforced then schemas can't be updated ever since it's impossible to have all message consumers switch to a new schema at the same time as the writer without downtime.
   Developers are in charge of schema evolution and, if stated properly in documentation, situations like change of enum order can be avoided



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1030077207


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   In this case, serialized data wasn't produced with a known writer schema and the deserializer should use a default value if present in the reader schema.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] opwvhk commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
opwvhk commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1035560795


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   In "Getting started (Java)", the doc says:
   > The writer’s schema is needed to know the order in which fields were written, while the reader’s schema is needed to know what fields are expected and how to fill in default values for fields added since the file was written. If there are differences between the two schemas, they are resolved according to the Schema Resolution specification.
   
   More on schema evolution has been written, for example by Martin Kleppmann: https://martin.kleppmann.com/2012/12/05/schema-evolution-in-avro-protocol-buffers-thrift.html  
   And on stackoverflow:  
   https://stackoverflow.com/questions/73323112/does-avro-supports-schema-evolution/73324135  
   https://stackoverflow.com/questions/15350509/avro-schema-evolution
   
   There is more to be found, but I'll leave that as an exercise for the reader.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on PR #1970:
URL: https://github.com/apache/avro/pull/1970#issuecomment-1319612052

   I was puzzled here. Should I leave the behavior as it is for absent default values, meaning expect `IndexOutOfBoundsException` or update it and explicitly throw `AvroTypeException` with a message like `Unknown Enum Ordinal #`.
   Thoughts?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] opwvhk commented on pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by "opwvhk (via GitHub)" <gi...@apache.org>.
opwvhk commented on PR #1970:
URL: https://github.com/apache/avro/pull/1970#issuecomment-1737159266

   I'm closing this PR, as it is based on a wrong premise (see the discussion starting at https://github.com/apache/avro/pull/1970#discussion_r1027251763). If merged, this would introduce a bug.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1035295020


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   Nothing in the doc says the reader should have access to writer's schema. Contrary, it says:
   ```
   the reader may be programmed to read data into a different schema. For example, if the data was written with a different version of the software than it is read
   ```
   If we insist on the reader to always has the writes' schema, it will mean that schema evolution is not possible at all in real-world scenarios.
   There might be several schema versions, and, as long as they are backward compatible (nullable fields, fields are added) reader should be able to read the data.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] KalleOlaviNiemitalo commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
KalleOlaviNiemitalo commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1027251763


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   A mismatch like that seems to indicate that the data was not actually written using the schema that the decoder believes was used. In that case, the defined enum symbols might not be correct, either. It might be best to throw an exception rather than map to the enum default, so that somebody can notice the problem and fix the bug that causes the mismatch.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] opwvhk commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
opwvhk commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1033171936


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   Without a (correct!) writer schema, Avro data is basically garbage. Attempting to fix this is a laudible effort, but also introduces bugs.
   
   What happens, for example if data was written with `{"type":"enum","name":"Switch","symbols":["OFF","DIMMED1","DIMMED2","DIMMED3","FULL"]}`, but subsequently read with the older `{"type":"enum","name":"Switch","symbols":["ON","OFF"]}`?
   
   IMHO, throwing an exception is the correct way to handle this. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] KalleOlaviNiemitalo commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
KalleOlaviNiemitalo commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1027341697


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   "if the writer’s symbol is not present" — but if the ordinal is out of range for the writer's schema then the library doesn't even know what the writer's symbol is.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] KalleOlaviNiemitalo commented on pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
KalleOlaviNiemitalo commented on PR #1970:
URL: https://github.com/apache/avro/pull/1970#issuecomment-1321073522

   AvroTypeException is used for out-of-range enum in ValidatingDecoder too, so throwing that makes sense.
   
   <https://github.com/apache/avro/blob/3a9e5a789b5165e0c8c4da799c387fdf84bfb75e/lang/java/avro/src/main/java/org/apache/avro/io/ValidatingDecoder.java#L165-L167>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] opwvhk commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
opwvhk commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1035225603


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   On the contrary: schema evolution is handled by schema resolution. This is the process that translates data written with the "write schema" into a structure defined by the "read schema" **while reading the data**.
   
   See https://avro.apache.org/docs/1.11.1/specification/#schema-resolution
   
   All consumers read the data into a structure defined by the read schema they were compiled/deployed with. This is static and changes only when the consumers are ready.
   
   To do so, consumers must have access to the write schema used to write the data, for example by reading the schema embedded in a `.avro` file, or via a service implemented by the `SchemaStore` interface. Schema resolution/evolution works as long as both schemas are compatible.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] opwvhk closed pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by "opwvhk (via GitHub)" <gi...@apache.org>.
opwvhk closed pull request #1970: Avro-3313: [Java] use default enum when reading with old schema
URL: https://github.com/apache/avro/pull/1970


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1027327812


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   that contradicts the documentation:
   if both are enums: if the writer’s symbol is not present in the reader’s enum and the reader has a default value, then that value is used, otherwise an error is signalled.
   
   If the default value is specified - it should be used, otherwise - throw an exception. Absen of this rule, it will be hard to promote schema evolution and all clients will need to be aware of the current writer schema before the writer could use it. Which means in reality, only one schema can be used and no evolution of enums suported



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [avro] yurybubnov commented on a diff in pull request #1970: Avro-3313: [Java] use default enum when reading with old schema

Posted by GitBox <gi...@apache.org>.
yurybubnov commented on code in PR #1970:
URL: https://github.com/apache/avro/pull/1970#discussion_r1030077207


##########
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumReader.java:
##########
@@ -265,7 +267,17 @@ protected void readField(Object record, Field field, Object oldDatum, ResolvingD
    * representations. By default, returns a GenericEnumSymbol.
    */
   protected Object readEnum(Schema expected, Decoder in) throws IOException {
-    return createEnum(expected.getEnumSymbols().get(in.readEnum()), expected);
+    List<String> enumSymbols = expected.getEnumSymbols();
+    int ordinal = in.readEnum();
+    if (ordinal >= enumSymbols.size()) {
+      if (expected.getEnumDefault() == null) {
+        throw new AvroTypeException("Unknown Enum Ordinal " + ordinal);
+      }
+
+      return createEnum(expected.getEnumDefault(), expected);

Review Comment:
   In this case, serialized data wasn't produced with a known writer schema and the deserializer should fall back to a default value if present in the reader schema or signal error otherwise



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org