Hello,
I am looking at using the Avro C Library API for a project and was wondering
why Record Fields are not first class "objects"? Meaning, there is not an
AVRO_FIELD type for them. Looking at the python and Java implementations there
is a Field Class in both languages that can be accessed
Suraj,
Few questions for clarifications:
- What do you mean by module - Java, C, Python or like an individual code
file?
- When you say, " ./build.sh test on the module you have made the change
to" how does it determine this?
- Once merged what will trigger the PreCommit Build?
+1
Would be great if this was fixed.
- John
On Aug 1, 2017, at 12:40 AM, Martin Broadhurst
wrote:
The links to the current API documentation are broken:
http://avro.apache.org/docs/current/api/java/index.html
http://avro.apache.org/docs/current/api/c/index.html
Is it valid for the items in an array to be Union schema?
{
"type": "array",
"items": { "type": [ "int", "boolean", "string" ] }
}
According to the spec it is ambiguous:
* items: the schema of the array's items.
I have tried this schema in both python and c and it generates exceptions
Who does the homebrew maintenance when new releases are made? It seems that the
avro-c library is still the 1.8.1 code base. Would be nice if this was updated.
- John
-Original Message-
From: suraj acharya
Reply-To: "dev@avro.apache.org"
Date:
's highly likely someone just uploaded it on their own.
Suraj
On Jun 19, 2017 12:08 PM, "Gill, John" <john.g...@teradata.com> wrote:
Who does the homebrew maintenance when new releases are made? It seems that
the avro-c library is still the 1.8.1 code base. Would be nice if this was
up