[ https://issues.apache.org/jira/browse/AVRO-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851347#comment-13851347 ]
Sean Busbey commented on AVRO-1063: ----------------------------------- I tested this with a few different json providing backends on MRI and JRuby 1.7.3. tests all passed fine. I thought the dependencies for this new version of the gem properly specified multi-json as a dependency that would be pulled in by the Gem utils when a user upgraded. If that's the case would it be sufficiently compatible? Or is a dependency change itself incompatible? > Ruby client should use multi_json rather than being locked down to yajl > ----------------------------------------------------------------------- > > Key: AVRO-1063 > URL: https://issues.apache.org/jira/browse/AVRO-1063 > Project: Avro > Issue Type: Improvement > Components: ruby > Reporter: Paul Dlug > Priority: Minor > Fix For: 1.8.0 > > Attachments: AVRO-1063.diff > > > The avro ruby client uses yajl for JSON serialization which is just one of > many suitable JSON implementations for ruby. The multi_json gem provides a > wrapper for JSON serialization selecting the fastest library available (Oj is > now even faster than Yajl) and falling back to a pure ruby implementation > bundled with multi_json. Requiring yajl also precludes the ruby gem from > being used under jruby since it requires a C extension. -- This message was sent by Atlassian JIRA (v6.1.4#6159)