Re: Apache Ignite 1.8 Release

[Denis Magda]

Thanks,

Created a ticket and assigned it on Nick
https://issues.apache.org/jira/browse/IGNITE-4402 


Nick, reassign it on me once the images are ready.

—
Denis

> On Dec 8, 2016, at 12:06 AM, Sergey Kozlov  wrote:
> 
> Hi Denis
> 
> Usually Nikolay makes  docker image for a new release. I just check it.
> 
> On Wed, Dec 7, 2016 at 4:32 AM, Denis Magda  wrote:
> 
>> Igniters,
>> 
>> Who usually prepares docker and other cloud images for each new Ignite
>> release and who will be able to handle it this time?
>> https://ignite.apache.org/download.cgi#docker > download.cgi#docker>
>> 
>> Sergey K., Nikolay T., are you aware about this?
>> 
>> —
>> Denis
>> 
>>> On Dec 3, 2016, at 12:54 PM, Sergey Kozlov  wrote:
>>> 
>>> Hi
>>> 
>>> More news for DML:
>>> 
>>> IGNITE-4364 DML: AssertionError: Row@ ... null 5 -> mapcol_asc_idx
>>> 
>>> - sporadic failure, not blocker but need pay attention
>>> 
>>> 
>>> 
>>> 
>>> On Sat, Dec 3, 2016 at 3:35 AM, Denis Magda  wrote:
>>> 
 Alexander, thanks for the update and all your efforts!
 
 Would agree that IGNITE-4340 sounds like a serious bug that should be
 fixed in 1.8 while IGNITE-4363 can be put off till the next release.
 
 As for the vote it should be started in the very beginning of the next
 week. We were, mostly, waiting for green light from your side :)
 
 —
 Denis
 
> On Dec 2, 2016, at 4:22 PM, Alexander Paschenko <
 alexander.a.pasche...@gmail.com> wrote:
> 
> Sergey, your issue has been resolved - apparently a won't fix as it's
> not an Ignite problem but a (rather rational) H2's behavior :) It was
> a fun brainteaser before sleep :D Please see details on issue page -
> it's about arithmetic and type conversions.
> 
> Dmitry, yes, I do or modify existing tests where applicable.
> 
> Latest DML news:
> 
> - https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
> new column values to expected types on SQL UPDATE - fixed (together
> with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
> not preserve metadata about array content's type and 4346 - the one
> about PHP PDO)
> 
> - found inner properties mutation problem
> (https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
> mutation broken in SQL UPDATE)
> 
> - the problem above will most likely be fixed post 1.8 with other
> issues/improvements related with DML - I've got a (small :) ) list of
> them and will create proper issues for all that tech debt during the
> weekend or on Monday.
> 
> - TC tests seem to be all green on DML side as well as all in all.
> What's the status of release vote guys?
> 
> - Alex
> 
> 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
>> Alexander, thanks for making the fixes to DML. Are you adding JUnits
>> for
>> all the fixes you are making?
>> 
>> On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov 
 wrote:
>> 
>>> Hi
>>> 
>>> Recent fixes from Alexander made DML much better!
>>> 
>>> I've found one issue but it is not blocker for the release:
>>> 
>>> IGNITE-4362 DML: the multiplication for SET uses the data type for
>> the
>>> result from the right side
>>> 
>>> 
>>> 
>>> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda 
>> wrote:
>>> 
 Vladimir,
 
 Agree. The issue looks critical. Who will be reviewing it?
 
 —
 Denis
 
> On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
 wrote:
> 
> Igniters,
> 
> I assembled and merged release notes to the branch ignite-1.8.
>> Looks
>>> like
> we are almost ready to start vote. The only outstanding issue which
>>> looks
> pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved
 and
> start vote, unless anyone has some other concerns.
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-4340
> 
> Vladimir.
> 
> On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
 wrote:
> 
>> Denis,
>> 
>> I've took a look on the first issue [1], and it seems like it was
 already
>> resolved
>> by another fix made by Alexander.
>> 
>> For the second issue [2] I have raised a PR.
>> 
>> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
>> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
>> 
>> Best Regards,
>> Igor
>> 
>> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
>>> wrote:
>> 
>>> I’ve faced with two more issues while was working with Igni

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi Denis

Usually Nikolay makes  docker image for a new release. I just check it.

On Wed, Dec 7, 2016 at 4:32 AM, Denis Magda  wrote:

> Igniters,
>
> Who usually prepares docker and other cloud images for each new Ignite
> release and who will be able to handle it this time?
> https://ignite.apache.org/download.cgi#docker  download.cgi#docker>
>
> Sergey K., Nikolay T., are you aware about this?
>
> —
> Denis
>
> > On Dec 3, 2016, at 12:54 PM, Sergey Kozlov  wrote:
> >
> > Hi
> >
> > More news for DML:
> >
> > IGNITE-4364 DML: AssertionError: Row@ ... null 5 -> mapcol_asc_idx
> > 
> > - sporadic failure, not blocker but need pay attention
> >
> >
> >
> >
> > On Sat, Dec 3, 2016 at 3:35 AM, Denis Magda  wrote:
> >
> >> Alexander, thanks for the update and all your efforts!
> >>
> >> Would agree that IGNITE-4340 sounds like a serious bug that should be
> >> fixed in 1.8 while IGNITE-4363 can be put off till the next release.
> >>
> >> As for the vote it should be started in the very beginning of the next
> >> week. We were, mostly, waiting for green light from your side :)
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 2, 2016, at 4:22 PM, Alexander Paschenko <
> >> alexander.a.pasche...@gmail.com> wrote:
> >>>
> >>> Sergey, your issue has been resolved - apparently a won't fix as it's
> >>> not an Ignite problem but a (rather rational) H2's behavior :) It was
> >>> a fun brainteaser before sleep :D Please see details on issue page -
> >>> it's about arithmetic and type conversions.
> >>>
> >>> Dmitry, yes, I do or modify existing tests where applicable.
> >>>
> >>> Latest DML news:
> >>>
> >>> - https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
> >>> new column values to expected types on SQL UPDATE - fixed (together
> >>> with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
> >>> not preserve metadata about array content's type and 4346 - the one
> >>> about PHP PDO)
> >>>
> >>> - found inner properties mutation problem
> >>> (https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
> >>> mutation broken in SQL UPDATE)
> >>>
> >>> - the problem above will most likely be fixed post 1.8 with other
> >>> issues/improvements related with DML - I've got a (small :) ) list of
> >>> them and will create proper issues for all that tech debt during the
> >>> weekend or on Monday.
> >>>
> >>> - TC tests seem to be all green on DML side as well as all in all.
> >>> What's the status of release vote guys?
> >>>
> >>> - Alex
> >>>
> >>> 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
>  Alexander, thanks for making the fixes to DML. Are you adding JUnits
> for
>  all the fixes you are making?
> 
>  On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov 
> >> wrote:
> 
> > Hi
> >
> > Recent fixes from Alexander made DML much better!
> >
> > I've found one issue but it is not blocker for the release:
> >
> > IGNITE-4362 DML: the multiplication for SET uses the data type for
> the
> > result from the right side
> > 
> >
> >
> > On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda 
> wrote:
> >
> >> Vladimir,
> >>
> >> Agree. The issue looks critical. Who will be reviewing it?
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
> >> wrote:
> >>>
> >>> Igniters,
> >>>
> >>> I assembled and merged release notes to the branch ignite-1.8.
> Looks
> > like
> >>> we are almost ready to start vote. The only outstanding issue which
> > looks
> >>> pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved
> >> and
> >>> start vote, unless anyone has some other concerns.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-4340
> >>>
> >>> Vladimir.
> >>>
> >>> On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
> >> wrote:
> >>>
>  Denis,
> 
>  I've took a look on the first issue [1], and it seems like it was
> >> already
>  resolved
>  by another fix made by Alexander.
> 
>  For the second issue [2] I have raised a PR.
> 
>  [1] - https://issues.apache.org/jira/browse/IGNITE-4346
>  [2] - https://issues.apache.org/jira/browse/IGNITE-4347
> 
>  Best Regards,
>  Igor
> 
>  On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
> > wrote:
> 
> > I’ve faced with two more issues while was working with Ignite
> from
> > PHP
>  PDO
> > side.
> >
> > The first one is related to DML.
> > DML and PHP PDO: double field is converted to bigdecimal <
> > https://issues.apache.org/jira/browse/IGNITE-4346>
> >
> > Alexander P. and Igor S. please pull together and fix this issue
> > befo

Re: Apache Ignite 1.8 Release

[Denis Magda]

Igniters,

Who usually prepares docker and other cloud images for each new Ignite release 
and who will be able to handle it this time?
https://ignite.apache.org/download.cgi#docker 


Sergey K., Nikolay T., are you aware about this?

—
Denis

> On Dec 3, 2016, at 12:54 PM, Sergey Kozlov  wrote:
> 
> Hi
> 
> More news for DML:
> 
> IGNITE-4364 DML: AssertionError: Row@ ... null 5 -> mapcol_asc_idx
> 
> - sporadic failure, not blocker but need pay attention
> 
> 
> 
> 
> On Sat, Dec 3, 2016 at 3:35 AM, Denis Magda  wrote:
> 
>> Alexander, thanks for the update and all your efforts!
>> 
>> Would agree that IGNITE-4340 sounds like a serious bug that should be
>> fixed in 1.8 while IGNITE-4363 can be put off till the next release.
>> 
>> As for the vote it should be started in the very beginning of the next
>> week. We were, mostly, waiting for green light from your side :)
>> 
>> —
>> Denis
>> 
>>> On Dec 2, 2016, at 4:22 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>> 
>>> Sergey, your issue has been resolved - apparently a won't fix as it's
>>> not an Ignite problem but a (rather rational) H2's behavior :) It was
>>> a fun brainteaser before sleep :D Please see details on issue page -
>>> it's about arithmetic and type conversions.
>>> 
>>> Dmitry, yes, I do or modify existing tests where applicable.
>>> 
>>> Latest DML news:
>>> 
>>> - https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
>>> new column values to expected types on SQL UPDATE - fixed (together
>>> with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
>>> not preserve metadata about array content's type and 4346 - the one
>>> about PHP PDO)
>>> 
>>> - found inner properties mutation problem
>>> (https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
>>> mutation broken in SQL UPDATE)
>>> 
>>> - the problem above will most likely be fixed post 1.8 with other
>>> issues/improvements related with DML - I've got a (small :) ) list of
>>> them and will create proper issues for all that tech debt during the
>>> weekend or on Monday.
>>> 
>>> - TC tests seem to be all green on DML side as well as all in all.
>>> What's the status of release vote guys?
>>> 
>>> - Alex
>>> 
>>> 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
 Alexander, thanks for making the fixes to DML. Are you adding JUnits for
 all the fixes you are making?
 
 On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov 
>> wrote:
 
> Hi
> 
> Recent fixes from Alexander made DML much better!
> 
> I've found one issue but it is not blocker for the release:
> 
> IGNITE-4362 DML: the multiplication for SET uses the data type for the
> result from the right side
> 
> 
> 
> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:
> 
>> Vladimir,
>> 
>> Agree. The issue looks critical. Who will be reviewing it?
>> 
>> —
>> Denis
>> 
>>> On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
>> wrote:
>>> 
>>> Igniters,
>>> 
>>> I assembled and merged release notes to the branch ignite-1.8. Looks
> like
>>> we are almost ready to start vote. The only outstanding issue which
> looks
>>> pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved
>> and
>>> start vote, unless anyone has some other concerns.
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-4340
>>> 
>>> Vladimir.
>>> 
>>> On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
>> wrote:
>>> 
 Denis,
 
 I've took a look on the first issue [1], and it seems like it was
>> already
 resolved
 by another fix made by Alexander.
 
 For the second issue [2] I have raised a PR.
 
 [1] - https://issues.apache.org/jira/browse/IGNITE-4346
 [2] - https://issues.apache.org/jira/browse/IGNITE-4347
 
 Best Regards,
 Igor
 
 On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
> wrote:
 
> I’ve faced with two more issues while was working with Ignite from
> PHP
 PDO
> side.
> 
> The first one is related to DML.
> DML and PHP PDO: double field is converted to bigdecimal <
> https://issues.apache.org/jira/browse/IGNITE-4346>
> 
> Alexander P. and Igor S. please pull together and fix this issue
> before
> 1.8 is sent for vote.
> 
> The second issue is related to ODBC and affects the usability only.
>> Igor
> S., please try to address it as a part of 1.8 as well.
> ODBC: NPE when cache name is different from the one configured in
> DSN <
> https://issues.apache.org/jira/browse/IGNITE-4347>
> 
> —
> Deni

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

More news for DML:

IGNITE-4364 DML: AssertionError: Row@ ... null 5 -> mapcol_asc_idx

 - sporadic failure, not blocker but need pay attention




On Sat, Dec 3, 2016 at 3:35 AM, Denis Magda  wrote:

> Alexander, thanks for the update and all your efforts!
>
> Would agree that IGNITE-4340 sounds like a serious bug that should be
> fixed in 1.8 while IGNITE-4363 can be put off till the next release.
>
> As for the vote it should be started in the very beginning of the next
> week. We were, mostly, waiting for green light from your side :)
>
> —
> Denis
>
> > On Dec 2, 2016, at 4:22 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > Sergey, your issue has been resolved - apparently a won't fix as it's
> > not an Ignite problem but a (rather rational) H2's behavior :) It was
> > a fun brainteaser before sleep :D Please see details on issue page -
> > it's about arithmetic and type conversions.
> >
> > Dmitry, yes, I do or modify existing tests where applicable.
> >
> > Latest DML news:
> >
> > - https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
> > new column values to expected types on SQL UPDATE - fixed (together
> > with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
> > not preserve metadata about array content's type and 4346 - the one
> > about PHP PDO)
> >
> > - found inner properties mutation problem
> > (https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
> > mutation broken in SQL UPDATE)
> >
> > - the problem above will most likely be fixed post 1.8 with other
> > issues/improvements related with DML - I've got a (small :) ) list of
> > them and will create proper issues for all that tech debt during the
> > weekend or on Monday.
> >
> > - TC tests seem to be all green on DML side as well as all in all.
> > What's the status of release vote guys?
> >
> > - Alex
> >
> > 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
> >> Alexander, thanks for making the fixes to DML. Are you adding JUnits for
> >> all the fixes you are making?
> >>
> >> On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov 
> wrote:
> >>
> >>> Hi
> >>>
> >>> Recent fixes from Alexander made DML much better!
> >>>
> >>> I've found one issue but it is not blocker for the release:
> >>>
> >>> IGNITE-4362 DML: the multiplication for SET uses the data type for the
> >>> result from the right side
> >>> 
> >>>
> >>>
> >>> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:
> >>>
>  Vladimir,
> 
>  Agree. The issue looks critical. Who will be reviewing it?
> 
>  —
>  Denis
> 
> > On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
>  wrote:
> >
> > Igniters,
> >
> > I assembled and merged release notes to the branch ignite-1.8. Looks
> >>> like
> > we are almost ready to start vote. The only outstanding issue which
> >>> looks
> > pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved
> and
> > start vote, unless anyone has some other concerns.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4340
> >
> > Vladimir.
> >
> > On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
>  wrote:
> >
> >> Denis,
> >>
> >> I've took a look on the first issue [1], and it seems like it was
>  already
> >> resolved
> >> by another fix made by Alexander.
> >>
> >> For the second issue [2] I have raised a PR.
> >>
> >> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
> >> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
> >>> wrote:
> >>
> >>> I’ve faced with two more issues while was working with Ignite from
> >>> PHP
> >> PDO
> >>> side.
> >>>
> >>> The first one is related to DML.
> >>> DML and PHP PDO: double field is converted to bigdecimal <
> >>> https://issues.apache.org/jira/browse/IGNITE-4346>
> >>>
> >>> Alexander P. and Igor S. please pull together and fix this issue
> >>> before
> >>> 1.8 is sent for vote.
> >>>
> >>> The second issue is related to ODBC and affects the usability only.
>  Igor
> >>> S., please try to address it as a part of 1.8 as well.
> >>> ODBC: NPE when cache name is different from the one configured in
> >>> DSN <
> >>> https://issues.apache.org/jira/browse/IGNITE-4347>
> >>>
> >>> —
> >>> Denis
> >>>
>  On Nov 30, 2016, at 12:01 PM, Sergey Kozlov  >
> >>> wrote:
> 
>  Hi
> 
>  Update for DML testing:
> 
>  IGNITE-4342 DML: clear() on atomic cache causes the exception from
> >>> previous
>  failed DML statement  >> jira/browse/IGNITE-4342>
> 
> 
> 
>  On Wed, Nov 30, 2016 a

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander, thanks for the update and all your efforts!

Would agree that IGNITE-4340 sounds like a serious bug that should be fixed in 
1.8 while IGNITE-4363 can be put off till the next release.

As for the vote it should be started in the very beginning of the next week. We 
were, mostly, waiting for green light from your side :)

—
Denis

> On Dec 2, 2016, at 4:22 PM, Alexander Paschenko 
>  wrote:
> 
> Sergey, your issue has been resolved - apparently a won't fix as it's
> not an Ignite problem but a (rather rational) H2's behavior :) It was
> a fun brainteaser before sleep :D Please see details on issue page -
> it's about arithmetic and type conversions.
> 
> Dmitry, yes, I do or modify existing tests where applicable.
> 
> Latest DML news:
> 
> - https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
> new column values to expected types on SQL UPDATE - fixed (together
> with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
> not preserve metadata about array content's type and 4346 - the one
> about PHP PDO)
> 
> - found inner properties mutation problem
> (https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
> mutation broken in SQL UPDATE)
> 
> - the problem above will most likely be fixed post 1.8 with other
> issues/improvements related with DML - I've got a (small :) ) list of
> them and will create proper issues for all that tech debt during the
> weekend or on Monday.
> 
> - TC tests seem to be all green on DML side as well as all in all.
> What's the status of release vote guys?
> 
> - Alex
> 
> 2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
>> Alexander, thanks for making the fixes to DML. Are you adding JUnits for
>> all the fixes you are making?
>> 
>> On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov  wrote:
>> 
>>> Hi
>>> 
>>> Recent fixes from Alexander made DML much better!
>>> 
>>> I've found one issue but it is not blocker for the release:
>>> 
>>> IGNITE-4362 DML: the multiplication for SET uses the data type for the
>>> result from the right side
>>> 
>>> 
>>> 
>>> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:
>>> 
 Vladimir,
 
 Agree. The issue looks critical. Who will be reviewing it?
 
 —
 Denis
 
> On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
 wrote:
> 
> Igniters,
> 
> I assembled and merged release notes to the branch ignite-1.8. Looks
>>> like
> we are almost ready to start vote. The only outstanding issue which
>>> looks
> pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
> start vote, unless anyone has some other concerns.
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-4340
> 
> Vladimir.
> 
> On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
 wrote:
> 
>> Denis,
>> 
>> I've took a look on the first issue [1], and it seems like it was
 already
>> resolved
>> by another fix made by Alexander.
>> 
>> For the second issue [2] I have raised a PR.
>> 
>> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
>> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
>> 
>> Best Regards,
>> Igor
>> 
>> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
>>> wrote:
>> 
>>> I’ve faced with two more issues while was working with Ignite from
>>> PHP
>> PDO
>>> side.
>>> 
>>> The first one is related to DML.
>>> DML and PHP PDO: double field is converted to bigdecimal <
>>> https://issues.apache.org/jira/browse/IGNITE-4346>
>>> 
>>> Alexander P. and Igor S. please pull together and fix this issue
>>> before
>>> 1.8 is sent for vote.
>>> 
>>> The second issue is related to ODBC and affects the usability only.
 Igor
>>> S., please try to address it as a part of 1.8 as well.
>>> ODBC: NPE when cache name is different from the one configured in
>>> DSN <
>>> https://issues.apache.org/jira/browse/IGNITE-4347>
>>> 
>>> —
>>> Denis
>>> 
 On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
>>> wrote:
 
 Hi
 
 Update for DML testing:
 
 IGNITE-4342 DML: clear() on atomic cache causes the exception from
>>> previous
 failed DML statement > jira/browse/IGNITE-4342>
 
 
 
 On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
>> wrote:
 
> Vladimir,
> 
> Please add to the release notes information regarding this feature
> https://issues.apache.org/jira/browse/IGNITE-2310 <
> https://issues.apache.org/jira/browse/IGNITE-2310>
> 
> Essentially, it allows locking a partition while a remote
>>> computation
>> is
> being executed on a node. I’ve already documented the feature here.
> http://apacheignite.gridgain.org/v1.7/docs/collocate-
>

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Sergey, your issue has been resolved - apparently a won't fix as it's
not an Ignite problem but a (rather rational) H2's behavior :) It was
a fun brainteaser before sleep :D Please see details on issue page -
it's about arithmetic and type conversions.

Dmitry, yes, I do or modify existing tests where applicable.

Latest DML news:

- https://issues.apache.org/jira/browse/IGNITE-4340 Implicitly cast
new column values to expected types on SQL UPDATE - fixed (together
with https://issues.apache.org/jira/browse/IGNITE-4333 SQL engine does
not preserve metadata about array content's type and 4346 - the one
about PHP PDO)

- found inner properties mutation problem
(https://issues.apache.org/jira/browse/IGNITE-4363 Inner properties
mutation broken in SQL UPDATE)

- the problem above will most likely be fixed post 1.8 with other
issues/improvements related with DML - I've got a (small :) ) list of
them and will create proper issues for all that tech debt during the
weekend or on Monday.

- TC tests seem to be all green on DML side as well as all in all.
What's the status of release vote guys?

- Alex

2016-12-03 2:08 GMT+03:00 Dmitriy Setrakyan :
> Alexander, thanks for making the fixes to DML. Are you adding JUnits for
> all the fixes you are making?
>
> On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov  wrote:
>
>> Hi
>>
>> Recent fixes from Alexander made DML much better!
>>
>> I've found one issue but it is not blocker for the release:
>>
>> IGNITE-4362 DML: the multiplication for SET uses the data type for the
>> result from the right side
>> 
>>
>>
>> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:
>>
>> > Vladimir,
>> >
>> > Agree. The issue looks critical. Who will be reviewing it?
>> >
>> > —
>> > Denis
>> >
>> > > On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
>> > wrote:
>> > >
>> > > Igniters,
>> > >
>> > > I assembled and merged release notes to the branch ignite-1.8. Looks
>> like
>> > > we are almost ready to start vote. The only outstanding issue which
>> looks
>> > > pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
>> > > start vote, unless anyone has some other concerns.
>> > >
>> > > [1] https://issues.apache.org/jira/browse/IGNITE-4340
>> > >
>> > > Vladimir.
>> > >
>> > > On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
>> > wrote:
>> > >
>> > >> Denis,
>> > >>
>> > >> I've took a look on the first issue [1], and it seems like it was
>> > already
>> > >> resolved
>> > >> by another fix made by Alexander.
>> > >>
>> > >> For the second issue [2] I have raised a PR.
>> > >>
>> > >> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
>> > >> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
>> > >>
>> > >> Best Regards,
>> > >> Igor
>> > >>
>> > >> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
>> wrote:
>> > >>
>> > >>> I’ve faced with two more issues while was working with Ignite from
>> PHP
>> > >> PDO
>> > >>> side.
>> > >>>
>> > >>> The first one is related to DML.
>> > >>> DML and PHP PDO: double field is converted to bigdecimal <
>> > >>> https://issues.apache.org/jira/browse/IGNITE-4346>
>> > >>>
>> > >>> Alexander P. and Igor S. please pull together and fix this issue
>> before
>> > >>> 1.8 is sent for vote.
>> > >>>
>> > >>> The second issue is related to ODBC and affects the usability only.
>> > Igor
>> > >>> S., please try to address it as a part of 1.8 as well.
>> > >>> ODBC: NPE when cache name is different from the one configured in
>> DSN <
>> > >>> https://issues.apache.org/jira/browse/IGNITE-4347>
>> > >>>
>> > >>> —
>> > >>> Denis
>> > >>>
>> >  On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
>> > >>> wrote:
>> > 
>> >  Hi
>> > 
>> >  Update for DML testing:
>> > 
>> >  IGNITE-4342 DML: clear() on atomic cache causes the exception from
>> > >>> previous
>> >  failed DML statement > > >> jira/browse/IGNITE-4342>
>> > 
>> > 
>> > 
>> >  On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
>> > >> wrote:
>> > 
>> > > Vladimir,
>> > >
>> > > Please add to the release notes information regarding this feature
>> > > https://issues.apache.org/jira/browse/IGNITE-2310 <
>> > > https://issues.apache.org/jira/browse/IGNITE-2310>
>> > >
>> > > Essentially, it allows locking a partition while a remote
>> computation
>> > >> is
>> > > being executed on a node. I’ve already documented the feature here.
>> > > http://apacheignite.gridgain.org/v1.7/docs/collocate-
>> > > compute-and-data#affinity-call-and-run-methods <
>> > > http://apacheignite.gridgain.org/v1.7/docs/collocate-
>> > > compute-and-data#affinity-call-and-run-methods>
>> > >
>> > > —
>> > > Denis
>> > >
>> > >> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov <
>> voze...@gridgain.com>
>> > > wrote:
>> > >>
>> > >> Folks,
>> > >>
>> > >> I need to create RELEASE NOTES. Please advise which notable
>> ti

Re: Apache Ignite 1.8 Release

[Dmitriy Setrakyan]

Alexander, thanks for making the fixes to DML. Are you adding JUnits for
all the fixes you are making?

On Fri, Dec 2, 2016 at 9:51 PM, Sergey Kozlov  wrote:

> Hi
>
> Recent fixes from Alexander made DML much better!
>
> I've found one issue but it is not blocker for the release:
>
> IGNITE-4362 DML: the multiplication for SET uses the data type for the
> result from the right side
> 
>
>
> On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:
>
> > Vladimir,
> >
> > Agree. The issue looks critical. Who will be reviewing it?
> >
> > —
> > Denis
> >
> > > On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
> > wrote:
> > >
> > > Igniters,
> > >
> > > I assembled and merged release notes to the branch ignite-1.8. Looks
> like
> > > we are almost ready to start vote. The only outstanding issue which
> looks
> > > pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
> > > start vote, unless anyone has some other concerns.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-4340
> > >
> > > Vladimir.
> > >
> > > On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
> > wrote:
> > >
> > >> Denis,
> > >>
> > >> I've took a look on the first issue [1], and it seems like it was
> > already
> > >> resolved
> > >> by another fix made by Alexander.
> > >>
> > >> For the second issue [2] I have raised a PR.
> > >>
> > >> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
> > >> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
> > >>
> > >> Best Regards,
> > >> Igor
> > >>
> > >> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda 
> wrote:
> > >>
> > >>> I’ve faced with two more issues while was working with Ignite from
> PHP
> > >> PDO
> > >>> side.
> > >>>
> > >>> The first one is related to DML.
> > >>> DML and PHP PDO: double field is converted to bigdecimal <
> > >>> https://issues.apache.org/jira/browse/IGNITE-4346>
> > >>>
> > >>> Alexander P. and Igor S. please pull together and fix this issue
> before
> > >>> 1.8 is sent for vote.
> > >>>
> > >>> The second issue is related to ODBC and affects the usability only.
> > Igor
> > >>> S., please try to address it as a part of 1.8 as well.
> > >>> ODBC: NPE when cache name is different from the one configured in
> DSN <
> > >>> https://issues.apache.org/jira/browse/IGNITE-4347>
> > >>>
> > >>> —
> > >>> Denis
> > >>>
> >  On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
> > >>> wrote:
> > 
> >  Hi
> > 
> >  Update for DML testing:
> > 
> >  IGNITE-4342 DML: clear() on atomic cache causes the exception from
> > >>> previous
> >  failed DML statement  > >> jira/browse/IGNITE-4342>
> > 
> > 
> > 
> >  On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
> > >> wrote:
> > 
> > > Vladimir,
> > >
> > > Please add to the release notes information regarding this feature
> > > https://issues.apache.org/jira/browse/IGNITE-2310 <
> > > https://issues.apache.org/jira/browse/IGNITE-2310>
> > >
> > > Essentially, it allows locking a partition while a remote
> computation
> > >> is
> > > being executed on a node. I’ve already documented the feature here.
> > > http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > > compute-and-data#affinity-call-and-run-methods <
> > > http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > > compute-and-data#affinity-call-and-run-methods>
> > >
> > > —
> > > Denis
> > >
> > >> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > wrote:
> > >>
> > >> Folks,
> > >>
> > >> I need to create RELEASE NOTES. Please advise which notable
> tickets
> > >> you
> > >> completed as a part of 1.8 release.
> > >>
> > >> Vladimir.
> > >>
> > >> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov <
> > skoz...@gridgain.com
> > >>>
> > > wrote:
> > >>
> > >>> Hi
> > >>>
> > >>> Could someone explain why Cassandra module splitted into three
> > parts
> > >>> in
> > >>> optional directory for binary fabric build? At the moment I see
> > > following
> > >>> unclear points
> > >>> 1. ignite-cassandra directory contains README.txt only
> > >>> 2. Does ignite-cassandra-serializers depend on
> > >> ignite-cassandra-store?
> > > In
> > >>> that case why do not make one module?
> > >>>
> > >>>
> > >>>
> > >>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > >>> alexander.a.pasche...@gmail.com> wrote:
> > >>>
> >  IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already
> > merged
> > >>> in
> >  1.8 branch).
> > 
> >  Meanwhile everything SQL/DML related seems to be in pull
> >  requests/reviewed/fixed/merged (no issues unapproached/not
> fixed).
> > 
> >  - Alex
> > 
> > 
> > 
> >  2016-11-24 22:59 GMT+03:00 Sergey Kozlov  >:
> > >>

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

Recent fixes from Alexander made DML much better!

I've found one issue but it is not blocker for the release:

IGNITE-4362 DML: the multiplication for SET uses the data type for the
result from the right side



On Fri, Dec 2, 2016 at 8:26 PM, Denis Magda  wrote:

> Vladimir,
>
> Agree. The issue looks critical. Who will be reviewing it?
>
> —
> Denis
>
> > On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov 
> wrote:
> >
> > Igniters,
> >
> > I assembled and merged release notes to the branch ignite-1.8. Looks like
> > we are almost ready to start vote. The only outstanding issue which looks
> > pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
> > start vote, unless anyone has some other concerns.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4340
> >
> > Vladimir.
> >
> > On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego 
> wrote:
> >
> >> Denis,
> >>
> >> I've took a look on the first issue [1], and it seems like it was
> already
> >> resolved
> >> by another fix made by Alexander.
> >>
> >> For the second issue [2] I have raised a PR.
> >>
> >> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
> >> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda  wrote:
> >>
> >>> I’ve faced with two more issues while was working with Ignite from PHP
> >> PDO
> >>> side.
> >>>
> >>> The first one is related to DML.
> >>> DML and PHP PDO: double field is converted to bigdecimal <
> >>> https://issues.apache.org/jira/browse/IGNITE-4346>
> >>>
> >>> Alexander P. and Igor S. please pull together and fix this issue before
> >>> 1.8 is sent for vote.
> >>>
> >>> The second issue is related to ODBC and affects the usability only.
> Igor
> >>> S., please try to address it as a part of 1.8 as well.
> >>> ODBC: NPE when cache name is different from the one configured in DSN <
> >>> https://issues.apache.org/jira/browse/IGNITE-4347>
> >>>
> >>> —
> >>> Denis
> >>>
>  On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
> >>> wrote:
> 
>  Hi
> 
>  Update for DML testing:
> 
>  IGNITE-4342 DML: clear() on atomic cache causes the exception from
> >>> previous
>  failed DML statement  >> jira/browse/IGNITE-4342>
> 
> 
> 
>  On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
> >> wrote:
> 
> > Vladimir,
> >
> > Please add to the release notes information regarding this feature
> > https://issues.apache.org/jira/browse/IGNITE-2310 <
> > https://issues.apache.org/jira/browse/IGNITE-2310>
> >
> > Essentially, it allows locking a partition while a remote computation
> >> is
> > being executed on a node. I’ve already documented the feature here.
> > http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > compute-and-data#affinity-call-and-run-methods <
> > http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > compute-and-data#affinity-call-and-run-methods>
> >
> > —
> > Denis
> >
> >> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> > wrote:
> >>
> >> Folks,
> >>
> >> I need to create RELEASE NOTES. Please advise which notable tickets
> >> you
> >> completed as a part of 1.8 release.
> >>
> >> Vladimir.
> >>
> >> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov <
> skoz...@gridgain.com
> >>>
> > wrote:
> >>
> >>> Hi
> >>>
> >>> Could someone explain why Cassandra module splitted into three
> parts
> >>> in
> >>> optional directory for binary fabric build? At the moment I see
> > following
> >>> unclear points
> >>> 1. ignite-cassandra directory contains README.txt only
> >>> 2. Does ignite-cassandra-serializers depend on
> >> ignite-cassandra-store?
> > In
> >>> that case why do not make one module?
> >>>
> >>>
> >>>
> >>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> >>> alexander.a.pasche...@gmail.com> wrote:
> >>>
>  IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already
> merged
> >>> in
>  1.8 branch).
> 
>  Meanwhile everything SQL/DML related seems to be in pull
>  requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> 
>  - Alex
> 
> 
> 
>  2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > Hi
> >
> > I found two issues for 1.8:
> > IGNITE-4304 ClusterTopologyCheckedException: Failed to send
> >> message
>  because
> > node left grid  jira/browse/IGNITE-4304
> >>>
> > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > 
> >
> > Could someone experienced take a look?
> >
> > On Thu, Nov 24, 2016 at 12:12 PM, Vl

Re: Apache Ignite 1.8 Release

[Denis Magda]

Vladimir,

Agree. The issue looks critical. Who will be reviewing it? 

—
Denis

> On Dec 2, 2016, at 2:35 AM, Vladimir Ozerov  wrote:
> 
> Igniters,
> 
> I assembled and merged release notes to the branch ignite-1.8. Looks like
> we are almost ready to start vote. The only outstanding issue which looks
> pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
> start vote, unless anyone has some other concerns.
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-4340
> 
> Vladimir.
> 
> On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego  wrote:
> 
>> Denis,
>> 
>> I've took a look on the first issue [1], and it seems like it was already
>> resolved
>> by another fix made by Alexander.
>> 
>> For the second issue [2] I have raised a PR.
>> 
>> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
>> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
>> 
>> Best Regards,
>> Igor
>> 
>> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda  wrote:
>> 
>>> I’ve faced with two more issues while was working with Ignite from PHP
>> PDO
>>> side.
>>> 
>>> The first one is related to DML.
>>> DML and PHP PDO: double field is converted to bigdecimal <
>>> https://issues.apache.org/jira/browse/IGNITE-4346>
>>> 
>>> Alexander P. and Igor S. please pull together and fix this issue before
>>> 1.8 is sent for vote.
>>> 
>>> The second issue is related to ODBC and affects the usability only. Igor
>>> S., please try to address it as a part of 1.8 as well.
>>> ODBC: NPE when cache name is different from the one configured in DSN <
>>> https://issues.apache.org/jira/browse/IGNITE-4347>
>>> 
>>> —
>>> Denis
>>> 
 On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
>>> wrote:
 
 Hi
 
 Update for DML testing:
 
 IGNITE-4342 DML: clear() on atomic cache causes the exception from
>>> previous
 failed DML statement > jira/browse/IGNITE-4342>
 
 
 
 On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
>> wrote:
 
> Vladimir,
> 
> Please add to the release notes information regarding this feature
> https://issues.apache.org/jira/browse/IGNITE-2310 <
> https://issues.apache.org/jira/browse/IGNITE-2310>
> 
> Essentially, it allows locking a partition while a remote computation
>> is
> being executed on a node. I’ve already documented the feature here.
> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> compute-and-data#affinity-call-and-run-methods <
> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> compute-and-data#affinity-call-and-run-methods>
> 
> —
> Denis
> 
>> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> wrote:
>> 
>> Folks,
>> 
>> I need to create RELEASE NOTES. Please advise which notable tickets
>> you
>> completed as a part of 1.8 release.
>> 
>> Vladimir.
>> 
>> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov >> 
> wrote:
>> 
>>> Hi
>>> 
>>> Could someone explain why Cassandra module splitted into three parts
>>> in
>>> optional directory for binary fabric build? At the moment I see
> following
>>> unclear points
>>> 1. ignite-cassandra directory contains README.txt only
>>> 2. Does ignite-cassandra-serializers depend on
>> ignite-cassandra-store?
> In
>>> that case why do not make one module?
>>> 
>>> 
>>> 
>>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>>> alexander.a.pasche...@gmail.com> wrote:
>>> 
 IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
>>> in
 1.8 branch).
 
 Meanwhile everything SQL/DML related seems to be in pull
 requests/reviewed/fixed/merged (no issues unapproached/not fixed).
 
 - Alex
 
 
 
 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> Hi
> 
> I found two issues for 1.8:
> IGNITE-4304 ClusterTopologyCheckedException: Failed to send
>> message
 because
> node left grid >> 
> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> 
> 
> Could someone experienced take a look?
> 
> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>>> voze...@gridgain.com>
> wrote:
> 
>> Folks,
>> 
>> DML is merged to ignite-1.8, but according to JIRA reports
>> several
 problems
>> with it were revealed. I propose to focus on DML finalization in
 ignite-1.8
>> branch, and minimize other merges to it, targeting them for the
>>> next
>> release (1.9, 2.0?).
>> 
>> Any objections?
>> 
>> Vladimir.
>> 
>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego <
>> isap...@gridgain.com
 
 wrote:
>>>

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Igniters,

I assembled and merged release notes to the branch ignite-1.8. Looks like
we are almost ready to start vote. The only outstanding issue which looks
pretty nasty to me is IGNITE-4340 [1]. Let's wait until it resolved and
start vote, unless anyone has some other concerns.

[1] https://issues.apache.org/jira/browse/IGNITE-4340

Vladimir.

On Thu, Dec 1, 2016 at 7:54 PM, Igor Sapego  wrote:

> Denis,
>
> I've took a look on the first issue [1], and it seems like it was already
> resolved
> by another fix made by Alexander.
>
> For the second issue [2] I have raised a PR.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-4346
> [2] - https://issues.apache.org/jira/browse/IGNITE-4347
>
> Best Regards,
> Igor
>
> On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda  wrote:
>
> > I’ve faced with two more issues while was working with Ignite from PHP
> PDO
> > side.
> >
> > The first one is related to DML.
> > DML and PHP PDO: double field is converted to bigdecimal <
> > https://issues.apache.org/jira/browse/IGNITE-4346>
> >
> > Alexander P. and Igor S. please pull together and fix this issue before
> > 1.8 is sent for vote.
> >
> > The second issue is related to ODBC and affects the usability only. Igor
> > S., please try to address it as a part of 1.8 as well.
> > ODBC: NPE when cache name is different from the one configured in DSN <
> > https://issues.apache.org/jira/browse/IGNITE-4347>
> >
> > —
> > Denis
> >
> > > On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
> > wrote:
> > >
> > > Hi
> > >
> > > Update for DML testing:
> > >
> > > IGNITE-4342 DML: clear() on atomic cache causes the exception from
> > previous
> > > failed DML statement  jira/browse/IGNITE-4342>
> > >
> > >
> > >
> > > On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda 
> wrote:
> > >
> > >> Vladimir,
> > >>
> > >> Please add to the release notes information regarding this feature
> > >> https://issues.apache.org/jira/browse/IGNITE-2310 <
> > >> https://issues.apache.org/jira/browse/IGNITE-2310>
> > >>
> > >> Essentially, it allows locking a partition while a remote computation
> is
> > >> being executed on a node. I’ve already documented the feature here.
> > >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > >> compute-and-data#affinity-call-and-run-methods <
> > >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> > >> compute-and-data#affinity-call-and-run-methods>
> > >>
> > >> —
> > >> Denis
> > >>
> > >>> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> > >> wrote:
> > >>>
> > >>> Folks,
> > >>>
> > >>> I need to create RELEASE NOTES. Please advise which notable tickets
> you
> > >>> completed as a part of 1.8 release.
> > >>>
> > >>> Vladimir.
> > >>>
> > >>> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov  >
> > >> wrote:
> > >>>
> >  Hi
> > 
> >  Could someone explain why Cassandra module splitted into three parts
> > in
> >  optional directory for binary fabric build? At the moment I see
> > >> following
> >  unclear points
> >  1. ignite-cassandra directory contains README.txt only
> >  2. Does ignite-cassandra-serializers depend on
> ignite-cassandra-store?
> > >> In
> >  that case why do not make one module?
> > 
> > 
> > 
> >  On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> >  alexander.a.pasche...@gmail.com> wrote:
> > 
> > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> > in
> > > 1.8 branch).
> > >
> > > Meanwhile everything SQL/DML related seems to be in pull
> > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > >
> > > - Alex
> > >
> > >
> > >
> > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > >> Hi
> > >>
> > >> I found two issues for 1.8:
> > >> IGNITE-4304 ClusterTopologyCheckedException: Failed to send
> message
> > > because
> > >> node left grid  >
> > >> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > >> 
> > >>
> > >> Could someone experienced take a look?
> > >>
> > >> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> >  voze...@gridgain.com>
> > >> wrote:
> > >>
> > >>> Folks,
> > >>>
> > >>> DML is merged to ignite-1.8, but according to JIRA reports
> several
> > > problems
> > >>> with it were revealed. I propose to focus on DML finalization in
> > > ignite-1.8
> > >>> branch, and minimize other merges to it, targeting them for the
> > next
> > >>> release (1.9, 2.0?).
> > >>>
> > >>> Any objections?
> > >>>
> > >>> Vladimir.
> > >>>
> > >>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego <
> isap...@gridgain.com
> > >
> > > wrote:
> > >>>
> >  Denis,
> > 
> >  I've raised PRs and Vladimir has merged them into ignite-1.8.
> But
> >  now
> > >

Re: Apache Ignite 1.8 Release

[Igor Sapego]

Denis,

I've took a look on the first issue [1], and it seems like it was already
resolved
by another fix made by Alexander.

For the second issue [2] I have raised a PR.

[1] - https://issues.apache.org/jira/browse/IGNITE-4346
[2] - https://issues.apache.org/jira/browse/IGNITE-4347

Best Regards,
Igor

On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda  wrote:

> I’ve faced with two more issues while was working with Ignite from PHP PDO
> side.
>
> The first one is related to DML.
> DML and PHP PDO: double field is converted to bigdecimal <
> https://issues.apache.org/jira/browse/IGNITE-4346>
>
> Alexander P. and Igor S. please pull together and fix this issue before
> 1.8 is sent for vote.
>
> The second issue is related to ODBC and affects the usability only. Igor
> S., please try to address it as a part of 1.8 as well.
> ODBC: NPE when cache name is different from the one configured in DSN <
> https://issues.apache.org/jira/browse/IGNITE-4347>
>
> —
> Denis
>
> > On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
> wrote:
> >
> > Hi
> >
> > Update for DML testing:
> >
> > IGNITE-4342 DML: clear() on atomic cache causes the exception from
> previous
> > failed DML statement 
> >
> >
> >
> > On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda  wrote:
> >
> >> Vladimir,
> >>
> >> Please add to the release notes information regarding this feature
> >> https://issues.apache.org/jira/browse/IGNITE-2310 <
> >> https://issues.apache.org/jira/browse/IGNITE-2310>
> >>
> >> Essentially, it allows locking a partition while a remote computation is
> >> being executed on a node. I’ve already documented the feature here.
> >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> >> compute-and-data#affinity-call-and-run-methods <
> >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> >> compute-and-data#affinity-call-and-run-methods>
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> >> wrote:
> >>>
> >>> Folks,
> >>>
> >>> I need to create RELEASE NOTES. Please advise which notable tickets you
> >>> completed as a part of 1.8 release.
> >>>
> >>> Vladimir.
> >>>
> >>> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> >> wrote:
> >>>
>  Hi
> 
>  Could someone explain why Cassandra module splitted into three parts
> in
>  optional directory for binary fabric build? At the moment I see
> >> following
>  unclear points
>  1. ignite-cassandra directory contains README.txt only
>  2. Does ignite-cassandra-serializers depend on ignite-cassandra-store?
> >> In
>  that case why do not make one module?
> 
> 
> 
>  On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>  alexander.a.pasche...@gmail.com> wrote:
> 
> > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> in
> > 1.8 branch).
> >
> > Meanwhile everything SQL/DML related seems to be in pull
> > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> >
> > - Alex
> >
> >
> >
> > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> >> Hi
> >>
> >> I found two issues for 1.8:
> >> IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > because
> >> node left grid 
> >> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> >> 
> >>
> >> Could someone experienced take a look?
> >>
> >> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>  voze...@gridgain.com>
> >> wrote:
> >>
> >>> Folks,
> >>>
> >>> DML is merged to ignite-1.8, but according to JIRA reports several
> > problems
> >>> with it were revealed. I propose to focus on DML finalization in
> > ignite-1.8
> >>> branch, and minimize other merges to it, targeting them for the
> next
> >>> release (1.9, 2.0?).
> >>>
> >>> Any objections?
> >>>
> >>> Vladimir.
> >>>
> >>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  >
> > wrote:
> >>>
>  Denis,
> 
>  I've raised PRs and Vladimir has merged them into ignite-1.8. But
>  now
> > we
>  have some
>  failing ODBC tests in the branch. I'm currently working on them.
>  There
> >>> is a
>  ticket for
>  that which you can track [1]. I'll add all my findings there.
> 
>  [1] https://issues.apache.org/jira/browse/IGNITE-4288
> 
>  Best Regards,
>  Igor
> 
>  On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > wrote:
> 
> > Alexander,
> >
> > Awesome news, thanks for making this happen!
> >
> > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
>  Can I
>  start
> > testing that PHP-PDO guidance [1] is correct?
> >
> >

Re: Apache Ignite 1.8 Release

[Denis Magda]

I’ve faced with two more issues while was working with Ignite from PHP PDO side.

The first one is related to DML.
DML and PHP PDO: double field is converted to bigdecimal 


Alexander P. and Igor S. please pull together and fix this issue before 1.8 is 
sent for vote.

The second issue is related to ODBC and affects the usability only. Igor S., 
please try to address it as a part of 1.8 as well.
ODBC: NPE when cache name is different from the one configured in DSN 


—
Denis

> On Nov 30, 2016, at 12:01 PM, Sergey Kozlov  wrote:
> 
> Hi
> 
> Update for DML testing:
> 
> IGNITE-4342 DML: clear() on atomic cache causes the exception from previous
> failed DML statement 
> 
> 
> 
> On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda  wrote:
> 
>> Vladimir,
>> 
>> Please add to the release notes information regarding this feature
>> https://issues.apache.org/jira/browse/IGNITE-2310 <
>> https://issues.apache.org/jira/browse/IGNITE-2310>
>> 
>> Essentially, it allows locking a partition while a remote computation is
>> being executed on a node. I’ve already documented the feature here.
>> http://apacheignite.gridgain.org/v1.7/docs/collocate-
>> compute-and-data#affinity-call-and-run-methods <
>> http://apacheignite.gridgain.org/v1.7/docs/collocate-
>> compute-and-data#affinity-call-and-run-methods>
>> 
>> —
>> Denis
>> 
>>> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
>> wrote:
>>> 
>>> Folks,
>>> 
>>> I need to create RELEASE NOTES. Please advise which notable tickets you
>>> completed as a part of 1.8 release.
>>> 
>>> Vladimir.
>>> 
>>> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
>> wrote:
>>> 
 Hi
 
 Could someone explain why Cassandra module splitted into three parts in
 optional directory for binary fabric build? At the moment I see
>> following
 unclear points
 1. ignite-cassandra directory contains README.txt only
 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store?
>> In
 that case why do not make one module?
 
 
 
 On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
 alexander.a.pasche...@gmail.com> wrote:
 
> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> 1.8 branch).
> 
> Meanwhile everything SQL/DML related seems to be in pull
> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> 
> - Alex
> 
> 
> 
> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
>> Hi
>> 
>> I found two issues for 1.8:
>> IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> because
>> node left grid 
>> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
>> 
>> 
>> Could someone experienced take a look?
>> 
>> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
 voze...@gridgain.com>
>> wrote:
>> 
>>> Folks,
>>> 
>>> DML is merged to ignite-1.8, but according to JIRA reports several
> problems
>>> with it were revealed. I propose to focus on DML finalization in
> ignite-1.8
>>> branch, and minimize other merges to it, targeting them for the next
>>> release (1.9, 2.0?).
>>> 
>>> Any objections?
>>> 
>>> Vladimir.
>>> 
>>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> wrote:
>>> 
 Denis,
 
 I've raised PRs and Vladimir has merged them into ignite-1.8. But
 now
> we
 have some
 failing ODBC tests in the branch. I'm currently working on them.
 There
>>> is a
 ticket for
 that which you can track [1]. I'll add all my findings there.
 
 [1] https://issues.apache.org/jira/browse/IGNITE-4288
 
 Best Regards,
 Igor
 
 On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> wrote:
 
> Alexander,
> 
> Awesome news, thanks for making this happen!
> 
> Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
 Can I
 start
> testing that PHP-PDO guidance [1] is correct?
> 
> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> https://apacheignite.readme.io/docs/pdo-interoperability>
> 
> —
> Denis
> 
>> On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>> 
>> Folks,
>> 
>> Yesterday it'd been agreed with Sergi that DML branch is now
 good
> to
>> be included into 1.8 branch that is to be created.
>> 
>> Minor review fixes, should they be made, and test fixes will be
>> incorporated into 1.8 as

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

Update for DML testing:

IGNITE-4342 DML: clear() on atomic cache causes the exception from previous
failed DML statement 



On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda  wrote:

> Vladimir,
>
> Please add to the release notes information regarding this feature
> https://issues.apache.org/jira/browse/IGNITE-2310 <
> https://issues.apache.org/jira/browse/IGNITE-2310>
>
> Essentially, it allows locking a partition while a remote computation is
> being executed on a node. I’ve already documented the feature here.
> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> compute-and-data#affinity-call-and-run-methods <
> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> compute-and-data#affinity-call-and-run-methods>
>
> —
> Denis
>
> > On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> wrote:
> >
> > Folks,
> >
> > I need to create RELEASE NOTES. Please advise which notable tickets you
> > completed as a part of 1.8 release.
> >
> > Vladimir.
> >
> > On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> wrote:
> >
> >> Hi
> >>
> >> Could someone explain why Cassandra module splitted into three parts in
> >> optional directory for binary fabric build? At the moment I see
> following
> >> unclear points
> >> 1. ignite-cassandra directory contains README.txt only
> >> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store?
> In
> >> that case why do not make one module?
> >>
> >>
> >>
> >> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> >> alexander.a.pasche...@gmail.com> wrote:
> >>
> >>> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> >>> 1.8 branch).
> >>>
> >>> Meanwhile everything SQL/DML related seems to be in pull
> >>> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> >>>
> >>> - Alex
> >>>
> >>>
> >>>
> >>> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
>  Hi
> 
>  I found two issues for 1.8:
>  IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> >>> because
>  node left grid 
>  IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
>  
> 
>  Could someone experienced take a look?
> 
>  On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> >> voze...@gridgain.com>
>  wrote:
> 
> > Folks,
> >
> > DML is merged to ignite-1.8, but according to JIRA reports several
> >>> problems
> > with it were revealed. I propose to focus on DML finalization in
> >>> ignite-1.8
> > branch, and minimize other merges to it, targeting them for the next
> > release (1.9, 2.0?).
> >
> > Any objections?
> >
> > Vladimir.
> >
> > On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> >>> wrote:
> >
> >> Denis,
> >>
> >> I've raised PRs and Vladimir has merged them into ignite-1.8. But
> >> now
> >>> we
> >> have some
> >> failing ODBC tests in the branch. I'm currently working on them.
> >> There
> > is a
> >> ticket for
> >> that which you can track [1]. I'll add all my findings there.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-4288
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> >>> wrote:
> >>
> >>> Alexander,
> >>>
> >>> Awesome news, thanks for making this happen!
> >>>
> >>> Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> >> Can I
> >> start
> >>> testing that PHP-PDO guidance [1] is correct?
> >>>
> >>> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> >>> https://apacheignite.readme.io/docs/pdo-interoperability>
> >>>
> >>> —
> >>> Denis
> >>>
>  On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> >>> alexander.a.pasche...@gmail.com> wrote:
> 
>  Folks,
> 
>  Yesterday it'd been agreed with Sergi that DML branch is now
> >> good
> >>> to
>  be included into 1.8 branch that is to be created.
> 
>  Minor review fixes, should they be made, and test fixes will be
>  incorporated into 1.8 as separate patches later.
> 
>  Also, it'd been agreed that, in order to deliver these new
> >>> features
> > on
>  time, two subtasks will be fixed in later releases (shortly):
> 
>  https://issues.apache.org/jira/browse/IGNITE-4268
>  https://issues.apache.org/jira/browse/IGNITE-4269
> 
>  On failing tests:
>  https://issues.apache.org/jira/browse/IGNITE-2294?
> >>> focusedCommentId=15683377
> 
>  - Alex
> 
>  2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>  :
> > Vlad,
> >
> > Most likely today.
> >
> > - Alex
> >
> > 2016-11-22 11:25 GMT+

Re: Apache Ignite 1.8 Release

[Denis Magda]

Vladimir,

Please add to the release notes information regarding this feature
https://issues.apache.org/jira/browse/IGNITE-2310 


Essentially, it allows locking a partition while a remote computation is being 
executed on a node. I’ve already documented the feature here.
http://apacheignite.gridgain.org/v1.7/docs/collocate-compute-and-data#affinity-call-and-run-methods
 


—
Denis

> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov  wrote:
> 
> Folks,
> 
> I need to create RELEASE NOTES. Please advise which notable tickets you
> completed as a part of 1.8 release.
> 
> Vladimir.
> 
> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov  wrote:
> 
>> Hi
>> 
>> Could someone explain why Cassandra module splitted into three parts in
>> optional directory for binary fabric build? At the moment I see following
>> unclear points
>> 1. ignite-cassandra directory contains README.txt only
>> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
>> that case why do not make one module?
>> 
>> 
>> 
>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> 
>>> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
>>> 1.8 branch).
>>> 
>>> Meanwhile everything SQL/DML related seems to be in pull
>>> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
>>> 
>>> - Alex
>>> 
>>> 
>>> 
>>> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
 Hi
 
 I found two issues for 1.8:
 IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
>>> because
 node left grid 
 IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
 
 
 Could someone experienced take a look?
 
 On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>> voze...@gridgain.com>
 wrote:
 
> Folks,
> 
> DML is merged to ignite-1.8, but according to JIRA reports several
>>> problems
> with it were revealed. I propose to focus on DML finalization in
>>> ignite-1.8
> branch, and minimize other merges to it, targeting them for the next
> release (1.9, 2.0?).
> 
> Any objections?
> 
> Vladimir.
> 
> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
>>> wrote:
> 
>> Denis,
>> 
>> I've raised PRs and Vladimir has merged them into ignite-1.8. But
>> now
>>> we
>> have some
>> failing ODBC tests in the branch. I'm currently working on them.
>> There
> is a
>> ticket for
>> that which you can track [1]. I'll add all my findings there.
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-4288
>> 
>> Best Regards,
>> Igor
>> 
>> On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
>>> wrote:
>> 
>>> Alexander,
>>> 
>>> Awesome news, thanks for making this happen!
>>> 
>>> Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
>> Can I
>> start
>>> testing that PHP-PDO guidance [1] is correct?
>>> 
>>> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
>>> https://apacheignite.readme.io/docs/pdo-interoperability>
>>> 
>>> —
>>> Denis
>>> 
 On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
>>> alexander.a.pasche...@gmail.com> wrote:
 
 Folks,
 
 Yesterday it'd been agreed with Sergi that DML branch is now
>> good
>>> to
 be included into 1.8 branch that is to be created.
 
 Minor review fixes, should they be made, and test fixes will be
 incorporated into 1.8 as separate patches later.
 
 Also, it'd been agreed that, in order to deliver these new
>>> features
> on
 time, two subtasks will be fixed in later releases (shortly):
 
 https://issues.apache.org/jira/browse/IGNITE-4268
 https://issues.apache.org/jira/browse/IGNITE-4269
 
 On failing tests:
 https://issues.apache.org/jira/browse/IGNITE-2294?
>>> focusedCommentId=15683377
 
 - Alex
 
 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
 :
> Vlad,
> 
> Most likely today.
> 
> - Alex
> 
> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
>> voze...@gridgain.com
 :
>> Igniters,
>> 
>> I went through remaining tickets assigned to 1.8 and it seems
>>> that
> we
>>> are
>> pretty close to release. As far as I understand the biggest
> remaining
>> feature is DML [1]. I think we can create separate branch for
>>> 1.8
> as
>>> soon
>> as it is merged. Alex, do you have any idea on when it might
> happen?
>> 
>> Vladimir.
>>>

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

The list of issues found today:

IGNITE-4334 DML: INSERT INTO SELECT FROM statement fails if copy from
partitioned to replicated cache


On Tue, Nov 29, 2016 at 9:56 PM, Sergey Kozlov  wrote:

> Denis
>
> We've good progress for DML. But unlike the regular queries DML has
> significantly more specific cases that required our attention. Though some
> cases aren't bugs but they've another behavior than user can expect using
> SQL-related experience.
>
>
> On Tue, Nov 29, 2016 at 8:33 PM, Denis Magda  wrote:
>
>> Alexander,
>>
>> Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document
>> this limitation on the DML page you have been working on.
>>
>> —
>> Denis
>>
>> > On Nov 29, 2016, at 9:31 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> >
>> > Denis,
>> >
>> > See the comment to issue. Note that this affects DML in case of INSERT
>> > from subquery with specific returned column result types AND aside of
>> > DML affects SELECTs - the user isn't able to retrieve exactly what
>> > they have put to cache as some object's field. However, according to
>> > Vlad, arrays of wrappers are seldom present in real SQL related use
>> > cases, so there's little to worry about.
>> >
>> > - Alex
>> >
>> > 2016-11-29 20:21 GMT+03:00 Denis Magda :
>> >> Alexander,
>> >>
>> >> Do you mean this issue recently opened by you?
>> >> https://issues.apache.org/jira/browse/IGNITE-4331 <
>> https://issues.apache.org/jira/browse/IGNITE-4331>
>> >>
>> >> How would it affect the overall user experience? Could you provide DML
>> queries examples that won’t work due to the bug.
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> >>>
>> >>> DML is done as for now, example is done too, currently there's no open
>> >>> issues related with it (besides documentation which I'm working on).
>> >>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>> >>> related and is currently in won't fix state as agreed with Vlad, I've
>> >>> created issues detailing it.
>> >>>
>> >>> - Alex
>> >>>
>> >>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>>  Hi
>> 
>>  There's update for DML testing and binary package:
>> 
>>  IGNITE-4321 Cassandra modules
>>  
>>  IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>>  IgniteException: Wrong value has been set
>>  
>> 
>>  On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov <
>> akuznet...@apache.org>
>>  wrote:
>> 
>> > Vladimir,
>> >
>> > IGNITE-3443 Implement collecting what SQL statements executed on
>> cluster
>> > and their metrics.
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>> 
>> 
>> 
>>  --
>>  Sergey Kozlov
>>  GridGain Systems
>>  www.gridgain.com
>> >>
>>
>>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Denis

We've good progress for DML. But unlike the regular queries DML has
significantly more specific cases that required our attention. Though some
cases aren't bugs but they've another behavior than user can expect using
SQL-related experience.


On Tue, Nov 29, 2016 at 8:33 PM, Denis Magda  wrote:

> Alexander,
>
> Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document
> this limitation on the DML page you have been working on.
>
> —
> Denis
>
> > On Nov 29, 2016, at 9:31 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > Denis,
> >
> > See the comment to issue. Note that this affects DML in case of INSERT
> > from subquery with specific returned column result types AND aside of
> > DML affects SELECTs - the user isn't able to retrieve exactly what
> > they have put to cache as some object's field. However, according to
> > Vlad, arrays of wrappers are seldom present in real SQL related use
> > cases, so there's little to worry about.
> >
> > - Alex
> >
> > 2016-11-29 20:21 GMT+03:00 Denis Magda :
> >> Alexander,
> >>
> >> Do you mean this issue recently opened by you?
> >> https://issues.apache.org/jira/browse/IGNITE-4331 <
> https://issues.apache.org/jira/browse/IGNITE-4331>
> >>
> >> How would it affect the overall user experience? Could you provide DML
> queries examples that won’t work due to the bug.
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >>>
> >>> DML is done as for now, example is done too, currently there's no open
> >>> issues related with it (besides documentation which I'm working on).
> >>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
> >>> related and is currently in won't fix state as agreed with Vlad, I've
> >>> created issues detailing it.
> >>>
> >>> - Alex
> >>>
> >>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>  Hi
> 
>  There's update for DML testing and binary package:
> 
>  IGNITE-4321 Cassandra modules
>  
>  IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>  IgniteException: Wrong value has been set
>  
> 
>  On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov <
> akuznet...@apache.org>
>  wrote:
> 
> > Vladimir,
> >
> > IGNITE-3443 Implement collecting what SQL statements executed on
> cluster
> > and their metrics.
> >
> > --
> > Alexey Kuznetsov
> >
> 
> 
> 
>  --
>  Sergey Kozlov
>  GridGain Systems
>  www.gridgain.com
> >>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Now I see, thanks. Ok, I would suggest fixing it under 2.0 and document this 
limitation on the DML page you have been working on.

—
Denis

> On Nov 29, 2016, at 9:31 AM, Alexander Paschenko 
>  wrote:
> 
> Denis,
> 
> See the comment to issue. Note that this affects DML in case of INSERT
> from subquery with specific returned column result types AND aside of
> DML affects SELECTs - the user isn't able to retrieve exactly what
> they have put to cache as some object's field. However, according to
> Vlad, arrays of wrappers are seldom present in real SQL related use
> cases, so there's little to worry about.
> 
> - Alex
> 
> 2016-11-29 20:21 GMT+03:00 Denis Magda :
>> Alexander,
>> 
>> Do you mean this issue recently opened by you?
>> https://issues.apache.org/jira/browse/IGNITE-4331 
>> 
>> 
>> How would it affect the overall user experience? Could you provide DML 
>> queries examples that won’t work due to the bug.
>> 
>> —
>> Denis
>> 
>>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>>>  wrote:
>>> 
>>> DML is done as for now, example is done too, currently there's no open
>>> issues related with it (besides documentation which I'm working on).
>>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>>> related and is currently in won't fix state as agreed with Vlad, I've
>>> created issues detailing it.
>>> 
>>> - Alex
>>> 
>>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
 Hi
 
 There's update for DML testing and binary package:
 
 IGNITE-4321 Cassandra modules
 
 IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
 IgniteException: Wrong value has been set
 
 
 On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
 wrote:
 
> Vladimir,
> 
> IGNITE-3443 Implement collecting what SQL statements executed on cluster
> and their metrics.
> 
> --
> Alexey Kuznetsov
> 
 
 
 
 --
 Sergey Kozlov
 GridGain Systems
 www.gridgain.com
>> 

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Denis,

See the comment to issue. Note that this affects DML in case of INSERT
from subquery with specific returned column result types AND aside of
DML affects SELECTs - the user isn't able to retrieve exactly what
they have put to cache as some object's field. However, according to
Vlad, arrays of wrappers are seldom present in real SQL related use
cases, so there's little to worry about.

- Alex

2016-11-29 20:21 GMT+03:00 Denis Magda :
> Alexander,
>
> Do you mean this issue recently opened by you?
> https://issues.apache.org/jira/browse/IGNITE-4331 
> 
>
> How would it affect the overall user experience? Could you provide DML 
> queries examples that won’t work due to the bug.
>
> —
> Denis
>
>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>>  wrote:
>>
>> DML is done as for now, example is done too, currently there's no open
>> issues related with it (besides documentation which I'm working on).
>> Yesterday's problem turned out to be binary/SQL engine (pre DML)
>> related and is currently in won't fix state as agreed with Vlad, I've
>> created issues detailing it.
>>
>> - Alex
>>
>> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>>> Hi
>>>
>>> There's update for DML testing and binary package:
>>>
>>> IGNITE-4321 Cassandra modules
>>> 
>>> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>>> IgniteException: Wrong value has been set
>>> 
>>>
>>> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
>>> wrote:
>>>
 Vladimir,

 IGNITE-3443 Implement collecting what SQL statements executed on cluster
 and their metrics.

 --
 Alexey Kuznetsov

>>>
>>>
>>>
>>> --
>>> Sergey Kozlov
>>> GridGain Systems
>>> www.gridgain.com
>

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Do you mean this issue recently opened by you?
https://issues.apache.org/jira/browse/IGNITE-4331 


How would it affect the overall user experience? Could you provide DML queries 
examples that won’t work due to the bug.

—
Denis

> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko 
>  wrote:
> 
> DML is done as for now, example is done too, currently there's no open
> issues related with it (besides documentation which I'm working on).
> Yesterday's problem turned out to be binary/SQL engine (pre DML)
> related and is currently in won't fix state as agreed with Vlad, I've
> created issues detailing it.
> 
> - Alex
> 
> 2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
>> Hi
>> 
>> There's update for DML testing and binary package:
>> 
>> IGNITE-4321 Cassandra modules
>> 
>> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
>> IgniteException: Wrong value has been set
>> 
>> 
>> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
>> wrote:
>> 
>>> Vladimir,
>>> 
>>> IGNITE-3443 Implement collecting what SQL statements executed on cluster
>>> and their metrics.
>>> 
>>> --
>>> Alexey Kuznetsov
>>> 
>> 
>> 
>> 
>> --
>> Sergey Kozlov
>> GridGain Systems
>> www.gridgain.com

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

DML is done as for now, example is done too, currently there's no open
issues related with it (besides documentation which I'm working on).
Yesterday's problem turned out to be binary/SQL engine (pre DML)
related and is currently in won't fix state as agreed with Vlad, I've
created issues detailing it.

- Alex

2016-11-28 21:59 GMT+03:00 Sergey Kozlov :
> Hi
>
> There's update for DML testing and binary package:
>
> IGNITE-4321 Cassandra modules
> 
> IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
> IgniteException: Wrong value has been set
> 
>
> On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
> wrote:
>
>> Vladimir,
>>
>> IGNITE-3443 Implement collecting what SQL statements executed on cluster
>> and their metrics.
>>
>> --
>> Alexey Kuznetsov
>>
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

There's update for DML testing and binary package:

IGNITE-4321 Cassandra modules

IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
IgniteException: Wrong value has been set


On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
wrote:

> Vladimir,
>
> IGNITE-3443 Implement collecting what SQL statements executed on cluster
> and their metrics.
>
> --
> Alexey Kuznetsov
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: Apache Ignite 1.8 Release

[Alexey Kuznetsov]

Vladimir,

IGNITE-3443 Implement collecting what SQL statements executed on cluster
and their metrics.

-- 
Alexey Kuznetsov

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

I’ll encourage you to close DML example related ticket under 1.8 release as well
https://issues.apache.org/jira/browse/IGNITE-4017 


Otherwise the users will hard time trying to figure out how to set up gears and 
use DML in practice.

—
Denis

> On Nov 25, 2016, at 4:37 AM, Alexander Paschenko 
>  wrote:
> 
> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> 1.8 branch).
> 
> Meanwhile everything SQL/DML related seems to be in pull
> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> 
> - Alex
> 
> 
> 
> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
>> Hi
>> 
>> I found two issues for 1.8:
>> IGNITE-4304 ClusterTopologyCheckedException: Failed to send message because
>> node left grid 
>> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
>> 
>> 
>> Could someone experienced take a look?
>> 
>> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov 
>> wrote:
>> 
>>> Folks,
>>> 
>>> DML is merged to ignite-1.8, but according to JIRA reports several problems
>>> with it were revealed. I propose to focus on DML finalization in ignite-1.8
>>> branch, and minimize other merges to it, targeting them for the next
>>> release (1.9, 2.0?).
>>> 
>>> Any objections?
>>> 
>>> Vladimir.
>>> 
>>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:
>>> 
 Denis,
 
 I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
 have some
 failing ODBC tests in the branch. I'm currently working on them. There
>>> is a
 ticket for
 that which you can track [1]. I'll add all my findings there.
 
 [1] https://issues.apache.org/jira/browse/IGNITE-4288
 
 Best Regards,
 Igor
 
 On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
 
> Alexander,
> 
> Awesome news, thanks for making this happen!
> 
> Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
 start
> testing that PHP-PDO guidance [1] is correct?
> 
> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> https://apacheignite.readme.io/docs/pdo-interoperability>
> 
> —
> Denis
> 
>> On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>> 
>> Folks,
>> 
>> Yesterday it'd been agreed with Sergi that DML branch is now good to
>> be included into 1.8 branch that is to be created.
>> 
>> Minor review fixes, should they be made, and test fixes will be
>> incorporated into 1.8 as separate patches later.
>> 
>> Also, it'd been agreed that, in order to deliver these new features
>>> on
>> time, two subtasks will be fixed in later releases (shortly):
>> 
>> https://issues.apache.org/jira/browse/IGNITE-4268
>> https://issues.apache.org/jira/browse/IGNITE-4269
>> 
>> On failing tests:
>> https://issues.apache.org/jira/browse/IGNITE-2294?
> focusedCommentId=15683377
>> 
>> - Alex
>> 
>> 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>> :
>>> Vlad,
>>> 
>>> Most likely today.
>>> 
>>> - Alex
>>> 
>>> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
 Igniters,
 
 I went through remaining tickets assigned to 1.8 and it seems that
>>> we
> are
 pretty close to release. As far as I understand the biggest
>>> remaining
 feature is DML [1]. I think we can create separate branch for 1.8
>>> as
> soon
 as it is merged. Alex, do you have any idea on when it might
>>> happen?
 
 Vladimir.
 
 [1] https://issues.apache.org/jira/browse/IGNITE-2294
 
 On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> wrote:
 
> Roman,
> 
> That versions will be created after 1.8 gets released. Recently
 there
> was
> a discussion on the dev list [1] regarding the difficulties
>>> related
 to
> documentation maintenance when several documentation versions
> co-exist at
> the same time.
> 
> It was decided that rather then create a new version for the
> documentation
> once a new feature added to Ignite it’s better to create a hidden
 page
> under the current documentation version and make it visible once
>>> the
> next
> version is created after the release.
> 
> The bottom line is that, please create a hidden page with a suffix
> “page_name-1.8” and once 1.8 gets released Prachi will create
> readme.io <
> http://readme.io/> 1.8 and make your doc visible.
> 
> [1] http://apache-ignite-developers.2346864.n4.nabble.
> com/Maintaining-documentation-consistency-on-readme-io-
>>> td10868.html
 <
> http

Re: Apache Ignite 1.8 Release

[Denis Magda]

In addition to DML, ODBC+DML support and .NET features that have been already 
listed by Pavel, we will release the first version of Redis protocol 
implementation contributed by Roman
http://apacheignite.gridgain.org/v1.7/docs/redis 


—
Denis

> On Nov 25, 2016, at 5:08 AM, Vladimir Ozerov  wrote:
> 
> Folks,
> 
> I need to create RELEASE NOTES. Please advise which notable tickets you
> completed as a part of 1.8 release.
> 
> Vladimir.
> 
> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov  wrote:
> 
>> Hi
>> 
>> Could someone explain why Cassandra module splitted into three parts in
>> optional directory for binary fabric build? At the moment I see following
>> unclear points
>> 1. ignite-cassandra directory contains README.txt only
>> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
>> that case why do not make one module?
>> 
>> 
>> 
>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> 
>>> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
>>> 1.8 branch).
>>> 
>>> Meanwhile everything SQL/DML related seems to be in pull
>>> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
>>> 
>>> - Alex
>>> 
>>> 
>>> 
>>> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
 Hi
 
 I found two issues for 1.8:
 IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
>>> because
 node left grid 
 IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
 
 
 Could someone experienced take a look?
 
 On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>> voze...@gridgain.com>
 wrote:
 
> Folks,
> 
> DML is merged to ignite-1.8, but according to JIRA reports several
>>> problems
> with it were revealed. I propose to focus on DML finalization in
>>> ignite-1.8
> branch, and minimize other merges to it, targeting them for the next
> release (1.9, 2.0?).
> 
> Any objections?
> 
> Vladimir.
> 
> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
>>> wrote:
> 
>> Denis,
>> 
>> I've raised PRs and Vladimir has merged them into ignite-1.8. But
>> now
>>> we
>> have some
>> failing ODBC tests in the branch. I'm currently working on them.
>> There
> is a
>> ticket for
>> that which you can track [1]. I'll add all my findings there.
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-4288
>> 
>> Best Regards,
>> Igor
>> 
>> On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
>>> wrote:
>> 
>>> Alexander,
>>> 
>>> Awesome news, thanks for making this happen!
>>> 
>>> Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
>> Can I
>> start
>>> testing that PHP-PDO guidance [1] is correct?
>>> 
>>> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
>>> https://apacheignite.readme.io/docs/pdo-interoperability>
>>> 
>>> —
>>> Denis
>>> 
 On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
>>> alexander.a.pasche...@gmail.com> wrote:
 
 Folks,
 
 Yesterday it'd been agreed with Sergi that DML branch is now
>> good
>>> to
 be included into 1.8 branch that is to be created.
 
 Minor review fixes, should they be made, and test fixes will be
 incorporated into 1.8 as separate patches later.
 
 Also, it'd been agreed that, in order to deliver these new
>>> features
> on
 time, two subtasks will be fixed in later releases (shortly):
 
 https://issues.apache.org/jira/browse/IGNITE-4268
 https://issues.apache.org/jira/browse/IGNITE-4269
 
 On failing tests:
 https://issues.apache.org/jira/browse/IGNITE-2294?
>>> focusedCommentId=15683377
 
 - Alex
 
 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
 :
> Vlad,
> 
> Most likely today.
> 
> - Alex
> 
> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
>> voze...@gridgain.com
 :
>> Igniters,
>> 
>> I went through remaining tickets assigned to 1.8 and it seems
>>> that
> we
>>> are
>> pretty close to release. As far as I understand the biggest
> remaining
>> feature is DML [1]. I think we can create separate branch for
>>> 1.8
> as
>>> soon
>> as it is merged. Alex, do you have any idea on when it might
> happen?
>> 
>> Vladimir.
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>> 
>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda <
>> dma...@apache.org
 
>>> wrote:
>> 
>>> Roman,
>>> 
>>> 

Re: Apache Ignite 1.8 Release

[Roman Shtykh]

Vladimir,

IGNITE-3066 Set of Redis commands.

Roman



On Friday, November 25, 2016 11:57 PM, Igor Sapego  wrote:
IGNITE-4249: ODBC latency improved.
IGNITE-3587: Added Distributed Joins support for ODBC.
IGNITE-3390: Added DSN support for ODBC.


Best Regards,
Igor

On Fri, Nov 25, 2016 at 5:29 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Vladimir,
>
> IGNITE-3735: ODBC escape sequences support
> IGNITE-3448: DISTINCT Aggregates support added
> IGNITE-4145: Fixed race in distributed SQL queries
> IGNITE-2974: ODBC NIO support
>
> On Fri, Nov 25, 2016 at 4:40 PM, Andrey Gura  wrote:
>
> > Vladimir,
> >
> > IGNITE-2968 and IGNITE-2969 introduce deadlock detection for transactions
> > on near caches and for optimistic transactions.
> > I think it should be added to release notes.
> >
> > On Fri, Nov 25, 2016 at 3:08 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Folks,
> > >
> > > I need to create RELEASE NOTES. Please advise which notable tickets you
> > > completed as a part of 1.8 release.
> > >
> > > Vladimir.
> > >
> > > On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > Could someone explain why Cassandra module splitted into three parts
> in
> > > > optional directory for binary fabric build? At the moment I see
> > following
> > > > unclear points
> > > > 1. ignite-cassandra directory contains README.txt only
> > > > 2. Does ignite-cassandra-serializers depend on
> ignite-cassandra-store?
> > In
> > > > that case why do not make one module?
> > > >
> > > >
> > > >
> > > > On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > > > alexander.a.pasche...@gmail.com> wrote:
> > > >
> > > > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> > in
> > > > > 1.8 branch).
> > > > >
> > > > > Meanwhile everything SQL/DML related seems to be in pull
> > > > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > > > >
> > > > > - Alex
> > > > >
> > > > >
> > > > >
> > > > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > > > > Hi
> > > > > >
> > > > > > I found two issues for 1.8:
> > > > > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send
> > message
> > > > > because
> > > > > > node left grid  jira/browse/IGNITE-4304>
> > > > > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > > > > 
> > > > > >
> > > > > > Could someone experienced take a look?
> > > > > >
> > > > > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> > > > voze...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Folks,
> > > > > >>
> > > > > >> DML is merged to ignite-1.8, but according to JIRA reports
> several
> > > > > problems
> > > > > >> with it were revealed. I propose to focus on DML finalization in
> > > > > ignite-1.8
> > > > > >> branch, and minimize other merges to it, targeting them for the
> > next
> > > > > >> release (1.9, 2.0?).
> > > > > >>
> > > > > >> Any objections?
> > > > > >>
> > > > > >> Vladimir.
> > > > > >>
> > > > > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego <
> > isap...@gridgain.com>
> > > > > wrote:
> > > > > >>
> > > > > >> > Denis,
> > > > > >> >
> > > > > >> > I've raised PRs and Vladimir has merged them into ignite-1.8.
> > But
> > > > now
> > > > > we
> > > > > >> > have some
> > > > > >> > failing ODBC tests in the branch. I'm currently working on
> them.
> > > > There
> > > > > >> is a
> > > > > >> > ticket for
> > > > > >> > that which you can track [1]. I'll add all my findings there.
> > > > > >> >
> > > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > > > > >> >
> > > > > >> > Best Regards,
> > > > > >> > Igor
> > > > > >> >
> > > > > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda <
> dma...@apache.org
> > >
> > > > > wrote:
> > > > > >> >
> > > > > >> > > Alexander,
> > > > > >> > >
> > > > > >> > > Awesome news, thanks for making this happen!
> > > > > >> > >
> > > > > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related
> changes?
> > > > Can I
> > > > > >> > start
> > > > > >> > > testing that PHP-PDO guidance [1] is correct?
> > > > > >> > >
> > > > > >> > > [1] https://apacheignite.readme.
> io/docs/pdo-interoperability
> > <
> > > > > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > > > > >> > >
> > > > > >> > > —
> > > > > >> > > Denis
> > > > > >> > >
> > > > > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > > > >> > > alexander.a.pasche...@gmail.com> wrote:
> > > > > >> > > >
> > > > > >> > > > Folks,
> > > > > >> > > >
> > > > > >> > > > Yesterday it'd been agreed with Sergi that DML branch is
> now
> > > > good
> > > > > to
> > > > > >> > > > be included into 1.8 branch that is to be created.
> > > > > >> > > >
> > > > > >> > > > Minor review fixes, should they be made, and test fixes
> will
> > > be
> > > > > >> > > > incorporated into 1.8 as separate patches later.
> > > > > >> > > >
> > > > > 

Re: Apache Ignite 1.8 Release

[Igor Sapego]

IGNITE-4249: ODBC latency improved.
IGNITE-3587: Added Distributed Joins support for ODBC.
IGNITE-3390: Added DSN support for ODBC.


Best Regards,
Igor

On Fri, Nov 25, 2016 at 5:29 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Vladimir,
>
> IGNITE-3735: ODBC escape sequences support
> IGNITE-3448: DISTINCT Aggregates support added
> IGNITE-4145: Fixed race in distributed SQL queries
> IGNITE-2974: ODBC NIO support
>
> On Fri, Nov 25, 2016 at 4:40 PM, Andrey Gura  wrote:
>
> > Vladimir,
> >
> > IGNITE-2968 and IGNITE-2969 introduce deadlock detection for transactions
> > on near caches and for optimistic transactions.
> > I think it should be added to release notes.
> >
> > On Fri, Nov 25, 2016 at 3:08 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Folks,
> > >
> > > I need to create RELEASE NOTES. Please advise which notable tickets you
> > > completed as a part of 1.8 release.
> > >
> > > Vladimir.
> > >
> > > On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > Could someone explain why Cassandra module splitted into three parts
> in
> > > > optional directory for binary fabric build? At the moment I see
> > following
> > > > unclear points
> > > > 1. ignite-cassandra directory contains README.txt only
> > > > 2. Does ignite-cassandra-serializers depend on
> ignite-cassandra-store?
> > In
> > > > that case why do not make one module?
> > > >
> > > >
> > > >
> > > > On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > > > alexander.a.pasche...@gmail.com> wrote:
> > > >
> > > > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> > in
> > > > > 1.8 branch).
> > > > >
> > > > > Meanwhile everything SQL/DML related seems to be in pull
> > > > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > > > >
> > > > > - Alex
> > > > >
> > > > >
> > > > >
> > > > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > > > > Hi
> > > > > >
> > > > > > I found two issues for 1.8:
> > > > > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send
> > message
> > > > > because
> > > > > > node left grid  jira/browse/IGNITE-4304>
> > > > > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > > > > 
> > > > > >
> > > > > > Could someone experienced take a look?
> > > > > >
> > > > > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> > > > voze...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Folks,
> > > > > >>
> > > > > >> DML is merged to ignite-1.8, but according to JIRA reports
> several
> > > > > problems
> > > > > >> with it were revealed. I propose to focus on DML finalization in
> > > > > ignite-1.8
> > > > > >> branch, and minimize other merges to it, targeting them for the
> > next
> > > > > >> release (1.9, 2.0?).
> > > > > >>
> > > > > >> Any objections?
> > > > > >>
> > > > > >> Vladimir.
> > > > > >>
> > > > > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego <
> > isap...@gridgain.com>
> > > > > wrote:
> > > > > >>
> > > > > >> > Denis,
> > > > > >> >
> > > > > >> > I've raised PRs and Vladimir has merged them into ignite-1.8.
> > But
> > > > now
> > > > > we
> > > > > >> > have some
> > > > > >> > failing ODBC tests in the branch. I'm currently working on
> them.
> > > > There
> > > > > >> is a
> > > > > >> > ticket for
> > > > > >> > that which you can track [1]. I'll add all my findings there.
> > > > > >> >
> > > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > > > > >> >
> > > > > >> > Best Regards,
> > > > > >> > Igor
> > > > > >> >
> > > > > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda <
> dma...@apache.org
> > >
> > > > > wrote:
> > > > > >> >
> > > > > >> > > Alexander,
> > > > > >> > >
> > > > > >> > > Awesome news, thanks for making this happen!
> > > > > >> > >
> > > > > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related
> changes?
> > > > Can I
> > > > > >> > start
> > > > > >> > > testing that PHP-PDO guidance [1] is correct?
> > > > > >> > >
> > > > > >> > > [1] https://apacheignite.readme.
> io/docs/pdo-interoperability
> > <
> > > > > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > > > > >> > >
> > > > > >> > > —
> > > > > >> > > Denis
> > > > > >> > >
> > > > > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > > > >> > > alexander.a.pasche...@gmail.com> wrote:
> > > > > >> > > >
> > > > > >> > > > Folks,
> > > > > >> > > >
> > > > > >> > > > Yesterday it'd been agreed with Sergi that DML branch is
> now
> > > > good
> > > > > to
> > > > > >> > > > be included into 1.8 branch that is to be created.
> > > > > >> > > >
> > > > > >> > > > Minor review fixes, should they be made, and test fixes
> will
> > > be
> > > > > >> > > > incorporated into 1.8 as separate patches later.
> > > > > >> > > >
> > > > > >> > > > Also, it'd been agreed that, in order to deliver these new
> > > > > features
> > > > > >> on
> > > > > >>

Re: Apache Ignite 1.8 Release

[Andrey Mashenkov]

Vladimir,

IGNITE-3735: ODBC escape sequences support
IGNITE-3448: DISTINCT Aggregates support added
IGNITE-4145: Fixed race in distributed SQL queries
IGNITE-2974: ODBC NIO support

On Fri, Nov 25, 2016 at 4:40 PM, Andrey Gura  wrote:

> Vladimir,
>
> IGNITE-2968 and IGNITE-2969 introduce deadlock detection for transactions
> on near caches and for optimistic transactions.
> I think it should be added to release notes.
>
> On Fri, Nov 25, 2016 at 3:08 PM, Vladimir Ozerov 
> wrote:
>
> > Folks,
> >
> > I need to create RELEASE NOTES. Please advise which notable tickets you
> > completed as a part of 1.8 release.
> >
> > Vladimir.
> >
> > On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> > wrote:
> >
> > > Hi
> > >
> > > Could someone explain why Cassandra module splitted into three parts in
> > > optional directory for binary fabric build? At the moment I see
> following
> > > unclear points
> > > 1. ignite-cassandra directory contains README.txt only
> > > 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store?
> In
> > > that case why do not make one module?
> > >
> > >
> > >
> > > On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > > alexander.a.pasche...@gmail.com> wrote:
> > >
> > > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> in
> > > > 1.8 branch).
> > > >
> > > > Meanwhile everything SQL/DML related seems to be in pull
> > > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > > >
> > > > - Alex
> > > >
> > > >
> > > >
> > > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > > > Hi
> > > > >
> > > > > I found two issues for 1.8:
> > > > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send
> message
> > > > because
> > > > > node left grid 
> > > > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > > > 
> > > > >
> > > > > Could someone experienced take a look?
> > > > >
> > > > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> > > voze...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > >> Folks,
> > > > >>
> > > > >> DML is merged to ignite-1.8, but according to JIRA reports several
> > > > problems
> > > > >> with it were revealed. I propose to focus on DML finalization in
> > > > ignite-1.8
> > > > >> branch, and minimize other merges to it, targeting them for the
> next
> > > > >> release (1.9, 2.0?).
> > > > >>
> > > > >> Any objections?
> > > > >>
> > > > >> Vladimir.
> > > > >>
> > > > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego <
> isap...@gridgain.com>
> > > > wrote:
> > > > >>
> > > > >> > Denis,
> > > > >> >
> > > > >> > I've raised PRs and Vladimir has merged them into ignite-1.8.
> But
> > > now
> > > > we
> > > > >> > have some
> > > > >> > failing ODBC tests in the branch. I'm currently working on them.
> > > There
> > > > >> is a
> > > > >> > ticket for
> > > > >> > that which you can track [1]. I'll add all my findings there.
> > > > >> >
> > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > > > >> >
> > > > >> > Best Regards,
> > > > >> > Igor
> > > > >> >
> > > > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  >
> > > > wrote:
> > > > >> >
> > > > >> > > Alexander,
> > > > >> > >
> > > > >> > > Awesome news, thanks for making this happen!
> > > > >> > >
> > > > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> > > Can I
> > > > >> > start
> > > > >> > > testing that PHP-PDO guidance [1] is correct?
> > > > >> > >
> > > > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability
> <
> > > > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > > > >> > >
> > > > >> > > —
> > > > >> > > Denis
> > > > >> > >
> > > > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > > >> > > alexander.a.pasche...@gmail.com> wrote:
> > > > >> > > >
> > > > >> > > > Folks,
> > > > >> > > >
> > > > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
> > > good
> > > > to
> > > > >> > > > be included into 1.8 branch that is to be created.
> > > > >> > > >
> > > > >> > > > Minor review fixes, should they be made, and test fixes will
> > be
> > > > >> > > > incorporated into 1.8 as separate patches later.
> > > > >> > > >
> > > > >> > > > Also, it'd been agreed that, in order to deliver these new
> > > > features
> > > > >> on
> > > > >> > > > time, two subtasks will be fixed in later releases
> (shortly):
> > > > >> > > >
> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > > > >> > > >
> > > > >> > > > On failing tests:
> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > > > >> > > focusedCommentId=15683377
> > > > >> > > >
> > > > >> > > > - Alex
> > > > >> > > >
> > > > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > > >> > > > :
> > > > >> > > >> Vlad,
> > > > >> > > >>
> > > > 

Re: Apache Ignite 1.8 Release

[Andrey Gura]

Vladimir,

IGNITE-2968 and IGNITE-2969 introduce deadlock detection for transactions
on near caches and for optimistic transactions.
I think it should be added to release notes.

On Fri, Nov 25, 2016 at 3:08 PM, Vladimir Ozerov 
wrote:

> Folks,
>
> I need to create RELEASE NOTES. Please advise which notable tickets you
> completed as a part of 1.8 release.
>
> Vladimir.
>
> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> wrote:
>
> > Hi
> >
> > Could someone explain why Cassandra module splitted into three parts in
> > optional directory for binary fabric build? At the moment I see following
> > unclear points
> > 1. ignite-cassandra directory contains README.txt only
> > 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
> > that case why do not make one module?
> >
> >
> >
> > On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> >
> > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> > > 1.8 branch).
> > >
> > > Meanwhile everything SQL/DML related seems to be in pull
> > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > >
> > > - Alex
> > >
> > >
> > >
> > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > > Hi
> > > >
> > > > I found two issues for 1.8:
> > > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > > because
> > > > node left grid 
> > > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > > 
> > > >
> > > > Could someone experienced take a look?
> > > >
> > > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> > voze...@gridgain.com>
> > > > wrote:
> > > >
> > > >> Folks,
> > > >>
> > > >> DML is merged to ignite-1.8, but according to JIRA reports several
> > > problems
> > > >> with it were revealed. I propose to focus on DML finalization in
> > > ignite-1.8
> > > >> branch, and minimize other merges to it, targeting them for the next
> > > >> release (1.9, 2.0?).
> > > >>
> > > >> Any objections?
> > > >>
> > > >> Vladimir.
> > > >>
> > > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> > > wrote:
> > > >>
> > > >> > Denis,
> > > >> >
> > > >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But
> > now
> > > we
> > > >> > have some
> > > >> > failing ODBC tests in the branch. I'm currently working on them.
> > There
> > > >> is a
> > > >> > ticket for
> > > >> > that which you can track [1]. I'll add all my findings there.
> > > >> >
> > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > > >> >
> > > >> > Best Regards,
> > > >> > Igor
> > > >> >
> > > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > > wrote:
> > > >> >
> > > >> > > Alexander,
> > > >> > >
> > > >> > > Awesome news, thanks for making this happen!
> > > >> > >
> > > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> > Can I
> > > >> > start
> > > >> > > testing that PHP-PDO guidance [1] is correct?
> > > >> > >
> > > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > > >> > >
> > > >> > > —
> > > >> > > Denis
> > > >> > >
> > > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > >> > > alexander.a.pasche...@gmail.com> wrote:
> > > >> > > >
> > > >> > > > Folks,
> > > >> > > >
> > > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
> > good
> > > to
> > > >> > > > be included into 1.8 branch that is to be created.
> > > >> > > >
> > > >> > > > Minor review fixes, should they be made, and test fixes will
> be
> > > >> > > > incorporated into 1.8 as separate patches later.
> > > >> > > >
> > > >> > > > Also, it'd been agreed that, in order to deliver these new
> > > features
> > > >> on
> > > >> > > > time, two subtasks will be fixed in later releases (shortly):
> > > >> > > >
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > > >> > > >
> > > >> > > > On failing tests:
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > > >> > > focusedCommentId=15683377
> > > >> > > >
> > > >> > > > - Alex
> > > >> > > >
> > > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > >> > > > :
> > > >> > > >> Vlad,
> > > >> > > >>
> > > >> > > >> Most likely today.
> > > >> > > >>
> > > >> > > >> - Alex
> > > >> > > >>
> > > >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
> > voze...@gridgain.com
> > > >:
> > > >> > > >>> Igniters,
> > > >> > > >>>
> > > >> > > >>> I went through remaining tickets assigned to 1.8 and it
> seems
> > > that
> > > >> we
> > > >> > > are
> > > >> > > >>> pretty close to release. As far as I understand the biggest
> > > >> remaining
> > > >> > > >>> feature is DML [1]. I think we can create separate branch
> for
> > > 1.8
> > > >> as
> > > >> > > soon
> 

Re: Apache Ignite 1.8 Release

[Pavel Tupitsyn]

Noteworthy .NET features:

   - Entity Framework 2nd Level Cache
   - ASP.NET Session State Store Provider
   - Custom logger support
   - NLog logging
   - Log4net logging


On Fri, Nov 25, 2016 at 3:08 PM, Vladimir Ozerov 
wrote:

> Folks,
>
> I need to create RELEASE NOTES. Please advise which notable tickets you
> completed as a part of 1.8 release.
>
> Vladimir.
>
> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> wrote:
>
> > Hi
> >
> > Could someone explain why Cassandra module splitted into three parts in
> > optional directory for binary fabric build? At the moment I see following
> > unclear points
> > 1. ignite-cassandra directory contains README.txt only
> > 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
> > that case why do not make one module?
> >
> >
> >
> > On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> >
> > > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> > > 1.8 branch).
> > >
> > > Meanwhile everything SQL/DML related seems to be in pull
> > > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> > >
> > > - Alex
> > >
> > >
> > >
> > > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > > Hi
> > > >
> > > > I found two issues for 1.8:
> > > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > > because
> > > > node left grid 
> > > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > > 
> > > >
> > > > Could someone experienced take a look?
> > > >
> > > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> > voze...@gridgain.com>
> > > > wrote:
> > > >
> > > >> Folks,
> > > >>
> > > >> DML is merged to ignite-1.8, but according to JIRA reports several
> > > problems
> > > >> with it were revealed. I propose to focus on DML finalization in
> > > ignite-1.8
> > > >> branch, and minimize other merges to it, targeting them for the next
> > > >> release (1.9, 2.0?).
> > > >>
> > > >> Any objections?
> > > >>
> > > >> Vladimir.
> > > >>
> > > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> > > wrote:
> > > >>
> > > >> > Denis,
> > > >> >
> > > >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But
> > now
> > > we
> > > >> > have some
> > > >> > failing ODBC tests in the branch. I'm currently working on them.
> > There
> > > >> is a
> > > >> > ticket for
> > > >> > that which you can track [1]. I'll add all my findings there.
> > > >> >
> > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > > >> >
> > > >> > Best Regards,
> > > >> > Igor
> > > >> >
> > > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > > wrote:
> > > >> >
> > > >> > > Alexander,
> > > >> > >
> > > >> > > Awesome news, thanks for making this happen!
> > > >> > >
> > > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> > Can I
> > > >> > start
> > > >> > > testing that PHP-PDO guidance [1] is correct?
> > > >> > >
> > > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > > >> > >
> > > >> > > —
> > > >> > > Denis
> > > >> > >
> > > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > >> > > alexander.a.pasche...@gmail.com> wrote:
> > > >> > > >
> > > >> > > > Folks,
> > > >> > > >
> > > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
> > good
> > > to
> > > >> > > > be included into 1.8 branch that is to be created.
> > > >> > > >
> > > >> > > > Minor review fixes, should they be made, and test fixes will
> be
> > > >> > > > incorporated into 1.8 as separate patches later.
> > > >> > > >
> > > >> > > > Also, it'd been agreed that, in order to deliver these new
> > > features
> > > >> on
> > > >> > > > time, two subtasks will be fixed in later releases (shortly):
> > > >> > > >
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > > >> > > >
> > > >> > > > On failing tests:
> > > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > > >> > > focusedCommentId=15683377
> > > >> > > >
> > > >> > > > - Alex
> > > >> > > >
> > > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > >> > > > :
> > > >> > > >> Vlad,
> > > >> > > >>
> > > >> > > >> Most likely today.
> > > >> > > >>
> > > >> > > >> - Alex
> > > >> > > >>
> > > >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
> > voze...@gridgain.com
> > > >:
> > > >> > > >>> Igniters,
> > > >> > > >>>
> > > >> > > >>> I went through remaining tickets assigned to 1.8 and it
> seems
> > > that
> > > >> we
> > > >> > > are
> > > >> > > >>> pretty close to release. As far as I understand the biggest
> > > >> remaining
> > > >> > > >>> feature is DML [1]. I think we can create separate branch
> for
> > > 1.8
> > > >> as
> > > >> > > soon
> > > 

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Alexey

The optional module means that we can copy it in libs and it will provide
its functionality. What new functionality provides empty directory?

On Fri, Nov 25, 2016 at 3:21 PM, Alexey Kuznetsov 
wrote:

> Sergey,
>
> As far as I know "ignite-cassandra" is a root folder.
>
> "ignite-cassandra-store" - contains module with Cassandra store.
> "ignite-cassandra-serializers" - module that contains optional serializers
>  for Cassandra store (for example with Kryo).
> it is implemented as separate (optional) module because of Kryo based
> serializers may bring not needed dependency.
>
> Igor, could you confirm this?
>
> On Fri, Nov 25, 2016 at 6:58 PM, Sergey Kozlov 
> wrote:
>
>> Hi
>>
>> Could someone explain why Cassandra module splitted into three parts in
>> optional directory for binary fabric build? At the moment I see following
>> unclear points
>> 1. ignite-cassandra directory contains README.txt only
>> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
>> that case why do not make one module?
>>
>>
>>
>> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>
>> > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
>> > 1.8 branch).
>> >
>> > Meanwhile everything SQL/DML related seems to be in pull
>> > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
>> >
>> > - Alex
>> >
>> >
>> >
>> > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
>> > > Hi
>> > >
>> > > I found two issues for 1.8:
>> > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
>> > because
>> > > node left grid 
>> > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
>> > > 
>> > >
>> > > Could someone experienced take a look?
>> > >
>> > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>> voze...@gridgain.com>
>> > > wrote:
>> > >
>> > >> Folks,
>> > >>
>> > >> DML is merged to ignite-1.8, but according to JIRA reports several
>> > problems
>> > >> with it were revealed. I propose to focus on DML finalization in
>> > ignite-1.8
>> > >> branch, and minimize other merges to it, targeting them for the next
>> > >> release (1.9, 2.0?).
>> > >>
>> > >> Any objections?
>> > >>
>> > >> Vladimir.
>> > >>
>> > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
>> > wrote:
>> > >>
>> > >> > Denis,
>> > >> >
>> > >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But
>> now
>> > we
>> > >> > have some
>> > >> > failing ODBC tests in the branch. I'm currently working on them.
>> There
>> > >> is a
>> > >> > ticket for
>> > >> > that which you can track [1]. I'll add all my findings there.
>> > >> >
>> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
>> > >> >
>> > >> > Best Regards,
>> > >> > Igor
>> > >> >
>> > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
>> > wrote:
>> > >> >
>> > >> > > Alexander,
>> > >> > >
>> > >> > > Awesome news, thanks for making this happen!
>> > >> > >
>> > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
>> Can I
>> > >> > start
>> > >> > > testing that PHP-PDO guidance [1] is correct?
>> > >> > >
>> > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
>> > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
>> > >> > >
>> > >> > > —
>> > >> > > Denis
>> > >> > >
>> > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
>> > >> > > alexander.a.pasche...@gmail.com> wrote:
>> > >> > > >
>> > >> > > > Folks,
>> > >> > > >
>> > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
>> good
>> > to
>> > >> > > > be included into 1.8 branch that is to be created.
>> > >> > > >
>> > >> > > > Minor review fixes, should they be made, and test fixes will be
>> > >> > > > incorporated into 1.8 as separate patches later.
>> > >> > > >
>> > >> > > > Also, it'd been agreed that, in order to deliver these new
>> > features
>> > >> on
>> > >> > > > time, two subtasks will be fixed in later releases (shortly):
>> > >> > > >
>> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
>> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
>> > >> > > >
>> > >> > > > On failing tests:
>> > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
>> > >> > > focusedCommentId=15683377
>> > >> > > >
>> > >> > > > - Alex
>> > >> > > >
>> > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>> > >> > > > :
>> > >> > > >> Vlad,
>> > >> > > >>
>> > >> > > >> Most likely today.
>> > >> > > >>
>> > >> > > >> - Alex
>> > >> > > >>
>> > >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
>> voze...@gridgain.com
>> > >:
>> > >> > > >>> Igniters,
>> > >> > > >>>
>> > >> > > >>> I went through remaining tickets assigned to 1.8 and it seems
>> > that
>> > >> we
>> > >> > > are
>> > >> > > >>> pretty close to release. As far as I understand the biggest
>> > >> remaining
>> > >> > > >

Re: Apache Ignite 1.8 Release

[Alexey Kuznetsov]

Sergey,

As far as I know "ignite-cassandra" is a root folder.

"ignite-cassandra-store" - contains module with Cassandra store.
"ignite-cassandra-serializers" - module that contains optional serializers
 for Cassandra store (for example with Kryo).
it is implemented as separate (optional) module because of Kryo based
serializers may bring not needed dependency.

Igor, could you confirm this?

On Fri, Nov 25, 2016 at 6:58 PM, Sergey Kozlov  wrote:

> Hi
>
> Could someone explain why Cassandra module splitted into three parts in
> optional directory for binary fabric build? At the moment I see following
> unclear points
> 1. ignite-cassandra directory contains README.txt only
> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
> that case why do not make one module?
>
>
>
> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> > 1.8 branch).
> >
> > Meanwhile everything SQL/DML related seems to be in pull
> > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> >
> > - Alex
> >
> >
> >
> > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > Hi
> > >
> > > I found two issues for 1.8:
> > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > because
> > > node left grid 
> > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > 
> > >
> > > Could someone experienced take a look?
> > >
> > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > wrote:
> > >
> > >> Folks,
> > >>
> > >> DML is merged to ignite-1.8, but according to JIRA reports several
> > problems
> > >> with it were revealed. I propose to focus on DML finalization in
> > ignite-1.8
> > >> branch, and minimize other merges to it, targeting them for the next
> > >> release (1.9, 2.0?).
> > >>
> > >> Any objections?
> > >>
> > >> Vladimir.
> > >>
> > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> > wrote:
> > >>
> > >> > Denis,
> > >> >
> > >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But
> now
> > we
> > >> > have some
> > >> > failing ODBC tests in the branch. I'm currently working on them.
> There
> > >> is a
> > >> > ticket for
> > >> > that which you can track [1]. I'll add all my findings there.
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > >> >
> > >> > Best Regards,
> > >> > Igor
> > >> >
> > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > wrote:
> > >> >
> > >> > > Alexander,
> > >> > >
> > >> > > Awesome news, thanks for making this happen!
> > >> > >
> > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> Can I
> > >> > start
> > >> > > testing that PHP-PDO guidance [1] is correct?
> > >> > >
> > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > >> > >
> > >> > > —
> > >> > > Denis
> > >> > >
> > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > >> > > alexander.a.pasche...@gmail.com> wrote:
> > >> > > >
> > >> > > > Folks,
> > >> > > >
> > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
> good
> > to
> > >> > > > be included into 1.8 branch that is to be created.
> > >> > > >
> > >> > > > Minor review fixes, should they be made, and test fixes will be
> > >> > > > incorporated into 1.8 as separate patches later.
> > >> > > >
> > >> > > > Also, it'd been agreed that, in order to deliver these new
> > features
> > >> on
> > >> > > > time, two subtasks will be fixed in later releases (shortly):
> > >> > > >
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > >> > > >
> > >> > > > On failing tests:
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > >> > > focusedCommentId=15683377
> > >> > > >
> > >> > > > - Alex
> > >> > > >
> > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > >> > > > :
> > >> > > >> Vlad,
> > >> > > >>
> > >> > > >> Most likely today.
> > >> > > >>
> > >> > > >> - Alex
> > >> > > >>
> > >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
> voze...@gridgain.com
> > >:
> > >> > > >>> Igniters,
> > >> > > >>>
> > >> > > >>> I went through remaining tickets assigned to 1.8 and it seems
> > that
> > >> we
> > >> > > are
> > >> > > >>> pretty close to release. As far as I understand the biggest
> > >> remaining
> > >> > > >>> feature is DML [1]. I think we can create separate branch for
> > 1.8
> > >> as
> > >> > > soon
> > >> > > >>> as it is merged. Alex, do you have any idea on when it might
> > >> happen?
> > >> > > >>>
> > >> > > >>> Vladimir.
> > >> > > >>>
> > >> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >> > > >>>
> > >> > > >>> On Thu, Nov 17, 2016 at 4:06 

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Folks,

I need to create RELEASE NOTES. Please advise which notable tickets you
completed as a part of 1.8 release.

Vladimir.

On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov  wrote:

> Hi
>
> Could someone explain why Cassandra module splitted into three parts in
> optional directory for binary fabric build? At the moment I see following
> unclear points
> 1. ignite-cassandra directory contains README.txt only
> 2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
> that case why do not make one module?
>
>
>
> On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> > 1.8 branch).
> >
> > Meanwhile everything SQL/DML related seems to be in pull
> > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> >
> > - Alex
> >
> >
> >
> > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > > Hi
> > >
> > > I found two issues for 1.8:
> > > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > because
> > > node left grid 
> > > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > > 
> > >
> > > Could someone experienced take a look?
> > >
> > > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > wrote:
> > >
> > >> Folks,
> > >>
> > >> DML is merged to ignite-1.8, but according to JIRA reports several
> > problems
> > >> with it were revealed. I propose to focus on DML finalization in
> > ignite-1.8
> > >> branch, and minimize other merges to it, targeting them for the next
> > >> release (1.9, 2.0?).
> > >>
> > >> Any objections?
> > >>
> > >> Vladimir.
> > >>
> > >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> > wrote:
> > >>
> > >> > Denis,
> > >> >
> > >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But
> now
> > we
> > >> > have some
> > >> > failing ODBC tests in the branch. I'm currently working on them.
> There
> > >> is a
> > >> > ticket for
> > >> > that which you can track [1]. I'll add all my findings there.
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> > >> >
> > >> > Best Regards,
> > >> > Igor
> > >> >
> > >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > wrote:
> > >> >
> > >> > > Alexander,
> > >> > >
> > >> > > Awesome news, thanks for making this happen!
> > >> > >
> > >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes?
> Can I
> > >> > start
> > >> > > testing that PHP-PDO guidance [1] is correct?
> > >> > >
> > >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > >> > >
> > >> > > —
> > >> > > Denis
> > >> > >
> > >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > >> > > alexander.a.pasche...@gmail.com> wrote:
> > >> > > >
> > >> > > > Folks,
> > >> > > >
> > >> > > > Yesterday it'd been agreed with Sergi that DML branch is now
> good
> > to
> > >> > > > be included into 1.8 branch that is to be created.
> > >> > > >
> > >> > > > Minor review fixes, should they be made, and test fixes will be
> > >> > > > incorporated into 1.8 as separate patches later.
> > >> > > >
> > >> > > > Also, it'd been agreed that, in order to deliver these new
> > features
> > >> on
> > >> > > > time, two subtasks will be fixed in later releases (shortly):
> > >> > > >
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > >> > > >
> > >> > > > On failing tests:
> > >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > >> > > focusedCommentId=15683377
> > >> > > >
> > >> > > > - Alex
> > >> > > >
> > >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > >> > > > :
> > >> > > >> Vlad,
> > >> > > >>
> > >> > > >> Most likely today.
> > >> > > >>
> > >> > > >> - Alex
> > >> > > >>
> > >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov <
> voze...@gridgain.com
> > >:
> > >> > > >>> Igniters,
> > >> > > >>>
> > >> > > >>> I went through remaining tickets assigned to 1.8 and it seems
> > that
> > >> we
> > >> > > are
> > >> > > >>> pretty close to release. As far as I understand the biggest
> > >> remaining
> > >> > > >>> feature is DML [1]. I think we can create separate branch for
> > 1.8
> > >> as
> > >> > > soon
> > >> > > >>> as it is merged. Alex, do you have any idea on when it might
> > >> happen?
> > >> > > >>>
> > >> > > >>> Vladimir.
> > >> > > >>>
> > >> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >> > > >>>
> > >> > > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda <
> dma...@apache.org
> > >
> > >> > > wrote:
> > >> > > >>>
> > >> > >  Roman,
> > >> > > 
> > >> > >  That versions will be created after 1.8 gets released.
> Recently
> > >> > there
> > >> > > was
> > >> > >  a discussion on the dev l

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

Could someone explain why Cassandra module splitted into three parts in
optional directory for binary fabric build? At the moment I see following
unclear points
1. ignite-cassandra directory contains README.txt only
2. Does ignite-cassandra-serializers depend on ignite-cassandra-store? In
that case why do not make one module?



On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:

> IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
> 1.8 branch).
>
> Meanwhile everything SQL/DML related seems to be in pull
> requests/reviewed/fixed/merged (no issues unapproached/not fixed).
>
> - Alex
>
>
>
> 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> > Hi
> >
> > I found two issues for 1.8:
> > IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> because
> > node left grid 
> > IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> > 
> >
> > Could someone experienced take a look?
> >
> > On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov 
> > wrote:
> >
> >> Folks,
> >>
> >> DML is merged to ignite-1.8, but according to JIRA reports several
> problems
> >> with it were revealed. I propose to focus on DML finalization in
> ignite-1.8
> >> branch, and minimize other merges to it, targeting them for the next
> >> release (1.9, 2.0?).
> >>
> >> Any objections?
> >>
> >> Vladimir.
> >>
> >> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego 
> wrote:
> >>
> >> > Denis,
> >> >
> >> > I've raised PRs and Vladimir has merged them into ignite-1.8. But now
> we
> >> > have some
> >> > failing ODBC tests in the branch. I'm currently working on them. There
> >> is a
> >> > ticket for
> >> > that which you can track [1]. I'll add all my findings there.
> >> >
> >> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> >> >
> >> > Best Regards,
> >> > Igor
> >> >
> >> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> wrote:
> >> >
> >> > > Alexander,
> >> > >
> >> > > Awesome news, thanks for making this happen!
> >> > >
> >> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
> >> > start
> >> > > testing that PHP-PDO guidance [1] is correct?
> >> > >
> >> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> >> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> >> > >
> >> > > —
> >> > > Denis
> >> > >
> >> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> >> > > alexander.a.pasche...@gmail.com> wrote:
> >> > > >
> >> > > > Folks,
> >> > > >
> >> > > > Yesterday it'd been agreed with Sergi that DML branch is now good
> to
> >> > > > be included into 1.8 branch that is to be created.
> >> > > >
> >> > > > Minor review fixes, should they be made, and test fixes will be
> >> > > > incorporated into 1.8 as separate patches later.
> >> > > >
> >> > > > Also, it'd been agreed that, in order to deliver these new
> features
> >> on
> >> > > > time, two subtasks will be fixed in later releases (shortly):
> >> > > >
> >> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> >> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> >> > > >
> >> > > > On failing tests:
> >> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> >> > > focusedCommentId=15683377
> >> > > >
> >> > > > - Alex
> >> > > >
> >> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> >> > > > :
> >> > > >> Vlad,
> >> > > >>
> >> > > >> Most likely today.
> >> > > >>
> >> > > >> - Alex
> >> > > >>
> >> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov  >:
> >> > > >>> Igniters,
> >> > > >>>
> >> > > >>> I went through remaining tickets assigned to 1.8 and it seems
> that
> >> we
> >> > > are
> >> > > >>> pretty close to release. As far as I understand the biggest
> >> remaining
> >> > > >>> feature is DML [1]. I think we can create separate branch for
> 1.8
> >> as
> >> > > soon
> >> > > >>> as it is merged. Alex, do you have any idea on when it might
> >> happen?
> >> > > >>>
> >> > > >>> Vladimir.
> >> > > >>>
> >> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> >> > > >>>
> >> > > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  >
> >> > > wrote:
> >> > > >>>
> >> > >  Roman,
> >> > > 
> >> > >  That versions will be created after 1.8 gets released. Recently
> >> > there
> >> > > was
> >> > >  a discussion on the dev list [1] regarding the difficulties
> >> related
> >> > to
> >> > >  documentation maintenance when several documentation versions
> >> > > co-exist at
> >> > >  the same time.
> >> > > 
> >> > >  It was decided that rather then create a new version for the
> >> > > documentation
> >> > >  once a new feature added to Ignite it’s better to create a
> hidden
> >> > page
> >> > >  under the current documentation version and make it visible
> once
> >> the
> >> > > next
> >> > >  version is created after the release.
> >> > > 
> >> > 

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged in
1.8 branch).

Meanwhile everything SQL/DML related seems to be in pull
requests/reviewed/fixed/merged (no issues unapproached/not fixed).

- Alex



2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> Hi
>
> I found two issues for 1.8:
> IGNITE-4304 ClusterTopologyCheckedException: Failed to send message because
> node left grid 
> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> 
>
> Could someone experienced take a look?
>
> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov 
> wrote:
>
>> Folks,
>>
>> DML is merged to ignite-1.8, but according to JIRA reports several problems
>> with it were revealed. I propose to focus on DML finalization in ignite-1.8
>> branch, and minimize other merges to it, targeting them for the next
>> release (1.9, 2.0?).
>>
>> Any objections?
>>
>> Vladimir.
>>
>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:
>>
>> > Denis,
>> >
>> > I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
>> > have some
>> > failing ODBC tests in the branch. I'm currently working on them. There
>> is a
>> > ticket for
>> > that which you can track [1]. I'll add all my findings there.
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
>> >
>> > Best Regards,
>> > Igor
>> >
>> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
>> >
>> > > Alexander,
>> > >
>> > > Awesome news, thanks for making this happen!
>> > >
>> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
>> > start
>> > > testing that PHP-PDO guidance [1] is correct?
>> > >
>> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
>> > > https://apacheignite.readme.io/docs/pdo-interoperability>
>> > >
>> > > —
>> > > Denis
>> > >
>> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
>> > > alexander.a.pasche...@gmail.com> wrote:
>> > > >
>> > > > Folks,
>> > > >
>> > > > Yesterday it'd been agreed with Sergi that DML branch is now good to
>> > > > be included into 1.8 branch that is to be created.
>> > > >
>> > > > Minor review fixes, should they be made, and test fixes will be
>> > > > incorporated into 1.8 as separate patches later.
>> > > >
>> > > > Also, it'd been agreed that, in order to deliver these new features
>> on
>> > > > time, two subtasks will be fixed in later releases (shortly):
>> > > >
>> > > > https://issues.apache.org/jira/browse/IGNITE-4268
>> > > > https://issues.apache.org/jira/browse/IGNITE-4269
>> > > >
>> > > > On failing tests:
>> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
>> > > focusedCommentId=15683377
>> > > >
>> > > > - Alex
>> > > >
>> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>> > > > :
>> > > >> Vlad,
>> > > >>
>> > > >> Most likely today.
>> > > >>
>> > > >> - Alex
>> > > >>
>> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> > > >>> Igniters,
>> > > >>>
>> > > >>> I went through remaining tickets assigned to 1.8 and it seems that
>> we
>> > > are
>> > > >>> pretty close to release. As far as I understand the biggest
>> remaining
>> > > >>> feature is DML [1]. I think we can create separate branch for 1.8
>> as
>> > > soon
>> > > >>> as it is merged. Alex, do you have any idea on when it might
>> happen?
>> > > >>>
>> > > >>> Vladimir.
>> > > >>>
>> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>> > > >>>
>> > > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
>> > > wrote:
>> > > >>>
>> > >  Roman,
>> > > 
>> > >  That versions will be created after 1.8 gets released. Recently
>> > there
>> > > was
>> > >  a discussion on the dev list [1] regarding the difficulties
>> related
>> > to
>> > >  documentation maintenance when several documentation versions
>> > > co-exist at
>> > >  the same time.
>> > > 
>> > >  It was decided that rather then create a new version for the
>> > > documentation
>> > >  once a new feature added to Ignite it’s better to create a hidden
>> > page
>> > >  under the current documentation version and make it visible once
>> the
>> > > next
>> > >  version is created after the release.
>> > > 
>> > >  The bottom line is that, please create a hidden page with a suffix
>> > >  “page_name-1.8” and once 1.8 gets released Prachi will create
>> > > readme.io <
>> > >  http://readme.io/> 1.8 and make your doc visible.
>> > > 
>> > >  [1] http://apache-ignite-developers.2346864.n4.nabble.
>> > >  com/Maintaining-documentation-consistency-on-readme-io-
>> td10868.html
>> > <
>> > >  http://apache-ignite-developers.2346864.n4.nabble.
>> > >  com/Maintaining-documentation-consistency-on-readme-io-
>> > td10868.html>
>> > > 
>> > >  —
>> > >  Denis
>> > > 
>> > > > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>> > > > > >
>> > >  wrote:
>> > > >
>> > > > Denis,
>> > > > 

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

I found two issues for 1.8:
IGNITE-4304 ClusterTopologyCheckedException: Failed to send message because
node left grid 
IGNITE-4303 CacheClientBinaryQueryExample returns wrong result


Could someone experienced take a look?

On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov 
wrote:

> Folks,
>
> DML is merged to ignite-1.8, but according to JIRA reports several problems
> with it were revealed. I propose to focus on DML finalization in ignite-1.8
> branch, and minimize other merges to it, targeting them for the next
> release (1.9, 2.0?).
>
> Any objections?
>
> Vladimir.
>
> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:
>
> > Denis,
> >
> > I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
> > have some
> > failing ODBC tests in the branch. I'm currently working on them. There
> is a
> > ticket for
> > that which you can track [1]. I'll add all my findings there.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> >
> > Best Regards,
> > Igor
> >
> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
> >
> > > Alexander,
> > >
> > > Awesome news, thanks for making this happen!
> > >
> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
> > start
> > > testing that PHP-PDO guidance [1] is correct?
> > >
> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > >
> > > —
> > > Denis
> > >
> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > alexander.a.pasche...@gmail.com> wrote:
> > > >
> > > > Folks,
> > > >
> > > > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > > > be included into 1.8 branch that is to be created.
> > > >
> > > > Minor review fixes, should they be made, and test fixes will be
> > > > incorporated into 1.8 as separate patches later.
> > > >
> > > > Also, it'd been agreed that, in order to deliver these new features
> on
> > > > time, two subtasks will be fixed in later releases (shortly):
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > > >
> > > > On failing tests:
> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > > focusedCommentId=15683377
> > > >
> > > > - Alex
> > > >
> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > > :
> > > >> Vlad,
> > > >>
> > > >> Most likely today.
> > > >>
> > > >> - Alex
> > > >>
> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > > >>> Igniters,
> > > >>>
> > > >>> I went through remaining tickets assigned to 1.8 and it seems that
> we
> > > are
> > > >>> pretty close to release. As far as I understand the biggest
> remaining
> > > >>> feature is DML [1]. I think we can create separate branch for 1.8
> as
> > > soon
> > > >>> as it is merged. Alex, do you have any idea on when it might
> happen?
> > > >>>
> > > >>> Vladimir.
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > > >>>
> > > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> > > wrote:
> > > >>>
> > >  Roman,
> > > 
> > >  That versions will be created after 1.8 gets released. Recently
> > there
> > > was
> > >  a discussion on the dev list [1] regarding the difficulties
> related
> > to
> > >  documentation maintenance when several documentation versions
> > > co-exist at
> > >  the same time.
> > > 
> > >  It was decided that rather then create a new version for the
> > > documentation
> > >  once a new feature added to Ignite it’s better to create a hidden
> > page
> > >  under the current documentation version and make it visible once
> the
> > > next
> > >  version is created after the release.
> > > 
> > >  The bottom line is that, please create a hidden page with a suffix
> > >  “page_name-1.8” and once 1.8 gets released Prachi will create
> > > readme.io <
> > >  http://readme.io/> 1.8 and make your doc visible.
> > > 
> > >  [1] http://apache-ignite-developers.2346864.n4.nabble.
> > >  com/Maintaining-documentation-consistency-on-readme-io-
> td10868.html
> > <
> > >  http://apache-ignite-developers.2346864.n4.nabble.
> > >  com/Maintaining-documentation-consistency-on-readme-io-
> > td10868.html>
> > > 
> > >  —
> > >  Denis
> > > 
> > > > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
> >  > > >
> > >  wrote:
> > > >
> > > > Denis,
> > > > Any plans to add 1.8.0 in readme.io for new features?
> > > > -Roman
> > > >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> > >  dma...@apache.org> wrote:
> > > >
> > > >
> > > > 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.
> > > >>

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Folks,

DML is merged to ignite-1.8, but according to JIRA reports several problems
with it were revealed. I propose to focus on DML finalization in ignite-1.8
branch, and minimize other merges to it, targeting them for the next
release (1.9, 2.0?).

Any objections?

Vladimir.

On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:

> Denis,
>
> I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
> have some
> failing ODBC tests in the branch. I'm currently working on them. There is a
> ticket for
> that which you can track [1]. I'll add all my findings there.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4288
>
> Best Regards,
> Igor
>
> On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
>
> > Alexander,
> >
> > Awesome news, thanks for making this happen!
> >
> > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
> start
> > testing that PHP-PDO guidance [1] is correct?
> >
> > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > https://apacheignite.readme.io/docs/pdo-interoperability>
> >
> > —
> > Denis
> >
> > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> > >
> > > Folks,
> > >
> > > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > > be included into 1.8 branch that is to be created.
> > >
> > > Minor review fixes, should they be made, and test fixes will be
> > > incorporated into 1.8 as separate patches later.
> > >
> > > Also, it'd been agreed that, in order to deliver these new features on
> > > time, two subtasks will be fixed in later releases (shortly):
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > https://issues.apache.org/jira/browse/IGNITE-4269
> > >
> > > On failing tests:
> > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > focusedCommentId=15683377
> > >
> > > - Alex
> > >
> > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > :
> > >> Vlad,
> > >>
> > >> Most likely today.
> > >>
> > >> - Alex
> > >>
> > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > >>> Igniters,
> > >>>
> > >>> I went through remaining tickets assigned to 1.8 and it seems that we
> > are
> > >>> pretty close to release. As far as I understand the biggest remaining
> > >>> feature is DML [1]. I think we can create separate branch for 1.8 as
> > soon
> > >>> as it is merged. Alex, do you have any idea on when it might happen?
> > >>>
> > >>> Vladimir.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >>>
> > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> > wrote:
> > >>>
> >  Roman,
> > 
> >  That versions will be created after 1.8 gets released. Recently
> there
> > was
> >  a discussion on the dev list [1] regarding the difficulties related
> to
> >  documentation maintenance when several documentation versions
> > co-exist at
> >  the same time.
> > 
> >  It was decided that rather then create a new version for the
> > documentation
> >  once a new feature added to Ignite it’s better to create a hidden
> page
> >  under the current documentation version and make it visible once the
> > next
> >  version is created after the release.
> > 
> >  The bottom line is that, please create a hidden page with a suffix
> >  “page_name-1.8” and once 1.8 gets released Prachi will create
> > readme.io <
> >  http://readme.io/> 1.8 and make your doc visible.
> > 
> >  [1] http://apache-ignite-developers.2346864.n4.nabble.
> >  com/Maintaining-documentation-consistency-on-readme-io-td10868.html
> <
> >  http://apache-ignite-developers.2346864.n4.nabble.
> >  com/Maintaining-documentation-consistency-on-readme-io-
> td10868.html>
> > 
> >  —
> >  Denis
> > 
> > > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>  > >
> >  wrote:
> > >
> > > Denis,
> > > Any plans to add 1.8.0 in readme.io for new features?
> > > -Roman
> > >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> >  dma...@apache.org> wrote:
> > >
> > >
> > > 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 
> > 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, P

Re: Apache Ignite 1.8 Release

[Igor Sapego]

Denis,

I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
have some
failing ODBC tests in the branch. I'm currently working on them. There is a
ticket for
that which you can track [1]. I'll add all my findings there.

[1] https://issues.apache.org/jira/browse/IGNITE-4288

Best Regards,
Igor

On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:

> Alexander,
>
> Awesome news, thanks for making this happen!
>
> Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I start
> testing that PHP-PDO guidance [1] is correct?
>
> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> https://apacheignite.readme.io/docs/pdo-interoperability>
>
> —
> Denis
>
> > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > Folks,
> >
> > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > be included into 1.8 branch that is to be created.
> >
> > Minor review fixes, should they be made, and test fixes will be
> > incorporated into 1.8 as separate patches later.
> >
> > Also, it'd been agreed that, in order to deliver these new features on
> > time, two subtasks will be fixed in later releases (shortly):
> >
> > https://issues.apache.org/jira/browse/IGNITE-4268
> > https://issues.apache.org/jira/browse/IGNITE-4269
> >
> > On failing tests:
> > https://issues.apache.org/jira/browse/IGNITE-2294?
> focusedCommentId=15683377
> >
> > - Alex
> >
> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > :
> >> Vlad,
> >>
> >> Most likely today.
> >>
> >> - Alex
> >>
> >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> >>> Igniters,
> >>>
> >>> I went through remaining tickets assigned to 1.8 and it seems that we
> are
> >>> pretty close to release. As far as I understand the biggest remaining
> >>> feature is DML [1]. I think we can create separate branch for 1.8 as
> soon
> >>> as it is merged. Alex, do you have any idea on when it might happen?
> >>>
> >>> Vladimir.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> >>>
> >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> wrote:
> >>>
>  Roman,
> 
>  That versions will be created after 1.8 gets released. Recently there
> was
>  a discussion on the dev list [1] regarding the difficulties related to
>  documentation maintenance when several documentation versions
> co-exist at
>  the same time.
> 
>  It was decided that rather then create a new version for the
> documentation
>  once a new feature added to Ignite it’s better to create a hidden page
>  under the current documentation version and make it visible once the
> next
>  version is created after the release.
> 
>  The bottom line is that, please create a hidden page with a suffix
>  “page_name-1.8” and once 1.8 gets released Prachi will create
> readme.io <
>  http://readme.io/> 1.8 and make your doc visible.
> 
>  [1] http://apache-ignite-developers.2346864.n4.nabble.
>  com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
>  http://apache-ignite-developers.2346864.n4.nabble.
>  com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> 
>  —
>  Denis
> 
> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh  >
>  wrote:
> >
> > Denis,
> > Any plans to add 1.8.0 in readme.io for new features?
> > -Roman
> >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>  dma...@apache.org> wrote:
> >
> >
> > 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 
> 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 <
> ptupit...@apache.org
>  > 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/brows

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Awesome news, thanks for making this happen!

Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I start 
testing that PHP-PDO guidance [1] is correct?

[1] https://apacheignite.readme.io/docs/pdo-interoperability 


—
Denis
 
> On Nov 23, 2016, at 12:01 AM, Alexander Paschenko 
>  wrote:
> 
> Folks,
> 
> Yesterday it'd been agreed with Sergi that DML branch is now good to
> be included into 1.8 branch that is to be created.
> 
> Minor review fixes, should they be made, and test fixes will be
> incorporated into 1.8 as separate patches later.
> 
> Also, it'd been agreed that, in order to deliver these new features on
> time, two subtasks will be fixed in later releases (shortly):
> 
> https://issues.apache.org/jira/browse/IGNITE-4268
> https://issues.apache.org/jira/browse/IGNITE-4269
> 
> On failing tests:
> https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377
> 
> - Alex
> 
> 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> :
>> Vlad,
>> 
>> Most likely today.
>> 
>> - Alex
>> 
>> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>>> Igniters,
>>> 
>>> I went through remaining tickets assigned to 1.8 and it seems that we are
>>> pretty close to release. As far as I understand the biggest remaining
>>> feature is DML [1]. I think we can create separate branch for 1.8 as soon
>>> as it is merged. Alex, do you have any idea on when it might happen?
>>> 
>>> Vladimir.
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>>> 
>>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
>>> 
 Roman,
 
 That versions will be created after 1.8 gets released. Recently there was
 a discussion on the dev list [1] regarding the difficulties related to
 documentation maintenance when several documentation versions co-exist at
 the same time.
 
 It was decided that rather then create a new version for the documentation
 once a new feature added to Ignite it’s better to create a hidden page
 under the current documentation version and make it visible once the next
 version is created after the release.
 
 The bottom line is that, please create a hidden page with a suffix
 “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
 http://readme.io/> 1.8 and make your doc visible.
 
 [1] http://apache-ignite-developers.2346864.n4.nabble.
 com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
 http://apache-ignite-developers.2346864.n4.nabble.
 com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
 
 —
 Denis
 
> On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
 wrote:
> 
> Denis,
> Any plans to add 1.8.0 in readme.io for new features?
> -Roman
>   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
 dma...@apache.org> wrote:
> 
> 
> 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  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 >>> > 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 >>> > 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/j

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Regarding failing tests mentioned in IGNITE-4280
(IgniteBinaryCacheQueryTestSuite related ones): reason found
(incorrect handling of old configurations where QueryEntities don't
have keyFields field), working on the patch.

- Alex

2016-11-23 16:01 GMT+03:00 Sergey Kozlov :
> Hi
>
> I've started the testing of the key feature introducing for 1.8: DML
>
> On Wed, Nov 23, 2016 at 1:01 PM, Vladimir Ozerov 
> wrote:
>
>> Hi Alex,
>> That is very good news! I created branch *ignite-1.8* and merged your
>> changes there. Thank you for contribution!
>>
>> Igniters,
>> Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
>> Hopefully we will be ready for vote in several days.
>>
>> Vladimir.
>>
>> On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>
>> > Folks,
>> >
>> > Yesterday it'd been agreed with Sergi that DML branch is now good to
>> > be included into 1.8 branch that is to be created.
>> >
>> > Minor review fixes, should they be made, and test fixes will be
>> > incorporated into 1.8 as separate patches later.
>> >
>> > Also, it'd been agreed that, in order to deliver these new features on
>> > time, two subtasks will be fixed in later releases (shortly):
>> >
>> > https://issues.apache.org/jira/browse/IGNITE-4268
>> > https://issues.apache.org/jira/browse/IGNITE-4269
>> >
>> > On failing tests:
>> > https://issues.apache.org/jira/browse/IGNITE-2294?
>> > focusedCommentId=15683377
>> >
>> > - Alex
>> >
>> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>> > :
>> > > Vlad,
>> > >
>> > > Most likely today.
>> > >
>> > > - Alex
>> > >
>> > > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> > >> Igniters,
>> > >>
>> > >> I went through remaining tickets assigned to 1.8 and it seems that we
>> > are
>> > >> pretty close to release. As far as I understand the biggest remaining
>> > >> feature is DML [1]. I think we can create separate branch for 1.8 as
>> > soon
>> > >> as it is merged. Alex, do you have any idea on when it might happen?
>> > >>
>> > >> Vladimir.
>> > >>
>> > >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>> > >>
>> > >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
>> wrote:
>> > >>
>> > >>> Roman,
>> > >>>
>> > >>> That versions will be created after 1.8 gets released. Recently there
>> > was
>> > >>> a discussion on the dev list [1] regarding the difficulties related
>> to
>> > >>> documentation maintenance when several documentation versions
>> co-exist
>> > at
>> > >>> the same time.
>> > >>>
>> > >>> It was decided that rather then create a new version for the
>> > documentation
>> > >>> once a new feature added to Ignite it’s better to create a hidden
>> page
>> > >>> under the current documentation version and make it visible once the
>> > next
>> > >>> version is created after the release.
>> > >>>
>> > >>> The bottom line is that, please create a hidden page with a suffix
>> > >>> “page_name-1.8” and once 1.8 gets released Prachi will create
>> > readme.io <
>> > >>> http://readme.io/> 1.8 and make your doc visible.
>> > >>>
>> > >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
>> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html
>> <
>> > >>> http://apache-ignite-developers.2346864.n4.nabble.
>> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>> > >>>
>> > >>> —
>> > >>> Denis
>> > >>>
>> > >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>> > > >
>> > >>> wrote:
>> > >>> >
>> > >>> > Denis,
>> > >>> > Any plans to add 1.8.0 in readme.io for new features?
>> > >>> > -Roman
>> > >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>> > >>> dma...@apache.org> wrote:
>> > >>> >
>> > >>> >
>> > >>> > 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 
>> > 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 <
>> > ptupit...@apache.org
>> > >>> > 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
>> 

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

I've started the testing of the key feature introducing for 1.8: DML

On Wed, Nov 23, 2016 at 1:01 PM, Vladimir Ozerov 
wrote:

> Hi Alex,
> That is very good news! I created branch *ignite-1.8* and merged your
> changes there. Thank you for contribution!
>
> Igniters,
> Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
> Hopefully we will be ready for vote in several days.
>
> Vladimir.
>
> On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > Folks,
> >
> > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > be included into 1.8 branch that is to be created.
> >
> > Minor review fixes, should they be made, and test fixes will be
> > incorporated into 1.8 as separate patches later.
> >
> > Also, it'd been agreed that, in order to deliver these new features on
> > time, two subtasks will be fixed in later releases (shortly):
> >
> > https://issues.apache.org/jira/browse/IGNITE-4268
> > https://issues.apache.org/jira/browse/IGNITE-4269
> >
> > On failing tests:
> > https://issues.apache.org/jira/browse/IGNITE-2294?
> > focusedCommentId=15683377
> >
> > - Alex
> >
> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > :
> > > Vlad,
> > >
> > > Most likely today.
> > >
> > > - Alex
> > >
> > > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > >> Igniters,
> > >>
> > >> I went through remaining tickets assigned to 1.8 and it seems that we
> > are
> > >> pretty close to release. As far as I understand the biggest remaining
> > >> feature is DML [1]. I think we can create separate branch for 1.8 as
> > soon
> > >> as it is merged. Alex, do you have any idea on when it might happen?
> > >>
> > >> Vladimir.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >>
> > >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> wrote:
> > >>
> > >>> Roman,
> > >>>
> > >>> That versions will be created after 1.8 gets released. Recently there
> > was
> > >>> a discussion on the dev list [1] regarding the difficulties related
> to
> > >>> documentation maintenance when several documentation versions
> co-exist
> > at
> > >>> the same time.
> > >>>
> > >>> It was decided that rather then create a new version for the
> > documentation
> > >>> once a new feature added to Ignite it’s better to create a hidden
> page
> > >>> under the current documentation version and make it visible once the
> > next
> > >>> version is created after the release.
> > >>>
> > >>> The bottom line is that, please create a hidden page with a suffix
> > >>> “page_name-1.8” and once 1.8 gets released Prachi will create
> > readme.io <
> > >>> http://readme.io/> 1.8 and make your doc visible.
> > >>>
> > >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html
> <
> > >>> http://apache-ignite-developers.2346864.n4.nabble.
> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> > >>>
> > >>> —
> > >>> Denis
> > >>>
> > >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>  > >
> > >>> wrote:
> > >>> >
> > >>> > Denis,
> > >>> > Any plans to add 1.8.0 in readme.io for new features?
> > >>> > -Roman
> > >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> > >>> dma...@apache.org> wrote:
> > >>> >
> > >>> >
> > >>> > 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 
> > 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 <
> > ptupit...@apache.org
> > >>> > 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, 

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Hi Alex,
That is very good news! I created branch *ignite-1.8* and merged your
changes there. Thank you for contribution!

Igniters,
Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
Hopefully we will be ready for vote in several days.

Vladimir.

On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:

> Folks,
>
> Yesterday it'd been agreed with Sergi that DML branch is now good to
> be included into 1.8 branch that is to be created.
>
> Minor review fixes, should they be made, and test fixes will be
> incorporated into 1.8 as separate patches later.
>
> Also, it'd been agreed that, in order to deliver these new features on
> time, two subtasks will be fixed in later releases (shortly):
>
> https://issues.apache.org/jira/browse/IGNITE-4268
> https://issues.apache.org/jira/browse/IGNITE-4269
>
> On failing tests:
> https://issues.apache.org/jira/browse/IGNITE-2294?
> focusedCommentId=15683377
>
> - Alex
>
> 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> :
> > Vlad,
> >
> > Most likely today.
> >
> > - Alex
> >
> > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> >> Igniters,
> >>
> >> I went through remaining tickets assigned to 1.8 and it seems that we
> are
> >> pretty close to release. As far as I understand the biggest remaining
> >> feature is DML [1]. I think we can create separate branch for 1.8 as
> soon
> >> as it is merged. Alex, do you have any idea on when it might happen?
> >>
> >> Vladimir.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> >>
> >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
> >>
> >>> Roman,
> >>>
> >>> That versions will be created after 1.8 gets released. Recently there
> was
> >>> a discussion on the dev list [1] regarding the difficulties related to
> >>> documentation maintenance when several documentation versions co-exist
> at
> >>> the same time.
> >>>
> >>> It was decided that rather then create a new version for the
> documentation
> >>> once a new feature added to Ignite it’s better to create a hidden page
> >>> under the current documentation version and make it visible once the
> next
> >>> version is created after the release.
> >>>
> >>> The bottom line is that, please create a hidden page with a suffix
> >>> “page_name-1.8” and once 1.8 gets released Prachi will create
> readme.io <
> >>> http://readme.io/> 1.8 and make your doc visible.
> >>>
> >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
> >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
> >>> http://apache-ignite-developers.2346864.n4.nabble.
> >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> >>>
> >>> —
> >>> Denis
> >>>
> >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh  >
> >>> wrote:
> >>> >
> >>> > Denis,
> >>> > Any plans to add 1.8.0 in readme.io for new features?
> >>> > -Roman
> >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> >>> dma...@apache.org> wrote:
> >>> >
> >>> >
> >>> > 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 
> 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 <
> ptupit...@apache.org
> >>> > 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  >>> > 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 b

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Folks,

Yesterday it'd been agreed with Sergi that DML branch is now good to
be included into 1.8 branch that is to be created.

Minor review fixes, should they be made, and test fixes will be
incorporated into 1.8 as separate patches later.

Also, it'd been agreed that, in order to deliver these new features on
time, two subtasks will be fixed in later releases (shortly):

https://issues.apache.org/jira/browse/IGNITE-4268
https://issues.apache.org/jira/browse/IGNITE-4269

On failing tests:
https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377

- Alex

2016-11-22 11:29 GMT+03:00 Alexander Paschenko
:
> Vlad,
>
> Most likely today.
>
> - Alex
>
> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> Igniters,
>>
>> I went through remaining tickets assigned to 1.8 and it seems that we are
>> pretty close to release. As far as I understand the biggest remaining
>> feature is DML [1]. I think we can create separate branch for 1.8 as soon
>> as it is merged. Alex, do you have any idea on when it might happen?
>>
>> Vladimir.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>>
>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
>>
>>> Roman,
>>>
>>> That versions will be created after 1.8 gets released. Recently there was
>>> a discussion on the dev list [1] regarding the difficulties related to
>>> documentation maintenance when several documentation versions co-exist at
>>> the same time.
>>>
>>> It was decided that rather then create a new version for the documentation
>>> once a new feature added to Ignite it’s better to create a hidden page
>>> under the current documentation version and make it visible once the next
>>> version is created after the release.
>>>
>>> The bottom line is that, please create a hidden page with a suffix
>>> “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
>>> http://readme.io/> 1.8 and make your doc visible.
>>>
>>> [1] http://apache-ignite-developers.2346864.n4.nabble.
>>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
>>> http://apache-ignite-developers.2346864.n4.nabble.
>>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>>>
>>> —
>>> Denis
>>>
>>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
>>> wrote:
>>> >
>>> > Denis,
>>> > Any plans to add 1.8.0 in readme.io for new features?
>>> > -Roman
>>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>>> dma...@apache.org> wrote:
>>> >
>>> >
>>> > 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  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 >> > 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 >> > 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 >> dma...@gridgain.com>> 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 

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Vlad,

Most likely today.

- Alex

2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> Igniters,
>
> I went through remaining tickets assigned to 1.8 and it seems that we are
> pretty close to release. As far as I understand the biggest remaining
> feature is DML [1]. I think we can create separate branch for 1.8 as soon
> as it is merged. Alex, do you have any idea on when it might happen?
>
> Vladimir.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>
> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
>
>> Roman,
>>
>> That versions will be created after 1.8 gets released. Recently there was
>> a discussion on the dev list [1] regarding the difficulties related to
>> documentation maintenance when several documentation versions co-exist at
>> the same time.
>>
>> It was decided that rather then create a new version for the documentation
>> once a new feature added to Ignite it’s better to create a hidden page
>> under the current documentation version and make it visible once the next
>> version is created after the release.
>>
>> The bottom line is that, please create a hidden page with a suffix
>> “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
>> http://readme.io/> 1.8 and make your doc visible.
>>
>> [1] http://apache-ignite-developers.2346864.n4.nabble.
>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
>> http://apache-ignite-developers.2346864.n4.nabble.
>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>>
>> —
>> Denis
>>
>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
>> wrote:
>> >
>> > Denis,
>> > Any plans to add 1.8.0 in readme.io for new features?
>> > -Roman
>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>> dma...@apache.org> wrote:
>> >
>> >
>> > 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  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 > > 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 > > 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 > dma...@gridgain.com>> 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 <
>> >>> alexander.a.pasche...@gmail.com > gmail.com>> 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:
>> >>> - testPutWithFi

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Igniters,

I went through remaining tickets assigned to 1.8 and it seems that we are
pretty close to release. As far as I understand the biggest remaining
feature is DML [1]. I think we can create separate branch for 1.8 as soon
as it is merged. Alex, do you have any idea on when it might happen?

Vladimir.

[1] https://issues.apache.org/jira/browse/IGNITE-2294

On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:

> Roman,
>
> That versions will be created after 1.8 gets released. Recently there was
> a discussion on the dev list [1] regarding the difficulties related to
> documentation maintenance when several documentation versions co-exist at
> the same time.
>
> It was decided that rather then create a new version for the documentation
> once a new feature added to Ignite it’s better to create a hidden page
> under the current documentation version and make it visible once the next
> version is created after the release.
>
> The bottom line is that, please create a hidden page with a suffix
> “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
> http://readme.io/> 1.8 and make your doc visible.
>
> [1] http://apache-ignite-developers.2346864.n4.nabble.
> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
> http://apache-ignite-developers.2346864.n4.nabble.
> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>
> —
> Denis
>
> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
> wrote:
> >
> > Denis,
> > Any plans to add 1.8.0 in readme.io for new features?
> > -Roman
> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> dma...@apache.org> wrote:
> >
> >
> > 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  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  > 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  > 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  dma...@gridgain.com>> 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 <
> >>> alexander.a.pasche...@gmail.com  gmail.com>> 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 

Re: Apache Ignite 1.8 Release

[Denis Magda]

Roman,

That versions will be created after 1.8 gets released. Recently there was a 
discussion on the dev list [1] regarding the difficulties related to 
documentation maintenance when several documentation versions co-exist at the 
same time.

It was decided that rather then create a new version for the documentation once 
a new feature added to Ignite it’s better to create a hidden page under the 
current documentation version and make it visible once the next version is 
created after the release.

The bottom line is that, please create a hidden page with a suffix 
“page_name-1.8” and once 1.8 gets released Prachi will create readme.io 
 1.8 and make your doc visible.

[1] 
http://apache-ignite-developers.2346864.n4.nabble.com/Maintaining-documentation-consistency-on-readme-io-td10868.html
 


—
Denis

> On Nov 16, 2016, at 5:00 PM, Roman Shtykh  wrote:
> 
> Denis,
> Any plans to add 1.8.0 in readme.io for new features?
> -Roman
>On Wednesday, November 16, 2016 6:08 AM, Denis Magda  
> wrote:
> 
> 
> 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  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 > > 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 > > 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 >> > 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 <
>>> alexander.a.pasche...@gmail.com > 
>>> 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
>>> 
>>> 
>>> 
>>> 
>> 
> 
> 

Re: Apache Ignite 1.8 Release

[Roman Shtykh]

Denis,
Any plans to add 1.8.0 in readme.io for new features?
-Roman
On Wednesday, November 16, 2016 6:08 AM, Denis Magda  
wrote:
 

 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  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  > 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  > 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  > > 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 <
> > alexander.a.pasche...@gmail.com > 
> > 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
> >
> >
> >
> >
> 


   

Re: Apache Ignite 1.8 Release

[Denis Magda]

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  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  > 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  > 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  > > 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 <
> > alexander.a.pasche...@gmail.com > 
> > 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
> >
> >
> >
> >
> 

Re: Apache Ignite 1.8 Release

[Denis Magda]

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  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  > 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 > > 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 
>>> mailto:alexander.a.pasche...@gmail.com>> 
>>> 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
>> 
> 
> 

Re: Apache Ignite 1.8 Release

[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  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 
> 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  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  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 <
> > > alexander.a.pasche...@gmail.com> 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
> > >
> > >
> > >
> > >
> >
>

Re: Apache Ignite 1.8 Release

[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 
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  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  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 <
> > alexander.a.pasche...@gmail.com> 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
> >
> >
> >
> >
>

Re: Apache Ignite 1.8 Release

[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  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  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 <
> alexander.a.pasche...@gmail.com> 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
>
>
>
>

Re: Apache Ignite 1.8 Release

[Denis Magda]

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  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 
>>  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
> 

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Alex,

Tests are fixed. Please merge them into your branch.

Vladimir.

On Wed, Nov 9, 2016 at 8:01 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> 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
>

Re: Apache Ignite 1.8 Release

[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 
>  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

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

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

Re: Apache Ignite 1.8 Release

[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 


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  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  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  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 
>> 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 <
>> dma...@apache.org> 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 >> 
 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
 
>>> 
>> 
>> 

Re: Apache Ignite 1.8 Release

[Dmitriy Setrakyan]

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  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  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 
> 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 <
> dma...@apache.org> 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  >
> >> 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
> >>
> >
>
>

Re: Apache Ignite 1.8 Release

[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 


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  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  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  
>> 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 
>> 
>> PHP PDO Support from ODBC side: 
>> 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 
>> 
>> 
>> 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
>> 
> 

Re: Apache Ignite 1.8 Release

[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  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  
> 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 
> 
> PHP PDO Support from ODBC side: 
> 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 
> 
> 
> 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
> 

Re: Apache Ignite 1.8 Release

[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  
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 

PHP PDO Support from ODBC side: 
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 


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

   

Re: Apache Ignite 1.8 Release

[Denis Magda]

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


This is a minor change.

—
Denis

> On Oct 27, 2016, at 10:56 AM, Igor Sapego  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 
> 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 
>> 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 
>>> 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 
>> 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 > 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
 
 
 
>>> 
>> 

Re: Apache Ignite 1.8 Release

[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 
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 
> 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 
> > 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 
> 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  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
> > >
> > >
> > >
> >
>

Re: Apache Ignite 1.8 Release

[Dmitriy Setrakyan]

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 
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 
> 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  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 
> >> 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
> >
> >
> >
>

Re: Apache Ignite 1.8 Release

[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 
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  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 
>> 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
>
>
>

Re: Apache Ignite 1.8 Release

[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  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  >
> 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