DRAFT ASF Board Report - Apache Avro October 2019
Hi folks! Here's the report I plan to post tomorrow morning for next week's board meeting. Please let me know if there's anything you think needs clarification or that I missed entirely. --- ## Description: Apache Avro is a data serialization system with a compact binary format. It is used for storing and transporting schema driven serialized data. The unique features of Avro include automatic schema resolution - when the reader's expected schema is different from the actual schema with which the data was serialized the data is automatically adapted to meet reader's requirements. This report is for the period of Aug 1 2019 through Oct 9 2019. ## Issues: The project currently has no issues that require board attention. ## Summary: Apache Avro was founded 2010-04-20 (9 years ago) There are currently 31 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quarter: - Sean Busbey became PMC Chair - Brian Lachniet was added to the PMC on 2019-08-23 - Nándor Kollár was added to the PMC on 2019-08-29 - No new committers. Last addition was Tim Perkins on 2018-12-12. Releases, past quarter: - Apache Avro 1.9.1 on 2019-09-02 ## Activity: The Avro project slowly is improving on our gains from the last year. We've gotten a fair bit of feedback on the 1.9.0 release and are working towards establishing a regular cadence for getting the result of that feedback into our downstream communities. As noted in the summary, we've gotten the follow-up 1.9.1 release out after a period of approximately 4 months. We're also working across all of our programming language implementations to update things for current build tools and third party dependencies. We had a brief discussion about how our library versioning differs from practices we see in other places. The discussion had low participation but consensus among those that did was to both better document our current practices and change them in the future. We did not come up with any specific plans to handle implementation. [ref: https://s.apache.org/gxfo0 ] ## Numbers For those interested in numeric metrics: Mailing lists: - dev@avro.apache.org had a 14% increase in traffic in the past quarter (757 emails compared to 661) - u...@avro.apache.org had a 85% increase in traffic in the past quarter (65 emails compared to 35) JIRA: - 107 issues opened in past quarter (8% increase) - 58 issues closed in past quarter (3% increase) GitHub: - 83 PRs opened in past quarter (2% increase) - 72 PRs closed in past quarter (7% increase) Code Repository: - 144 commits in the past quarter (38% increase) - 18 code contributors in the past quarter (-33% decrease)
[jira] [Commented] (AVRO-2498) UUID generation is not working avro 1.9 version
[
https://issues.apache.org/jira/browse/AVRO-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947119#comment-16947119
]
Ivan Greene commented on AVRO-2498:
---
[~ryanskraba] The problem with UUID logical type is setting a stringType in the
generator configuration causes the logical type to be ignored. See AVRO-2548
for info. So the specific compiler will generate java.util.UUID with this issue
resolved. I have a PR out for that one waiting on review
> UUID generation is not working avro 1.9 version
> ---
>
> Key: AVRO-2498
> URL: https://issues.apache.org/jira/browse/AVRO-2498
> Project: Apache Avro
> Issue Type: Bug
>Reporter: Raj G
>Priority: Major
>
> Hi,
>
> I've downloaded avro-tools 1.9 jar and trying to generate a java file from an
> avro schema using below command
>
> java -jar avro-tools-1.9.0.jar compile schema ./myschema.avsc ./avro_java
>
> and have below schema in my .avsc file to generate a UUID field
> {
> "name": "myField",
> "type": {
> "type": "long",
> "logicalType": "uuid"
> }
> }
>
> But this is generating a long field instead of UUID type. Please suggest.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AVRO-2498) UUID generation is not working avro 1.9 version
[
https://issues.apache.org/jira/browse/AVRO-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947027#comment-16947027
]
Ryan Skraba commented on AVRO-2498:
---
[~raj2019] For the moment, it looks like specific records generated with
avro-tools have never treated UUIDs as anything other than strings.
I think there are two potential bugs or issues here:
1) There's no warning or error when the logical type annotation is ignored
(when generating a specific record).
I don't think this is a bug or bad behaviour: the spec says to fall back on the
underlying type if it's otherwise inconsistent. A warning during schema
compilation might be a good idea.
N.B. There was a simple typo in [~igreene]'s code, but his comment was correct
– the type should be {{string}}, not {{long}} or {{text}}
{code:java}
{"type": "record", "name": "Avro2498",
"fields": [
{"name": "myField", "type": {"type": "string", "logicalType": "uuid"}}
]
}
{code}
2) Unlike decimal or date/time logical types, the specific compiler *never*
generates fields of type {{java.util.UUID}}.
This might be an interesting new feature to be more consistent with the decimal
and date/time types built into the SpecificCompiler, especially now that UUID
has made its appearance in the spec in Avro 1.9.
Is there any strong push to implement a UUID type in generated records? Should
we repurpose this JIRA to provide some extra dev feedback when a logical type
annotation is ignored by the specific compiler or maven plugin?
> UUID generation is not working avro 1.9 version
> ---
>
> Key: AVRO-2498
> URL: https://issues.apache.org/jira/browse/AVRO-2498
> Project: Apache Avro
> Issue Type: Bug
>Reporter: Raj G
>Priority: Major
>
> Hi,
>
> I've downloaded avro-tools 1.9 jar and trying to generate a java file from an
> avro schema using below command
>
> java -jar avro-tools-1.9.0.jar compile schema ./myschema.avsc ./avro_java
>
> and have below schema in my .avsc file to generate a UUID field
> {
> "name": "myField",
> "type": {
> "type": "long",
> "logicalType": "uuid"
> }
> }
>
> But this is generating a long field instead of UUID type. Please suggest.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
