[jira] [Commented] (AVRO-2076) Combine already serialized Avro records to an Avro file
[ https://issues.apache.org/jira/browse/AVRO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167422#comment-16167422 ] Erik van Oosten commented on AVRO-2076: --- Awesome! Thanks Doug. Somehow I missed that method. > Combine already serialized Avro records to an Avro file > --- > > Key: AVRO-2076 > URL: https://issues.apache.org/jira/browse/AVRO-2076 > Project: Avro > Issue Type: Wish >Reporter: Erik van Oosten > > In some use cases Avro events arrive already serialized (e.g. when listening > to a Kafka topic). It would be great if there would an API that allows > writing an Avro file without the need for deserializing and serializing these > Avro records. > Providing such an API allows for very efficient creation of Avro files: given > that these Avro records are written with the same schema, an Avro file would > write will the exact same bytes anyway (before block compression). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AVRO-2076) Combine already serialized Avro records to an Avro file
[ https://issues.apache.org/jira/browse/AVRO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik van Oosten resolved AVRO-2076. --- Resolution: Not A Problem > Combine already serialized Avro records to an Avro file > --- > > Key: AVRO-2076 > URL: https://issues.apache.org/jira/browse/AVRO-2076 > Project: Avro > Issue Type: Wish >Reporter: Erik van Oosten > > In some use cases Avro events arrive already serialized (e.g. when listening > to a Kafka topic). It would be great if there would an API that allows > writing an Avro file without the need for deserializing and serializing these > Avro records. > Providing such an API allows for very efficient creation of Avro files: given > that these Avro records are written with the same schema, an Avro file would > write will the exact same bytes anyway (before block compression). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AVRO-2076) Combine already serialized Avro records to an Avro file
Erik van Oosten created AVRO-2076: - Summary: Combine already serialized Avro records to an Avro file Key: AVRO-2076 URL: https://issues.apache.org/jira/browse/AVRO-2076 Project: Avro Issue Type: Wish Reporter: Erik van Oosten In some use cases Avro events arrive already serialized (e.g. when listening to a Kafka topic). It would be great if there would an API that allows writing an Avro file without the need for deserializing and serializing these Avro records. Providing such an API allows for very efficient creation of Avro files: given that these Avro records are written with the same schema, an Avro file would write will the exact same bytes anyway (before block compression). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AVRO-2022) IDL does not allow `schema` as identifier
[
https://issues.apache.org/jira/browse/AVRO-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021085#comment-16021085
]
Erik van Oosten commented on AVRO-2022:
---
After working with this change for some time we decided to abandon this idea
and change the schema after all. The problem is that much code generation tools
assume they can create method {{Schema getSchema()}}. Unfortunately this
collides with the value we want it to return.
> IDL does not allow `schema` as identifier
> -
>
> Key: AVRO-2022
> URL: https://issues.apache.org/jira/browse/AVRO-2022
> Project: Avro
> Issue Type: Bug
> Components: java
>Affects Versions: 1.7.7, 1.8.1
>Reporter: Erik van Oosten
>
> The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
> following does not compile:
> {noformat}
> record {
>string `schema`;
> }
> {noformat}
> Patches are available for the master branch:
> https://github.com/apache/avro/pull/209 and 1.7 branch:
> https://github.com/apache/avro/pull/211
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AVRO-2022) IDL does not allow `schema` as identifier
[
https://issues.apache.org/jira/browse/AVRO-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik van Oosten resolved AVRO-2022.
---
Resolution: Invalid
> IDL does not allow `schema` as identifier
> -
>
> Key: AVRO-2022
> URL: https://issues.apache.org/jira/browse/AVRO-2022
> Project: Avro
> Issue Type: Bug
> Components: java
>Affects Versions: 1.7.7, 1.8.1
>Reporter: Erik van Oosten
>
> The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
> following does not compile:
> {noformat}
> record {
>string `schema`;
> }
> {noformat}
> Patches are available for the master branch:
> https://github.com/apache/avro/pull/209 and 1.7 branch:
> https://github.com/apache/avro/pull/211
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AVRO-2022) IDL does not allow `schema` as identifier
[
https://issues.apache.org/jira/browse/AVRO-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik van Oosten updated AVRO-2022:
--
Description:
The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
following does not compile:
{noformat}
record {
string `schema`;
}
{noformat}
Patches are available for the master branch:
https://github.com/apache/avro/pull/209 and 1.7 branch:
https://github.com/apache/avro/pull/211
was:
The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
following does not compile:
{noformat}
record {
string `schema`;
}
{noformat}
Patches are available for the master and 1.7 branches here: (todo)
> IDL does not allow `schema` as identifier
> -
>
> Key: AVRO-2022
> URL: https://issues.apache.org/jira/browse/AVRO-2022
> Project: Avro
> Issue Type: Bug
> Components: java
>Affects Versions: 1.7.7, 1.8.1
>Reporter: Erik van Oosten
>
> The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
> following does not compile:
> {noformat}
> record {
>string `schema`;
> }
> {noformat}
> Patches are available for the master branch:
> https://github.com/apache/avro/pull/209 and 1.7 branch:
> https://github.com/apache/avro/pull/211
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AVRO-2022) IDL does not allow `schema` as identifier
Erik van Oosten created AVRO-2022:
-
Summary: IDL does not allow `schema` as identifier
Key: AVRO-2022
URL: https://issues.apache.org/jira/browse/AVRO-2022
Project: Avro
Issue Type: Bug
Components: java
Affects Versions: 1.8.1, 1.7.7
Reporter: Erik van Oosten
The keyword {{schema}} is now allowed as escaped identifier in IDL. E.g. the
following does not compile:
{noformat}
record {
string `schema`;
}
{noformat}
Patches are available for the master and 1.7 branches here: (todo)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
