[
https://issues.apache.org/jira/browse/AVRO-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106836#comment-15106836
]
Douglas Creager commented on AVRO-1663:
---------------------------------------
[This|https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html]
is the cheat sheet I've always used for figuring out what changes to make to
each number. (I've been known to [copy the
rules|https://github.com/redjack/libcork/blob/develop/src/CMakeLists.txt#L12]
into other build scripts before since I sometimes forget the link.) I think
you're right in the what changes should be made.
As for when, I think it would be cleaner to do it during the release process,
but I don't know that we've ever been strict about that. Is there a
project-wide pre-release process that we can hook into?
> C Library does not handle enum's namespace
> ------------------------------------------
>
> Key: AVRO-1663
> URL: https://issues.apache.org/jira/browse/AVRO-1663
> Project: Avro
> Issue Type: Bug
> Components: c
> Affects Versions: 1.7.7
> Reporter: Thomas Sanchez
> Assignee: Martin Kleppmann
> Attachments: AVRO-1663-2.patch, AVRO-1663-3.patch, AVRO-1663-4.patch,
> AVRO-1663.patch
>
>
> {code}{
> "type": "record",
> "name": "EventName",
> "namespace": "com.company.avro.schemas",
> "fields": [
> {"name": "eventname_model",
> "type": {
> "type": "enum",
> "namespace": "com.company.models",
> "name": "EventName",
> "symbols": ["XXXX"]
> }
> }
> ]
> }
> {code}
> Such a schema is perfectly valid but the C library does no handle it because
> it does not parse the namespace field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
