[
https://issues.apache.org/jira/browse/AVRO-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096815#comment-17096815
]
Hudson commented on AVRO-2723:
--
SUCCESS: Integrated in Jenkins build AvroJava #853 (See
[
https://issues.apache.org/jira/browse/AVRO-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved AVRO-2723.
Fix Version/s: 1.10.0
Assignee: Andy Le
Resolution: Fixed
I committed this.
[
https://issues.apache.org/jira/browse/AVRO-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096758#comment-17096758
]
ASF subversion and git services commented on AVRO-2723:
---
Commit
zolyfarkas commented on pull request #864:
URL: https://github.com/apache/avro/pull/864#issuecomment-621804272
@Fokko @RyanSkraba can you let me know what you think about the latests
updates to this PR?
This is an automated
zolyfarkas commented on pull request #869:
URL: https://github.com/apache/avro/pull/869#issuecomment-621802979
It would be nice to expose Schema.Names for the purpose of customizing
schema reference resolution.
Here are the use cases I have:
1) Avsc files referencing other
Previous emails on this list have discussed the "why" questions. But when
and how should we go about it? Could 1.10 be the last avro release to
include avro-python3? This would allow us to play a little less ticket
tennis with folks reporting bugs (can you reproduce this in "the other"
python
Arturas Kuznecovas created AVRO-2824:
Summary: avrogen.exe tool requires unsupported .Net Core 2.2
runtime
Key: AVRO-2824
URL: https://issues.apache.org/jira/browse/AVRO-2824
Project: Apache Avro
tjwp commented on pull request #628:
URL: https://github.com/apache/avro/pull/628#issuecomment-621789200
Looks like the build is currently failing due to an issue with C#
dependencies.
This is an automated message from the
masatana commented on pull request #865:
URL: https://github.com/apache/avro/pull/865#issuecomment-621652418
Thanks @kojiromike !
This is an automated message from the Apache Git Service.
To respond to the message, please
