Re: Interoperable Ignite.NET Dates

Pavel, Thank you for your positive feedback! I will create an IEP. вт, 3 нояб. 2020 г. в 15:48, Pavel Tupitsyn : > Alexey, > > The proposal looks good to me. > > Usually I would try to avoid extra dependencies in the core assembly, > but NodaTime seems to be worth it. > > Would you like to

Re: Interoperable Ignite.NET Dates

Alexey, The proposal looks good to me. Usually I would try to avoid extra dependencies in the core assembly, but NodaTime seems to be worth it. Would you like to prepare an IEP? Thanks, Pavel On Tue, Nov 3, 2020 at 3:15 PM Alexey Kukushkin wrote: > We already created tickets and tested

Re: Interoperable Ignite.NET Dates

We already created tickets and tested the proposed solution with our applications (already in PROD) and an internal fork of Ignite. This discussion is a proposal to donate this change to open source Apache Ignite is the community accepts it: - IGNITE-12824 .NET: Write DateTime in interoperable

Re: Interoperable Ignite.NET Dates

Cool, makes sense to me then. Please feel free to create a ticket and mark it with the "ignite-3" label. -Val On Tue, Nov 3, 2020 at 4:03 AM Alexey Kukushkin wrote: > Val, absolutely - our proposal affects .NET API only. > > вт, 3 нояб. 2020 г. в 15:00, Valentin Kulichenko < >

Re: Interoperable Ignite.NET Dates

Val, absolutely - our proposal affects .NET API only. вт, 3 нояб. 2020 г. в 15:00, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Got it. So it only affects the .NET side, correct? > > -Val > > On Tue, Nov 3, 2020 at 3:52 AM Alexey Kukushkin > > wrote: > > > Hi Val, > > > > Our

Re: Interoperable Ignite.NET Dates

Got it. So it only affects the .NET side, correct? -Val On Tue, Nov 3, 2020 at 3:52 AM Alexey Kukushkin wrote: > Hi Val, > > Our proposal does not overlap with IEP-54 > < > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach > >, > which proposes changing Ignite

Re: Interoperable Ignite.NET Dates

Hi Val, Our proposal does not overlap with IEP-54 , which proposes changing Ignite date storage format. Our proposal is enhancing Ignite to handle .NET dates in a truly portable way instead of requiring the

Re: Interoperable Ignite.NET Dates

Hi Alexey, The IEP-54 [1] describes the data layout proposed for Ignite 3.0, it includes various date/time types. Can you please take a look and check if this addresses your concerns? We can then discuss further if needed.

Re: Interoperable Ignite.NET Dates

Pavel, We propose changing public API so this is for Ignite 3.0. Thanks! вт, 3 нояб. 2020 г. в 02:17, Pavel Tupitsyn : > Alexey, > > Just to clarify before we start the discussion: > this proposal seems to introduce some breaking changes, so we are talking > about Ignite 3.0, correct? > >

Re: Interoperable Ignite.NET Dates

Alexey, Just to clarify before we start the discussion: this proposal seems to introduce some breaking changes, so we are talking about Ignite 3.0, correct? Pavel On Tue, Nov 3, 2020 at 12:13 AM Alexey Kukushkin wrote: > Igniters, > > What do you think about changing .NET API to read/write

Interoperable Ignite.NET Dates

Igniters, What do you think about changing .NET API to read/write portable dates by default and making that really portable? *The Problem* Presently .NET API writes dates as composite Ignite objects. Only .NET clients can read such dates: any other client (JDBC, Java, etc) does not understand it