You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Douglas Service <ds...@gmail.com> on 2016/10/14 01:31:10 UTC
Re: Protobuf version upgrade?
There is an announcement for new version of .NET called .NET standard 2.0
that appears to follow .NET Core fairly soon https://blogs.msdn.
microsoft.com/dotnet/2016/09/26/introducing-net-standard/ which would make
it much easier for us to continue using Avro with C# and remove the need to
convert all of our current usage of Avro to protobuf. We would most likely
need to pull the code base for the C# version of Avro we currently use into
REEF, fix a small number of compatibility issues (much smaller than for
.NET Core 1.0 or 1.1), and then try to eventually get the features we need
which are different from the Apache Avro C# API merged into Apache Avro.
Thoughts?
Doug
Re: Protobuf version upgrade?
Posted by Gyewon Lee <st...@gmail.com>.
Thank you for response, Douglas. That plan seems good to me.
Best regards,
Gyewon Lee
2016-10-18 8:21 GMT+09:00 Douglas Service <ds...@gmail.com>:
> As a first estimate I would expect that type of functionally to begin
> coming online by the end of the year. It depends on how quickly the work
> goes the extent of which I am still investigating.
>
> Doug
>
> On Thu, Oct 13, 2016 at 8:11 PM, Gyewon Lee <st...@gmail.com> wrote:
>
> > Hi, Douglas.
> >
> > Thank you a lot for notifying us.
> >
> > Actually, there was long lasting need for using some of the new features
> of
> > Apache Avro (like Union) in C# Reef, especially in Tang. How long will it
> > take for C# Reef to support the latest schema of Apache Avro according to
> > this plan?
> >
> > Best regards,
> > Gyewon Lee
> >
> > 2016-10-14 10:31 GMT+09:00 Douglas Service <ds...@gmail.com>:
> >
> > > There is an announcement for new version of .NET called .NET standard
> 2.0
> > > that appears to follow .NET Core fairly soon https://blogs.msdn.
> > > microsoft.com/dotnet/2016/09/26/introducing-net-standard/ which would
> > make
> > > it much easier for us to continue using Avro with C# and remove the
> need
> > to
> > > convert all of our current usage of Avro to protobuf. We would most
> > likely
> > > need to pull the code base for the C# version of Avro we currently use
> > into
> > > REEF, fix a small number of compatibility issues (much smaller than for
> > > .NET Core 1.0 or 1.1), and then try to eventually get the features we
> > need
> > > which are different from the Apache Avro C# API merged into Apache
> Avro.
> > >
> > > Thoughts?
> > >
> > > Doug
> > >
> >
>
>
>
> --
>
> On Mon, Oct 3, 2016 at 5:50 PM, Markus Weimer <ma...@weimo.de> wrote:
> On Mon, Oct 3, 2016 at 4:55 PM, Douglas Service <ds...@gmail.com> wrote:
> > Questions:
> > 1) If the extra messages are not used by both sides they should probably
> > not be in this file. Will these messages be shared in the futur
>
Re: Protobuf version upgrade?
Posted by Douglas Service <ds...@gmail.com>.
As a first estimate I would expect that type of functionally to begin
coming online by the end of the year. It depends on how quickly the work
goes the extent of which I am still investigating.
Doug
On Thu, Oct 13, 2016 at 8:11 PM, Gyewon Lee <st...@gmail.com> wrote:
> Hi, Douglas.
>
> Thank you a lot for notifying us.
>
> Actually, there was long lasting need for using some of the new features of
> Apache Avro (like Union) in C# Reef, especially in Tang. How long will it
> take for C# Reef to support the latest schema of Apache Avro according to
> this plan?
>
> Best regards,
> Gyewon Lee
>
> 2016-10-14 10:31 GMT+09:00 Douglas Service <ds...@gmail.com>:
>
> > There is an announcement for new version of .NET called .NET standard 2.0
> > that appears to follow .NET Core fairly soon https://blogs.msdn.
> > microsoft.com/dotnet/2016/09/26/introducing-net-standard/ which would
> make
> > it much easier for us to continue using Avro with C# and remove the need
> to
> > convert all of our current usage of Avro to protobuf. We would most
> likely
> > need to pull the code base for the C# version of Avro we currently use
> into
> > REEF, fix a small number of compatibility issues (much smaller than for
> > .NET Core 1.0 or 1.1), and then try to eventually get the features we
> need
> > which are different from the Apache Avro C# API merged into Apache Avro.
> >
> > Thoughts?
> >
> > Doug
> >
>
--
On Mon, Oct 3, 2016 at 5:50 PM, Markus Weimer <ma...@weimo.de> wrote:
On Mon, Oct 3, 2016 at 4:55 PM, Douglas Service <ds...@gmail.com> wrote:
> Questions:
> 1) If the extra messages are not used by both sides they should probably
> not be in this file. Will these messages be shared in the futur
Re: Protobuf version upgrade?
Posted by Gyewon Lee <st...@gmail.com>.
Hi, Douglas.
Thank you a lot for notifying us.
Actually, there was long lasting need for using some of the new features of
Apache Avro (like Union) in C# Reef, especially in Tang. How long will it
take for C# Reef to support the latest schema of Apache Avro according to
this plan?
Best regards,
Gyewon Lee
2016-10-14 10:31 GMT+09:00 Douglas Service <ds...@gmail.com>:
> There is an announcement for new version of .NET called .NET standard 2.0
> that appears to follow .NET Core fairly soon https://blogs.msdn.
> microsoft.com/dotnet/2016/09/26/introducing-net-standard/ which would make
> it much easier for us to continue using Avro with C# and remove the need to
> convert all of our current usage of Avro to protobuf. We would most likely
> need to pull the code base for the C# version of Avro we currently use into
> REEF, fix a small number of compatibility issues (much smaller than for
> .NET Core 1.0 or 1.1), and then try to eventually get the features we need
> which are different from the Apache Avro C# API merged into Apache Avro.
>
> Thoughts?
>
> Doug
>
Re: Protobuf version upgrade?
Posted by Boris Shulman <sh...@gmail.com>.
The question is what .NET core version will support .NET standard 2.0 and when it will be available.
Sent from my iPhone
> On Oct 13, 2016, at 6:31 PM, Douglas Service <ds...@gmail.com> wrote:
>
> There is an announcement for new version of .NET called .NET standard 2.0
> that appears to follow .NET Core fairly soon https://blogs.msdn.
> microsoft.com/dotnet/2016/09/26/introducing-net-standard/ which would make
> it much easier for us to continue using Avro with C# and remove the need to
> convert all of our current usage of Avro to protobuf. We would most likely
> need to pull the code base for the C# version of Avro we currently use into
> REEF, fix a small number of compatibility issues (much smaller than for
> .NET Core 1.0 or 1.1), and then try to eventually get the features we need
> which are different from the Apache Avro C# API merged into Apache Avro.
>
> Thoughts?
>
> Doug