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

[GitHub] ignite pull request #1273: IGNITE-4282: Javadoc broken.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1273


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1258: Ignite-4243: Added a Python/PHP examples for Redi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1258


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1288: Ignite 3904

[ntikhonov]

GitHub user ntikhonov opened a pull request:

https://github.com/apache/ignite/pull/1288

Ignite 3904



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3904

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1288.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1288


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit bf330251734018467fa3291fccf0414c9da7dd1b
Author: Andrey Novikov 
Date:   2016-11-24T10:08:08Z

Web console beta-6.

commit 7d88c5bfe7d6f130974fab1ed4266fff859afd3d
Author: Andrey Novikov 
Date:   2016-11-24T10:59:33Z

Web console beta-6. Minor fix.

commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 4f59c52ef64be244cdb967a083a31fb7b320345c
Author: nikolay_tikhonov 
Date:   2016-11-22T15:11:43Z

IGNITE-3904 WIP.

commit 77f120ceaa647c226c4a582715989da02df404df
Author: nikolay_tikhonov 
Date:   2016-11-24T17:56:15Z

IGNITE-3904 WIP

commit ba9f74d35bfc11ead9f22d455e7fbd9bec601e45
Author: nikolay_tikhonov 
Date:   2016-11-25T17:22:37Z

IGNITE-3904 WIP




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #665: 7.5.16

[ntikhonov]

Github user ntikhonov closed the pull request at:

https://github.com/apache/ignite/pull/665


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1240: ignite-3958

[ntikhonov]

Github user ntikhonov closed the pull request at:

https://github.com/apache/ignite/pull/1240


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #743: Ignite 3164

[ntikhonov]

Github user ntikhonov closed the pull request at:

https://github.com/apache/ignite/pull/743


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1176: TC 3164

[ntikhonov]

Github user ntikhonov closed the pull request at:

https://github.com/apache/ignite/pull/1176


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1287: IGNITE-3169 .NET: Provide error messages for inco...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/1287

IGNITE-3169 .NET: Provide error messages for incorrect Apache.Ignite.exe 
command line arguments



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-3169

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1287.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1287


commit 06c21e5c93c7f2b02c5e681bfe02feac854a27d7
Author: Pavel Tupitsyn 
Date:   2016-11-25T12:02:32Z

Add failure on unknown argument

commit cbcc6dd219df309f798fa9cd6ea56c035610af57
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:11:54Z

Add empty args validation

commit d99ebe4493b1e180f783a6290b272574392cc21a
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:30:14Z

wip tests

commit b1c65cc4a4aa117604c12295099dc6eb4a12bd67
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:52:27Z

wip tests

commit d7dc96c6718091a6f223e4fdf9464a29d877792d
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:55:05Z

tests

commit b804326ede37e7421275eed1a4c7bf972a83cce2
Author: Pavel Tupitsyn 
Date:   2016-11-25T15:02:03Z

wip

commit 62460472b4860a81c35ad943020881168dd3c69d
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:36:44Z

wip test

commit 9fd8166b5e3cb1d2ff6c9e890de299731aa0c2c7
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:45:35Z

more tests

commit b1d453ea870d030e32f21fabff5de98c285a341c
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:55:30Z

wip

commit dc760dce03fb19ec2145a30f5bcd63a971b0419f
Author: Pavel Tupitsyn 
Date:   2016-11-25T17:00:32Z

Tests done




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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 

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 

[jira] [Created] (IGNITE-4314) Cache.clear should not destroy offheap map

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4314:


 Summary: Cache.clear should not destroy offheap map
 Key: IGNITE-4314
 URL: https://issues.apache.org/jira/browse/IGNITE-4314
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Semen Boikov
 Fix For: 1.9


Currently when offheap is enabled then cache.clear() operations fully destroys 
offheap map (GridCacheClearAllRunnable calls 
GridCacheSwapManager.clearOffHeap). This is not correct since there can be 
entry referenceing cleared memory, it seems offheap should be cleared in the 
same way as swap using offheap keys iterator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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
> 

[GitHub] ignite pull request #1286: IGNITE-4308 Ignore QueryEntity.keyFields when key...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/1286

IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4308

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1286.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1286


commit 8a522ec9457363b107fe4a6df0742e5c629689ca
Author: Alexander Paschenko 
Date:   2016-11-25T13:33:46Z

IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4313:
-

 Summary: DML: update causes IgniteCheckedException: Not enough 
data to read the value
 Key: IGNITE-4313
 URL: https://issues.apache.org/jira/browse/IGNITE-4313
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


0. Extract teh attachment in {{examples}} directory.
1. Start node {{ExtSqlExampleNodeStartup}}
2. Run {{ExtSqlExample}}. It failed:
{noformat}
Processing the caches...
Exception in thread "main" javax.cache.CacheException: Failed to run map query 
remotely.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:652)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:483)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
104496cc-dd94-4150-90de-8628c2ddf6ff, class 
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:278)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:268)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:249)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:197)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1915)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[16:10:49] Ignite node stopped OK [uptime=00:00:00:372]

Process finished with exit code 1
{noformat}

Exception on the node:
{noformat}
[16:10:49,679][ERROR][sys-#75%null%][GridMapQueryExecutor] Failed to execute 
local query.
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:958)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1010)
at 

[jira] [Created] (IGNITE-4312) DML: update causes IgniteCheckedException: Invalid flag value: -2

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4312:
-

 Summary: DML: update causes IgniteCheckedException: Invalid flag 
value: -2
 Key: IGNITE-4312
 URL: https://issues.apache.org/jira/browse/IGNITE-4312
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


{noformat}
[15:58:04] Ignite node stopped OK [uptime=00:00:00:111]
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Invalid flag value: -2
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteException: Invalid flag value: -2
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:817)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
... 6 more
Caused by: class org.apache.ignite.IgniteCheckedException: Invalid flag value: 
-2
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1788)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
... 7 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Invalid flag 
value: -2
at 
org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:285)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:186)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:524)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
... 8 more

Process finished with exit code 1
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

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

[jira] [Created] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4311:
---

 Summary: .NET: MultiTieredCacheExample has some issues 
 Key: IGNITE-4311
 URL: https://issues.apache.org/jira/browse/IGNITE-4311
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova


Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:

1) Typo
{noformat}
Console.WriteLine(">>> Lifecycle example started.");
{noformat}

2) 
{noformat}
OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
{noformat}
This size is not enough to store 10 entries, overhead is not taked into 
account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
minimum.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4310) Add release notes for Ignite 1.8.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4310:
---

 Summary: Add release notes for Ignite 1.8.
 Key: IGNITE-4310
 URL: https://issues.apache.org/jira/browse/IGNITE-4310
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 1.8






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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 

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

[GitHub] ignite pull request #1285: IGNITE-4200: Added copying of the C++ binaries.

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/1285

IGNITE-4200: Added copying of the C++ binaries.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-4200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1285.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1285


commit 5858f746a5aec9dd697199c2b7a0961d839119f8
Author: Igor Sapego 
Date:   2016-11-25T11:32:22Z

IGNITE-4200: Added copying of the C++ binaries.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[jira] [Created] (IGNITE-4309) IgniteLockExample hangs in multi-node mode.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4309:
---

 Summary: IgniteLockExample hangs in multi-node mode.
 Key: IGNITE-4309
 URL: https://issues.apache.org/jira/browse/IGNITE-4309
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 1.8


Steps to reproduce:
1) Start CacheExamplesMultiNodeSelfTest.testCacheLockExample.
2) Observe that example hangs and the following metrics printout appears form 
time to time:
{code}
^-- Public thread pool [active=2, idle=0, qSize=0]
{code}
or
{code}
^-- Public thread pool [active=3, idle=0, qSize=0]
{code}

Logs with thread dumps on TC: 
http://195.239.208.174/viewLog.html?buildId=368311=IgniteTests_IgniteExamples=buildLog#_focus=24510



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4308) Make QueryEntity.keyFields optional for caches having SQL types as keys

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4308:
---

 Summary: Make QueryEntity.keyFields optional for caches having SQL 
types as keys
 Key: IGNITE-4308
 URL: https://issues.apache.org/jira/browse/IGNITE-4308
 Project: Ignite
  Issue Type: Improvement
  Components: SQL
Affects Versions: 1.8
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko


Initial implementation of DML requires the user to specify keyFields in 
configuration explicitly, even if it's empty, in cases when DML is used and 
binary marshaller is used. As [~vozerov] noted, it could affect usability, if 
even a little, so this should be fixed - when a primitive/simple SQL type is 
used as a key, it's obvious that there's no key fields and hence it's not 
necessary to specify empty keyFields in this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1284: IGNITE-4279 Fix for testFetchSize in JdbcResultSe...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/1284

IGNITE-4279 Fix for testFetchSize in JdbcResultSetSelfTest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4279

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1284.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1284


commit c8936fbe4708f6901c49f0aa69f0932843b67c76
Author: Alexander Paschenko 
Date:   2016-11-25T11:04:37Z

IGNITE-4279 Fix for testFetchSize in JdbcResultSetSelfTest




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1283: Ignite 4305

[kdudkov]

GitHub user kdudkov opened a pull request:

https://github.com/apache/ignite/pull/1283

Ignite 4305



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4305

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1283.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1283


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 86d143bb8bdbdccba9209762b1fd802d5dc40268
Author: Alexander Paschenko 
Date:   2016-11-23T09:58:26Z

IGNITE-2294: Implemented DML.

commit 4ba1386987cdd7ee26c14a6d599d6c6a970ca08a
Author: devozerov 
Date:   2016-11-23T14:56:50Z

Merge branch 'ignite-1.7.4' into ignite-1.8

commit f4524a6a7b86df9cd008dcd22fa5cfa400c3af27
Author: isapego 
Date:   2016-11-23T14:58:41Z

IGNITE-4096: Added ODBC-DML tests. Fixed issues. This closes #1178.

commit 83363d8e0cab93b62f674ce0215082364881254b
Author: isapego 
Date:   2016-11-23T15:07:06Z

IGNITE-4016: ODBC: Example now uses DML. This closes #1265.

commit 4d243251006bc8d1de85d7b6a481976899755a82
Author: isapego 
Date:   2016-11-23T15:11:35Z

IGNITE-3910: ODBC: Implemented SQLDescribeParam. This closes #1269.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit bf330251734018467fa3291fccf0414c9da7dd1b
Author: Andrey Novikov 
Date:   2016-11-24T10:08:08Z

Web console beta-6.

commit e43ea5ee9b6982b2b2086fd2a678882d24c1654c
Author: Andrey Novikov 
Date:   2016-11-24T10:12:07Z

Merge branch 'ignite-1.7.4' into 'ignite-1.8'.

commit 7d88c5bfe7d6f130974fab1ed4266fff859afd3d
Author: Andrey Novikov 
Date:   2016-11-24T10:59:33Z

Web console beta-6. Minor fix.

commit d2b915e50c8e3cbe07f565f14d14474342662550
Author: Andrey Novikov 
Date:   2016-11-24T11:01:31Z

Merge branch 'ignite-1.7.4' into 'ignite-1.8'.

commit 4a758d1a6285f9441af7c894e2a31e0df895cb03
Author: isapego 
Date:   2016-11-24T12:49:08Z

IGNITE-4288: ODBC: Fixed DML interoperability. This closes #1272.

commit d5dc5815416cc13f7b2b8a323fa5a39ec95ecb95
Author: isapego 
Date:   2016-11-24T12:53:35Z

IGNITE-4299: ODBC Minor example fix. This closes #1277.

commit c4badeef809851c1ab890e2d6358834f698e94ad
Author: Pavel Tupitsyn 
Date:   2016-11-24T13:32:02Z

IGNITE-4297 .NET: Update NuGet scripts to clean up jars in bin folder

commit fabb77d17859a0a6318c2fe11182ab753e2198e0
Author: Alexander Paschenko 
Date:   2016-11-24T15:51:07Z

IGNITE-4280 Test fix for IgniteBinaryCacheQueryTestSuite. This closes #1275.

commit deee3b9f64406e084e65c1f7e48e14270e8ad688
Author: devozerov 
Date:   2016-11-25T08:15:17Z

Fixed JavaDoc warnings in Redis REST classes.

commit 7b35ba730edbb91a30a59b1efdc22eceea7298e1
Author: devozerov 
Date:   2016-11-25T08:22:05Z

IGNITE-4270: Fixed system property name.

commit 2463abf21682a8686a2b751779a2f57e05879a1b
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4307) .NET: AtomicSequenceExample uses AtomicConfiguration incorrectly

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4307:
--

 Summary: .NET: AtomicSequenceExample uses AtomicConfiguration 
incorrectly
 Key: IGNITE-4307
 URL: https://issues.apache.org/jira/browse/IGNITE-4307
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.9


AtomicConfiguration is specified only on local node. Standalone nodes use 
default configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4306) .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4306:
--

 Summary: .NET: TestRemoteNodesClientMode(AtomicSequenceExample) 
fails intermittently
 Key: IGNITE-4306
 URL: https://issues.apache.org/jira/browse/IGNITE-4306
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


Looks like standalone node fails to join



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Server Node Stops Unexpectedly

[Alper Tekinalp]

Hi all.

On one of our clusters we have 3 server nodes. 2 times in this week one of
the nodes in cluster stops. We are getting errors that stating the node is
stopping. We listen node joined and left events and before errors we see
logs saying node x left cluster. I suspect that the reason is kinda network
timeout or similar. Because other nodes are up and running.

1 - Is it possible that in a network timeout nodes stops themself?
2 - Is there any parameter or property that we can increase to avoid such
timeouts?
3 - What could be another reason that nodes stops themself?

I will try to collect more information like logs etc.

Regard.

-- 
Alper Tekinalp

Software Developer
Evam Streaming Analytics

Atatürk Mah. Turgut Özal Bulv.
Gardenya 5 Plaza K:6 Ataşehir
34758 İSTANBUL

Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
www.evam.com.tr

[jira] [Created] (IGNITE-4305) GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal invoke arguments properly.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4305:
---

 Summary: GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal 
invoke arguments properly.
 Key: IGNITE-4305
 URL: https://issues.apache.org/jira/browse/IGNITE-4305
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 1.8


Steps to reproduce:
1) Set binary marshaller as deafult for 
{{GridCacheBinaryAtomicEntryProcessorDeploymentSelfTest}}:
{code}
static {
GridTestProperties.setProperty(GridTestProperties.MARSH_CLASS_NAME, 
BinaryMarshaller.class.getName());
GridTestProperties.setProperty(GridTestProperties.ENTRY_PROCESSOR_CLASS_NAME,
"org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor");
}
{code}

2) Run the test, observe failures in {{testInvokeDeployment*}} tests.

3) Go to {{GridNearAtomicSingleUpdateFuture.mapSingleUpdate}} and force single 
transform to use old {{GridNearAtomicFullUpdateRequest}}

4) Re-run test. No all pass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1282: IGNITE-4295

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/1282

IGNITE-4295



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4295

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1282.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1282


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit b73fa8c4e9f52e96bd806e1cdbec1bed3623a54f
Author: devozerov 
Date:   2016-11-24T08:53:29Z

IGNITE-4295: Replaced "unsafe" byte[]->byte[] copying with System.arrayCopy.

commit 29a3a4fa12ed7642ec750f339ed36279323931b7
Author: devozerov 
Date:   2016-11-24T09:35:00Z

offheap->heap routine.

commit 3af04bd1326aa08796b9876795c227be25089d9b
Author: devozerov 
Date:   2016-11-24T09:38:52Z

heap->offheap routine.

commit 3539b448aa81dbdd541a5c168826b1806bdfded6
Author: devozerov 
Date:   2016-11-24T10:05:19Z

Added threshold.

commit bdbf64d55d76c91ed214bb34625dad4a10a3453d
Author: devozerov 
Date:   2016-11-24T10:26:22Z

Fix to default value.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Use Upsource for Code Review

[Pavel Tupitsyn]

Vladimir, right, see my reply to Sergi above.

On Fri, Nov 25, 2016 at 10:58 AM, Vladimir Ozerov 
wrote:

> Igniters,
>
> As I understand nobody is forced to use this tool, right?
>
> On Fri, Nov 25, 2016 at 12:01 AM, Konstantin Boudnik 
> wrote:
>
> > On Mon, Nov 21, 2016 at 12:57PM, Dmitriy Setrakyan wrote:
> > > Cos, I see your point, but I think this one falls under procedural
> issue,
> > > no?
> >
> > Not really. We are talking about a use of a tool to improve the review
> > process. Dictating a tool would be a step to a wrong direction. It's like
> > imposing the use of IDEA and banishing all Eclipse users (although, I
> > wouldn't
> > mind really ;)
> >
> > Dictation of a development technology is where the rift happens, IMO. But
> > when
> > we are on the same page as the result of the consensus, rather than a
> fiat
> > -
> > that's a different story.
> >
> > Cos
> >
> > k On Mon, Nov 21, 2016 at 12:21 PM, Konstantin Boudnik 
> > wrote:
> > >
> > > > What are we voting for this?
> > > >
> > > > Fortunately, Apache isn't about democracy. [1]
> > > >
> > > > [1] https://www.apache.org/foundation/voting.html
> > > >
> > > > Cos
> > > >
> > > > On Wed, Nov 16, 2016 at 01:08PM, Pavel Tupitsyn wrote:
> > > > > Following the discussion on Upsource [1],
> > > > > I would like to call a vote on accepting it as our official code
> > review
> > > > > tool.
> > > > >
> > > > > [ ] +1  approve
> > > > > [ ] +0  no opinion
> > > > > [ ] -1  disapprove (and reason why)
> > > > >
> > > > > This vote will go on for 5 days.
> > > > >
> > > > > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > > > > com/Code-Review-Tool-Proposal-Upsource-td12195.html
> > > >
> >
>