[jira] [Commented] (AVRO-2329) Avro C# hides inner exceptions
[
https://issues.apache.org/jira/browse/AVRO-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782054#comment-16782054
]
ASF subversion and git services commented on AVRO-2329:
---
Commit a56108835a0aa35530c8f367ce8a50d0c5861192 in avro's branch
refs/heads/master from Brian Lachniet
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=a561088 ]
AVRO-2329: Set inner exception when available
> Avro C# hides inner exceptions
> --
>
> Key: AVRO-2329
> URL: https://issues.apache.org/jira/browse/AVRO-2329
> Project: Apache Avro
> Issue Type: Improvement
> Components: csharp
>Affects Versions: 1.8.2
>Reporter: Brian Lachniet
>Assignee: Brian Lachniet
>Priority: Major
> Fix For: 1.9.0
>
>
> The Avro C# library hides the inner exception in many places where it throws
> {{AvroException}}. This makes it difficult to track down the root cause of
> some problems.
> Update places that throw {{AvroException}} to include the inner exception
> when available/applicable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2324) Update Apache parent POM to version 21
[ https://issues.apache.org/jira/browse/AVRO-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783215#comment-16783215 ] ASF subversion and git services commented on AVRO-2324: --- Commit 3ec3db79af89d5674c2cfe5cedb7c784787e9bcd in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=3ec3db7 ] [AVRO-2324] Bump Apache to 21 > Update Apache parent POM to version 21 > -- > > Key: AVRO-2324 > URL: https://issues.apache.org/jira/browse/AVRO-2324 > Project: Apache Avro > Issue Type: Improvement >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1810) GenericDatumWriter broken with Enum
[
https://issues.apache.org/jira/browse/AVRO-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783853#comment-16783853
]
ASF subversion and git services commented on AVRO-1810:
---
Commit 4a3609cd854e9ef5bdda5b43e188a3309a93aef9 in avro's branch
refs/heads/master from ivangreene
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=4a3609c ]
AVRO-1810: Fix GenericDatumWriter w/ enums (#462)
> GenericDatumWriter broken with Enum
> ---
>
> Key: AVRO-1810
> URL: https://issues.apache.org/jira/browse/AVRO-1810
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Affects Versions: 1.8.0
>Reporter: Ryon Day
>Priority: Blocker
> Fix For: 1.9.0, 1.8.4
>
>
> {panel:title=Description|titleBGColor=#3FA|bgColor=#DDD}
> Using the GenericDatumWriter with either Generic OR SpecificRecord will break
> if an Enum is present.
> {panel}
> {panel:title=Steps To Reproduce|titleBGColor=#8DB|bgColor=#DDD}
> I have been tracking Avro decoding oddities for a while.
> The tests for this issue can be found
> [here|https://github.com/ryonday/avroDecodingHelp/blob/master/src/test/java/com/ryonday/test/Avro180EnumFail.java]
> {panel}
> {panel:title=Notes|titleBGColor=#3AF|bgColor=#DDD}
> Due to the debacle that is the Avro "UTF8" object, we have been avoiding it
> by using the following scheme:
> * Write incoming records to a byte array using the GenericDatumWriter
> * Read back the byte array to our compiled Java domain objects using a
> SpecificDatumWriter
> This worked great with Avro 1.7.7, and this is a binary-incompatable breaking
> change with 1.8.0.
> This would appear to be caused by an addition in the
> {{GenericDatumWriter:163-164}}:
> {code}
> if (!data.isEnum(datum))
> throw new AvroTypeException("Not an enum: "+datum);
> {code}
> {panel}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2339) Remove Unused LengthLimitedInputStream
[ https://issues.apache.org/jira/browse/AVRO-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786557#comment-16786557 ] ASF subversion and git services commented on AVRO-2339: --- Commit 2f2025201bf937cb163d263396a097bbc5fad1b0 in avro's branch refs/heads/master from BELUGABEHR [ https://gitbox.apache.org/repos/asf?p=avro.git;h=2f20252 ] AVRO-2339: Remove Unused LengthLimitedInputStream (#472) > Remove Unused LengthLimitedInputStream > -- > > Key: AVRO-2339 > URL: https://issues.apache.org/jira/browse/AVRO-2339 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Minor > > Package scoped class and it is not used at all. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2338) Remove Deprecated Use of JsonStringEncoder
[
https://issues.apache.org/jira/browse/AVRO-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786566#comment-16786566
]
ASF subversion and git services commented on AVRO-2338:
---
Commit f173ae8d690b5f90e8cc5899b654762a9d11e17d in avro's branch
refs/heads/master from BELUGABEHR
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=f173ae8 ]
AVRO-2338: Remove Deprecated Use of JsonStringEncoder (#471)
> Remove Deprecated Use of JsonStringEncoder
> --
>
> Key: AVRO-2338
> URL: https://issues.apache.org/jira/browse/AVRO-2338
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Affects Versions: 1.9.0
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> {code:java|title=SchemaBuilder.java}
> char[] quoted = JsonStringEncoder.getInstance().quoteAsString(s);
> {code}
> [Deprecated. Since 2.9.2 use BufferRecyclers.getJsonStringEncoder()
> instead|https://fasterxml.github.io/jackson-core/javadoc/2.9/com/fasterxml/jackson/core/io/JsonStringEncoder.html#getInstance--]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2334) Update Docs to Reference Java 8 API
[ https://issues.apache.org/jira/browse/AVRO-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786500#comment-16786500 ] ASF subversion and git services commented on AVRO-2334: --- Commit 02e08dafd35b31e9e596564b0996dc63bd2fb1ed in avro's branch refs/heads/master from BELUGABEHR [ https://gitbox.apache.org/repos/asf?p=avro.git;h=02e08da ] AVRO-2334: Update Docs to Reference Java 8 API (#469) > Update Docs to Reference Java 8 API > --- > > Key: AVRO-2334 > URL: https://issues.apache.org/jira/browse/AVRO-2334 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Trivial > > https://github.com/apache/avro/blob/master/lang/java/pom.xml#L113-L114 > > [https://github.com/apache/avro/blob/master/lang/java/pom.xml#L193] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2351) Long/Int in Binary Decoder
[
https://issues.apache.org/jira/browse/AVRO-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790727#comment-16790727
]
ASF subversion and git services commented on AVRO-2351:
---
Commit d195e1fc626f960eef7ef9a5aaeb3851cb4fda31 in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=d195e1f ]
AVRO-2351: Long/Int in Binary Decoder
> Long/Int in Binary Decoder
> --
>
> Key: AVRO-2351
> URL: https://issues.apache.org/jira/browse/AVRO-2351
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Affects Versions: 1.9.0
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> {code:java|title=BinaryDecoder.java}
> /**
>* Returns the number of items to follow in the current array or map.
> Returns
>* 0 if there are no more items in the current array and the array/map has
>* ended.
>*
>* @throws IOException
>*/
> protected long doReadItemCount() throws IOException {
> long result = readLong();
> if (result < 0) {
> readLong(); // Consume byte-count if present
> result = -result;
> }
> return result;
> }
> /**
>* Reads the count of items in the current array or map and skip those
> items,
>* if possible. If it could skip the items, keep repeating until there are
> no
>* more items left in the array or map. If items cannot be skipped (because
>* byte count to skip is not found in the stream) return the count of the
>* items found. The client needs to skip the items individually.
>*
>* @return Zero if there are no more items to skip and end of array/map is
>* reached. Positive number if some items are found that cannot be
>* skipped and the client needs to skip them individually.
>* @throws IOException
>*/
> private long doSkipItems() throws IOException {
> long result = readInt();
> while (result < 0) {
> long bytecount = readLong();
> doSkipBytes(bytecount);
> result = readInt();
> }
> return result;
> }
> {code}
> https://github.com/apache/avro/blob/master/lang/java/avro/src/main/java/org/apache/avro/io/BinaryDecoder.java#L370-L406
> The spec states that the sizes are {{long}} values.The {{doReadItemCount}}
> method has it correct and the {{doSkipItems}} method uses {{int]} values
> values.
> https://avro.apache.org/docs/1.8.2/spec.html#binary_encode_complex
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2349) Review Usage of Arrays.asList
[
https://issues.apache.org/jira/browse/AVRO-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790748#comment-16790748
]
ASF subversion and git services commented on AVRO-2349:
---
Commit 0e6977d1b89c9a103cec0be5bd4bbeceb740d50f in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=0e6977d ]
AVRO-2349: Review Usage of Arrays.asList
> Review Usage of Arrays.asList
> -
>
> Key: AVRO-2349
> URL: https://issues.apache.org/jira/browse/AVRO-2349
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Affects Versions: 1.9.0
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> The method {{Arrays.asList}} is used in several different places in the
> project and is used differently each place. I have reviewed all uses of it
> and made it consistent and removed it in a couple of places that would be
> better implemented with a different approach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2352) BinaryDecoder isEnd
[ https://issues.apache.org/jira/browse/AVRO-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790728#comment-16790728 ] ASF subversion and git services commented on AVRO-2352: --- Commit 6fddbae08fcf0aba1d51289d1b90681c3bfa9477 in avro's branch refs/heads/master from Beluga Behr [ https://gitbox.apache.org/repos/asf?p=avro.git;h=6fddbae ] AVRO-2352: Cleanup BinaryDecoder isEnd Method > BinaryDecoder isEnd > --- > > Key: AVRO-2352 > URL: https://issues.apache.org/jira/browse/AVRO-2352 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Trivial > > * Add additional JavaDoc > * Simplify code -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2350) Use Switch Statement for Strings in LogicalTypes
[
https://issues.apache.org/jira/browse/AVRO-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790744#comment-16790744
]
ASF subversion and git services commented on AVRO-2350:
---
Commit 63e02101cf94d8ab0e1ae01baafe04c5767aa371 in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=63e0210 ]
AVRO-2350: Use Switch Statement for Strings in LogicalTypes
> Use Switch Statement for Strings in LogicalTypes
>
>
> Key: AVRO-2350
> URL: https://issues.apache.org/jira/browse/AVRO-2350
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Affects Versions: 1.9.0
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> https://github.com/apache/avro/blob/master/lang/java/avro/src/main/java/org/apache/avro/LogicalTypes.java#L59-L101
> {quote}
> The switch statement compares the String object in its expression with the
> expressions associated with each case label as if it were using the
> String.equals method; consequently, the comparison of String objects in
> switch statements is case sensitive. The Java compiler generates generally
> more efficient bytecode from switch statements that use String objects than
> from chained if-then-else statements.
> https://docs.oracle.com/javase/7/docs/technotes/guides/language/strings-switch.html
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2348) Do Not Wrap JSON Strings in StringReader for Parsing
[
https://issues.apache.org/jira/browse/AVRO-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790867#comment-16790867
]
ASF subversion and git services commented on AVRO-2348:
---
Commit fb3c25f92baa17249219e263e0fe17568c67eadc in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=fb3c25f ]
AVRO-2348: Remove use of Deprecated createJsonParser
> Do Not Wrap JSON Strings in StringReader for Parsing
>
>
> Key: AVRO-2348
> URL: https://issues.apache.org/jira/browse/AVRO-2348
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Affects Versions: 1.9.0
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> {code}
> public JsonParser createParser(String content)
> throws IOException,
>JsonParseException
> Method for constructing parser for parsing contents of given String.
> {code}
> https://fasterxml.github.io/jackson-core/javadoc/2.3.0/com/fasterxml/jackson/core/JsonFactory.html#createParser(java.lang.String)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2341) Simplify ByteArrayByteSource Min Buffer Size
[ https://issues.apache.org/jira/browse/AVRO-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789882#comment-16789882 ] ASF subversion and git services commented on AVRO-2341: --- Commit 8c3c590d7bfa6d486f5741c5e2f5214a1f2436c1 in avro's branch refs/heads/master from Beluga Behr [ https://gitbox.apache.org/repos/asf?p=avro.git;h=8c3c590 ] AVRO-2341: Simplify ByteArrayByteSource Min Buffer Size > Simplify ByteArrayByteSource Min Buffer Size > > > Key: AVRO-2341 > URL: https://issues.apache.org/jira/browse/AVRO-2341 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Trivial > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2340) Use JDK compareTo and hashcode Methods
[
https://issues.apache.org/jira/browse/AVRO-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789881#comment-16789881
]
ASF subversion and git services commented on AVRO-2340:
---
Commit ef8349ffd6da5c6f4693ac46548c96e22eeb7cd7 in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=ef8349f ]
AVRO-2340: Use JDK compareTo and hashcode Methods
> Use JDK compareTo and hashcode Methods
> --
>
> Key: AVRO-2340
> URL: https://issues.apache.org/jira/browse/AVRO-2340
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> There are a few different ways that {{hashCode()}} and {{compare}} are
> implemented. Just use the JDK methods.
> I set a breakpoint and ran the 'perf' program, but it did not hit, so these
> methods are not on the critical paths. Best to do this work in a consistent
> behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2347) Use Java8 Map API for SpecificData
[ https://issues.apache.org/jira/browse/AVRO-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789883#comment-16789883 ] ASF subversion and git services commented on AVRO-2347: --- Commit 6d0698705299e67e2f463216b95bf962ab6f11a2 in avro's branch refs/heads/master from Beluga Behr [ https://gitbox.apache.org/repos/asf?p=avro.git;h=6d06987 ] AVRO-2347: Use Java8 Map API for SpecificData > Use Java8 Map API for SpecificData > -- > > Key: AVRO-2347 > URL: https://issues.apache.org/jira/browse/AVRO-2347 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2333) Remove commons-logging dependency
[
https://issues.apache.org/jira/browse/AVRO-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787156#comment-16787156
]
ASF subversion and git services commented on AVRO-2333:
---
Commit f715c974b9f7eb4d4809c1e0f04b7b4ff12837b3 in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=f715c97 ]
AVRO-2333: Remove commons-logging dependency
> Remove commons-logging dependency
> -
>
> Key: AVRO-2333
> URL: https://issues.apache.org/jira/browse/AVRO-2333
> Project: Apache Avro
> Issue Type: Improvement
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>
> Remove dependency on {{commons-logging}}. Now using {{SLF4J}} + {{Log4J}}.
> https://github.com/apache/avro/blob/master/lang/java/tools/pom.xml#L221-L225
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2331) Remove commons-codec dependency
[ https://issues.apache.org/jira/browse/AVRO-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787160#comment-16787160 ] ASF subversion and git services commented on AVRO-2331: --- Commit e16f30abf6d1b7befcc36f49a5bc39166a75f814 in avro's branch refs/heads/master from Beluga Behr [ https://gitbox.apache.org/repos/asf?p=avro.git;h=e16f30a ] AVRO-2331: Use JDK Base64 > Remove commons-codec dependency > --- > > Key: AVRO-2331 > URL: https://issues.apache.org/jira/browse/AVRO-2331 > Project: Apache Avro > Issue Type: Improvement >Reporter: David Mollitor >Assignee: David Mollitor >Priority: Minor > Fix For: 1.9.0 > > > Use [JDK > Base64|https://docs.oracle.com/javase/8/docs/api/java/util/Base64.html] > instead of Apache Codec. > Will allow for removal of Apache Commons Codec dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2302) Invalid namespace importing Avro files generated from Protobuf
[
https://issues.apache.org/jira/browse/AVRO-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763072#comment-16763072
]
ASF subversion and git services commented on AVRO-2302:
---
Commit e0ab6bd54ab632569782a577b7e9a1d419e08845 in avro's branch
refs/heads/master from Pedro Carneiro
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e0ab6bd ]
AVRO-2302 Fix invalid namespace on BigQuery import
This change fixes an issue when importing Avro files into BigQuery, when
such files have been generated using `ProtobufData`. The schema
namespace may end in a dollar sign, if using nested classes.
The correction piggybacks on the fix provided for AVRO-2143 (#283). In
it, `SpecificData` will attempt to load a class joining the namespace
and the name with a dot, and if that fails, it tries again with a dollar
sign.
The same behaviour is hereby reused for `ProtobufData`.
> Invalid namespace importing Avro files generated from Protobuf
> --
>
> Key: AVRO-2302
> URL: https://issues.apache.org/jira/browse/AVRO-2302
> Project: Apache Avro
> Issue Type: Bug
>Affects Versions: 1.8.2
>Reporter: Pedro Carneiro
>Priority: Major
> Fix For: 1.9.0
>
>
> An error occurs when importing Avro files into BigQuery.
> The files were generated using a ProtobufData schema.
> The error shown is similar to:
> {code}
> BigQuery error in load operation: Error processing job
> '': Error while reading data, error message: The
> Apache Avro library failed to parse the header with the following error:
> Invalid namespace:
> some.package.SomeClassProto$
> {code}
> When using a modified version of the ProtobufData class, that yields a
> namespace like
> {noformat}
> some.package.SomeClassProto
> {noformat}
> (without the dollar), the import worked without errors.
> Potentially related to AVRO-2143?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2106) Revisit dependencies on Jetty, servlet-api, and Netty
[ https://issues.apache.org/jira/browse/AVRO-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763063#comment-16763063 ] ASF subversion and git services commented on AVRO-2106: --- Commit ac95febf82b15ffa564cac1d92475cdf6efed9f6 in avro's branch refs/heads/master from Daniel Kulp [ https://gitbox.apache.org/repos/asf?p=avro.git;h=ac95feb ] [AVRO-2106] Split netty/jetty out of avro-ipc > Revisit dependencies on Jetty, servlet-api, and Netty > - > > Key: AVRO-2106 > URL: https://issues.apache.org/jira/browse/AVRO-2106 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.7.2, 1.8.0 >Reporter: Nandor Kollar >Priority: Major > > The compile scoped dependency on jetty servlet-api in the IPC pom file can be > problematic if using Avro in a webapp environment. Would it be possible to > make this dependency either optional or provided? Or maybe Avro modularize > into sub-modules in such a way that desired features can be assembled > piecemeal? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2143) ReflectData should determine inner class names in a different way.
[
https://issues.apache.org/jira/browse/AVRO-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763073#comment-16763073
]
ASF subversion and git services commented on AVRO-2143:
---
Commit e0ab6bd54ab632569782a577b7e9a1d419e08845 in avro's branch
refs/heads/master from Pedro Carneiro
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e0ab6bd ]
AVRO-2302 Fix invalid namespace on BigQuery import
This change fixes an issue when importing Avro files into BigQuery, when
such files have been generated using `ProtobufData`. The schema
namespace may end in a dollar sign, if using nested classes.
The correction piggybacks on the fix provided for AVRO-2143 (#283). In
it, `SpecificData` will attempt to load a class joining the namespace
and the name with a dot, and if that fails, it tries again with a dollar
sign.
The same behaviour is hereby reused for `ProtobufData`.
> ReflectData should determine inner class names in a different way.
> --
>
> Key: AVRO-2143
> URL: https://issues.apache.org/jira/browse/AVRO-2143
> Project: Apache Avro
> Issue Type: Improvement
>Affects Versions: 1.7.7
>Reporter: Miguel
>Assignee: Doug Cutting
>Priority: Major
> Fix For: 1.9.0
>
>
> I used ReflectData to generate schemas containing inner classes. These
> classes were named automatically by ReflectData with dollar ('$'), with, for
> example com.company.avro.House$Type. Nevertheless @AvroAlias does not support
> aliases containing '$' in names. In particulr, it fails in validateName in
> Schema core class. The failure is correct given that AVRO name specs does
> notinclude the '$' symbol.
> I suppose that ReflectData should, for example, generate inner class names in
> a different way, such as replacing '$' by dots ('.'), or it should fail.
> And a detail: Although I cannot add aliases with '$', I can still encode and
> decode such objects and inner classes using that schema.
> I think that it newer versions it is also happening.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2311) Remove findbugs annotations dependency
[ https://issues.apache.org/jira/browse/AVRO-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762086#comment-16762086 ] ASF subversion and git services commented on AVRO-2311: --- Commit c1faf3b56504de9e366000ceeb4a65ef9567f8d2 in avro's branch refs/heads/master from Ismaël Mejía [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c1faf3b ] AVRO-2311: Remove findbugs annotations dependency > Remove findbugs annotations dependency > -- > > Key: AVRO-2311 > URL: https://issues.apache.org/jira/browse/AVRO-2311 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: Ismaël Mejía >Assignee: Ismaël Mejía >Priority: Blocker > > Avro grpc still uses findbugs "com.google.code.findbugs" through a dependency > that leaks findbugs into the classpath. This dependency is LGPL licensed and > forbidden by the ASF -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2317) Update hamcrest-library to version 2.1 and remove hamcrest-all
[ https://issues.apache.org/jira/browse/AVRO-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762170#comment-16762170 ] ASF subversion and git services commented on AVRO-2317: --- Commit 1f88d9ede26daad76f1343ca300f16cc824ef712 in avro's branch refs/heads/master from Ismaël Mejía [ https://gitbox.apache.org/repos/asf?p=avro.git;h=1f88d9e ] AVRO-2317 Update hamcrest-library to version 2.1 and remove hamcrest-all (#447) > Update hamcrest-library to version 2.1 and remove hamcrest-all > -- > > Key: AVRO-2317 > URL: https://issues.apache.org/jira/browse/AVRO-2317 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: Ismaël Mejía >Assignee: Ismaël Mejía >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2316) Update ant to version 1.10.5
[ https://issues.apache.org/jira/browse/AVRO-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762171#comment-16762171 ] ASF subversion and git services commented on AVRO-2316: --- Commit c4f880eb00b07a4cc6fbab24ae9f5c9d970d269b in avro's branch refs/heads/master from Ismaël Mejía [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c4f880e ] AVRO-2316: Update ant to version 1.10.5 (#446) > Update ant to version 1.10.5 > > > Key: AVRO-2316 > URL: https://issues.apache.org/jira/browse/AVRO-2316 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: Ismaël Mejía >Assignee: Ismaël Mejía >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2315) Update zstd-jni to version 1.3.8-3
[ https://issues.apache.org/jira/browse/AVRO-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762169#comment-16762169 ] ASF subversion and git services commented on AVRO-2315: --- Commit ba30662a00fe5f883d643c956d7b982a5d4b8751 in avro's branch refs/heads/master from Ismaël Mejía [ https://gitbox.apache.org/repos/asf?p=avro.git;h=ba30662 ] AVRO-2315: Update zstd-jni to version 1.3.8-3 (#445) > Update zstd-jni to version 1.3.8-3 > -- > > Key: AVRO-2315 > URL: https://issues.apache.org/jira/browse/AVRO-2315 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: Ismaël Mejía >Assignee: Ismaël Mejía >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2321) Replace hasattr with getattr
[ https://issues.apache.org/jira/browse/AVRO-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766140#comment-16766140 ] ASF subversion and git services commented on AVRO-2321: --- Commit 2aa4946f42541369b31094538801c2caec251c67 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=2aa4946 ] AVRO-2321: Avoid hasattr in Python 2 (#453) > Replace hasattr with getattr > > > Key: AVRO-2321 > URL: https://issues.apache.org/jira/browse/AVRO-2321 > Project: Apache Avro > Issue Type: Improvement > Components: python >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Michael A. Smith >Priority: Major > Fix For: 1.9.0 > > > Please refer to the blog: https://hynek.me/articles/hasattr/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message
[
https://issues.apache.org/jira/browse/AVRO-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766176#comment-16766176
]
ASF subversion and git services commented on AVRO-1989:
---
Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]
AVRO-1989: Ruby schema validation should use bytesize in error msg (#451)
* AVRO-1989: Ruby schema validation should use bytesize in error msg
* AVRO-1989: Add a test to verify the behaviour
* AVRO-1989: Add a test to verify the behaviour
> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
> Issue Type: Bug
> Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
> + when :fixed
> + if datum.is_a? String
> +message = "expected fixed with size #{expected_schema.size},
> got \"#{datum}\" with size #{datum.size}"
> +result.add_error(path, message) unless datum.bytesize ==
> expected_schema.size
> + else
> +result.add_error(path, "expected fixed with size
> #{expected_schema.size}, got #{actual_value_message(datum)}")
> + end
> {code}
> the message here should use datum.bytesize instead of datum.size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message
[
https://issues.apache.org/jira/browse/AVRO-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766175#comment-16766175
]
ASF subversion and git services commented on AVRO-1989:
---
Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]
AVRO-1989: Ruby schema validation should use bytesize in error msg (#451)
* AVRO-1989: Ruby schema validation should use bytesize in error msg
* AVRO-1989: Add a test to verify the behaviour
* AVRO-1989: Add a test to verify the behaviour
> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
> Issue Type: Bug
> Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
> + when :fixed
> + if datum.is_a? String
> +message = "expected fixed with size #{expected_schema.size},
> got \"#{datum}\" with size #{datum.size}"
> +result.add_error(path, message) unless datum.bytesize ==
> expected_schema.size
> + else
> +result.add_error(path, "expected fixed with size
> #{expected_schema.size}, got #{actual_value_message(datum)}")
> + end
> {code}
> the message here should use datum.bytesize instead of datum.size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message
[
https://issues.apache.org/jira/browse/AVRO-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766177#comment-16766177
]
ASF subversion and git services commented on AVRO-1989:
---
Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]
AVRO-1989: Ruby schema validation should use bytesize in error msg (#451)
* AVRO-1989: Ruby schema validation should use bytesize in error msg
* AVRO-1989: Add a test to verify the behaviour
* AVRO-1989: Add a test to verify the behaviour
> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
> Issue Type: Bug
> Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
> + when :fixed
> + if datum.is_a? String
> +message = "expected fixed with size #{expected_schema.size},
> got \"#{datum}\" with size #{datum.size}"
> +result.add_error(path, message) unless datum.bytesize ==
> expected_schema.size
> + else
> +result.add_error(path, "expected fixed with size
> #{expected_schema.size}, got #{actual_value_message(datum)}")
> + end
> {code}
> the message here should use datum.bytesize instead of datum.size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1816) Add support for logical decimal type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765970#comment-16765970 ] ASF subversion and git services commented on AVRO-1816: --- Commit e44acccf69a0b40f12f904144df67b345a5138ad in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=e44accc ] [AVRO-1816] Add support for logical decimal type for python AVRO Remove empty file > Add support for logical decimal type for python AVRO > > > Key: AVRO-1816 > URL: https://issues.apache.org/jira/browse/AVRO-1816 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Prem Santosh >Assignee: Prem Santosh >Priority: Major > Fix For: 1.9.0 > > > Currently, python Avro does not seem to support a DECIMAL type. > I > [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8] > support for encoding and decoding logical decimal type for python avro. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1816) Add support for logical decimal type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765966#comment-16765966 ] ASF subversion and git services commented on AVRO-1816: --- Commit 114fee5317ca2bb2b09864c66da99e86190faffb in avro's branch refs/heads/master from Prem Santosh [ https://gitbox.apache.org/repos/asf?p=avro.git;h=114fee5 ] [AVRO-1816] Add support for logical decimal type for python AVRO (#82) * Added decimal logical type support for python avro * Fixed issues with encoder and decoder [variable length] * Revamped logical schema design * Fixed bug with bytes packed in decimal encoder * Fixed exponent scale > Add support for logical decimal type for python AVRO > > > Key: AVRO-1816 > URL: https://issues.apache.org/jira/browse/AVRO-1816 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Prem Santosh >Assignee: Prem Santosh >Priority: Major > Fix For: 1.9.0 > > > Currently, python Avro does not seem to support a DECIMAL type. > I > [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8] > support for encoding and decoding logical decimal type for python avro. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2319) Bump grpc.version from 1.17.1 to 1.18.0
[ https://issues.apache.org/jira/browse/AVRO-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762421#comment-16762421 ] ASF subversion and git services commented on AVRO-2319: --- Commit 95cd62055fd24910d8873b4d8ab209eec198239e in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=95cd620 ] AVRO-2319: Bump grpc.version from 1.17.1 to 1.18.0 (#449) > Bump grpc.version from 1.17.1 to 1.18.0 > --- > > Key: AVRO-2319 > URL: https://issues.apache.org/jira/browse/AVRO-2319 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2314) Bump protobuf to 3.6.1
[ https://issues.apache.org/jira/browse/AVRO-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761582#comment-16761582 ] ASF subversion and git services commented on AVRO-2314: --- Commit 6b5963d64e8c339c5266b6b14c707ea9cb10f8fa in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=6b5963d ] [AVRO-2314] Bump protobuf to 3.6.1 There is an outstanding CVE on 3.4.0+ https://ossindex.sonatype.org/vuln/d47d20ab-eb2a-4cfd-8064-bbf6283649cb > Bump protobuf to 3.6.1 > -- > > Key: AVRO-2314 > URL: https://issues.apache.org/jira/browse/AVRO-2314 > Project: Apache Avro > Issue Type: Improvement >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > > There is an outstanding CVE: > https://ossindex.sonatype.org/vuln/d47d20ab-eb2a-4cfd-8064-bbf6283649cb -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2313) Bump libthrift from 0.11.0 to 0.12.0
[ https://issues.apache.org/jira/browse/AVRO-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761585#comment-16761585 ] ASF subversion and git services commented on AVRO-2313: --- Commit f4425913940a11870bc8fda602d29217cff53af0 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=f442591 ] AVRO-2313: Bump libthrift from 0.11.0 to 0.12.0 > Bump libthrift from 0.11.0 to 0.12.0 > > > Key: AVRO-2313 > URL: https://issues.apache.org/jira/browse/AVRO-2313 > Project: Apache Avro > Issue Type: Improvement >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > > To keep up with Parquet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2323) Bump maven-jar-plugin to 3.1.1
[ https://issues.apache.org/jira/browse/AVRO-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772389#comment-16772389 ] ASF subversion and git services commented on AVRO-2323: --- Commit ff11298e397977b820bdeed612e61dab17f118b9 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=ff11298 ] [AVRO-2323] Bump maven-jar-plugin to 3.1.1 > Bump maven-jar-plugin to 3.1.1 > -- > > Key: AVRO-2323 > URL: https://issues.apache.org/jira/browse/AVRO-2323 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2310) GenericData Array Add Use JDK Copy Facilities
[
https://issues.apache.org/jira/browse/AVRO-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754788#comment-16754788
]
ASF subversion and git services commented on AVRO-2310:
---
Commit 0de805575f41c2d7deff9fcbe408e51606f88269 in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=0de8055 ]
AVRO-2310: GenericData Array Add Use JDK Copy Facilities
> GenericData Array Add Use JDK Copy Facilities
> -
>
> Key: AVRO-2310
> URL: https://issues.apache.org/jira/browse/AVRO-2310
> Project: Apache Avro
> Issue Type: Improvement
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Trivial
>
> Use {{Arrays.copyOf}} to increase readability
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2309) Conversions.java - Use JDK Array Manipulations
[
https://issues.apache.org/jira/browse/AVRO-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754781#comment-16754781
]
ASF subversion and git services commented on AVRO-2309:
---
Commit bcc79e90540f55dc9e1dd34da7a1f5901ee22b2a in avro's branch
refs/heads/master from Beluga Behr
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=bcc79e9 ]
AVRO-2309: Conversions.java - Use JDK Array Manipulations
> Conversions.java - Use JDK Array Manipulations
> --
>
> Key: AVRO-2309
> URL: https://issues.apache.org/jira/browse/AVRO-2309
> Project: Apache Avro
> Issue Type: Improvement
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Trivial
>
> {code:java|title=Conversions.java}
> for (int i = 0; i < bytes.length; i += 1) {
> if (i < offset) {
> bytes[i] = fillByte;
> } else {
> bytes[i] = unscaled[i - offset];
> }
> }
> {code}
> Improve readability with {{Arrays.fill}} method to fill the first {{offset}}
> bytes and then copy over the remaining.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1381) Publish C# artifacts to NuGet
[ https://issues.apache.org/jira/browse/AVRO-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759701#comment-16759701 ] ASF subversion and git services commented on AVRO-1381: --- Commit e03f9d44f5fd0908f9402340164972415c0d in avro's branch refs/heads/master from Brian Lachniet [ https://gitbox.apache.org/repos/asf?p=avro.git;h=e03f9d4 ] AVRO-1381: Generate NuGet package for main Avro library (#428) > Publish C# artifacts to NuGet > - > > Key: AVRO-1381 > URL: https://issues.apache.org/jira/browse/AVRO-1381 > Project: Apache Avro > Issue Type: New Feature > Components: csharp >Affects Versions: 1.7.5 >Reporter: Mark Lamley >Assignee: Brian Lachniet >Priority: Major > Fix For: 1.9.0 > > > Currently referencing Avro requires manually downloading, compiling and > referencing the compiled library. It would be nice to simply reference the > compiled library from http://www.nuget.org/ instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2373) Remove Empty Package 'ipc'
[ https://issues.apache.org/jira/browse/AVRO-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813685#comment-16813685 ] ASF subversion and git services commented on AVRO-2373: --- Commit 350a3f0beb779c783daecf6f1b1de58e53e5f3fa in avro's branch refs/heads/master from Daniel Kulp [ https://gitbox.apache.org/repos/asf?p=avro.git;h=350a3f0 ] [AVRO-2373] Move package.html for ipc from avro to ipc jar > Remove Empty Package 'ipc' > -- > > Key: AVRO-2373 > URL: https://issues.apache.org/jira/browse/AVRO-2373 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.0 >Reporter: David Mollitor >Priority: Minor > Fix For: 1.9.0 > > > https://github.com/apache/avro/tree/master/lang/java/avro/src/main/java/org/apache/avro/ipc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2374) Remove hardcoded Jackson versions from tests
[ https://issues.apache.org/jira/browse/AVRO-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814153#comment-16814153 ] ASF subversion and git services commented on AVRO-2374: --- Commit ee6386f44a288f20cf2df5933fd29b4ab54f9e55 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=ee6386f ] [AVRO-2374] Remove hardcodede Jackson versions > Remove hardcoded Jackson versions from tests > > > Key: AVRO-2374 > URL: https://issues.apache.org/jira/browse/AVRO-2374 > Project: Apache Avro > Issue Type: Improvement >Affects Versions: 1.8.2 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2394) commit-msg Expects CHANGES.txt
[
https://issues.apache.org/jira/browse/AVRO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842042#comment-16842042
]
ASF subversion and git services commented on AVRO-2394:
---
Commit d2d26f9ef9f498063484a001d64617e993bce751 in avro's branch
refs/heads/master from Brian Lachniet
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=d2d26f9 ]
AVRO-2394: Remove CHANGES.txt check from commit-msg hook (#519)
> commit-msg Expects CHANGES.txt
> --
>
> Key: AVRO-2394
> URL: https://issues.apache.org/jira/browse/AVRO-2394
> Project: Apache Avro
> Issue Type: Bug
> Components: misc
>Reporter: Brian Lachniet
>Assignee: Brian Lachniet
>Priority: Minor
>
> The {{commit-msg}} client-side git hook looks for the issue ID in a
> {{CHANGES.txt}} file, which was removed in AVRO-2173. Remove this check from
> the {{commit-msg}} hook.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2405) Make Travis green again
[ https://issues.apache.org/jira/browse/AVRO-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848901#comment-16848901 ] ASF subversion and git services commented on AVRO-2405: --- Commit 48e518f5e7ad0e1bd456537e6ae0e640d5a46ef2 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=48e518f ] AVRO-2405 Make Travis green again (#527) * AVRO-2405 Make Travis green again * Disable Forest for JDK11 * Remove Apache Forrest from the Dockerfile * Remove Forrest references > Make Travis green again > --- > > Key: AVRO-2405 > URL: https://issues.apache.org/jira/browse/AVRO-2405 > Project: Apache Avro > Issue Type: Improvement > Components: build >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2405) Make Travis green again
[ https://issues.apache.org/jira/browse/AVRO-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848900#comment-16848900 ] ASF subversion and git services commented on AVRO-2405: --- Commit 48e518f5e7ad0e1bd456537e6ae0e640d5a46ef2 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=48e518f ] AVRO-2405 Make Travis green again (#527) * AVRO-2405 Make Travis green again * Disable Forest for JDK11 * Remove Apache Forrest from the Dockerfile * Remove Forrest references > Make Travis green again > --- > > Key: AVRO-2405 > URL: https://issues.apache.org/jira/browse/AVRO-2405 > Project: Apache Avro > Issue Type: Improvement > Components: build >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2408) Make Forrest work again in the Docker image for local development
[ https://issues.apache.org/jira/browse/AVRO-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849438#comment-16849438 ] ASF subversion and git services commented on AVRO-2408: --- Commit 41759e6c92d1d2578db0e878ead822a7f1abef99 in avro's branch refs/heads/master from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=41759e6 ] AVRO-2408: Create local dev environment with Apache Forrest (#530) > Make Forrest work again in the Docker image for local development > - > > Key: AVRO-2408 > URL: https://issues.apache.org/jira/browse/AVRO-2408 > Project: Apache Avro > Issue Type: Bug >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2104) Schema normalisation and fingerprint support for Python 3
[ https://issues.apache.org/jira/browse/AVRO-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854663#comment-16854663 ] ASF subversion and git services commented on AVRO-2104: --- Commit d3011c98d746e211c06a0308f759ef4d8312566c in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d3011c9 ] AVRO-2104: Schema normalization and fingerprinting for Python 3 (#536) * AVRO-2104: Schema normalization and fingerprinting for Python 3. An implementation of schema normalization and fingerprinting for Python 3. The code is a fairly literal translation of the Java code and is entirely additional to the existing code, except for one small change in the way schema.Name is implemented to improve compatibility with the Java version. The new implementation is covered by 138 unit tests which have been automatically generated by a script (not provided) which executed the Java Avro normalization and fingerprinting code to provide expected values for the Python implementation to reproduce. * AVRO-2104: Include License Header Closes #258 Closes #536 > Schema normalisation and fingerprint support for Python 3 > - > > Key: AVRO-2104 > URL: https://issues.apache.org/jira/browse/AVRO-2104 > Project: Apache Avro > Issue Type: Improvement > Components: python >Reporter: Robert Smallshire >Priority: Major > > The existing Python 3 implementation supports neither schema canonicalisation > to parsing normal form, nor fingerprinting of normalised schemas. This limits > the interoperability of Python 3 Avro systems with other Avro implementations > including the Java and Ruby versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2104) Schema normalisation and fingerprint support for Python 3
[ https://issues.apache.org/jira/browse/AVRO-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854661#comment-16854661 ] ASF subversion and git services commented on AVRO-2104: --- Commit d3011c98d746e211c06a0308f759ef4d8312566c in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d3011c9 ] AVRO-2104: Schema normalization and fingerprinting for Python 3 (#536) * AVRO-2104: Schema normalization and fingerprinting for Python 3. An implementation of schema normalization and fingerprinting for Python 3. The code is a fairly literal translation of the Java code and is entirely additional to the existing code, except for one small change in the way schema.Name is implemented to improve compatibility with the Java version. The new implementation is covered by 138 unit tests which have been automatically generated by a script (not provided) which executed the Java Avro normalization and fingerprinting code to provide expected values for the Python implementation to reproduce. * AVRO-2104: Include License Header Closes #258 Closes #536 > Schema normalisation and fingerprint support for Python 3 > - > > Key: AVRO-2104 > URL: https://issues.apache.org/jira/browse/AVRO-2104 > Project: Apache Avro > Issue Type: Improvement > Components: python >Reporter: Robert Smallshire >Priority: Major > > The existing Python 3 implementation supports neither schema canonicalisation > to parsing normal form, nor fingerprinting of normalised schemas. This limits > the interoperability of Python 3 Avro systems with other Avro implementations > including the Java and Ruby versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2104) Schema normalisation and fingerprint support for Python 3
[ https://issues.apache.org/jira/browse/AVRO-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854662#comment-16854662 ] ASF subversion and git services commented on AVRO-2104: --- Commit d3011c98d746e211c06a0308f759ef4d8312566c in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d3011c9 ] AVRO-2104: Schema normalization and fingerprinting for Python 3 (#536) * AVRO-2104: Schema normalization and fingerprinting for Python 3. An implementation of schema normalization and fingerprinting for Python 3. The code is a fairly literal translation of the Java code and is entirely additional to the existing code, except for one small change in the way schema.Name is implemented to improve compatibility with the Java version. The new implementation is covered by 138 unit tests which have been automatically generated by a script (not provided) which executed the Java Avro normalization and fingerprinting code to provide expected values for the Python implementation to reproduce. * AVRO-2104: Include License Header Closes #258 Closes #536 > Schema normalisation and fingerprint support for Python 3 > - > > Key: AVRO-2104 > URL: https://issues.apache.org/jira/browse/AVRO-2104 > Project: Apache Avro > Issue Type: Improvement > Components: python >Reporter: Robert Smallshire >Priority: Major > > The existing Python 3 implementation supports neither schema canonicalisation > to parsing normal form, nor fingerprinting of normalised schemas. This limits > the interoperability of Python 3 Avro systems with other Avro implementations > including the Java and Ruby versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2388) Drop Python 3.4 from Trove Classifiers and Setup in 1.9
[ https://issues.apache.org/jira/browse/AVRO-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854584#comment-16854584 ] ASF subversion and git services commented on AVRO-2388: --- Commit 9cfc27ae51bece7e84dcf01263ce67175d67ad86 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=9cfc27a ] AVRO-2388: Drop Python 3.4 Support (#513) > Drop Python 3.4 from Trove Classifiers and Setup in 1.9 > --- > > Key: AVRO-2388 > URL: https://issues.apache.org/jira/browse/AVRO-2388 > Project: Apache Avro > Issue Type: Task >Affects Versions: 1.9.0 >Reporter: Michael A. Smith >Assignee: Michael A. Smith >Priority: Major > Fix For: 1.10.0 > > > [~Fokko] Is it too late for me to open a small PR just removing the notes for > python 3.4 support from the pending 1.9 release? It wouldn't be an actual > code change. > > The vote is still technically open, but I'll be surprised if there's any > contention. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2391) Simplify and modernize setup.py
[ https://issues.apache.org/jira/browse/AVRO-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853259#comment-16853259 ] ASF subversion and git services commented on AVRO-2391: --- Commit f33e36f70f5f149b38b9056273f584184591c23f in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=f33e36f ] AVRO-2391 Refactor Py3 Setup (#514) The main purpose of this change is to simplify and modernize the setup code without really changing its behavior. The main change is that I moved most of the setup code into the declarative setup.cfg, where I hope it is somewhat clearer. I also fleshed out the setup.py commands so that the build.sh and setup.py have parity -- that is, the build.sh is entirely implemented using setup.py. > Simplify and modernize setup.py > --- > > Key: AVRO-2391 > URL: https://issues.apache.org/jira/browse/AVRO-2391 > Project: Apache Avro > Issue Type: Task > Components: python >Affects Versions: 1.9.0 >Reporter: Michael A. Smith >Assignee: Michael A. Smith >Priority: Major > Fix For: 1.10.0 > > > The main purpose of this change is to simplify and modernize the setup code > without really changing its behavior. > * The main change is that I moved most of the setup code into the > declarative setup.cfg, where I hope it is somewhat clearer. > * I also fleshed out the setup.py commands so that the build.sh and setup.py > have parity -- that is, the build.sh is entirely implemented using setup.py. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2392) Logical type time-micros and timestamp-micros generate as long types.
[
https://issues.apache.org/jira/browse/AVRO-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853270#comment-16853270
]
ASF subversion and git services commented on AVRO-2392:
---
Commit 63d51487daad17458a0edcec1c65ae76619de76e in avro's branch
refs/heads/branch-1.9 from Shameera Yodage
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=63d5148 ]
AVRO-2392: enble joda micros logical types supports (#517)
> Logical type time-micros and timestamp-micros generate as long types.
> -
>
> Key: AVRO-2392
> URL: https://issues.apache.org/jira/browse/AVRO-2392
> Project: Apache Avro
> Issue Type: Bug
> Components: java, logical types
>Affects Versions: 1.8.2
>Reporter: Shameera Rathnayaka
>Priority: Major
> Fix For: 1.9.1
>
>
> With Java code gen *time-micros* and *timestamp-micros* logical types
> generate as long typed value with Joda.
> Following will generate AvroLogicalTypeExample class, which has both
> `*timeMicrosField*` and '*timestampMicrosField*` values as *long* typed
> instance variables.
> {code:java}
> {
> "type": "record",
> "namespace": "com.shameera.test",
> "name": "AvroLogicalTypeExample",
> "fields": [
> {"name": "timeMicrosField",
> "type": {
> "type": "long",
> "logicalType": "time-micros"
> }
> },
> {"name": "timestampMicrosField",
> "type": {
> "type": "long",
> "logicalType": "timestamp-micros"
> }
> }
> ]
> }
> {code}
> https://issues.apache.org/jira/browse/AVRO-2123 partially address this issue,
> that is why I created a separate issue to track only the issue with micros
> times.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1928) Python double/float encoding implementation should use built-in struct support for little endian
[
https://issues.apache.org/jira/browse/AVRO-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853320#comment-16853320
]
ASF subversion and git services commented on AVRO-1928:
---
Commit b990042604b8bf83db3a137de0f54d726c1af9f0 in avro's branch
refs/heads/master from Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=b990042 ]
AVRO-1928: Simplify Python float/double encoding (#528)
Switch to using built-in little endian support in the struct
module, instead of explicit bit manipulation.
> Python double/float encoding implementation should use built-in struct
> support for little endian
>
>
> Key: AVRO-1928
> URL: https://issues.apache.org/jira/browse/AVRO-1928
> Project: Apache Avro
> Issue Type: Improvement
> Components: python
>Affects Versions: 1.8.1, 1.8.2, 1.8.3
>Reporter: Shalabh Chaturvedi
>Priority: Minor
>
> The encoding and decoding of double and float types in Python uses
> unnecessary bit operations and packing/unpacking. Python's {{struct}} module
> supports little-endian encoding and could be used directly, instead of using
> the big-endian and then bit-fiddling to reverse the endianness.
> This could have a big impact of encoding/decoding speed of large buffers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2405) Make Travis green again
[ https://issues.apache.org/jira/browse/AVRO-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853431#comment-16853431 ] ASF subversion and git services commented on AVRO-2405: --- Commit c069deac4f9f2b432bf1d5d2ff4ca55d8545ae41 in avro's branch refs/heads/branch-1.9 from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c069dea ] AVRO-2405 Make Travis green again (#527) * AVRO-2405 Make Travis green again * Disable Forest for JDK11 * Remove Apache Forrest from the Dockerfile * Remove Forrest references > Make Travis green again > --- > > Key: AVRO-2405 > URL: https://issues.apache.org/jira/browse/AVRO-2405 > Project: Apache Avro > Issue Type: Improvement > Components: build >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2405) Make Travis green again
[ https://issues.apache.org/jira/browse/AVRO-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853432#comment-16853432 ] ASF subversion and git services commented on AVRO-2405: --- Commit c069deac4f9f2b432bf1d5d2ff4ca55d8545ae41 in avro's branch refs/heads/branch-1.9 from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c069dea ] AVRO-2405 Make Travis green again (#527) * AVRO-2405 Make Travis green again * Disable Forest for JDK11 * Remove Apache Forrest from the Dockerfile * Remove Forrest references > Make Travis green again > --- > > Key: AVRO-2405 > URL: https://issues.apache.org/jira/browse/AVRO-2405 > Project: Apache Avro > Issue Type: Improvement > Components: build >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2409) Add Github PR template
[ https://issues.apache.org/jira/browse/AVRO-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855040#comment-16855040 ] ASF subversion and git services commented on AVRO-2409: --- Commit d88900ce2eebd2200a9f1a6912719854fba7a102 in avro's branch refs/heads/master from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d88900c ] AVRO-2409: Add Github template (#531) > Add Github PR template > -- > > Key: AVRO-2409 > URL: https://issues.apache.org/jira/browse/AVRO-2409 > Project: Apache Avro > Issue Type: Improvement > Components: misc >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2392) Logical type time-micros and timestamp-micros generate as long types.
[
https://issues.apache.org/jira/browse/AVRO-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855335#comment-16855335
]
ASF subversion and git services commented on AVRO-2392:
---
Commit f23eabb42f315b0db9135b075434b8a88680659c in avro's branch
refs/heads/branch-1.8 from Shameera Yodage
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=f23eabb ]
AVRO-2392: Enable Joda micros logical types supports (#533)
> Logical type time-micros and timestamp-micros generate as long types.
> -
>
> Key: AVRO-2392
> URL: https://issues.apache.org/jira/browse/AVRO-2392
> Project: Apache Avro
> Issue Type: Bug
> Components: java, logical types
>Affects Versions: 1.8.2
>Reporter: Shameera Rathnayaka
>Assignee: Shameera Rathnayaka
>Priority: Major
> Fix For: 1.9.1
>
>
> With Java code gen *time-micros* and *timestamp-micros* logical types
> generate as long typed value with Joda.
> Following will generate AvroLogicalTypeExample class, which has both
> `*timeMicrosField*` and '*timestampMicrosField*` values as *long* typed
> instance variables.
> {code:java}
> {
> "type": "record",
> "namespace": "com.shameera.test",
> "name": "AvroLogicalTypeExample",
> "fields": [
> {"name": "timeMicrosField",
> "type": {
> "type": "long",
> "logicalType": "time-micros"
> }
> },
> {"name": "timestampMicrosField",
> "type": {
> "type": "long",
> "logicalType": "timestamp-micros"
> }
> }
> ]
> }
> {code}
> https://issues.apache.org/jira/browse/AVRO-2123 partially address this issue,
> that is why I created a separate issue to track only the issue with micros
> times.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2421) Allow multiple @AvroAlias annotations on java classes and their fields
[ https://issues.apache.org/jira/browse/AVRO-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866990#comment-16866990 ] ASF subversion and git services commented on AVRO-2421: --- Commit d8d73c8ea74268cd6d98d5ea9f83774d371ffed6 in avro's branch refs/heads/master from baunz [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d8d73c8 ] AVRO-2421 Allow multiple @AvroAliases annotations on classes and fields (#544) > Allow multiple @AvroAlias annotations on java classes and their fields > -- > > Key: AVRO-2421 > URL: https://issues.apache.org/jira/browse/AVRO-2421 > Project: Apache Avro > Issue Type: Improvement >Reporter: Johannes Schulte >Priority: Minor > > The avro schema specification allows defining multiple aliases for fields and > records and this can be useful especially when using java classes to define > the schema (refactoring & namespace/package changes). > With the introduction of @Repeatable in java 1.8 there exists an easy way to > expose this flexibility in the Reflect-based world. This patch enables > defining multiple @AvroAlias annotation on both fields and classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2436) Add snappy packages for python2/3 to Dockerfile
[
https://issues.apache.org/jira/browse/AVRO-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870357#comment-16870357
]
ASF subversion and git services commented on AVRO-2436:
---
Commit 42ef522cd6ad38487b09ebc9933e4e312c1beece in avro's branch
refs/heads/master from Kengo Seki
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=42ef522 ]
AVRO-2436: Add snappy packages for python2/3 to Dockerfile (#551)
> Add snappy packages for python2/3 to Dockerfile
> ---
>
> Key: AVRO-2436
> URL: https://issues.apache.org/jira/browse/AVRO-2436
> Project: Apache Avro
> Issue Type: Improvement
> Components: build, docker
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
>
> I ran {{./build.sh docker-test}} and found the following message was shown in
> the test for Python2:
> {code}
> [py-test] Snappy not present, will skip testing it.
> {code}
> Docker image should contain the python-snappy and python3-snappy packages so
> that tests for the snappy codec is not skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2433) Update the dependencies for Perl binding in BUILD.md
[
https://issues.apache.org/jira/browse/AVRO-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870358#comment-16870358
]
ASF subversion and git services commented on AVRO-2433:
---
Commit d7621a0ece3f6d326f018a9ccc0e27213af1e222 in avro's branch
refs/heads/master from Kengo Seki
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=d7621a0 ]
AVRO-2433: Update the dependencies for Perl binding in BUILD.md (#555)
> Update the dependencies for Perl binding in BUILD.md
>
>
> Key: AVRO-2433
> URL: https://issues.apache.org/jira/browse/AVRO-2433
> Project: Apache Avro
> Issue Type: Bug
> Components: doc, perl
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Trivial
>
> I tried to run the tests for Perl bindings, but failed as follows:
> {code}
> $ cd lang/perl
> $ ./build.sh test
> (snip)
> t/01_names.t ... 1/?
> # Failed test 'use Avro::Schema;'
> # at t/01_names.t line 23.
> # Tried to use 'Avro::Schema'.
> # Error: Can't locate Error/Simple.pm in @INC (@INC contains:
> /home/sekikn/repo/avro/lang/perl/inc
> /home/sekikn/repo/avro/lang/perl/blib/lib /home/sekik
> n/repo/avro/lang/perl/blib/arch
> /home/sekikn/perl5/perlbrew/perls/perl-5.14.2/lib/site_perl/5.14.2/x86_64-linux
> /home/sekikn/perl5/perlbrew/perls/perl-5.14.2
> /lib/site_perl/5.14.2
> /home/sekikn/perl5/perlbrew/perls/perl-5.14.2/lib/5.14.2/x86_64-linux
> /home/sekikn/perl5/perlbrew/perls/perl-5.14.2/lib/5.14.2 .) at /h
> ome/sekikn/perl5/perlbrew/perls/perl-5.14.2/lib/5.14.2/parent.pm line 20.
> # BEGIN failed--compilation aborted at
> /home/sekikn/repo/avro/lang/perl/blib/lib/Avro/Schema.pm line 830.
> # Compilation failed in require at (eval 6) line 2.
> # BEGIN failed--compilation aborted at (eval 6) line 2.
> (snip)
> Files=7, Tests=81, 1 wallclock secs ( 0.05 usr 0.02 sys + 0.23 cusr 0.03
> csys = 0.33 CPU)
> Result: FAIL
> Failed 6/7 test programs. 79/81 subtests failed.
> Makefile:793: recipe for target 'test_dynamic' failed
> make: *** [test_dynamic] Error 255
> {code}
> This is due to the lack of the Error::Simple module, [which is not a core
> module for Perl 5.24.1|https://perldoc.perl.org/5.24.1/index-modules-E.html].
> But BUILD.md doesn't refer to this dependency.
> {code}
> The following packages must be installed before Avro can be built:
> (snip)
> - Perl: Perl 5.24.1 or greater, gmake, Module::Install,
>Module::Install::ReadmeFromPod, Module::Install::Repository,
>Math::BigInt, JSON::XS, Try::Tiny, Regexp::Common, Encode,
>IO::String, Object::Tiny, Compress::ZLib, Test::More,
>Test::Exception, Test::Pod
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2440) Allow BinaryMessageDecoder to read (generic) records with the same schema they were written with.
[ https://issues.apache.org/jira/browse/AVRO-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872343#comment-16872343 ] ASF subversion and git services commented on AVRO-2440: --- Commit c3e79364b905c5414e65118ad218850ec76f204c in avro's branch refs/heads/branch-1.9 from Oscar WvH-K [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c3e7936 ] AVRO-2440: Decode messages by their write schema This implements AVRO-2440 by allowing a null value for the readSchema field in the BinaryMessageDecoder. It is interpreted as "no preference", and makes the decoder use the write schema of an incoming buffer as its read schema. (cherry picked from commit 371e22468baa045b5eb5f1e05ee716d3996f520e) > Allow BinaryMessageDecoder to read (generic) records with the same schema > they were written with. > - > > Key: AVRO-2440 > URL: https://issues.apache.org/jira/browse/AVRO-2440 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Oscar Westra van Holthe - Kind >Priority: Minor > Fix For: 1.10.0 > > > At work we have a use case to read Avro records from Kafka, and to write them > to one of several BigQuery tables (based on compatibility). This means that > there is no single schema (with all data) that is compatible with all records > we'll be reading. > In order to allow this, we'd like to be able to use the BinaryMessageDecoder > without any read schema, and have it use the write schema of each record as > the read schema for that record. > -Pull request will follow.- > Pull request submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2440) Allow BinaryMessageDecoder to read (generic) records with the same schema they were written with.
[ https://issues.apache.org/jira/browse/AVRO-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872344#comment-16872344 ] ASF subversion and git services commented on AVRO-2440: --- Commit c3e79364b905c5414e65118ad218850ec76f204c in avro's branch refs/heads/branch-1.9 from Oscar WvH-K [ https://gitbox.apache.org/repos/asf?p=avro.git;h=c3e7936 ] AVRO-2440: Decode messages by their write schema This implements AVRO-2440 by allowing a null value for the readSchema field in the BinaryMessageDecoder. It is interpreted as "no preference", and makes the decoder use the write schema of an incoming buffer as its read schema. (cherry picked from commit 371e22468baa045b5eb5f1e05ee716d3996f520e) > Allow BinaryMessageDecoder to read (generic) records with the same schema > they were written with. > - > > Key: AVRO-2440 > URL: https://issues.apache.org/jira/browse/AVRO-2440 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Oscar Westra van Holthe - Kind >Priority: Minor > Fix For: 1.10.0 > > > At work we have a use case to read Avro records from Kafka, and to write them > to one of several BigQuery tables (based on compatibility). This means that > there is no single schema (with all data) that is compatible with all records > we'll be reading. > In order to allow this, we'd like to be able to use the BinaryMessageDecoder > without any read schema, and have it use the write schema of each record as > the read schema for that record. > -Pull request will follow.- > Pull request submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2440) Allow BinaryMessageDecoder to read (generic) records with the same schema they were written with.
[ https://issues.apache.org/jira/browse/AVRO-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872223#comment-16872223 ] ASF subversion and git services commented on AVRO-2440: --- Commit 371e22468baa045b5eb5f1e05ee716d3996f520e in avro's branch refs/heads/master from Oscar WvH-K [ https://gitbox.apache.org/repos/asf?p=avro.git;h=371e224 ] AVRO-2440: Decode messages by their write schema This implements AVRO-2440 by allowing a null value for the readSchema field in the BinaryMessageDecoder. It is interpreted as "no preference", and makes the decoder use the write schema of an incoming buffer as its read schema. > Allow BinaryMessageDecoder to read (generic) records with the same schema > they were written with. > - > > Key: AVRO-2440 > URL: https://issues.apache.org/jira/browse/AVRO-2440 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Oscar Westra van Holthe - Kind >Priority: Minor > > At work we have a use case to read Avro records from Kafka, and to write them > to one of several BigQuery tables (based on compatibility). This means that > there is no single schema (with all data) that is compatible with all records > we'll be reading. > In order to allow this, we'd like to be able to use the BinaryMessageDecoder > without any read schema, and have it use the write schema of each record as > the read schema for that record. > -Pull request will follow.- > Pull request submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2440) Allow BinaryMessageDecoder to read (generic) records with the same schema they were written with.
[ https://issues.apache.org/jira/browse/AVRO-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1687#comment-1687 ] ASF subversion and git services commented on AVRO-2440: --- Commit 371e22468baa045b5eb5f1e05ee716d3996f520e in avro's branch refs/heads/master from Oscar WvH-K [ https://gitbox.apache.org/repos/asf?p=avro.git;h=371e224 ] AVRO-2440: Decode messages by their write schema This implements AVRO-2440 by allowing a null value for the readSchema field in the BinaryMessageDecoder. It is interpreted as "no preference", and makes the decoder use the write schema of an incoming buffer as its read schema. > Allow BinaryMessageDecoder to read (generic) records with the same schema > they were written with. > - > > Key: AVRO-2440 > URL: https://issues.apache.org/jira/browse/AVRO-2440 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Oscar Westra van Holthe - Kind >Priority: Minor > > At work we have a use case to read Avro records from Kafka, and to write them > to one of several BigQuery tables (based on compatibility). This means that > there is no single schema (with all data) that is compatible with all records > we'll be reading. > In order to allow this, we'd like to be able to use the BinaryMessageDecoder > without any read schema, and have it use the write schema of each record as > the read schema for that record. > -Pull request will follow.- > Pull request submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2298) Specific Avro compiler does not annotate generated Builder class with AvroGenerated
[
https://issues.apache.org/jira/browse/AVRO-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872649#comment-16872649
]
ASF subversion and git services commented on AVRO-2298:
---
Commit 0b7ac89771461dfd610a56a1463532eeac96c892 in avro's branch
refs/heads/master from ScottHarwoodTech
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=0b7ac89 ]
AVRO-2298: Add Avro generated annotation to builder class (#542)
> Specific Avro compiler does not annotate generated Builder class with
> AvroGenerated
> ---
>
> Key: AVRO-2298
> URL: https://issues.apache.org/jira/browse/AVRO-2298
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Affects Versions: 1.8.2
>Reporter: Olli Salonen
>Priority: Major
>
> According to current [AvroGenerated
> documentation|https://avro.apache.org/docs/1.8.2/api/java/org/apache/avro/specific/AvroGenerated.html]
> {quote}All Avro generated classes will be annotated with this annotation.
> {quote}
> However, the nested Builder class that the specific Avro compiler generates
> does not get annotated with AvroGenerated or any user specified
> javaAnnotations. The Builder template is missing annotation generation as can
> be seen in the [template file on
> Github|https://github.com/apache/avro/blob/7ed38d7c7e150987ef8bf035196576fc158e03eb/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/record.vm#L296]
> This has implications for tools relying on Generated annotations, such as
> test coverage tools like JaCoCo, which can ignore the generated
> SpecificRecord class but not the nested SpecificBuilder class as a result.
> [Here is one JaCoCo bug describing the
> issue|https://github.com/jacoco/jacoco/issues/814].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872644#comment-16872644 ] ASF subversion and git services commented on AVRO-2404: --- Commit b83441d5d5a88c3ea6e9f7df9746e3060beb4512 in avro's branch refs/heads/branch-1.9 from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=b83441d ] AVRO 2404: Fix insecure urls. - branch 1.9 (#564) * AVRO-2404: Make jar download secure (cherry picked from commit fb2d025a3d6d4a786283c770ec955f644d133b9a) * AVRO-2404: Make all references to apache.org https (cherry picked from commit 70260919426f89825ca148f5ee815f3b2cf4764d) * AVRO-2404: Make all external links https (cherry picked from commit 2d3b1fe7efd865639663ba785877182e7e038c45) > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > Fix For: 1.10.0 > > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872645#comment-16872645 ] ASF subversion and git services commented on AVRO-2404: --- Commit b83441d5d5a88c3ea6e9f7df9746e3060beb4512 in avro's branch refs/heads/branch-1.9 from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=b83441d ] AVRO 2404: Fix insecure urls. - branch 1.9 (#564) * AVRO-2404: Make jar download secure (cherry picked from commit fb2d025a3d6d4a786283c770ec955f644d133b9a) * AVRO-2404: Make all references to apache.org https (cherry picked from commit 70260919426f89825ca148f5ee815f3b2cf4764d) * AVRO-2404: Make all external links https (cherry picked from commit 2d3b1fe7efd865639663ba785877182e7e038c45) > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > Fix For: 1.10.0 > > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872646#comment-16872646 ] ASF subversion and git services commented on AVRO-2404: --- Commit b83441d5d5a88c3ea6e9f7df9746e3060beb4512 in avro's branch refs/heads/branch-1.9 from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=b83441d ] AVRO 2404: Fix insecure urls. - branch 1.9 (#564) * AVRO-2404: Make jar download secure (cherry picked from commit fb2d025a3d6d4a786283c770ec955f644d133b9a) * AVRO-2404: Make all references to apache.org https (cherry picked from commit 70260919426f89825ca148f5ee815f3b2cf4764d) * AVRO-2404: Make all external links https (cherry picked from commit 2d3b1fe7efd865639663ba785877182e7e038c45) > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > Fix For: 1.10.0 > > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2417) Update Jetty to version 9.4.18.v20190429
[ https://issues.apache.org/jira/browse/AVRO-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862290#comment-16862290 ] ASF subversion and git services commented on AVRO-2417: --- Commit 0b074fea04bad3a95ee0581cab5af195ca96b8c9 in avro's branch refs/heads/branch-1.9 from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=avro.git;h=0b074fe ] AVRO-2417 - Update Jetty > Update Jetty to version 9.4.18.v20190429 > > > Key: AVRO-2417 > URL: https://issues.apache.org/jira/browse/AVRO-2417 > Project: Apache Avro > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: 1.10.0, 1.9.1 > > > We should update Jetty to avoid security advisories: > [https://nvd.nist.gov/vuln/detail/CVE-2019-10241] > [https://nvd.nist.gov/vuln/detail/CVE-2019-10247] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2417) Update Jetty to version 9.4.18.v20190429
[ https://issues.apache.org/jira/browse/AVRO-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862084#comment-16862084 ] ASF subversion and git services commented on AVRO-2417: --- Commit 57b22212351f6a9d0fc2fe7ca737c7f688e37829 in avro's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=avro.git;h=57b2221 ] AVRO-2417 - Update Jetty > Update Jetty to version 9.4.18.v20190429 > > > Key: AVRO-2417 > URL: https://issues.apache.org/jira/browse/AVRO-2417 > Project: Apache Avro > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: 1.10.0, 1.9.1 > > > We should update Jetty to avoid security advisories: > [https://nvd.nist.gov/vuln/detail/CVE-2019-10241] > [https://nvd.nist.gov/vuln/detail/CVE-2019-10247] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863813#comment-16863813
]
ASF subversion and git services commented on AVRO-2400:
---
Commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551 in avro's branch
refs/heads/master from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=aa972ce ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863812#comment-16863812
]
ASF subversion and git services commented on AVRO-2400:
---
Commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551 in avro's branch
refs/heads/master from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=aa972ce ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863814#comment-16863814
]
ASF subversion and git services commented on AVRO-2400:
---
Commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551 in avro's branch
refs/heads/master from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=aa972ce ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863811#comment-16863811
]
ASF subversion and git services commented on AVRO-2400:
---
Commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551 in avro's branch
refs/heads/master from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=aa972ce ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863830#comment-16863830
]
ASF subversion and git services commented on AVRO-2400:
---
Commit 907558c65fa754a53b4a9493cebe692aecddfe02 in avro's branch
refs/heads/branch-1.9 from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=907558c ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
(cherry picked from commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551)
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863831#comment-16863831
]
ASF subversion and git services commented on AVRO-2400:
---
Commit 907558c65fa754a53b4a9493cebe692aecddfe02 in avro's branch
refs/heads/branch-1.9 from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=907558c ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
(cherry picked from commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551)
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863828#comment-16863828
]
ASF subversion and git services commented on AVRO-2400:
---
Commit 907558c65fa754a53b4a9493cebe692aecddfe02 in avro's branch
refs/heads/branch-1.9 from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=907558c ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
(cherry picked from commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551)
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2400) Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
[
https://issues.apache.org/jira/browse/AVRO-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863829#comment-16863829
]
ASF subversion and git services commented on AVRO-2400:
---
Commit 907558c65fa754a53b4a9493cebe692aecddfe02 in avro's branch
refs/heads/branch-1.9 from jacobtolar
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=907558c ]
AVRO-2400: Make schema resolution behave the same as previous versions (#526)
* [AVRO-2400] Make schema resolution behave the same as previous versions
* AVRO-2400 make same schema resolution changes to SchemaCompatibility
* make style check happy
* fix failing tests
* AVRO-2400 fix checkstyle issue
(cherry picked from commit aa972ced3c001e0d9d8de6cd5013a1cb3b989551)
> Avro 1.9.0 can't resolve schemas that can be resolved in 1.8.2
> --
>
> Key: AVRO-2400
> URL: https://issues.apache.org/jira/browse/AVRO-2400
> Project: Apache Avro
> Issue Type: Bug
> Components: java
>Reporter: Jacob Tolar
>Assignee: Jacob Tolar
>Priority: Blocker
> Fix For: 1.10.0, 1.9.1
>
>
> The failure occurs in ResolvingGrammarGenerator when reader and writer schema
> have an array of records with different full names (e.g. different
> namespace).
> {code:java}
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.avro.Resolver$ReaderUnion cannot be cast to
> org.apache.avro.Resolver$Container{code}
> Avro 1.8.2 allowed this behavior but it now fails in 1.9.0. Looking at the
> jiras and code, I don't believe this was intentional ( AVRO-2275,
> [https://github.com/apache/avro/commit/39d959e1c6a1f339f03dab18289e47f27c10be7f]
> ).
>
> It looks like there were some attempts to keep compatibility (
> [https://github.com/apache/avro/blob/branch-1.9/lang/java/avro/src/main/java/org/apache/avro/Resolver.java]
> , e.g. see the commented out check for w.getFullName() in resolve()) but
> this case was missed.
>
> See this simple example to reproduce.
> [https://gist.github.com/jacobtolar/c88d43ab4e8767227891e5cdc188ffad]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867593#comment-16867593 ] ASF subversion and git services commented on AVRO-1837: --- Commit 349d35c632e87b453dda3392673a325fbd4a3d81 in avro's branch refs/heads/branch-1.9 from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=349d35c ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 (cherry picked from commit 81605f7d6467e687c518be5c3097521edcbb9494) > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867592#comment-16867592 ] ASF subversion and git services commented on AVRO-1837: --- Commit 349d35c632e87b453dda3392673a325fbd4a3d81 in avro's branch refs/heads/branch-1.9 from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=349d35c ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 (cherry picked from commit 81605f7d6467e687c518be5c3097521edcbb9494) > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867591#comment-16867591 ] ASF subversion and git services commented on AVRO-1837: --- Commit 349d35c632e87b453dda3392673a325fbd4a3d81 in avro's branch refs/heads/branch-1.9 from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=349d35c ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 (cherry picked from commit 81605f7d6467e687c518be5c3097521edcbb9494) > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867594#comment-16867594 ] ASF subversion and git services commented on AVRO-1837: --- Commit 349d35c632e87b453dda3392673a325fbd4a3d81 in avro's branch refs/heads/branch-1.9 from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=349d35c ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 (cherry picked from commit 81605f7d6467e687c518be5c3097521edcbb9494) > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867565#comment-16867565 ] ASF subversion and git services commented on AVRO-1837: --- Commit 81605f7d6467e687c518be5c3097521edcbb9494 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=81605f7 ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867564#comment-16867564 ] ASF subversion and git services commented on AVRO-1837: --- Commit 81605f7d6467e687c518be5c3097521edcbb9494 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=81605f7 ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867563#comment-16867563 ] ASF subversion and git services commented on AVRO-1837: --- Commit 81605f7d6467e687c518be5c3097521edcbb9494 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=81605f7 ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1837) Add support for logical date, time, timestamp type for python AVRO
[ https://issues.apache.org/jira/browse/AVRO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867562#comment-16867562 ] ASF subversion and git services commented on AVRO-1837: --- Commit 81605f7d6467e687c518be5c3097521edcbb9494 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=81605f7 ] AVRO-1837: Logical Types: date, time & timestamp (#545) * AVRO-1837: Logicaltype support for date, time and timestamp * AVRO-1837: add timezones.py file * AVRO-1837: fix init file in py closes #207 closes #82 > Add support for logical date, time, timestamp type for python AVRO > -- > > Key: AVRO-1837 > URL: https://issues.apache.org/jira/browse/AVRO-1837 > Project: Apache Avro > Issue Type: New Feature > Components: python >Affects Versions: 1.9.0 >Reporter: Abrar Ahmed Sheikh >Priority: Major > > Currently, python Avro does not seem to support a TIME, TIMESTAMP and DATE > logicalType type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2428) Update Hadoop version in the MR document
[ https://issues.apache.org/jira/browse/AVRO-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867714#comment-16867714 ] ASF subversion and git services commented on AVRO-2428: --- Commit 347d209d2b07c46a2f9e2f2545abb2e6f89b8ff5 in avro's branch refs/heads/master from Kengo Seki [ https://gitbox.apache.org/repos/asf?p=avro.git;h=347d209 ] AVRO-2428: Update Hadoop version in the MR document (#548) > Update Hadoop version in the MR document > > > Key: AVRO-2428 > URL: https://issues.apache.org/jira/browse/AVRO-2428 > Project: Apache Avro > Issue Type: Improvement > Components: doc >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Minor > > Support for Hadoop 1.x is removed by AVRO-2059, but the examples still use > Hadoop 1.1.0 (e.g., http://avro.apache.org/docs/1.9.0/mr.html). Should we > also update them? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868758#comment-16868758 ] ASF subversion and git services commented on AVRO-2404: --- Commit fb2d025a3d6d4a786283c770ec955f644d133b9a in avro's branch refs/heads/master from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=fb2d025 ] AVRO-2404: Make jar download secure > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868760#comment-16868760 ] ASF subversion and git services commented on AVRO-2404: --- Commit 2d3b1fe7efd865639663ba785877182e7e038c45 in avro's branch refs/heads/master from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=2d3b1fe ] AVRO-2404: Make all external links https > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2404) Security sweep of build scripts and urls
[ https://issues.apache.org/jira/browse/AVRO-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868759#comment-16868759 ] ASF subversion and git services commented on AVRO-2404: --- Commit 70260919426f89825ca148f5ee815f3b2cf4764d in avro's branch refs/heads/master from Niels Basjes [ https://gitbox.apache.org/repos/asf?p=avro.git;h=7026091 ] AVRO-2404: Make all references to apache.org https > Security sweep of build scripts and urls > > > Key: AVRO-2404 > URL: https://issues.apache.org/jira/browse/AVRO-2404 > Project: Apache Avro > Issue Type: Task > Components: build >Reporter: Niels Basjes >Assignee: Niels Basjes >Priority: Major > > In some places we still use insecure URLs. > We should fix that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2430) Bump zstd 1.3.8-6 to 1.4.0-1
[ https://issues.apache.org/jira/browse/AVRO-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868585#comment-16868585 ] ASF subversion and git services commented on AVRO-2430: --- Commit 191b52b8d573974f79bf6e5769abf37c9e95be8b in avro's branch refs/heads/branch-1.9 from Fokko Driesprong [ https://gitbox.apache.org/repos/asf?p=avro.git;h=191b52b ] AVRO-2430: Bump zstd 1.3.8-6 to 1.4.0-1 (#549) (cherry picked from commit 89cf20fd44af8ce7b734e7455cd57f4dda7168f9) > Bump zstd 1.3.8-6 to 1.4.0-1 > > > Key: AVRO-2430 > URL: https://issues.apache.org/jira/browse/AVRO-2430 > Project: Apache Avro > Issue Type: Improvement >Affects Versions: 1.9.0 >Reporter: Fokko Driesprong >Assignee: Fokko Driesprong >Priority: Major > Fix For: 1.10.0, 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2428) Update Hadoop version in the MR document
[ https://issues.apache.org/jira/browse/AVRO-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868537#comment-16868537 ] ASF subversion and git services commented on AVRO-2428: --- Commit 8d9fe023bfb0c32b5279434a31ffd460ceabcd44 in avro's branch refs/heads/branch-1.9 from Kengo Seki [ https://gitbox.apache.org/repos/asf?p=avro.git;h=8d9fe02 ] AVRO-2428: Update Hadoop version in the MR document (#548) (cherry picked from commit 347d209d2b07c46a2f9e2f2545abb2e6f89b8ff5) > Update Hadoop version in the MR document > > > Key: AVRO-2428 > URL: https://issues.apache.org/jira/browse/AVRO-2428 > Project: Apache Avro > Issue Type: Improvement > Components: doc >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Minor > Fix For: 1.10.0 > > > Support for Hadoop 1.x is removed by AVRO-2059, but the examples still use > Hadoop 1.1.0 (e.g., http://avro.apache.org/docs/1.9.0/mr.html). Should we > also update them? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2413) Simplify Python Validate Code
[ https://issues.apache.org/jira/browse/AVRO-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871010#comment-16871010 ] ASF subversion and git services commented on AVRO-2413: --- Commit d5f46ac8789f86aa29d4da756ac1b6a5d6a66f35 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d5f46ac ] AVRO-2413: Refactor io.Validate to use a mapping (#516) * AVRO-2413: Refactor Validate to Use a Mapping * AVRO-2443: Fix Invalid AvroTypeException Invocation > Simplify Python Validate Code > - > > Key: AVRO-2413 > URL: https://issues.apache.org/jira/browse/AVRO-2413 > Project: Apache Avro > Issue Type: Task >Reporter: Michael A. Smith >Priority: Major > > The implementation of `validate` in python (2 and 3) has high cyclomatic > complexity and can be simplified into a dictionary lookup based on the type > being validated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2413) Simplify Python Validate Code
[ https://issues.apache.org/jira/browse/AVRO-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871011#comment-16871011 ] ASF subversion and git services commented on AVRO-2413: --- Commit d5f46ac8789f86aa29d4da756ac1b6a5d6a66f35 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d5f46ac ] AVRO-2413: Refactor io.Validate to use a mapping (#516) * AVRO-2413: Refactor Validate to Use a Mapping * AVRO-2443: Fix Invalid AvroTypeException Invocation > Simplify Python Validate Code > - > > Key: AVRO-2413 > URL: https://issues.apache.org/jira/browse/AVRO-2413 > Project: Apache Avro > Issue Type: Task >Reporter: Michael A. Smith >Priority: Major > > The implementation of `validate` in python (2 and 3) has high cyclomatic > complexity and can be simplified into a dictionary lookup based on the type > being validated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2443) Python: incorrect call of AvroTypeException
[ https://issues.apache.org/jira/browse/AVRO-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871012#comment-16871012 ] ASF subversion and git services commented on AVRO-2443: --- Commit d5f46ac8789f86aa29d4da756ac1b6a5d6a66f35 in avro's branch refs/heads/master from Michael A. Smith [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d5f46ac ] AVRO-2413: Refactor io.Validate to use a mapping (#516) * AVRO-2413: Refactor Validate to Use a Mapping * AVRO-2443: Fix Invalid AvroTypeException Invocation > Python: incorrect call of AvroTypeException > > > Key: AVRO-2443 > URL: https://issues.apache.org/jira/browse/AVRO-2443 > Project: Apache Avro > Issue Type: Bug > Components: python >Reporter: Piotr Gołąb >Priority: Minor > > There is a bug in the Validate function for py3 validator. > [https://github.com/apache/avro/blob/master/lang/py3/avro/io.py#L149] > The `AvroTypeException` will fail (if ever reached), because the exception > accepts two arguments: `expected_schema, datum`. > > This issue was found here: > [https://github.com/apache/avro/pull/516/files#r287870842] and might be as > well fixed in AVRO-2413. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-2444) Fix gen_interop_data.py to work with interop.avsc
[
https://issues.apache.org/jira/browse/AVRO-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870996#comment-16870996
]
ASF subversion and git services commented on AVRO-2444:
---
Commit 8bffed2c95cefb062d1593f7c59eae62da012c52 in avro's branch
refs/heads/master from Kengo Seki
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=8bffed2 ]
AVRO-2444: Fix gen_interop_data.py to work with interop.avsc (#559)
> Fix gen_interop_data.py to work with interop.avsc
> -
>
> Key: AVRO-2444
> URL: https://issues.apache.org/jira/browse/AVRO-2444
> Project: Apache Avro
> Issue Type: Bug
> Components: interop, python
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
>
> The following command fails, since the value assigned to bytesField in
> gen_interop_data.py is a str, not bytes.
> {code}
> $ python3 lang/py3/avro/tests/gen_interop_data.py
> share/test/schemas/interop.avsc /tmp/py3.avro
> Traceback (most recent call last):
> File "lang/py3/avro/tests/gen_interop_data.py", line 55, in
> dfw.append(DATUM)
> File "/home/sekikn/.local/lib/python3.6/site-packages/avro/datafile.py",
> line 303, in append
> self.datum_writer.write(datum, self.buffer_encoder)
> File "/home/sekikn/.local/lib/python3.6/site-packages/avro/io.py", line
> 817, in write
> raise AvroTypeException(self.writer_schema, datum)
> avro.io.AvroTypeException: The datum {'intField': 12, 'longField': 15234324,
> 'stringField': 'hey', 'boolField': True, 'floatField': 1234.0, 'doubleField':
> -1234.0, 'bytesField': '12312adf', 'nullField': None, 'arrayField': [5.0,
> 0.0, 12.0], 'mapField': {'a': {'label': 'a'}, 'bee': {'label': 'cee'}},
> 'unionField': 12.0, 'enumField': 'C', 'fixedField': b'1019181716151413',
> 'recordField': {'label': 'blah', 'children': [{'label': 'inner', 'children':
> []}]}} is not an example of the schema {
> "type": "record",
> "name": "Interop",
> "namespace": "org.apache.avro",
> "fields": [
> {
> "type": "int",
> "name": "intField"
> },
> {
> "type": "long",
> "name": "longField"
> },
> {
> "type": "string",
> "name": "stringField"
> },
> {
> "type": "boolean",
>
> "name": "boolField"
> },
> {
> "type": "float",
> "name": "floatField"
>
> },
> {
> "type": "double",
> "name": "doubleField"
> },
>
> {
> "type": "bytes",
>
> "name": "bytesField"
> },
>
> {
>
> "type": "null",
>
> "name": "nullField"
>
> },
> {
> "type": {
> "type": "array",
> "items": "double"
> },
> "name": "arrayField"
> },
> {
> "type": {
> "type": "map",
> "values": {
> "type": "record",
> "name": "Foo",
> "namespace": "org.apache.avro",
> "namespace": "org.apache.avro",
> "fields": [
> {
> "type": "string",
> "name": "label"
> }
> ]
> }
> },
> "name": "mapField"
> },
> {
> "type": [
> "boolean",
> "double",
>
[jira] [Commented] (AVRO-2396) Huge performance regression on SpecificDatumReader for array reading
[
https://issues.apache.org/jira/browse/AVRO-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860223#comment-16860223
]
ASF subversion and git services commented on AVRO-2396:
---
Commit 675e6f017d3758da1f79c2407df5c0c6d2b83e99 in avro's branch
refs/heads/branch-1.9 from Brian Lachniet
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=675e6f0 ]
AVRO-2396: Cache types in ObjectCreator (#538)
> Huge performance regression on SpecificDatumReader for array reading
>
>
> Key: AVRO-2396
> URL: https://issues.apache.org/jira/browse/AVRO-2396
> Project: Apache Avro
> Issue Type: Bug
> Components: csharp
>Affects Versions: 1.9.0
>Reporter: wangying
>Assignee: Brian Lachniet
>Priority: Blocker
> Fix For: 1.9.1
>
>
> The company where I'm working as a .NET developer is using Avro format for
> message.
> Recently, after upgrade to 1.9.0-rc2 and 1.9.0-rc4, there is a hug regression
> the read array object.
> Our test case reads a ETP defined object "Energistics.Datatypes.ChannelData"
> inside which contains 5000 dataitems, with previous avro version, it only
> took 300~ms to read the data, which with the last version it wooks 1+ min.
> (the protocol can found from
> [https://www.energistics.org/etp-developers-users/])
>
> After look through the code, I find that should be caused by a change in
> SpecificRecordAccess class
> public object CreateRecord(object reuse)
> {
> return reuse ?? ObjectCreator.Instance.New(typeName, Schema.Type.Record);
> }
> Here, the reuse is null, thus ObjectCreator.Instance.New is run 5000 times
> and each time use reflection to get specific types.
>
> the previously version only do it in constructor:
> private class SpecificRecordAccess : RecordAccess
> {
> private ObjectCreator.CtorDelegate objCreator;
> public SpecificRecordAccess(RecordSchema readerSchema)
> {
> objCreator = GetConstructor(readerSchema.Fullname, Schema.Type.Record);
> }
> public object CreateRecord(object reuse)
> {
> return reuse ?? objCreator();
> }
> }
>
> I'm trying to make a workaround and pass a reuse object in method public T
> Read(T reuse, Decoder decoder), but still not working since the
> SpecificDatumReader doesn't pass it through in below method.
> public void AddElements( object array, int elements, int index, ReadItem
> itemReader, Decoder decoder, bool reuse, object reuseobj)
> {
> var list = (IList)array;
> for (int i=0; i < elements; i++)
> {
> list.Add( itemReader(null, decoder ) );
> }
> }
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-2396) Huge performance regression on SpecificDatumReader for array reading
[
https://issues.apache.org/jira/browse/AVRO-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860226#comment-16860226
]
ASF subversion and git services commented on AVRO-2396:
---
Commit e72aae63be4d5ceb2ad05822e85894e868c7b2d6 in avro's branch
refs/heads/master from Brian Lachniet
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e72aae6 ]
AVRO-2396: Cache types in ObjectCreator (#538)
(cherry picked from commit 675e6f017d3758da1f79c2407df5c0c6d2b83e99)
> Huge performance regression on SpecificDatumReader for array reading
>
>
> Key: AVRO-2396
> URL: https://issues.apache.org/jira/browse/AVRO-2396
> Project: Apache Avro
> Issue Type: Bug
> Components: csharp
>Affects Versions: 1.9.0
>Reporter: wangying
>Assignee: Brian Lachniet
>Priority: Blocker
> Fix For: 1.9.1
>
>
> The company where I'm working as a .NET developer is using Avro format for
> message.
> Recently, after upgrade to 1.9.0-rc2 and 1.9.0-rc4, there is a hug regression
> the read array object.
> Our test case reads a ETP defined object "Energistics.Datatypes.ChannelData"
> inside which contains 5000 dataitems, with previous avro version, it only
> took 300~ms to read the data, which with the last version it wooks 1+ min.
> (the protocol can found from
> [https://www.energistics.org/etp-developers-users/])
>
> After look through the code, I find that should be caused by a change in
> SpecificRecordAccess class
> public object CreateRecord(object reuse)
> {
> return reuse ?? ObjectCreator.Instance.New(typeName, Schema.Type.Record);
> }
> Here, the reuse is null, thus ObjectCreator.Instance.New is run 5000 times
> and each time use reflection to get specific types.
>
> the previously version only do it in constructor:
> private class SpecificRecordAccess : RecordAccess
> {
> private ObjectCreator.CtorDelegate objCreator;
> public SpecificRecordAccess(RecordSchema readerSchema)
> {
> objCreator = GetConstructor(readerSchema.Fullname, Schema.Type.Record);
> }
> public object CreateRecord(object reuse)
> {
> return reuse ?? objCreator();
> }
> }
>
> I'm trying to make a workaround and pass a reuse object in method public T
> Read(T reuse, Decoder decoder), but still not working since the
> SpecificDatumReader doesn't pass it through in below method.
> public void AddElements( object array, int elements, int index, ReadItem
> itemReader, Decoder decoder, bool reuse, object reuseobj)
> {
> var list = (IList)array;
> for (int i=0; i < elements; i++)
> {
> list.Add( itemReader(null, decoder ) );
> }
> }
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860229#comment-16860229 ] ASF subversion and git services commented on AVRO-1762: --- Commit a897c50bf28720373b89b10661902a8b9754f7a5 in avro's branch refs/heads/master from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=a897c50 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860231#comment-16860231 ] ASF subversion and git services commented on AVRO-1762: --- Commit a897c50bf28720373b89b10661902a8b9754f7a5 in avro's branch refs/heads/master from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=a897c50 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860232#comment-16860232 ] ASF subversion and git services commented on AVRO-1762: --- Commit a897c50bf28720373b89b10661902a8b9754f7a5 in avro's branch refs/heads/master from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=a897c50 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860233#comment-16860233 ] ASF subversion and git services commented on AVRO-1762: --- Commit a897c50bf28720373b89b10661902a8b9754f7a5 in avro's branch refs/heads/master from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=a897c50 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860230#comment-16860230 ] ASF subversion and git services commented on AVRO-1762: --- Commit a897c50bf28720373b89b10661902a8b9754f7a5 in avro's branch refs/heads/master from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=a897c50 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template
[ https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860238#comment-16860238 ] ASF subversion and git services commented on AVRO-1762: --- Commit 97e20b0d0dbea09b14affa8e1188f000a1fe0026 in avro's branch refs/heads/branch-1.9 from Nicola Bova [ https://gitbox.apache.org/repos/asf?p=avro.git;h=97e20b0 ] AVRO-1762: Velocity custom objects (#524) * AVRO-1762. Java: Put additional objects into Velocity template It provides more flexibility when generating code with custom Velocity templates. * AVRO-1762. Java: Put additional objects into Velocity template Rebased on master * AVRO-1762. Java: Put additional objects into Velocity template Improved unit tests * AVRO-1762: Velocity custom objects velocityTools is now of type List (cherry picked from commit a897c50bf28720373b89b10661902a8b9754f7a5) > Allow putting additional objects into the Velocity template > --- > > Key: AVRO-1762 > URL: https://issues.apache.org/jira/browse/AVRO-1762 > Project: Apache Avro > Issue Type: Improvement > Components: java >Reporter: Matheus Santana >Assignee: Nicola Bova >Priority: Major > Fix For: 1.10.0, 1.9.1 > > Attachments: AVRO-1762.patch > > > This JIRA proposes the ability to inject custom POJOs into the Velocity > template. > It is possible [to override template directory > configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22] > and thus make the compiler to generate customized code. However, > customization possibilities are constrained to [Velocity Template > Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction] > and [objects > injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340] > into the template's context. > The ability of injecting custom objects into the template's context would > leverage customization possibilities to the whole Java language itself. The > patch I'm about to attach modifies both compiler and maven-plugin in order to > provide client applications with the ability of easy injecting custom Java > objects into the Velocity templates' context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
