Apache Ignite 1.8 Release

[dmagda]

Igniters,

Looking at the discussions that happen on our dev list regarding Ignite's improvements I should say that we’re ready to prepare and roll out one more Ignite minor release before the end of the year - Apache Ignite 1.8.0. My proposal is to make it available by mid November, somewhere around November 21st.

Personally, the following features have to be included in it due to the importance and readiness:
DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <https://issues.apache.org/jira/browse/IGNITE-2294>
PHP PDO Support from ODBC side: https://issues.apache.org/jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
Ignite as a second level cache for .NET Entity Framework: https://issues.apache.org/jira/browse/IGNITE-1915 <https://issues.apache.org/jira/browse/IGNITE-1915>

The first feature make it realistic to execute INSERT, UPDATE, DELETE queries over Ignite caches using Java APIs or by connecting to a cluster using JDBC or ODBC drivers and send DML queries not only from Java side but from a variety of technologies and tools. As an example, the second feature from the list is intended to enable support for PHP by mixing DML with SELECT SQL queries plus sending them over Ignite’s ODBC driver.

The third feature will allow to broaden the usage of Apache Ignite .NET client among .NET community by providing more advanced support for .NET Entity Framework.

Feature owners of the above mentioned tickets, please provide the current status on them?

If anyone else wants to see something else as a part of Ignite 1.8 and ready to contribute it by the mid of November please reply to the thread as well.

Regards,
Denis

[Pavel Tupitsyn]

IGNITE-1915 is being reviewed, I think we can make it into 1.8.

On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda <[hidden email]> wrote:

> Igniters,
>
> Looking at the discussions that happen on our dev list regarding Ignite's
> improvements I should say that we’re ready to prepare and roll out one more
> Ignite minor release before the end of the year - Apache Ignite 1.8.0. My
> proposal is to make it available by mid November, somewhere around November
> 21st.
>
> Personally, the following features have to be included in it due to the
> importance and readiness:
> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
> https://issues.apache.org/jira/browse/IGNITE-2294>
> PHP PDO Support from ODBC side: https://issues.apache.org/
> jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865
> >
> Ignite as a second level cache for .NET Entity Framework:
> https://issues.apache.org/jira/browse/IGNITE-1915 <
> https://issues.apache.org/jira/browse/IGNITE-1915>
>
> The first feature make it realistic to execute INSERT, UPDATE, DELETE
> queries over Ignite caches using Java APIs or by connecting to a cluster
> using JDBC or ODBC drivers and send DML queries not only from Java side but
> from a variety of technologies and tools. As an example, the second feature
> from the list is intended to enable support for PHP by mixing DML with
> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>
> The third feature will allow to broaden the usage of Apache Ignite .NET
> client among .NET community by providing more advanced support for .NET
> Entity Framework.
>
> Feature owners of the above mentioned tickets, please provide the current
> status on them?
>
> If anyone else wants to see something else as a part of Ignite 1.8 and
> ready to contribute it by the mid of November please reply to the thread as
> well.
>
> Regards,
> Denis

[Pavel Tupitsyn]

Also I'd like to include at least some of .NET Usability Improvements (
https://issues.apache.org/jira/browse/IGNITE-4114).

On Tue, Oct 25, 2016 at 7:38 PM, Pavel Tupitsyn <[hidden email]>
wrote:

> IGNITE-1915 is being reviewed, I think we can make it into 1.8.
>
> On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda <[hidden email]> wrote:
>
>> Igniters,
>>
>> Looking at the discussions that happen on our dev list regarding Ignite's
>> improvements I should say that we’re ready to prepare and roll out one more
>> Ignite minor release before the end of the year - Apache Ignite 1.8.0. My
>> proposal is to make it available by mid November, somewhere around November
>> 21st.
>>
>> Personally, the following features have to be included in it due to the
>> importance and readiness:
>> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
>> https://issues.apache.org/jira/browse/IGNITE-2294>
>> PHP PDO Support from ODBC side: https://issues.apache.org/jira
>> /browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
>> Ignite as a second level cache for .NET Entity Framework:
>> https://issues.apache.org/jira/browse/IGNITE-1915 <
>> https://issues.apache.org/jira/browse/IGNITE-1915>
>>
>> The first feature make it realistic to execute INSERT, UPDATE, DELETE
>> queries over Ignite caches using Java APIs or by connecting to a cluster
>> using JDBC or ODBC drivers and send DML queries not only from Java side but
>> from a variety of technologies and tools. As an example, the second feature
>> from the list is intended to enable support for PHP by mixing DML with
>> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>>
>> The third feature will allow to broaden the usage of Apache Ignite .NET
>> client among .NET community by providing more advanced support for .NET
>> Entity Framework.
>>
>> Feature owners of the above mentioned tickets, please provide the current
>> status on them?
>>
>> If anyone else wants to see something else as a part of Ignite 1.8 and
>> ready to contribute it by the mid of November please reply to the thread as
>> well.
>>
>> Regards,
>> Denis
>
>
>

[dsetrakyan]

Do we know the status of the DML support? It looks like Alexander Paschenko
is working on it. Alexander, can you provide an update?

On Thu, Oct 27, 2016 at 9:13 AM, Pavel Tupitsyn <[hidden email]>
wrote:

> Also I'd like to include at least some of .NET Usability Improvements (
> https://issues.apache.org/jira/browse/IGNITE-4114).
>
> On Tue, Oct 25, 2016 at 7:38 PM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > IGNITE-1915 is being reviewed, I think we can make it into 1.8.
> >
> > On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda <[hidden email]> wrote:
> >
> >> Igniters,
> >>
> >> Looking at the discussions that happen on our dev list regarding
> Ignite's
> >> improvements I should say that we’re ready to prepare and roll out one
> more
> >> Ignite minor release before the end of the year - Apache Ignite 1.8.0.
> My
> >> proposal is to make it available by mid November, somewhere around
> November
> >> 21st.
> >>
> >> Personally, the following features have to be included in it due to the
> >> importance and readiness:
> >> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
> >> https://issues.apache.org/jira/browse/IGNITE-2294>
> >> PHP PDO Support from ODBC side: https://issues.apache.org/jira
> >> /browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
> >> Ignite as a second level cache for .NET Entity Framework:
> >> https://issues.apache.org/jira/browse/IGNITE-1915 <
> >> https://issues.apache.org/jira/browse/IGNITE-1915>
> >>
> >> The first feature make it realistic to execute INSERT, UPDATE, DELETE
> >> queries over Ignite caches using Java APIs or by connecting to a cluster
> >> using JDBC or ODBC drivers and send DML queries not only from Java side
> but
> >> from a variety of technologies and tools. As an example, the second
> feature
> >> from the list is intended to enable support for PHP by mixing DML with
> >> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
> >>
> >> The third feature will allow to broaden the usage of Apache Ignite .NET
> >> client among .NET community by providing more advanced support for .NET
> >> Entity Framework.
> >>
> >> Feature owners of the above mentioned tickets, please provide the
> current
> >> status on them?
> >>
> >> If anyone else wants to see something else as a part of Ignite 1.8 and
> >> ready to contribute it by the mid of November please reply to the
> thread as
> >> well.
> >>
> >> Regards,
> >> Denis
> >
> >
> >
>

[Igor Sapego]

Hi,

I have added some tests for ODBC that include DML - they are passing on the
DML branch. I've also made some changes to ODBC for it to work better with
PDO. Some of them are already merged, other will be merged once DML is
ready.

Ksenia currently works on testing PDO with our ODBC driver very
thoughtfully. We work together to improve PDO users experience. Ksenia
already filed several tickets which I'm going to fix in nearest days.

To sum up I'd say that we are going to have PDO working and well-tested by
the release time.

Best Regards,
Igor

On Thu, Oct 27, 2016 at 8:26 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Do we know the status of the DML support? It looks like Alexander Paschenko
> is working on it. Alexander, can you provide an update?
>
> On Thu, Oct 27, 2016 at 9:13 AM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Also I'd like to include at least some of .NET Usability Improvements (
> > https://issues.apache.org/jira/browse/IGNITE-4114).
> >
> > On Tue, Oct 25, 2016 at 7:38 PM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > IGNITE-1915 is being reviewed, I think we can make it into 1.8.
> > >
> > > On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > >> Igniters,
> > >>
> > >> Looking at the discussions that happen on our dev list regarding
> > Ignite's
> > >> improvements I should say that we’re ready to prepare and roll out one
> > more
> > >> Ignite minor release before the end of the year - Apache Ignite 1.8.0.
> > My
> > >> proposal is to make it available by mid November, somewhere around
> > November
> > >> 21st.
> > >>
> > >> Personally, the following features have to be included in it due to
> the
> > >> importance and readiness:
> > >> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
> > >> https://issues.apache.org/jira/browse/IGNITE-2294>
> > >> PHP PDO Support from ODBC side: https://issues.apache.org/jira
> > >> /browse/IGNITE-3865 <https://issues.apache.org/
> jira/browse/IGNITE-3865>
> > >> Ignite as a second level cache for .NET Entity Framework:
> > >> https://issues.apache.org/jira/browse/IGNITE-1915 <
> > >> https://issues.apache.org/jira/browse/IGNITE-1915>
> > >>
> > >> The first feature make it realistic to execute INSERT, UPDATE, DELETE
> > >> queries over Ignite caches using Java APIs or by connecting to a
> cluster
> > >> using JDBC or ODBC drivers and send DML queries not only from Java
> side
> > but
> > >> from a variety of technologies and tools. As an example, the second
> > feature
> > >> from the list is intended to enable support for PHP by mixing DML with
> > >> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
> > >>
> > >> The third feature will allow to broaden the usage of Apache Ignite
> .NET
> > >> client among .NET community by providing more advanced support for
> .NET
> > >> Entity Framework.
> > >>
> > >> Feature owners of the above mentioned tickets, please provide the
> > current
> > >> status on them?
> > >>
> > >> If anyone else wants to see something else as a part of Ignite 1.8 and
> > >> ready to contribute it by the mid of November please reply to the
> > thread as
> > >> well.
> > >>
> > >> Regards,
> > >> Denis
> > >
> > >
> > >
> >
>

[Denis Magda]

Let’s make shmem lib optional starting from this release
https://issues.apache.org/jira/browse/IGNITE-4152 <https://issues.apache.org/jira/browse/IGNITE-4152>

This is a minor change.

—
Denis

> On Oct 27, 2016, at 10:56 AM, Igor Sapego <[hidden email]> wrote:
>
> Hi,
>
> I have added some tests for ODBC that include DML - they are passing on the
> DML branch. I've also made some changes to ODBC for it to work better with
> PDO. Some of them are already merged, other will be merged once DML is
> ready.
>
> Ksenia currently works on testing PDO with our ODBC driver very
> thoughtfully. We work together to improve PDO users experience. Ksenia
> already filed several tickets which I'm going to fix in nearest days.
>
> To sum up I'd say that we are going to have PDO working and well-tested by
> the release time.
>
> Best Regards,
> Igor
>
> On Thu, Oct 27, 2016 at 8:26 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
>> Do we know the status of the DML support? It looks like Alexander Paschenko
>> is working on it. Alexander, can you provide an update?
>>
>> On Thu, Oct 27, 2016 at 9:13 AM, Pavel Tupitsyn <[hidden email]>
>> wrote:
>>
>>> Also I'd like to include at least some of .NET Usability Improvements (
>>> https://issues.apache.org/jira/browse/IGNITE-4114).
>>>
>>> On Tue, Oct 25, 2016 at 7:38 PM, Pavel Tupitsyn <[hidden email]>
>>> wrote:
>>>
>>>> IGNITE-1915 is being reviewed, I think we can make it into 1.8.
>>>>
>>>> On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda <[hidden email]>
>> wrote:
>>>>
>>>>> Igniters,
>>>>>
>>>>> Looking at the discussions that happen on our dev list regarding
>>> Ignite's
>>>>> improvements I should say that we’re ready to prepare and roll out one
>>> more
>>>>> Ignite minor release before the end of the year - Apache Ignite 1.8.0.
>>> My
>>>>> proposal is to make it available by mid November, somewhere around
>>> November
>>>>> 21st.
>>>>>
>>>>> Personally, the following features have to be included in it due to
>> the
>>>>> importance and readiness:
>>>>> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
>>>>> https://issues.apache.org/jira/browse/IGNITE-2294>
>>>>> PHP PDO Support from ODBC side: https://issues.apache.org/jira
>>>>> /browse/IGNITE-3865 <https://issues.apache.org/
>> jira/browse/IGNITE-3865>
>>>>> Ignite as a second level cache for .NET Entity Framework:
>>>>> https://issues.apache.org/jira/browse/IGNITE-1915 <
>>>>> https://issues.apache.org/jira/browse/IGNITE-1915>
>>>>>
>>>>> The first feature make it realistic to execute INSERT, UPDATE, DELETE
>>>>> queries over Ignite caches using Java APIs or by connecting to a
>> cluster
>>>>> using JDBC or ODBC drivers and send DML queries not only from Java
>> side
>>> but
>>>>> from a variety of technologies and tools. As an example, the second
>>> feature
>>>>> from the list is intended to enable support for PHP by mixing DML with
>>>>> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>>>>>
>>>>> The third feature will allow to broaden the usage of Apache Ignite
>> .NET
>>>>> client among .NET community by providing more advanced support for
>> .NET
>>>>> Entity Framework.
>>>>>
>>>>> Feature owners of the above mentioned tickets, please provide the
>>> current
>>>>> status on them?
>>>>>
>>>>> If anyone else wants to see something else as a part of Ignite 1.8 and
>>>>> ready to contribute it by the mid of November please reply to the
>>> thread as
>>>>> well.
>>>>>
>>>>> Regards,
>>>>> Denis
>>>>
>>>>
>>>>
>>>
>>

[Roman Shtykh]

Igniters,
I have implemented a basic set of Redis protocol commands a while ago -- those I could wrap Ignite's REST/memcached commands with.
Since Redis protocol has a richer set of commands compared to REST's, there are some limitations in the current implementation (and I think it will be not that easy to implement more advanced commands). Please see the ticket, it has a list of commands and the limitation described.
https://issues.apache.org/jira/browse/IGNITE-3066
Can it be reviewed, and possibly receive recommendations how to remove the limitations? Probably it can be considered for 1.8 release.
-Roman
 

    On Wednesday, October 26, 2016 1:26 AM, Denis Magda <[hidden email]> wrote:
 

 Igniters,

Looking at the discussions that happen on our dev list regarding Ignite's improvements I should say that we’re ready to prepare and roll out one more Ignite minor release before the end of the year - Apache Ignite 1.8.0. My proposal is to make it available by mid November, somewhere around November 21st.

Personally, the following features have to be included in it due to the importance and readiness:
DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <https://issues.apache.org/jira/browse/IGNITE-2294>
PHP PDO Support from ODBC side: https://issues.apache.org/jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
Ignite as a second level cache for .NET Entity Framework: https://issues.apache.org/jira/browse/IGNITE-1915 <https://issues.apache.org/jira/browse/IGNITE-1915>

The first feature make it realistic to execute INSERT, UPDATE, DELETE queries over Ignite caches using Java APIs or by connecting to a cluster using JDBC or ODBC drivers and send DML queries not only from Java side but from a variety of technologies and tools. As an example, the second feature from the list is intended to enable support for PHP by mixing DML with SELECT SQL queries plus sending them over Ignite’s ODBC driver.

The third feature will allow to broaden the usage of Apache Ignite .NET client among .NET community by providing more advanced support for .NET Entity Framework.

Feature owners of the above mentioned tickets, please provide the current status on them?

If anyone else wants to see something else as a part of Ignite 1.8 and ready to contribute it by the mid of November please reply to the thread as well.

Regards,
Denis

   

[Denis Magda]

Roman,

Sure, it makes sense to include this into the release highlighting that presently Ignite provides a limited support.

Please create a pull-request and send a message (not a part of this discussion) to the dev list asking for review.

—
Denis

> On Nov 1, 2016, at 6:46 PM, Roman Shtykh <[hidden email]> wrote:
>
> Igniters,
> I have implemented a basic set of Redis protocol commands a while ago -- those I could wrap Ignite's REST/memcached commands with.
> Since Redis protocol has a richer set of commands compared to REST's, there are some limitations in the current implementation (and I think it will be not that easy to implement more advanced commands). Please see the ticket, it has a list of commands and the limitation described.
> https://issues.apache.org/jira/browse/IGNITE-3066
> Can it be reviewed, and possibly receive recommendations how to remove the limitations? Probably it can be considered for 1.8 release.
> -Roman
>
>
>    On Wednesday, October 26, 2016 1:26 AM, Denis Magda <[hidden email]> wrote:
>
>
> Igniters,
>
> Looking at the discussions that happen on our dev list regarding Ignite's improvements I should say that we’re ready to prepare and roll out one more Ignite minor release before the end of the year - Apache Ignite 1.8.0. My proposal is to make it available by mid November, somewhere around November 21st.
>
> Personally, the following features have to be included in it due to the importance and readiness:
> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <https://issues.apache.org/jira/browse/IGNITE-2294>
> PHP PDO Support from ODBC side: https://issues.apache.org/jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
> Ignite as a second level cache for .NET Entity Framework: https://issues.apache.org/jira/browse/IGNITE-1915 <https://issues.apache.org/jira/browse/IGNITE-1915>
>
> The first feature make it realistic to execute INSERT, UPDATE, DELETE queries over Ignite caches using Java APIs or by connecting to a cluster using JDBC or ODBC drivers and send DML queries not only from Java side but from a variety of technologies and tools. As an example, the second feature from the list is intended to enable support for PHP by mixing DML with SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>
> The third feature will allow to broaden the usage of Apache Ignite .NET client among .NET community by providing more advanced support for .NET Entity Framework.
>
> Feature owners of the above mentioned tickets, please provide the current status on them?
>
> If anyone else wants to see something else as a part of Ignite 1.8 and ready to contribute it by the mid of November please reply to the thread as well.
>
> Regards,
> Denis
>

[Denis Magda]

Igniters,

I’ve prepared the page with all the tickets that are assigned on 1.8
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8 <https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8>

The number is enormous (850 tickets) because we silly move tickets from one version to another if something is not ready to be released.

Please, everyone go through your tickets that are assigned on 1.8 and:
- remove the version at all if you’re not sure when a ticket is going to be fixed or
- move it to the next release version (2.0) if you’re confident to finalize the dev by that time or
- fix and include enhancements in 1.8 (by November 14th).

Any alternative thoughts or suggestions are highly appreciated.

—
Denis

> On Nov 2, 2016, at 10:42 AM, Denis Magda <[hidden email]> wrote:
>
> Roman,
>
> Sure, it makes sense to include this into the release highlighting that presently Ignite provides a limited support.
>
> Please create a pull-request and send a message (not a part of this discussion) to the dev list asking for review.
>
> —
> Denis
>
>> On Nov 1, 2016, at 6:46 PM, Roman Shtykh <[hidden email]> wrote:
>>
>> Igniters,
>> I have implemented a basic set of Redis protocol commands a while ago -- those I could wrap Ignite's REST/memcached commands with.
>> Since Redis protocol has a richer set of commands compared to REST's, there are some limitations in the current implementation (and I think it will be not that easy to implement more advanced commands). Please see the ticket, it has a list of commands and the limitation described.
>> https://issues.apache.org/jira/browse/IGNITE-3066
>> Can it be reviewed, and possibly receive recommendations how to remove the limitations? Probably it can be considered for 1.8 release.
>> -Roman
>>
>>
>>   On Wednesday, October 26, 2016 1:26 AM, Denis Magda <[hidden email]> wrote:
>>
>>
>> Igniters,
>>
>> Looking at the discussions that happen on our dev list regarding Ignite's improvements I should say that we’re ready to prepare and roll out one more Ignite minor release before the end of the year - Apache Ignite 1.8.0. My proposal is to make it available by mid November, somewhere around November 21st.
>>
>> Personally, the following features have to be included in it due to the importance and readiness:
>> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <https://issues.apache.org/jira/browse/IGNITE-2294>
>> PHP PDO Support from ODBC side: https://issues.apache.org/jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865>
>> Ignite as a second level cache for .NET Entity Framework: https://issues.apache.org/jira/browse/IGNITE-1915 <https://issues.apache.org/jira/browse/IGNITE-1915>
>>
>> The first feature make it realistic to execute INSERT, UPDATE, DELETE queries over Ignite caches using Java APIs or by connecting to a cluster using JDBC or ODBC drivers and send DML queries not only from Java side but from a variety of technologies and tools. As an example, the second feature from the list is intended to enable support for PHP by mixing DML with SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>>
>> The third feature will allow to broaden the usage of Apache Ignite .NET client among .NET community by providing more advanced support for .NET Entity Framework.
>>
>> Feature owners of the above mentioned tickets, please provide the current status on them?
>>
>> If anyone else wants to see something else as a part of Ignite 1.8 and ready to contribute it by the mid of November please reply to the thread as well.
>>
>> Regards,
>> Denis
>>
>

[dsetrakyan]

Thanks, Denis. The Wiki page for 1.8 tickets is definitely a good way to
organize ourselves! I hope that everyone involved will look at it and
provide an update.

D.

On Thu, Nov 3, 2016 at 10:52 AM, Denis Magda <[hidden email]> wrote:

> Igniters,
>
> I’ve prepared the page with all the tickets that are assigned on 1.8
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8 <
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8>
>
> The number is enormous (850 tickets) because we silly move tickets from
> one version to another if something is not ready to be released.
>
> Please, everyone go through your tickets that are assigned on 1.8 and:
> - remove the version at all if you’re not sure when a ticket is going to
> be fixed or
> - move it to the next release version (2.0) if you’re confident to
> finalize the dev by that time or
> - fix and include enhancements in 1.8 (by November 14th).
>
> Any alternative thoughts or suggestions are highly appreciated.
>
> —
> Denis
>
> > On Nov 2, 2016, at 10:42 AM, Denis Magda <[hidden email]> wrote:
> >
> > Roman,
> >
> > Sure, it makes sense to include this into the release highlighting that
> presently Ignite provides a limited support.
> >
> > Please create a pull-request and send a message (not a part of this
> discussion) to the dev list asking for review.
> >
> > —
> > Denis
> >
> >> On Nov 1, 2016, at 6:46 PM, Roman Shtykh <[hidden email]>
> wrote:
> >>
> >> Igniters,
> >> I have implemented a basic set of Redis protocol commands a while ago
> -- those I could wrap Ignite's REST/memcached commands with.
> >> Since Redis protocol has a richer set of commands compared to REST's,
> there are some limitations in the current implementation (and I think it
> will be not that easy to implement more advanced commands). Please see the
> ticket, it has a list of commands and the limitation described.
> >> https://issues.apache.org/jira/browse/IGNITE-3066
> >> Can it be reviewed, and possibly receive recommendations how to remove
> the limitations? Probably it can be considered for 1.8 release.
> >> -Roman
> >>
> >>
> >>   On Wednesday, October 26, 2016 1:26 AM, Denis Magda <
> [hidden email]> wrote:
> >>
> >>
> >> Igniters,
> >>
> >> Looking at the discussions that happen on our dev list regarding
> Ignite's improvements I should say that we’re ready to prepare and roll out
> one more Ignite minor release before the end of the year - Apache Ignite
> 1.8.0. My proposal is to make it available by mid November, somewhere
> around November 21st.
> >>
> >> Personally, the following features have to be included in it due to the
> importance and readiness:
> >> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
> https://issues.apache.org/jira/browse/IGNITE-2294>
> >> PHP PDO Support from ODBC side: https://issues.apache.org/
> jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865
> >
> >> Ignite as a second level cache for .NET Entity Framework:
> https://issues.apache.org/jira/browse/IGNITE-1915 <
> https://issues.apache.org/jira/browse/IGNITE-1915>
> >>
> >> The first feature make it realistic to execute INSERT, UPDATE, DELETE
> queries over Ignite caches using Java APIs or by connecting to a cluster
> using JDBC or ODBC drivers and send DML queries not only from Java side but
> from a variety of technologies and tools. As an example, the second feature
> from the list is intended to enable support for PHP by mixing DML with
> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
> >>
> >> The third feature will allow to broaden the usage of Apache Ignite .NET
> client among .NET community by providing more advanced support for .NET
> Entity Framework.
> >>
> >> Feature owners of the above mentioned tickets, please provide the
> current status on them?
> >>
> >> If anyone else wants to see something else as a part of Ignite 1.8 and
> ready to contribute it by the mid of November please reply to the thread as
> well.
> >>
> >> Regards,
> >> Denis
> >>
> >
>
>

[Denis Magda]

Igniter,

I constantly see a lot of complains around the situation that Ignite still uses an old Spark version for its Spark module. This definitely prevents from using Ignite inside of Spark community. Here you can see the latest concerns and complains raised in our chat
https://gitter.im/apacheignite/ignite?at=581e5d43e097df7575759e4a <https://gitter.im/apacheignite/ignite?at=581e5d43e097df7575759e4a>

I would propose to escalate and renew Spark version’s on Ignite side as a part of 1.8 release.

Who would like to take over this activity? Any thought, concerns so far?

—
Denis

> On Nov 3, 2016, at 12:20 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> Thanks, Denis. The Wiki page for 1.8 tickets is definitely a good way to
> organize ourselves! I hope that everyone involved will look at it and
> provide an update.
>
> D.
>
> On Thu, Nov 3, 2016 at 10:52 AM, Denis Magda <[hidden email]> wrote:
>
>> Igniters,
>>
>> I’ve prepared the page with all the tickets that are assigned on 1.8
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8 <
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.8>
>>
>> The number is enormous (850 tickets) because we silly move tickets from
>> one version to another if something is not ready to be released.
>>
>> Please, everyone go through your tickets that are assigned on 1.8 and:
>> - remove the version at all if you’re not sure when a ticket is going to
>> be fixed or
>> - move it to the next release version (2.0) if you’re confident to
>> finalize the dev by that time or
>> - fix and include enhancements in 1.8 (by November 14th).
>>
>> Any alternative thoughts or suggestions are highly appreciated.
>>
>> —
>> Denis
>>
>>> On Nov 2, 2016, at 10:42 AM, Denis Magda <[hidden email]> wrote:
>>>
>>> Roman,
>>>
>>> Sure, it makes sense to include this into the release highlighting that
>> presently Ignite provides a limited support.
>>>
>>> Please create a pull-request and send a message (not a part of this
>> discussion) to the dev list asking for review.
>>>
>>> —
>>> Denis
>>>
>>>> On Nov 1, 2016, at 6:46 PM, Roman Shtykh <[hidden email]>
>> wrote:
>>>>
>>>> Igniters,
>>>> I have implemented a basic set of Redis protocol commands a while ago
>> -- those I could wrap Ignite's REST/memcached commands with.
>>>> Since Redis protocol has a richer set of commands compared to REST's,
>> there are some limitations in the current implementation (and I think it
>> will be not that easy to implement more advanced commands). Please see the
>> ticket, it has a list of commands and the limitation described.
>>>> https://issues.apache.org/jira/browse/IGNITE-3066
>>>> Can it be reviewed, and possibly receive recommendations how to remove
>> the limitations? Probably it can be considered for 1.8 release.
>>>> -Roman
>>>>
>>>>
>>>>  On Wednesday, October 26, 2016 1:26 AM, Denis Magda <
>> [hidden email]> wrote:
>>>>
>>>>
>>>> Igniters,
>>>>
>>>> Looking at the discussions that happen on our dev list regarding
>> Ignite's improvements I should say that we’re ready to prepare and roll out
>> one more Ignite minor release before the end of the year - Apache Ignite
>> 1.8.0. My proposal is to make it available by mid November, somewhere
>> around November 21st.
>>>>
>>>> Personally, the following features have to be included in it due to the
>> importance and readiness:
>>>> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 <
>> https://issues.apache.org/jira/browse/IGNITE-2294>
>>>> PHP PDO Support from ODBC side: https://issues.apache.org/
>> jira/browse/IGNITE-3865 <https://issues.apache.org/jira/browse/IGNITE-3865
>>>
>>>> Ignite as a second level cache for .NET Entity Framework:
>> https://issues.apache.org/jira/browse/IGNITE-1915 <
>> https://issues.apache.org/jira/browse/IGNITE-1915>
>>>>
>>>> The first feature make it realistic to execute INSERT, UPDATE, DELETE
>> queries over Ignite caches using Java APIs or by connecting to a cluster
>> using JDBC or ODBC drivers and send DML queries not only from Java side but
>> from a variety of technologies and tools. As an example, the second feature
>> from the list is intended to enable support for PHP by mixing DML with
>> SELECT SQL queries plus sending them over Ignite’s ODBC driver.
>>>>
>>>> The third feature will allow to broaden the usage of Apache Ignite .NET
>> client among .NET community by providing more advanced support for .NET
>> Entity Framework.
>>>>
>>>> Feature owners of the above mentioned tickets, please provide the
>> current status on them?
>>>>
>>>> If anyone else wants to see something else as a part of Ignite 1.8 and
>> ready to contribute it by the mid of November please reply to the thread as
>> well.
>>>>
>>>> Regards,
>>>> Denis
>>>>
>>>
>>
>>

[al.psc]

Current status on DML:

- Basic data streamer support implemented (basicness is mostly about
configuration - say, currently there's no way to specify streamer's
batch size via JDBC driver, but this can be improved easily).

- Fixed all minor stuff agreed with Vladimir.

- There are some tests that started failing after binary hash codes
generation rework made by Vladimir in ignite-4011-1 branch, I will ask
him to look into it and fix those. Failing tests live in
GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
      - testPutWithFieldsHashing
      - testCrossFormatObjectsIdentity
      - testPutWithCustomHashing
I added them personally during working on first version of auto
hashing few weeks ago, and what they do is test these very hashing
features. Again, prior to Vlad's rework those tests passed. So could
you please take a look?

- Working on Sergey V.'s comments about current code.

- Alex

[Denis Magda]

Do we have a branch for ignite-1.8? Is there anyone who can take over the release process of 1.8?

—
Denis

> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <[hidden email]> wrote:
>
> Current status on DML:
>
> - Basic data streamer support implemented (basicness is mostly about
> configuration - say, currently there's no way to specify streamer's
> batch size via JDBC driver, but this can be improved easily).
>
> - Fixed all minor stuff agreed with Vladimir.
>
> - There are some tests that started failing after binary hash codes
> generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> him to look into it and fix those. Failing tests live in
> GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
>      - testPutWithFieldsHashing
>      - testCrossFormatObjectsIdentity
>      - testPutWithCustomHashing
> I added them personally during working on first version of auto
> hashing few weeks ago, and what they do is test these very hashing
> features. Again, prior to Vlad's rework those tests passed. So could
> you please take a look?
>
> - Working on Sergey V.'s comments about current code.
>
> - Alex

[Vladimir Ozerov]

Alex,

Tests are fixed. Please merge them into your branch.

Vladimir.

On Wed, Nov 9, 2016 at 8:01 AM, Alexander Paschenko <
[hidden email]> wrote:

> Current status on DML:
>
> - Basic data streamer support implemented (basicness is mostly about
> configuration - say, currently there's no way to specify streamer's
> batch size via JDBC driver, but this can be improved easily).
>
> - Fixed all minor stuff agreed with Vladimir.
>
> - There are some tests that started failing after binary hash codes
> generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> him to look into it and fix those. Failing tests live in
> GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
>       - testPutWithFieldsHashing
>       - testCrossFormatObjectsIdentity
>       - testPutWithCustomHashing
> I added them personally during working on first version of auto
> hashing few weeks ago, and what they do is test these very hashing
> features. Again, prior to Vlad's rework those tests passed. So could
> you please take a look?
>
> - Working on Sergey V.'s comments about current code.
>
> - Alex
>

[dmagda]

Alexander P., Igor S.,

When will your merge all DML and ODBC (PDO) related changes into 1.8 branch? I’m looking forward to go through PDO [1] documentation and be sure that everything works as described on my side.

Pavel,

Do you think it will be possible to complete all the .NET usability tickets [2] under 1.8 and roll them out to the Apache Ignite users?

[1] https://issues.apache.org/jira/browse/IGNITE-3921 <https://issues.apache.org/jira/browse/IGNITE-3921>
[2] https://issues.apache.org/jira/browse/IGNITE-4114 <https://issues.apache.org/jira/browse/IGNITE-4114>

—
Denis

> On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email]> wrote:
>
> Do we have a branch for ignite-1.8? Is there anyone who can take over the release process of 1.8?
>
> —
> Denis
>
>> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <[hidden email]> wrote:
>>
>> Current status on DML:
>>
>> - Basic data streamer support implemented (basicness is mostly about
>> configuration - say, currently there's no way to specify streamer's
>> batch size via JDBC driver, but this can be improved easily).
>>
>> - Fixed all minor stuff agreed with Vladimir.
>>
>> - There are some tests that started failing after binary hash codes
>> generation rework made by Vladimir in ignite-4011-1 branch, I will ask
>> him to look into it and fix those. Failing tests live in
>> GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
>>     - testPutWithFieldsHashing
>>     - testCrossFormatObjectsIdentity
>>     - testPutWithCustomHashing
>> I added them personally during working on first version of auto
>> hashing few weeks ago, and what they do is test these very hashing
>> features. Again, prior to Vlad's rework those tests passed. So could
>> you please take a look?
>>
>> - Working on Sergey V.'s comments about current code.
>>
>> - Alex
>

[Pavel Tupitsyn]

Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary mode)
is not a simple thing. We won't be able to do that for 1.8.
Other than that, I'll try to fit as many of them as I can. But I can't
answer your question since I don't see any date yet.

By the way, you were going to help with the reviews.

[1] https://issues.apache.org/jira/browse/IGNITE-4128
[2] https://issues.apache.org/jira/browse/IGNITE-3825

On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <[hidden email]> wrote:

> *Alexander P., Igor S.,*
>
> When will your merge all DML and ODBC (PDO) related changes into 1.8
> branch? I’m looking forward to go through PDO [1] documentation and be sure
> that everything works as described on my side.
>
> *Pavel,*
>
> Do you think it will be possible to complete all the .NET usability
> tickets [2] under 1.8 and roll them out to the Apache Ignite users?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3921
> [2] https://issues.apache.org/jira/browse/IGNITE-4114
>
> —
> Denis
>
> On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email]> wrote:
>
> Do we have a branch for ignite-1.8? Is there anyone who can take over the
> release process of 1.8?
>
> —
> Denis
>
> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <
> [hidden email]> wrote:
>
> Current status on DML:
>
> - Basic data streamer support implemented (basicness is mostly about
> configuration - say, currently there's no way to specify streamer's
> batch size via JDBC driver, but this can be improved easily).
>
> - Fixed all minor stuff agreed with Vladimir.
>
> - There are some tests that started failing after binary hash codes
> generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> him to look into it and fix those. Failing tests live in
> GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
>     - testPutWithFieldsHashing
>     - testCrossFormatObjectsIdentity
>     - testPutWithCustomHashing
> I added them personally during working on first version of auto
> hashing few weeks ago, and what they do is test these very hashing
> features. Again, prior to Vlad's rework those tests passed. So could
> you please take a look?
>
> - Working on Sergey V.'s comments about current code.
>
> - Alex
>
>
>
>

[Igor Sapego]

Denis,

I can merge PDO-related changes into 1.8 but without DML they will break
tests
and even compilation so I don't see any sense in doing that before DML is
merged.

After DML is ready and merged I'll need some time to merge my changes and
check
that everything works as intended. The code itself, tests and examples are
ready.


Best Regards,
Igor

On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <[hidden email]>
wrote:

> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary mode)
> is not a simple thing. We won't be able to do that for 1.8.
> Other than that, I'll try to fit as many of them as I can. But I can't
> answer your question since I don't see any date yet.
>
> By the way, you were going to help with the reviews.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4128
> [2] https://issues.apache.org/jira/browse/IGNITE-3825
>
> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <[hidden email]> wrote:
>
> > *Alexander P., Igor S.,*
> >
> > When will your merge all DML and ODBC (PDO) related changes into 1.8
> > branch? I’m looking forward to go through PDO [1] documentation and be
> sure
> > that everything works as described on my side.
> >
> > *Pavel,*
> >
> > Do you think it will be possible to complete all the .NET usability
> > tickets [2] under 1.8 and roll them out to the Apache Ignite users?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-3921
> > [2] https://issues.apache.org/jira/browse/IGNITE-4114
> >
> > —
> > Denis
> >
> > On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email]> wrote:
> >
> > Do we have a branch for ignite-1.8? Is there anyone who can take over the
> > release process of 1.8?
> >
> > —
> > Denis
> >
> > On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <
> > [hidden email]> wrote:
> >
> > Current status on DML:
> >
> > - Basic data streamer support implemented (basicness is mostly about
> > configuration - say, currently there's no way to specify streamer's
> > batch size via JDBC driver, but this can be improved easily).
> >
> > - Fixed all minor stuff agreed with Vladimir.
> >
> > - There are some tests that started failing after binary hash codes
> > generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> > him to look into it and fix those. Failing tests live in
> > GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
> >     - testPutWithFieldsHashing
> >     - testCrossFormatObjectsIdentity
> >     - testPutWithCustomHashing
> > I added them personally during working on first version of auto
> > hashing few weeks ago, and what they do is test these very hashing
> > features. Again, prior to Vlad's rework those tests passed. So could
> > you please take a look?
> >
> > - Working on Sergey V.'s comments about current code.
> >
> > - Alex
> >
> >
> >
> >
>

[Vladimir Ozerov]

Folks,
As DML is the main feature for now, I propose to create *ignite-1.8 *branch
when DML is ready. If nobody minds I will do that as soon as DML is merged
and start vote when the rest minor things are cleared.
Also I would like to remind that we still have a lot of tickets assigned on
1.8 version. Please look through tickets assigned to yourself and move them
further if you do not think they will be ready in the nearest time.

Alexander,
Do you have any estimates on when we can expect DML to be ready for merge?

Igor,
I looked at DML code and it appears to be almost ready at the moment. I
think you can simply merge it into your PRs and continue with testing even
before DML is officially merged.

Vladimir.

On Tue, Nov 15, 2016 at 12:45 PM, Igor Sapego <[hidden email]> wrote:

> Denis,
>
> I can merge PDO-related changes into 1.8 but without DML they will break
> tests
> and even compilation so I don't see any sense in doing that before DML is
> merged.
>
> After DML is ready and merged I'll need some time to merge my changes and
> check
> that everything works as intended. The code itself, tests and examples are
> ready.
>
>
> Best Regards,
> Igor
>
> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary mode)
> > is not a simple thing. We won't be able to do that for 1.8.
> > Other than that, I'll try to fit as many of them as I can. But I can't
> > answer your question since I don't see any date yet.
> >
> > By the way, you were going to help with the reviews.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4128
> > [2] https://issues.apache.org/jira/browse/IGNITE-3825
> >
> > On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <[hidden email]> wrote:
> >
> > > *Alexander P., Igor S.,*
> > >
> > > When will your merge all DML and ODBC (PDO) related changes into 1.8
> > > branch? I’m looking forward to go through PDO [1] documentation and be
> > sure
> > > that everything works as described on my side.
> > >
> > > *Pavel,*
> > >
> > > Do you think it will be possible to complete all the .NET usability
> > > tickets [2] under 1.8 and roll them out to the Apache Ignite users?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-3921
> > > [2] https://issues.apache.org/jira/browse/IGNITE-4114
> > >
> > > —
> > > Denis
> > >
> > > On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email]> wrote:
> > >
> > > Do we have a branch for ignite-1.8? Is there anyone who can take over
> the
> > > release process of 1.8?
> > >
> > > —
> > > Denis
> > >
> > > On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <
> > > [hidden email]> wrote:
> > >
> > > Current status on DML:
> > >
> > > - Basic data streamer support implemented (basicness is mostly about
> > > configuration - say, currently there's no way to specify streamer's
> > > batch size via JDBC driver, but this can be improved easily).
> > >
> > > - Fixed all minor stuff agreed with Vladimir.
> > >
> > > - There are some tests that started failing after binary hash codes
> > > generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> > > him to look into it and fix those. Failing tests live in
> > > GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
> > >     - testPutWithFieldsHashing
> > >     - testCrossFormatObjectsIdentity
> > >     - testPutWithCustomHashing
> > > I added them personally during working on first version of auto
> > > hashing few weeks ago, and what they do is test these very hashing
> > > features. Again, prior to Vlad's rework those tests passed. So could
> > > you please take a look?
> > >
> > > - Working on Sergey V.'s comments about current code.
> > >
> > > - Alex
> > >
> > >
> > >
> > >
> >
>

[dmagda]

Pavel,

Got you thanks. I’ve reviewed all the tickets that were waiting for my review. Please have a look at minor comments.

—
Denis

> On Nov 15, 2016, at 12:31 AM, Pavel Tupitsyn <[hidden email]> wrote:
>
> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary mode) is not a simple thing. We won't be able to do that for 1.8.
> Other than that, I'll try to fit as many of them as I can. But I can't answer your question since I don't see any date yet.
>
> By the way, you were going to help with the reviews.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <https://issues.apache.org/jira/browse/IGNITE-4128>
> [2] https://issues.apache.org/jira/browse/IGNITE-3825 <https://issues.apache.org/jira/browse/IGNITE-3825>
>
> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <[hidden email] <mailto:[hidden email]>> wrote:
> Alexander P., Igor S.,
>
> When will your merge all DML and ODBC (PDO) related changes into 1.8 branch? I’m looking forward to go through PDO [1] documentation and be sure that everything works as described on my side.
>
> Pavel,
>
> Do you think it will be possible to complete all the .NET usability tickets [2] under 1.8 and roll them out to the Apache Ignite users?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3921 <https://issues.apache.org/jira/browse/IGNITE-3921>
> [2] https://issues.apache.org/jira/browse/IGNITE-4114 <https://issues.apache.org/jira/browse/IGNITE-4114>
>
> —
> Denis
>
>> On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email] <mailto:[hidden email]>> wrote:
>>
>> Do we have a branch for ignite-1.8? Is there anyone who can take over the release process of 1.8?
>>
>> —
>> Denis
>>
>>> On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>> Current status on DML:
>>>
>>> - Basic data streamer support implemented (basicness is mostly about
>>> configuration - say, currently there's no way to specify streamer's
>>> batch size via JDBC driver, but this can be improved easily).
>>>
>>> - Fixed all minor stuff agreed with Vladimir.
>>>
>>> - There are some tests that started failing after binary hash codes
>>> generation rework made by Vladimir in ignite-4011-1 branch, I will ask
>>> him to look into it and fix those. Failing tests live in
>>> GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
>>>     - testPutWithFieldsHashing
>>>     - testCrossFormatObjectsIdentity
>>>     - testPutWithCustomHashing
>>> I added them personally during working on first version of auto
>>> hashing few weeks ago, and what they do is test these very hashing
>>> features. Again, prior to Vlad's rework those tests passed. So could
>>> you please take a look?
>>>
>>> - Working on Sergey V.'s comments about current code.
>>>
>>> - Alex
>>
>
>

[dmagda]

Igor,

It makes sense to wait for me while everything gets merged into 1.8 then. Please let me know over this discussion when the overall merge happens.

—
Denis

> On Nov 15, 2016, at 1:45 AM, Igor Sapego <[hidden email]> wrote:
>
> Denis,
>
> I can merge PDO-related changes into 1.8 but without DML they will break tests
> and even compilation so I don't see any sense in doing that before DML is merged.
>
> After DML is ready and merged I'll need some time to merge my changes and check
> that everything works as intended. The code itself, tests and examples are ready.
>
>
> Best Regards,
> Igor
>
> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <[hidden email] <mailto:[hidden email]>> wrote:
> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary mode)
> is not a simple thing. We won't be able to do that for 1.8.
> Other than that, I'll try to fit as many of them as I can. But I can't
> answer your question since I don't see any date yet.
>
> By the way, you were going to help with the reviews.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <https://issues.apache.org/jira/browse/IGNITE-4128>
> [2] https://issues.apache.org/jira/browse/IGNITE-3825 <https://issues.apache.org/jira/browse/IGNITE-3825>
>
> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda <[hidden email] <mailto:[hidden email]>> wrote:
>
> > *Alexander P., Igor S.,*
> >
> > When will your merge all DML and ODBC (PDO) related changes into 1.8
> > branch? I’m looking forward to go through PDO [1] documentation and be sure
> > that everything works as described on my side.
> >
> > *Pavel,*
> >
> > Do you think it will be possible to complete all the .NET usability
> > tickets [2] under 1.8 and roll them out to the Apache Ignite users?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-3921 <https://issues.apache.org/jira/browse/IGNITE-3921>
> > [2] https://issues.apache.org/jira/browse/IGNITE-4114 <https://issues.apache.org/jira/browse/IGNITE-4114>
> >
> > —
> > Denis
> >
> > On Nov 9, 2016, at 6:55 AM, Denis Magda <[hidden email] <mailto:[hidden email]>> wrote:
> >
> > Do we have a branch for ignite-1.8? Is there anyone who can take over the
> > release process of 1.8?
> >
> > —
> > Denis
> >
> > On Nov 8, 2016, at 9:01 PM, Alexander Paschenko <
> > [hidden email] <mailto:[hidden email]>> wrote:
> >
> > Current status on DML:
> >
> > - Basic data streamer support implemented (basicness is mostly about
> > configuration - say, currently there's no way to specify streamer's
> > batch size via JDBC driver, but this can be improved easily).
> >
> > - Fixed all minor stuff agreed with Vladimir.
> >
> > - There are some tests that started failing after binary hash codes
> > generation rework made by Vladimir in ignite-4011-1 branch, I will ask
> > him to look into it and fix those. Failing tests live in
> > GridCacheBinaryObjectsAbstractSelfTest, and are as follows:
> >     - testPutWithFieldsHashing
> >     - testCrossFormatObjectsIdentity
> >     - testPutWithCustomHashing
> > I added them personally during working on first version of auto
> > hashing few weeks ago, and what they do is test these very hashing
> > features. Again, prior to Vlad's rework those tests passed. So could
> > you please take a look?
> >
> > - Working on Sergey V.'s comments about current code.
> >
> > - Alex
> >
> >
> >
> >
>