[jira] [Commented] (AVRO-2647) specification does not fully specify semantics for unions in default types
[
https://issues.apache.org/jira/browse/AVRO-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093021#comment-17093021
]
Thorsten Hake commented on AVRO-2647:
-
I actually would say that the schema is not ambiguous. The default value is
correct given the type of the field. I would argue that the implementation (at
least the Java implementation) does not correctly check the default type.
The following check will be executed for each element of the defined default
array (Java-Method Schema#isValidDefault):{color:#ffc66d}
{color}
{code:java}
for (JsonNode value : defaultValue)
if (!isValidDefault(schema.getValueType(), value))
return false;
return true;
{code}
At this point, one shouldn't check if the value is a valid default but if it is
a valid value for the type of the array. The array is a valid default if all
its values are valid according to the array type. The elements do not have to
be a valid default of the array type, only array as a whole.
The same problem should also exist for the check of map types (only checked by
reading the code).
> specification does not fully specify semantics for unions in default types
> --
>
> Key: AVRO-2647
> URL: https://issues.apache.org/jira/browse/AVRO-2647
> Project: Apache Avro
> Issue Type: Bug
> Components: doc
>Reporter: Roger
>Priority: Minor
>
> Currently the specification does not make the semantics clear for union types
> within complex types clear. In particular, the spec talks about union fields,
> but leaves the semantics for unions in other contexts unspecified.
> Here's an example which is undefined according to the current specification:
> {code:json}
> {
> "type": "record",
> "name": "R",
> "fields": [
> {
> "name": "F",
> "type": {
> "type": "array",
> "items": [
> {
> "type": "enum",
> "name": "E1",
> "symbols": ["A", "B"]
> },
> {
> "type": "enum",
> "name": "E2",
> "symbols": ["B", "A", "C"]
> }
> ]
> },
> "default": ["A", "B", "C"]
> }
> ]
> }
> {code}
> By experiment, most implementations seem to have chosen the semantics that
> are documented in this PR.
> In Java, the schema above is parsed without error, but when attempting to use
> the default value, it fails with a NullPointerException (trying to find the
> symbol C in E1). (Thanks for Ryan Skraba for this).
> In [gogen-avro|https://github.com/actgardner/gogen-avro] it generates invalid
> code because it's assuming E1 but generating the symbol for "C" anyway.
> FWIW at some point in the future, I believe that it would be nice to align
> the default value specification with the JSON encoding for Avro so there
> aren't two subtly different JSON encodings of an Avro value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [avro] anhldbk commented on pull request #842: AVRO-2723: Refactor ReflectData to allow derived classes to customize default values for fields
anhldbk commented on pull request #842: URL: https://github.com/apache/avro/pull/842#issuecomment-619706282 @cutting @Fokko would you please have a look at my PR? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [avro] zeshuai007 commented on pull request #859: AVRO-2819:Add BigInteger and BigDecimal support for JacksonUtils
zeshuai007 commented on pull request #859: URL: https://github.com/apache/avro/pull/859#issuecomment-619665754 Thanks for the review and approval, a ticket has been created in Jira. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (AVRO-2819) Add BigInteger and BigDecimal support for JacksonUtils
Zezeng Wang created AVRO-2819: - Summary: Add BigInteger and BigDecimal support for JacksonUtils Key: AVRO-2819 URL: https://issues.apache.org/jira/browse/AVRO-2819 Project: Apache Avro Issue Type: Improvement Components: java Affects Versions: 1.9.2 Reporter: Zezeng Wang Assignee: Zezeng Wang this change is relatively small, so I didn't submit a issue in jira. It allows JacksonUtils.toJsonNode(Object datum) receive type BigInteger and BigDecimal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [avro] tjwp commented on a change in pull request #855: AVRO-2800 validate enum symbol values
tjwp commented on a change in pull request #855:
URL: https://github.com/apache/avro/pull/855#discussion_r415292937
##
File path: lang/ruby/test/test_schema.rb
##
@@ -541,4 +541,33 @@ def test_bytes_schema
schema_str = 'bytes'
assert_equal schema_str, schema.to_avro
end
+
+ def test_validate_duplicate_symbols
+exception = assert_raise(Avro::SchemaParseError) do
+ hash_to_schema(
+type: 'enum',
+name: 'name',
+symbols: ['erica', 'erica']
+ )
+end
+assert_equal(
+ 'Duplicate symbol: ["erica", "erica"]',
+ exception.to_s
+)
+ end
+
+ def test_validate_enum_symbols
+exception = assert_raise(Avro::SchemaParseError) do
+ hash_to_schema(
+type: 'enum',
+name: 'operator_enum',
+symbols: ['==', '>=']
Review comment:
Consider including an example that has a hyphen ("-")? That is probably
the most common invalid example. Also, a value beginning with a digit?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (AVRO-2790) Necessity of using Object as parameter of javaEscape method
[ https://issues.apache.org/jira/browse/AVRO-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092657#comment-17092657 ] Hudson commented on AVRO-2790: -- SUCCESS: Integrated in Jenkins build AvroJava #848 (See [https://builds.apache.org/job/AvroJava/848/]) AVRO-2790: Necessity of using Object as parameter of javaEscape method (github: [https://github.com/apache/avro/commit/d83e43b3cf087aa1911befd39e9df0c9f5e82628]) * (edit) lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java > Necessity of using Object as parameter of javaEscape method > --- > > Key: AVRO-2790 > URL: https://issues.apache.org/jira/browse/AVRO-2790 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Assignee: Zezeng Wang >Priority: Minor > Fix For: 1.10.0 > > > Hi, > The > [javaEscape|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L976] > method in *SpecificCompiler* is a utility used by templates. Escaping quotes > and backslashes, which means it's dealing with strings. > And I checked the caller > ([enum.vm|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/enum.vm#L31], > > [fixed.vm|https://github.com/apache/avro/blob/master/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/fixed.vm#L31]) > of javaEscape, all passed in as java.lang.String, > So I'm sure this should use java.lang.String as the input parameter and > remove unnecessary Object.toString operations. > > Cheers, > Ze Zeng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [avro] masatana commented on pull request #865: AVRO-2814: Add __version__ to __init__.py (PEP396)
masatana commented on pull request #865: URL: https://github.com/apache/avro/pull/865#issuecomment-619524276 Thanks @Fokko , I updated my commit. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (AVRO-2790) Necessity of using Object as parameter of javaEscape method
[ https://issues.apache.org/jira/browse/AVRO-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092629#comment-17092629 ] ASF subversion and git services commented on AVRO-2790: --- Commit d83e43b3cf087aa1911befd39e9df0c9f5e82628 in avro's branch refs/heads/master from Zezeng Wang [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d83e43b ] AVRO-2790: Necessity of using Object as parameter of javaEscape method > Necessity of using Object as parameter of javaEscape method > --- > > Key: AVRO-2790 > URL: https://issues.apache.org/jira/browse/AVRO-2790 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Assignee: Zezeng Wang >Priority: Minor > Fix For: 1.10.0 > > > Hi, > The > [javaEscape|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L976] > method in *SpecificCompiler* is a utility used by templates. Escaping quotes > and backslashes, which means it's dealing with strings. > And I checked the caller > ([enum.vm|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/enum.vm#L31], > > [fixed.vm|https://github.com/apache/avro/blob/master/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/fixed.vm#L31]) > of javaEscape, all passed in as java.lang.String, > So I'm sure this should use java.lang.String as the input parameter and > remove unnecessary Object.toString operations. > > Cheers, > Ze Zeng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AVRO-2790) Necessity of using Object as parameter of javaEscape method
[ https://issues.apache.org/jira/browse/AVRO-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fokko Driesprong resolved AVRO-2790. Resolution: Fixed > Necessity of using Object as parameter of javaEscape method > --- > > Key: AVRO-2790 > URL: https://issues.apache.org/jira/browse/AVRO-2790 > Project: Apache Avro > Issue Type: Improvement > Components: java >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Assignee: Zezeng Wang >Priority: Minor > Fix For: 1.10.0 > > > Hi, > The > [javaEscape|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L976] > method in *SpecificCompiler* is a utility used by templates. Escaping quotes > and backslashes, which means it's dealing with strings. > And I checked the caller > ([enum.vm|https://github.com/apache/avro/blob/c81ea58c601a2f600d9d45cf50b9f6434b911d5a/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/enum.vm#L31], > > [fixed.vm|https://github.com/apache/avro/blob/master/lang/java/compiler/src/main/velocity/org/apache/avro/compiler/specific/templates/java/classic/fixed.vm#L31]) > of javaEscape, all passed in as java.lang.String, > So I'm sure this should use java.lang.String as the input parameter and > remove unnecessary Object.toString operations. > > Cheers, > Ze Zeng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AVRO-2813) Add cppcheck as a C++ linter
[ https://issues.apache.org/jira/browse/AVRO-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092622#comment-17092622 ] Hudson commented on AVRO-2813: -- SUCCESS: Integrated in Jenkins build AvroJava #847 (See [https://builds.apache.org/job/AvroJava/847/]) AVRO-2813: Add cppcheck as a C++ linter (#862) (github: [https://github.com/apache/avro/commit/f56cafb83854a7529625bd1d82521f5848399ccc]) * (edit) lang/c++/impl/Zigzag.cc * (edit) build.sh * (edit) lang/c++/build.sh * (edit) share/docker/Dockerfile > Add cppcheck as a C++ linter > > > Key: AVRO-2813 > URL: https://issues.apache.org/jira/browse/AVRO-2813 > Project: Apache Avro > Issue Type: Improvement > Components: c++ >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Fix For: 1.10.0 > > > Avro C++ doesn't have a linter feature for now, so let's add it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AVRO-2811) Upgrade grpc 1.26 to 1.28
[ https://issues.apache.org/jira/browse/AVRO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092621#comment-17092621 ] Hudson commented on AVRO-2811: -- SUCCESS: Integrated in Jenkins build AvroJava #847 (See [https://builds.apache.org/job/AvroJava/847/]) AVRO-2811:Upgrade grpc 1.26 to 1.28 (#863) (github: [https://github.com/apache/avro/commit/b6f49705ad3cc81020117d04938e1ae03d3a99d9]) * (edit) lang/java/pom.xml > Upgrade grpc 1.26 to 1.28 > - > > Key: AVRO-2811 > URL: https://issues.apache.org/jira/browse/AVRO-2811 > Project: Apache Avro > Issue Type: Task >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Assignee: Zezeng Wang >Priority: Major > Fix For: 1.10.0 > > > In netty 1.26 there are bugs that need attention. > Eg: [Deadlock on start gRPC > server|https://github.com/grpc/grpc-java/issues/6601] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [avro] Fokko commented on pull request #865: AVRO-2814: Add __version__ to __init__.py (PEP396)
Fokko commented on pull request #865: URL: https://github.com/apache/avro/pull/865#issuecomment-619517195 Looks like an unrelated error, can you pull in latest master @masatana ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (AVRO-2813) Add cppcheck as a C++ linter
[ https://issues.apache.org/jira/browse/AVRO-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092609#comment-17092609 ] ASF subversion and git services commented on AVRO-2813: --- Commit f56cafb83854a7529625bd1d82521f5848399ccc in avro's branch refs/heads/master from Kengo Seki [ https://gitbox.apache.org/repos/asf?p=avro.git;h=f56cafb ] AVRO-2813: Add cppcheck as a C++ linter (#862) > Add cppcheck as a C++ linter > > > Key: AVRO-2813 > URL: https://issues.apache.org/jira/browse/AVRO-2813 > Project: Apache Avro > Issue Type: Improvement > Components: c++ >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Fix For: 1.10.0 > > > Avro C++ doesn't have a linter feature for now, so let's add it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AVRO-2813) Add cppcheck as a C++ linter
[ https://issues.apache.org/jira/browse/AVRO-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fokko Driesprong updated AVRO-2813: --- Fix Version/s: 1.10.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add cppcheck as a C++ linter > > > Key: AVRO-2813 > URL: https://issues.apache.org/jira/browse/AVRO-2813 > Project: Apache Avro > Issue Type: Improvement > Components: c++ >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Fix For: 1.10.0 > > > Avro C++ doesn't have a linter feature for now, so let's add it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AVRO-2811) Upgrade grpc 1.26 to 1.28
[ https://issues.apache.org/jira/browse/AVRO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fokko Driesprong reassigned AVRO-2811: -- Assignee: Zezeng Wang > Upgrade grpc 1.26 to 1.28 > - > > Key: AVRO-2811 > URL: https://issues.apache.org/jira/browse/AVRO-2811 > Project: Apache Avro > Issue Type: Task >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Assignee: Zezeng Wang >Priority: Major > Fix For: 1.10.0 > > > In netty 1.26 there are bugs that need attention. > Eg: [Deadlock on start gRPC > server|https://github.com/grpc/grpc-java/issues/6601] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AVRO-2811) Upgrade grpc 1.26 to 1.28
[ https://issues.apache.org/jira/browse/AVRO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fokko Driesprong resolved AVRO-2811. Fix Version/s: (was: 1.9.3) 1.10.0 Resolution: Fixed > Upgrade grpc 1.26 to 1.28 > - > > Key: AVRO-2811 > URL: https://issues.apache.org/jira/browse/AVRO-2811 > Project: Apache Avro > Issue Type: Task >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Priority: Major > Fix For: 1.10.0 > > > In netty 1.26 there are bugs that need attention. > Eg: [Deadlock on start gRPC > server|https://github.com/grpc/grpc-java/issues/6601] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [avro] Fokko commented on pull request #862: AVRO-2813: Add cppcheck as a C++ linter
Fokko commented on pull request #862: URL: https://github.com/apache/avro/pull/862#issuecomment-619516867 Love it, thanks @sekikn This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (AVRO-2811) Upgrade grpc 1.26 to 1.28
[ https://issues.apache.org/jira/browse/AVRO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092605#comment-17092605 ] ASF subversion and git services commented on AVRO-2811: --- Commit b6f49705ad3cc81020117d04938e1ae03d3a99d9 in avro's branch refs/heads/master from Zezeng Wang [ https://gitbox.apache.org/repos/asf?p=avro.git;h=b6f4970 ] AVRO-2811:Upgrade grpc 1.26 to 1.28 (#863) > Upgrade grpc 1.26 to 1.28 > - > > Key: AVRO-2811 > URL: https://issues.apache.org/jira/browse/AVRO-2811 > Project: Apache Avro > Issue Type: Task >Affects Versions: 1.9.2 >Reporter: Zezeng Wang >Priority: Major > Fix For: 1.10.0 > > > In netty 1.26 there are bugs that need attention. > Eg: [Deadlock on start gRPC > server|https://github.com/grpc/grpc-java/issues/6601] -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Proposal: RFCs for Avro 2.x
Hi Andy, Thanks for reaching out. Sorry for not being so active in the community lately. Since Avro 1.8.2 there has been some activity on the repository again, fixing stuff like security issues and migrating to later versions of Java. Avro has been around for 10 years now, and I would like to keep (some) backward compatibility to make sure that people are still going to use it for another 10 years :) In the past, the idea was to keep the format backward compatibility, this excludes the Java API to. So we did some changes to the API, such as removing Jackson from the public API and aggressively migrating from Joda Time to Java JSR-310. This caused a lot of issues because Avro is deeply nested in a lot of projects. For example, it is a huge task to update Avro in Hive or Hadoop. Therefore we believe that backward compatibility is very important. And I agree that we should mainly focus on the Avro spec itself, and not too much on File I/O and Network etc :) However, if we decide to break an API, we should do it for a good reason. Cheers, Fokko Op wo 22 apr. 2020 om 16:09 schreef Andy Le : > Hi guys, > > I'm new to this vibrant open source community. My story with Avro can be > found here [1] > > While implementing the feature, I got stuck and had various discussions > with Dough Cutting, Fokko Driesprong You may see here [2] > > Here my (bias) observations about our current Avro 1.9.x: > > - Some improvements can't be made due to fear of backward > incompatibilities. For example: specifications about named Union. > > - If `Apache Avro™ is a data serialization system.` then the repository > `apache/avro` should solely focus on (de)serialization, right? Currently > our repository contains many nice-to-have-but-not-critical things like: > File I/O, Network I/O > > IMHO, I think: > > - We should publicly gather RFCs for Avro 2.x > > - We should move such nice things out of Avro 2.x (may be to other > dedicated repositories) > > What do you think about my suggestions. Pls kindly let me know. > > Thank you & be strong. > > [1] My fork: https://github.com/anhldbk/avro-fork#why-this-fork > [2] My opened issue: > https://issues.apache.org/jira/browse/AVRO-2808?jql=reporter%3Danhldbk%20AND%20resolution%20is%20EMPTY > > >
[jira] [Commented] (AVRO-2816) Remove duplicated Perl library from Dockerfile
[ https://issues.apache.org/jira/browse/AVRO-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092594#comment-17092594 ] Hudson commented on AVRO-2816: -- SUCCESS: Integrated in Jenkins build AvroJava #846 (See [https://builds.apache.org/job/AvroJava/846/]) AVRO-2816: Remove duplicated Perl library from Dockerfile (#866) (github: [https://github.com/apache/avro/commit/d336babe3e0a11d90613083de72652f358207b29]) * (edit) share/docker/Dockerfile > Remove duplicated Perl library from Dockerfile > -- > > Key: AVRO-2816 > URL: https://issues.apache.org/jira/browse/AVRO-2816 > Project: Apache Avro > Issue Type: Improvement > Components: docker, perl >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Trivial > Fix For: 1.10.0 > > > Test::Pod module is installed twice in the Dockerfile. Removing either of > them might save the CI time a bit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AVRO-2816) Remove duplicated Perl library from Dockerfile
[ https://issues.apache.org/jira/browse/AVRO-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092578#comment-17092578 ] ASF subversion and git services commented on AVRO-2816: --- Commit d336babe3e0a11d90613083de72652f358207b29 in avro's branch refs/heads/master from Kengo Seki [ https://gitbox.apache.org/repos/asf?p=avro.git;h=d336bab ] AVRO-2816: Remove duplicated Perl library from Dockerfile (#866) > Remove duplicated Perl library from Dockerfile > -- > > Key: AVRO-2816 > URL: https://issues.apache.org/jira/browse/AVRO-2816 > Project: Apache Avro > Issue Type: Improvement > Components: docker, perl >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Trivial > > Test::Pod module is installed twice in the Dockerfile. Removing either of > them might save the CI time a bit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AVRO-2816) Remove duplicated Perl library from Dockerfile
[ https://issues.apache.org/jira/browse/AVRO-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fokko Driesprong updated AVRO-2816: --- Fix Version/s: 1.10.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove duplicated Perl library from Dockerfile > -- > > Key: AVRO-2816 > URL: https://issues.apache.org/jira/browse/AVRO-2816 > Project: Apache Avro > Issue Type: Improvement > Components: docker, perl >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Trivial > Fix For: 1.10.0 > > > Test::Pod module is installed twice in the Dockerfile. Removing either of > them might save the CI time a bit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
