avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Monsch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1747) JavaScript implementation
Date Thu, 05 Nov 2015 06:14:27 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991210#comment-14991210

Matthieu Monsch commented on AVRO-1747:

Thanks for the feedback!

1. Will do.
2. Sure, I can do that. Do you have an example of email I could use for this? I'm not familiar
with this process. And this is the only piece of code from outside.
3. The validator's schema property isn't available since it exposes internals of the implementation
and shimming it would mean reimplementing the whole library. We could, though I'm thinking
it'll actually be better then to just include the previous implementation itself and import
it with deprecation warnings. I'll add the previous author back as well.
4. Packaging typically works by running `npm publish` which packages an artifact and publishes
it to NPM's registry. I believe it is possible to split it into two steps: `npm pack`, which
creates a tarball; and `npm publish avro-js.tgz`, which will upload it. This might work better
with the Apache distribution process.

> JavaScript implementation
> -------------------------
>                 Key: AVRO-1747
>                 URL: https://issues.apache.org/jira/browse/AVRO-1747
>             Project: Avro
>          Issue Type: Improvement
>          Components: javascript
>            Reporter: Matthieu Monsch
>         Attachments: AVRO-1747.patch
> Hello,
> I'm not sure if there is still interest in a JavaScript implementation of the Avro spec,
or if this is the right place for this message (apologies if not), but in case it's useful
here is one: https://github.com/mtth/avsc
> It's pretty fast, fully featured aside from protocols (AFAIK), and runs in the browser.
> Disclaimer: I wrote this library. (I initially searched around for existing implementations,
and even saw a few tickets on this board about JavaScript decoders, but couldn't find one
to support the schemas I have to process.)
> Best,
> -Matthieu

This message was sent by Atlassian JIRA

View raw message