Ryan Blue created AVRO-1789:
---
Summary: Publish JS documentation
Key: AVRO-1789
URL: https://issues.apache.org/jira/browse/AVRO-1789
Project: Avro
Issue Type: Bug
Components: js
Hi Ryan
Thanks for your answer. Here is what i am doing in my environment
1. Write the data using the old schema
*SpecificDatumWriter datumWriter = new
SpecificDatumWriter<>(SCHEMA_V1)*
2. Now trying to read the data written by the old schema using the new
schema
*DatumReader payloadReader =
Ryan Blue created AVRO-1790:
---
Summary: Publish avro-js to NPM
Key: AVRO-1790
URL: https://issues.apache.org/jira/browse/AVRO-1790
Project: Avro
Issue Type: Task
Components: js
[
https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128691#comment-15128691
]
Ryan Blue commented on AVRO-1778:
-
Having a look now.
> IPC/RPC for JavaScript
> --
>
[
https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129054#comment-15129054
]
Ryan Blue commented on AVRO-1778:
-
This looks mostly good to me. Tests pass and coverage is at 100%
Sebb created AVRO-1791:
--
Summary: Please delete old releases from mirroring system
Key: AVRO-1791
URL: https://issues.apache.org/jira/browse/AVRO-1791
Project: Avro
Issue Type: Bug
Affects
Great, Thank you very much guys, this works. Very much appreciated.
On Tue, Feb 2, 2016 at 12:46 PM, kulkarni.swar...@gmail.com <
kulkarni.swar...@gmail.com> wrote:
> Raghvendra,
>
> You need to use
>
> *DatumReader payloadReader = new
> SpecificDatumReader<>(SCHEMA_V1, **SCHEMA_V2**)*
>
> So
Kevin J. Price created AVRO-1792:
Summary: Cannot specify a 'null' default value
Key: AVRO-1792
URL: https://issues.apache.org/jira/browse/AVRO-1792
Project: Avro
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AVRO-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin J. Price updated AVRO-1792:
-
Description:
Using the new Schema.Field constructors added in 1.8.0, it is no longer
possible to
+1
Tom
On Mon, Feb 1, 2016 at 8:02 PM, Ryan Blue wrote:
> Hi everyone,
>
> A couple months ago, on the "Release and code management" discussion thread
> [1], I suggested moving Avro to git. Everyone was for the idea on that
> thread and now that the 1.8.0 release is finished I
Thanks for asking, Nicolae!
You're looking in the right place for bugs. I recommend choosing an
implementation (python, avro, C, JS, Java, etc) and learning that first.
You can typically know whether someone intends to work on a bug or
feature if they have assigned it to themselves, but when
+1
On Mon, Feb 1, 2016, at 03:02 PM, Ryan Blue wrote:
> Hi everyone,
>
> A couple months ago, on the "Release and code management" discussion
> thread [1], I suggested moving Avro to git. Everyone was for the idea on
> that thread and now that the 1.8.0 release is finished I think we can
>
+1, yes please!
> On 1 Feb 2016, at 20:02, Ryan Blue wrote:
>
> Hi everyone,
>
> A couple months ago, on the "Release and code management" discussion thread
> [1], I suggested moving Avro to git. Everyone was for the idea on that thread
> and now that the 1.8.0 release is
13 matches
Mail list logo