Hi,
For a Ruby project, I am using AVRO schemas to validate Ruby objects. Because I
ran into some issues with the official avro gem, so I forked it:
https://github.com/wvanbergen/tros. (The name probably only makes sense to
Dutch people :)
### Changes
- Fixed a round trip encoding issue for
how far back did you fork?
could we have a Ruby 1.8 gem and a Ruby 1.9+ gem?
we have python and python 3 support broken out, for example.
On Wed, Jun 25, 2014 at 3:51 AM, Willem van Bergen wil...@vanbergen.org
wrote:
Hi,
For a Ruby project, I am using AVRO schemas to validate Ruby objects.
I forked off trunk 2 days ago.
It's possible to have 2 different gems, but this is not very common in the Ruby
world. Because Ruby 1.8 is not maintained anymore, not even for security
issues, most people have moved on to newer versions. This is in contrast with
Python 2, which is still
IIRC, the multijson issue is fixed in the current snapshot.
I dunno, I certainly stopped using Ruby 1.8 several years ago. The issue is
that Avro has a strong history of favoring compatibility. It would be
surprising for us to drop Ruby 1.8 support while still in the Avro 1.7 line.
We could plan
[
https://issues.apache.org/jira/browse/AVRO-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
O. Reißig updated AVRO-1532:
Attachment: RemovalOfUnionSubtype.java
Thanks for your suggestion with AvroAlias, that's a lot better than
Dropping support for Ruby 1.8 in the Avro 1.8.x series sounds like a plan. Is
there already a branch for the 1.8 series?
Until that time happens, I can maintain my fork for people requiring unicode
UTF support on Ruby 1.9+.
I know the multi_json issue is fixed in trunk. However, due to the
[
https://issues.apache.org/jira/browse/AVRO-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043745#comment-14043745
]
Thunder Stumpges commented on AVRO-1124:
Hi Francois, I noticed you applied these
[
https://issues.apache.org/jira/browse/AVRO-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043777#comment-14043777
]
Thunder Stumpges commented on AVRO-1124:
Hi Felix, was just reading through
[
https://issues.apache.org/jira/browse/AVRO-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043801#comment-14043801
]
Felix GV commented on AVRO-1124:
Hi Thunder,
Disclaimer: I don't work for Mate1 anymore,
There isn't a branch for 1.8. Patches that target that version just get
generated based on trunk and attached to tickets with a fix version of
1.8.0. Generally, they also get hte incompatible flag.
Sure, I agree that using the unreleased versions isn't tenable. Doug made a
call for a 1.7.7
On Wed, Jun 25, 2014 at 2:16 AM, Willem van Bergen wil...@vanbergen.org wrote:
It's possible to have 2 different gems, but this is not very common in the
Ruby world.
Because Ruby 1.8 is not maintained anymore, not even for security issues, most
people have moved on to newer versions.
I can
[
https://issues.apache.org/jira/browse/AVRO-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044190#comment-14044190
]
Doug Cutting commented on AVRO-1124:
BTW, are we expecting AVRO-1124 to end up in an
[
https://issues.apache.org/jira/browse/AVRO-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044193#comment-14044193
]
Doug Cutting commented on AVRO-1530:
That would be an incompatible change. Some folks
[
https://issues.apache.org/jira/browse/AVRO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sachin Goyal updated AVRO-695:
--
Attachment: circular_refs_and_nonstring_map_keys_2014_06_25.zip
Cycle Reference Support
[
https://issues.apache.org/jira/browse/AVRO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044266#comment-14044266
]
Sachin Goyal commented on AVRO-695:
---
h3.Circular References
Personally, I'd rather see #2.
I think it's very hard to know what the current use of Ruby 1.8 is. Support
from the MRI community only ended ~1 year ago[1]. JRuby still supports
running in 1.8 mode. They'll be dropping it in their next major release,
but there isn't a schedule for that yet and
16 matches
Mail list logo
