You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Driesprong, Fokko" <fo...@driesprong.frl> on 2019/03/26 13:31:32 UTC

Feature freeze Apache Avro 1.9

Hi all,

I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
start moving to a release candidate so we can test. If there are any
features that you would like to get in, please let me know.

Cheers, Fokko

Re: Feature freeze Apache Avro 1.9

Posted by Martin Tzvetanov Grigorov <mg...@apache.org>.
Hi,


On 2019/03/29 21:26:02, "Driesprong, Fokko" <fo...@driesprong.frl> wrote: 
> Thanks all for the feedback.
> 
> Regarding the discussion Joda time, I've made a PR to completely remove the
> Joda dependency: https://github.com/apache/avro/pull/495
> 
> What do you guys think, could we push this for 1.9? This would obviously
> break backward compatibility, but then again, people should not use Joda
> time anymore.

New projects should not use Joda, but some old projects still use/support it. 

I'd suggest to keep Joda conversions in 1.9 (as Deprecated, maybe) and drop them in 1.10.
This way you would give people chance to upgrade and migrate in their own pace. Doing a big upgrade+migrate usually is a pain and people just stay with the old version.

Looking forward for 1.9 to being released!
Thank you!

Regards,
Martin

> 
> Cheers, Fokko
> 
> Op vr 29 mrt. 2019 om 10:37 schreef Nandor Kollar
> <nk...@cloudera.com.invalid>:
> 
> > I totally support making JSR310 as the default instead of Joda
> > time. Should we consider removing the JSR310 from the class names, for
> > example rename Jsr310TimeConversions to TimeConversions and the existing
> > TimeConversions to JodaTimeConversions, and deprecate the latter?
> >
> > On Thu, Mar 28, 2019 at 6:53 PM Daniel Kulp <dk...@apache.org> wrote:
> >
> > > I made few commits today that change the generated code from the Schema
> > > compiler a bit….  The changes make Avro 1.9 a bit more incompatible with
> > > 1.8, but since they are going to have to migrate anyway, I thought it
> > would
> > > be important to make the changes now rather then forcing everyone to do
> > so
> > > in 1.10.   The changes:
> > >
> > > 1) Default for “time” classes change from Joda to JSR310.  There is a
> > flag
> > > to specify joda if they need/want it, but I think the “default” should be
> > > what we plan on supporting going forward, and I don’t think joda should
> > be
> > > it.     At this point, joda should go away.  :)
> > >
> > > 2) Private fields  - we were, by default, generating “@Deprecated public”
> > > fields.   The idea of generating deprecated code by default annoys me.
> > >  Thus, I changed the default to “private”.  Again, there is a setting to
> > > make them public (or deprecated/public) if they want it, but for the
> > > default, I believe private is what we want.
> > >
> > > While those will increase the effort to migrate from 1.8 to 1.9, I think
> > > it’s better to do that now than waiting any longer.
> > >
> > > Thoughts?
> > > Dan
> > >
> > >
> > > > On Mar 26, 2019, at 9:31 AM, Driesprong, Fokko <fo...@driesprong.frl>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> > > > start moving to a release candidate so we can test. If there are any
> > > > features that you would like to get in, please let me know.
> > > >
> > > > Cheers, Fokko
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <
> > > http://dankulp.com/blog>
> > > Talend Community Coder - http://talend.com <http://coders.talend.com/>
> > >
> >
> 

Re: Feature freeze Apache Avro 1.9

Posted by Ivan Greene <ig...@fanthreesixty.com>.
Just to clarify, the UUID logical type was included in 1.8.2 (and perhaps a release prior to that?), it was just undocumented. So I think one option could be providing a conversion both to/from string and to/from 16-length fixed, similar to the way that the decimal type provides conversion to/from fixed as well as to/from bytes, which can be chosen by the user.

—Ivan

> On Apr 9, 2019, at 9:02 AM, Driesprong, Fokko <fo...@driesprong.frl> wrote:
> 
> Hi Ivan,
> 
> Thanks for the input. Personally, I'm not using the UUID at all. Any
> comments on it Ryan? Since it isn't introduced in any release, we could
> remove it if there is a consensus if it doesn't add any value to the Avro
> format.
> 
> Apart from that, I did some testing last week on some internal projects,
> and it went surprisingly well. I would like to proceed into cutting a first
> RC.
> 
> Cheers, Fokko
> 
> Op di 2 apr. 2019 om 03:49 schreef Ivan Greene <ig...@fanthreesixty.com>:
> 
>> Somehow only now after I sent this last message did I realize the
>> conversion can already be controlled by adding the LogicalType to
>> ReflectData as in TestReflectLogicalTypes.java :) So never mind on that
>> second part.
>> 
>> However it's worth making a consideration about whether we are interested
>> in revising the UUID logicalType to be 16-byte fixed rather than a 36-byte
>> string before it is documented in this release.
>> 
>> -- Ivan
>> 
>> On Mon, Apr 1, 2019 at 8:30 PM Ivan Greene <ig...@fanthreesixty.com>
>> wrote:
>> 
>>> Another outstanding bit for the release in my mind is the state of the
>>> UUID logicalType. As Ryan commented here:
>>> 
>> https://issues.apache.org/jira/browse/AVRO-2021?focusedCommentId=16242524&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242524
>>> there is currently an implemented logical type of 'uuid', however it uses
>>> the naive toString/fromString rather than a more compact 16-byte fixed. I
>>> think we should think about whether we really need this logical type as
>> it
>>> doesn't provide much benefit as it is. What do you think?
>>> 
>>> Related is UUID support for ReflectData, which is currently nil (we
>> cannot
>>> even annotate @Stringable; UUID has no String constructor). Basically the
>>> only option for using UUIDs in ReflectData is the user implementing their
>>> own CustomEncoding. A long unanswered query on another Jira is here:
>>> 
>> https://issues.apache.org/jira/browse/AVRO-1497?focusedCommentId=16283656&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16283656
>>> We could either:
>>> - Provide CustomEncoding implementation(s), such as UUIDAsStringEncoding
>>> and/or UUIDAsFixedEncoding
>>> - Add support for LogicalTypes in ReflectData definitions, through a new
>>> annotation a la @AvroLogicalType("timestamp-millis"), etc. where we can
>> use
>>> the uuid logicalType if we decide to keep that in
>>> 
>>> Taking a look at the history it seems as though LogicalTypes and
>>> CustomEncodings share some of the same intentions. It's not clear what
>> the
>>> better option is in this case. CustomEncoding predates LogicalType by a
>> few
>>> years, but CustomEncoding is more Java-centric.
>>> 
>>> Please let me know what the thoughts are. I should have some time to work
>>> on what we decide on this week. Would like to get these items in for 1.9.
>>> 
>>> -- Ivan
>>> 
>> 


Re: Feature freeze Apache Avro 1.9

Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
Hi Ivan,

Thanks for the input. Personally, I'm not using the UUID at all. Any
comments on it Ryan? Since it isn't introduced in any release, we could
remove it if there is a consensus if it doesn't add any value to the Avro
format.

Apart from that, I did some testing last week on some internal projects,
and it went surprisingly well. I would like to proceed into cutting a first
RC.

Cheers, Fokko

Op di 2 apr. 2019 om 03:49 schreef Ivan Greene <ig...@fanthreesixty.com>:

> Somehow only now after I sent this last message did I realize the
> conversion can already be controlled by adding the LogicalType to
> ReflectData as in TestReflectLogicalTypes.java :) So never mind on that
> second part.
>
> However it's worth making a consideration about whether we are interested
> in revising the UUID logicalType to be 16-byte fixed rather than a 36-byte
> string before it is documented in this release.
>
> -- Ivan
>
> On Mon, Apr 1, 2019 at 8:30 PM Ivan Greene <ig...@fanthreesixty.com>
> wrote:
>
> > Another outstanding bit for the release in my mind is the state of the
> > UUID logicalType. As Ryan commented here:
> >
> https://issues.apache.org/jira/browse/AVRO-2021?focusedCommentId=16242524&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242524
> > there is currently an implemented logical type of 'uuid', however it uses
> > the naive toString/fromString rather than a more compact 16-byte fixed. I
> > think we should think about whether we really need this logical type as
> it
> > doesn't provide much benefit as it is. What do you think?
> >
> > Related is UUID support for ReflectData, which is currently nil (we
> cannot
> > even annotate @Stringable; UUID has no String constructor). Basically the
> > only option for using UUIDs in ReflectData is the user implementing their
> > own CustomEncoding. A long unanswered query on another Jira is here:
> >
> https://issues.apache.org/jira/browse/AVRO-1497?focusedCommentId=16283656&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16283656
> > We could either:
> > - Provide CustomEncoding implementation(s), such as UUIDAsStringEncoding
> > and/or UUIDAsFixedEncoding
> > - Add support for LogicalTypes in ReflectData definitions, through a new
> > annotation a la @AvroLogicalType("timestamp-millis"), etc. where we can
> use
> > the uuid logicalType if we decide to keep that in
> >
> > Taking a look at the history it seems as though LogicalTypes and
> > CustomEncodings share some of the same intentions. It's not clear what
> the
> > better option is in this case. CustomEncoding predates LogicalType by a
> few
> > years, but CustomEncoding is more Java-centric.
> >
> > Please let me know what the thoughts are. I should have some time to work
> > on what we decide on this week. Would like to get these items in for 1.9.
> >
> > -- Ivan
> >
>

Re: Feature freeze Apache Avro 1.9

Posted by Ivan Greene <ig...@fanthreesixty.com>.
Somehow only now after I sent this last message did I realize the
conversion can already be controlled by adding the LogicalType to
ReflectData as in TestReflectLogicalTypes.java :) So never mind on that
second part.

However it's worth making a consideration about whether we are interested
in revising the UUID logicalType to be 16-byte fixed rather than a 36-byte
string before it is documented in this release.

-- Ivan

On Mon, Apr 1, 2019 at 8:30 PM Ivan Greene <ig...@fanthreesixty.com>
wrote:

> Another outstanding bit for the release in my mind is the state of the
> UUID logicalType. As Ryan commented here:
> https://issues.apache.org/jira/browse/AVRO-2021?focusedCommentId=16242524&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242524
> there is currently an implemented logical type of 'uuid', however it uses
> the naive toString/fromString rather than a more compact 16-byte fixed. I
> think we should think about whether we really need this logical type as it
> doesn't provide much benefit as it is. What do you think?
>
> Related is UUID support for ReflectData, which is currently nil (we cannot
> even annotate @Stringable; UUID has no String constructor). Basically the
> only option for using UUIDs in ReflectData is the user implementing their
> own CustomEncoding. A long unanswered query on another Jira is here:
> https://issues.apache.org/jira/browse/AVRO-1497?focusedCommentId=16283656&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16283656
> We could either:
> - Provide CustomEncoding implementation(s), such as UUIDAsStringEncoding
> and/or UUIDAsFixedEncoding
> - Add support for LogicalTypes in ReflectData definitions, through a new
> annotation a la @AvroLogicalType("timestamp-millis"), etc. where we can use
> the uuid logicalType if we decide to keep that in
>
> Taking a look at the history it seems as though LogicalTypes and
> CustomEncodings share some of the same intentions. It's not clear what the
> better option is in this case. CustomEncoding predates LogicalType by a few
> years, but CustomEncoding is more Java-centric.
>
> Please let me know what the thoughts are. I should have some time to work
> on what we decide on this week. Would like to get these items in for 1.9.
>
> -- Ivan
>

Re: Feature freeze Apache Avro 1.9

Posted by Ivan Greene <ig...@fanthreesixty.com>.
Another outstanding bit for the release in my mind is the state of the UUID
logicalType. As Ryan commented here:
https://issues.apache.org/jira/browse/AVRO-2021?focusedCommentId=16242524&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242524
there is currently an implemented logical type of 'uuid', however it uses
the naive toString/fromString rather than a more compact 16-byte fixed. I
think we should think about whether we really need this logical type as it
doesn't provide much benefit as it is. What do you think?

Related is UUID support for ReflectData, which is currently nil (we cannot
even annotate @Stringable; UUID has no String constructor). Basically the
only option for using UUIDs in ReflectData is the user implementing their
own CustomEncoding. A long unanswered query on another Jira is here:
https://issues.apache.org/jira/browse/AVRO-1497?focusedCommentId=16283656&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16283656
We could either:
- Provide CustomEncoding implementation(s), such as UUIDAsStringEncoding
and/or UUIDAsFixedEncoding
- Add support for LogicalTypes in ReflectData definitions, through a new
annotation a la @AvroLogicalType("timestamp-millis"), etc. where we can use
the uuid logicalType if we decide to keep that in

Taking a look at the history it seems as though LogicalTypes and
CustomEncodings share some of the same intentions. It's not clear what the
better option is in this case. CustomEncoding predates LogicalType by a few
years, but CustomEncoding is more Java-centric.

Please let me know what the thoughts are. I should have some time to work
on what we decide on this week. Would like to get these items in for 1.9.

-- Ivan

Re: Feature freeze Apache Avro 1.9

Posted by Ivan Greene <ig...@fanthreesixty.com>.
Hi Fokko, just now seeing your original email about features for 1.9. I have a small enhancement to ReflectData's protocol building ready for review here: https://github.com/apache/avro/pull/490 <https://github.com/apache/avro/pull/490>

I also opened a Jira earlier today about enhancements to the new ‘induce’ maven goal in the plugin: https://issues.apache.org/jira/browse/AVRO-2365 <https://issues.apache.org/jira/browse/AVRO-2365>

I would love to address at least a few of the items listed in that Jira before 1.9 is ultimately released, as the induce goal is an entirely new feature and we should make it as usable as possible out of the gate. I will try to get a PR opened up this weekend for those.

—Ivan

> On Mar 29, 2019, at 4:26 PM, Driesprong, Fokko <fo...@driesprong.frl> wrote:
> 
> Thanks all for the feedback.
> 
> Regarding the discussion Joda time, I've made a PR to completely remove the
> Joda dependency: https://github.com/apache/avro/pull/495
> 
> What do you guys think, could we push this for 1.9? This would obviously
> break backward compatibility, but then again, people should not use Joda
> time anymore.
> 
> Cheers, Fokko
> 
> Op vr 29 mrt. 2019 om 10:37 schreef Nandor Kollar
> <nk...@cloudera.com.invalid>:
> 
>> I totally support making JSR310 as the default instead of Joda
>> time. Should we consider removing the JSR310 from the class names, for
>> example rename Jsr310TimeConversions to TimeConversions and the existing
>> TimeConversions to JodaTimeConversions, and deprecate the latter?
>> 
>> On Thu, Mar 28, 2019 at 6:53 PM Daniel Kulp <dk...@apache.org> wrote:
>> 
>>> I made few commits today that change the generated code from the Schema
>>> compiler a bit….  The changes make Avro 1.9 a bit more incompatible with
>>> 1.8, but since they are going to have to migrate anyway, I thought it
>> would
>>> be important to make the changes now rather then forcing everyone to do
>> so
>>> in 1.10.   The changes:
>>> 
>>> 1) Default for “time” classes change from Joda to JSR310.  There is a
>> flag
>>> to specify joda if they need/want it, but I think the “default” should be
>>> what we plan on supporting going forward, and I don’t think joda should
>> be
>>> it.     At this point, joda should go away.  :)
>>> 
>>> 2) Private fields  - we were, by default, generating “@Deprecated public”
>>> fields.   The idea of generating deprecated code by default annoys me.
>>> Thus, I changed the default to “private”.  Again, there is a setting to
>>> make them public (or deprecated/public) if they want it, but for the
>>> default, I believe private is what we want.
>>> 
>>> While those will increase the effort to migrate from 1.8 to 1.9, I think
>>> it’s better to do that now than waiting any longer.
>>> 
>>> Thoughts?
>>> Dan
>>> 
>>> 
>>>> On Mar 26, 2019, at 9:31 AM, Driesprong, Fokko <fo...@driesprong.frl>
>>> wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
>>>> start moving to a release candidate so we can test. If there are any
>>>> features that you would like to get in, please let me know.
>>>> 
>>>> Cheers, Fokko
>>> 
>>> --
>>> Daniel Kulp
>>> dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <
>>> http://dankulp.com/blog>
>>> Talend Community Coder - http://talend.com <http://coders.talend.com/>
>>> 
>> 


Re: Feature freeze Apache Avro 1.9

Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
Thanks all for the feedback.

Regarding the discussion Joda time, I've made a PR to completely remove the
Joda dependency: https://github.com/apache/avro/pull/495

What do you guys think, could we push this for 1.9? This would obviously
break backward compatibility, but then again, people should not use Joda
time anymore.

Cheers, Fokko

Op vr 29 mrt. 2019 om 10:37 schreef Nandor Kollar
<nk...@cloudera.com.invalid>:

> I totally support making JSR310 as the default instead of Joda
> time. Should we consider removing the JSR310 from the class names, for
> example rename Jsr310TimeConversions to TimeConversions and the existing
> TimeConversions to JodaTimeConversions, and deprecate the latter?
>
> On Thu, Mar 28, 2019 at 6:53 PM Daniel Kulp <dk...@apache.org> wrote:
>
> > I made few commits today that change the generated code from the Schema
> > compiler a bit….  The changes make Avro 1.9 a bit more incompatible with
> > 1.8, but since they are going to have to migrate anyway, I thought it
> would
> > be important to make the changes now rather then forcing everyone to do
> so
> > in 1.10.   The changes:
> >
> > 1) Default for “time” classes change from Joda to JSR310.  There is a
> flag
> > to specify joda if they need/want it, but I think the “default” should be
> > what we plan on supporting going forward, and I don’t think joda should
> be
> > it.     At this point, joda should go away.  :)
> >
> > 2) Private fields  - we were, by default, generating “@Deprecated public”
> > fields.   The idea of generating deprecated code by default annoys me.
> >  Thus, I changed the default to “private”.  Again, there is a setting to
> > make them public (or deprecated/public) if they want it, but for the
> > default, I believe private is what we want.
> >
> > While those will increase the effort to migrate from 1.8 to 1.9, I think
> > it’s better to do that now than waiting any longer.
> >
> > Thoughts?
> > Dan
> >
> >
> > > On Mar 26, 2019, at 9:31 AM, Driesprong, Fokko <fo...@driesprong.frl>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> > > start moving to a release candidate so we can test. If there are any
> > > features that you would like to get in, please let me know.
> > >
> > > Cheers, Fokko
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <
> > http://dankulp.com/blog>
> > Talend Community Coder - http://talend.com <http://coders.talend.com/>
> >
>

Re: Feature freeze Apache Avro 1.9

Posted by Nandor Kollar <nk...@cloudera.com.INVALID>.
I totally support making JSR310 as the default instead of Joda
time. Should we consider removing the JSR310 from the class names, for
example rename Jsr310TimeConversions to TimeConversions and the existing
TimeConversions to JodaTimeConversions, and deprecate the latter?

On Thu, Mar 28, 2019 at 6:53 PM Daniel Kulp <dk...@apache.org> wrote:

> I made few commits today that change the generated code from the Schema
> compiler a bit….  The changes make Avro 1.9 a bit more incompatible with
> 1.8, but since they are going to have to migrate anyway, I thought it would
> be important to make the changes now rather then forcing everyone to do so
> in 1.10.   The changes:
>
> 1) Default for “time” classes change from Joda to JSR310.  There is a flag
> to specify joda if they need/want it, but I think the “default” should be
> what we plan on supporting going forward, and I don’t think joda should be
> it.     At this point, joda should go away.  :)
>
> 2) Private fields  - we were, by default, generating “@Deprecated public”
> fields.   The idea of generating deprecated code by default annoys me.
>  Thus, I changed the default to “private”.  Again, there is a setting to
> make them public (or deprecated/public) if they want it, but for the
> default, I believe private is what we want.
>
> While those will increase the effort to migrate from 1.8 to 1.9, I think
> it’s better to do that now than waiting any longer.
>
> Thoughts?
> Dan
>
>
> > On Mar 26, 2019, at 9:31 AM, Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
> >
> > Hi all,
> >
> > I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> > start moving to a release candidate so we can test. If there are any
> > features that you would like to get in, please let me know.
> >
> > Cheers, Fokko
>
> --
> Daniel Kulp
> dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <
> http://dankulp.com/blog>
> Talend Community Coder - http://talend.com <http://coders.talend.com/>
>

Re: Feature freeze Apache Avro 1.9

Posted by Daniel Kulp <dk...@apache.org>.
I made few commits today that change the generated code from the Schema compiler a bit….  The changes make Avro 1.9 a bit more incompatible with 1.8, but since they are going to have to migrate anyway, I thought it would be important to make the changes now rather then forcing everyone to do so in 1.10.   The changes:

1) Default for “time” classes change from Joda to JSR310.  There is a flag to specify joda if they need/want it, but I think the “default” should be what we plan on supporting going forward, and I don’t think joda should be it.     At this point, joda should go away.  :)

2) Private fields  - we were, by default, generating “@Deprecated public” fields.   The idea of generating deprecated code by default annoys me.   Thus, I changed the default to “private”.  Again, there is a setting to make them public (or deprecated/public) if they want it, but for the default, I believe private is what we want.

While those will increase the effort to migrate from 1.8 to 1.9, I think it’s better to do that now than waiting any longer.   

Thoughts?
Dan


> On Mar 26, 2019, at 9:31 AM, Driesprong, Fokko <fo...@driesprong.frl> wrote:
> 
> Hi all,
> 
> I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> start moving to a release candidate so we can test. If there are any
> features that you would like to get in, please let me know.
> 
> Cheers, Fokko

-- 
Daniel Kulp
dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
Talend Community Coder - http://talend.com <http://coders.talend.com/>

Re: Feature freeze Apache Avro 1.9

Posted by suraj acharya <su...@gmail.com>.
Agree
-Suraj Acharya


On Tue, Mar 26, 2019 at 8:27 AM Ismaël Mejía <ie...@gmail.com> wrote:

> Thanks for taking care of this Fokko, I am really excited of getting a
> new version out!
>
> I went through the list of open issues that are tagged for 2.9.0
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.9.0
>
> Can others contributors please take a look at that list and update the
> "Fix version" field to 2.10.0 if the fix won't be able to be in place
> before the cut, or leave without version if not sure when this will be
> done. This way we can track what is missing that should get in too.
>
> Thanks,
>
> On Tue, Mar 26, 2019 at 2:31 PM Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
> >
> > Hi all,
> >
> > I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> > start moving to a release candidate so we can test. If there are any
> > features that you would like to get in, please let me know.
> >
> > Cheers, Fokko
>

Re: Feature freeze Apache Avro 1.9

Posted by Ismaël Mejía <ie...@gmail.com>.
Thanks for taking care of this Fokko, I am really excited of getting a
new version out!

I went through the list of open issues that are tagged for 2.9.0

https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.9.0

Can others contributors please take a look at that list and update the
"Fix version" field to 2.10.0 if the fix won't be able to be in place
before the cut, or leave without version if not sure when this will be
done. This way we can track what is missing that should get in too.

Thanks,

On Tue, Mar 26, 2019 at 2:31 PM Driesprong, Fokko <fo...@driesprong.frl> wrote:
>
> Hi all,
>
> I'd like to cut the branch for Apache Avro 1.9 release this Friday, and
> start moving to a release candidate so we can test. If there are any
> features that you would like to get in, please let me know.
>
> Cheers, Fokko