Re: Removing "fabric" from Ignite binary package name

[Petr Ivanov]

Assigned myself — done the same work while preparing RPM package.
But for fixing DEVNOTES.txt waiting for review and merge of IGNITE-7107 [1].


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



> On 19 Dec 2017, at 22:55, Denis Magda  wrote:
> 
> All the bids were accepted and the verdict is executed:
> https://issues.apache.org/jira/browse/IGNITE-7251 
> 
> 
> Who is ready to pick this up?
> 
> —
> Denis
> 
>> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov  
>> wrote:
>> 
>> +1б фо шур
>> 
>> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov 
>> wrote:
>> 
>>> +1б вуаштшеудн
>>> 
>>> On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com> wrote:
>>> 
 +1
 
 On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org
> 
 wrote:
 
> +1 (completely agree)
> 
> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda 
>>> wrote:
> 
>> Igniters,
>> 
>> Apache Ignite binary releases still include “fabric” word in their
 names:
>> https://ignite.apache.org/download.cgi#binaries <
>> https://ignite.apache.org/download.cgi#binaries>
>> 
>> For instance, this is a full name of the previous release -
>> apache-ignite-fabric-2.3.0-bin.
>> It’s a little oversight on our side because the project has not been
>> positioned as a fabric for a while.
>> 
>> Proposal! Remove “fabric” from the name and have the binary releases
> named
>> as - apache-ignite-{version}-bin.
>> 
>> If we’re in consensus then let’s make the change in 2.4.
>> 
>> —
>> Denis
>> 
> 
 
>>> 
> 

Re: Time and scope for Apache Ignite 2.4

[Petr Ivanov]

Hi, Denis!


What about switching to Java 8 by default? [1]
I guess this task is inseparably connected to Java 7 support drop and Java 9 
support introducing.


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



> On 19 Dec 2017, at 23:07, Denis Magda  wrote:
> 
> Igniters,
> 
> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets
>  
> 
> 
> How good are we if to assume 5th of Jan as a code freeze date? Please comment:
> - Nikolay Izhikov: Data Frames.
> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
> - Yuri: Machine Learning + neural networks
> - Vladimir Ozerov: Java 9 and Java 7
> - Sergey Kozlov: SQL scope testing
> - etc.: please check the link with the features.
> 
> —
> Denis
>> On Dec 4, 2017, at 1:11 PM, Denis Magda  wrote:
>> 
>> Igniters,
>> 
>> Basing on the amount of improvements, fixes and features stacked in the 
>> master branch I think it’s a right time to negotiate the scope and time of 
>> the next Apache Ignite 2.4 release. I’m ready to step in as a release 
>> manager if none of the committers wants to try on this role.
>> 
>> Here is a release page:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 
>> 
>> 
>> Proposed time date: Jan 5 - code freeze -> stabilization and testing -> Jan 
>> 24 - voting -> Jan 31 release.
>> 
>> In my view improvements such Java 9 support and Java 7 discontinuation, 
>> memory metrics in bytes [1], binary client protocol, etc. needs to get into 
>> the release. All the features like that are labeled “important” in JIRA. Use 
>> this label if you are convinced a task has to be release in 2.4.
>> 
>> What’s about machine learning, bulk loading [2], internals problems 
>> resolution [3], metrics [4] related tasks? What goes in 2.4 and what’s 
>> shifted?
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-6902 
>> 
>> [2] 
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bulk+data+loading+performance+improvements
>>  
>> 
>> [3] 
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
>>  
>> 
>> [4] 
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements
>>  
>> 
>> 
>> —
>> Denis
> 

[GitHub] ignite pull request #3186: Ignite 1.8.16

[alamar]

Github user alamar closed the pull request at:

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


---

[jira] [Created] (IGNITE-7255) SQL: Failed to execute explain via new "non-caches" API

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7255:


 Summary: SQL: Failed to execute explain via new "non-caches" API
 Key: IGNITE-7255
 URL: https://issues.apache.org/jira/browse/IGNITE-7255
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Kuznetsov


I'm executing code via querySqlFieldsNoCache API:
{code}
 qryCursor = ignite.context().query().querySqlFieldsNoCache(qry, true);
{code}

And got exception:
{noformat}
[CacheException] class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: EXPLAIN select count(*) from Person
   [IgniteSQLException] Failed to parse query: EXPLAIN select count(*) from 
Person
   [JdbcSQLException] Table "PERSON" not found; SQL statement: EXPLAIN select 
count(*) from Person [42102-195]
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3254: Ignite 4191 mvcc enabled

[devozerov]

GitHub user devozerov opened a pull request:

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

Ignite 4191 mvcc enabled



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-4191-mvcc-enabled

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

https://github.com/apache/ignite/pull/3254.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 #3254


commit f6e982540e65ab17d439dba990794f35616a30dd
Author: sboikov 
Date:   2017-08-30T09:45:40Z

ignite-3478

commit 275a85db5cd6923b36126166ae99b15e876192be
Author: sboikov 
Date:   2017-08-31T07:44:07Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit b7b9089f0102b8cab9942a9c887d93e9f26cc7d2
Author: sboikov 
Date:   2017-08-31T09:00:36Z

disco cache cleanup

commit 855c2d45794c300d41e386b4e6fa40736cc3e40d
Author: sboikov 
Date:   2017-08-31T09:09:58Z

Merge branch 'ignite-3478-1' into ignite-3478

commit 08be7310a93d3ce455215b97cf8ab1a2c3f0ab31
Author: sboikov 
Date:   2017-08-31T09:52:23Z

ignite-3478

commit fce2e31f0fd2f4f6a9944422e40408a0c65cfe90
Author: sboikov 
Date:   2017-09-04T08:13:50Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit d3c049952384750c5543a9f88b383c033ef74096
Author: sboikov 
Date:   2017-09-04T08:52:11Z

ignite-3478

commit e71ce1937a18dd32448e92b1038dc48d4cb6f8ab
Author: sboikov 
Date:   2017-09-04T10:16:03Z

ignite-3478

commit 5fac5b0965e97f8951e16e10ca9229a2e78ddb0c
Author: sboikov 
Date:   2017-09-05T10:16:44Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit 2e0c9c08e046e8d6af1b5358d9053eae999b1fb4
Author: sboikov 
Date:   2017-09-05T11:30:55Z

ignite-3478

commit e1e07ffdf2d711ba3e72f316f5a3970eff27372e
Author: sboikov 
Date:   2017-09-05T11:31:14Z

ignite-3478

commit cbada3934a386668da0b11d4de7d0f58a4d04dfe
Author: sboikov 
Date:   2017-09-05T11:49:49Z

ignite-3484

commit 5a82c68dcd1927bb6fded8b7def38c91ff6e145b
Author: sboikov 
Date:   2017-09-05T11:59:49Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit bc9134c94b7a738dc1664e96ca6eabb059f1c268
Author: sboikov 
Date:   2017-09-05T12:03:39Z

Merge branch 'ignite-3478' into ignite-3484

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/tree/AbstractDataInnerIO.java

commit b4bfcde78825c6517232e49d389bdb5de19f05a9
Author: sboikov 
Date:   2017-09-05T12:27:51Z

ignite-3484

commit 43834aaab9e2c3cd5fdd55289fdc4a9ff8ab6599
Author: sboikov 
Date:   2017-09-05T13:13:00Z

ignite-3478

commit d1b828095713fcadfa260cf94fef01b42a1b12fd
Author: sboikov 
Date:   2017-09-05T13:13:33Z

Merge branch 'ignite-3478' into ignite-3484

commit 6be6779b6336c36cd71eef0a25199a6a877ce6b5
Author: sboikov 
Date:   2017-09-05T13:47:11Z

ignite-3484

commit e3bba83256c1eb53c4b40fbd9ddba47fcf9d58d5
Author: sboikov 
Date:   2017-09-06T07:10:26Z

ignite-3484

commit dd0afb28466094b801506da8afa3601bfaebd853
Author: sboikov 
Date:   2017-09-06T07:30:04Z

ignite-3484

commit 27b87b413348b03986a463551db24b7726321732
Author: sboikov 
Date:   2017-09-06T08:19:18Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit dcaf8801accd6ee089849a82b2ccd558aec81895
Author: sboikov 
Date:   2017-09-06T08:19:30Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit c966451d0bf7059575de92bcfae43d72096ebce4
Author: sboikov 
Date:   2017-09-06T08:27:04Z

Merge branch 'ignite-3478' into ignite-3484

commit 91b9911731a387a3199ddbbc22704bc14af09995
Author: sboikov 
Date:   2017-09-06T09:22:22Z

ignite-3484

commit e40b4d9dcd6fe6c1cd2640bdd7116ca5a08ed781
Author: sboikov 
Date:   2017-09-07T09:12:32Z

ignite-3484

commit 41a1c571e6ba1765941e2f1679dc4ac1582275c4
Author: sboikov 
Date:   2017-09-08T07:55:24Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3484

commit 1626130801dc330bcaf693f46906f6564cce6802
Author: sboikov 
Date:   2017-09-08T08:04:57Z

ignite-3484

commit 91bbb7cd24f38a38e2e65fc3ebf5637572b11b25
Author: sboikov 
Date:   2017-09-08T12:34:52Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-6149

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxP

[jira] [Created] (IGNITE-7256) Web Console: Improve notification management.

[Alexander Kalinin (JIRA)]

Alexander Kalinin created IGNITE-7256:
-

 Summary: Web Console: Improve notification management.
 Key: IGNITE-7256
 URL: https://issues.apache.org/jira/browse/IGNITE-7256
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Kalinin
Assignee: Alexander Kalinin


Add checkbox with "Show message" and remeber last input text.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3222: IGNITE-7197 Avoid NPE in serviced() by waiting on...

[alamar]

Github user alamar closed the pull request at:

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


---

[GitHub] ignite pull request #3255: Ignite gg 12015

[alamar]

GitHub user alamar opened a pull request:

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

Ignite gg 12015

IGNITE-7197 Avoid NPE in services() by waiting on latch=

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

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

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

https://github.com/apache/ignite/pull/3255.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 #3255


commit 03e507f5021f3aee9728e5cbcbc85ed731e5e538
Author: Andrey V. Mashenkov 
Date:   2017-06-26T16:37:27Z

Fixed tests.

commit 17b7586a73f6b1179612d601caa38d41924a4fac
Author: Andrey V. Mashenkov 
Date:   2017-06-26T16:38:39Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit ad6add47b29caf44dadfe2e32acd4d245ee256ab
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Fixed tests.

commit 527c71805ac502290a20c631c8d4484f011f77c2
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:57:56Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit 897f4c00c4945eda3f9f4a41d064ded2f6f27ccc
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

commit 90e96db22dbb7a341bfe1a8130b6dc16d5d8ae81
Author: agura 
Date:   2017-06-27T11:43:06Z

Compilation is fixed.

commit 3f33a902ed0d0a3e27be548209fe8e7933da57a9
Author: Andrey V. Mashenkov 
Date:   2017-06-26T09:27:58Z

Minor fix for GG-12197 "Ignore events for discarded update in CLOCK mode".

commit 3668b91817c1da7958cc3d7c4dddf890a2237772
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Partially reverted GG-12352.

commit 172f41c489c0ca5b7613163cd325b0c01d5b28b1
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

(cherry picked from commit 897f4c0)

commit 0521b7780756788d92bfa35ef00f56b5bb01367d
Author: Andrey V. Mashenkov 
Date:   2017-06-27T17:43:07Z

GG-12370: Fixed massive NODE_FAILED events lead to excessive momentary 
memory consumption.

commit 6abe5bf5bd732bf9f79df577e159243520dd5c0b
Author: Andrey V. Mashenkov 
Date:   2017-06-28T06:47:45Z

Fixed compilation.

commit 6b54f991c13efb3630527a3010c4f90105a4fc76
Author: agura 
Date:   2017-06-21T16:09:37Z

ignite-5574 For offheap_tiered cache first try read value from offheap in 
order to avoid redundant synchronization on entry

commit 7d5217260b293b7224340349b5e44792999600f3
Author: Andrey V. Mashenkov 
Date:   2017-06-28T08:47:21Z

Rethrow handshake exceptions as it done for ConnectionException.

commit 81cdea40743131cac9dae49150c1038073595f7e
Author: Andrey V. Mashenkov 
Date:   2017-06-28T10:00:30Z

Fixed tests.

commit 473abcafca568c7c898b0b1ae91fe964084fdf43
Author: agura 
Date:   2017-06-28T11:49:49Z

Tests fixed

commit 4f383ae772631987c3f4ac29bb654b4811fbc407
Author: agura 
Date:   2017-06-28T11:49:49Z

Tests fixed.

commit 4b11bb27d5caeb7ba7bc2929685d7c548f4c327d
Author: Andrey V. Mashenkov 
Date:   2017-06-28T12:45:42Z

Tests fixed.

commit 9b92dac5756619ed5218db269acdae1ef02ef8ae
Author: Andrey V. Mashenkov 
Date:   2017-06-28T15:20:02Z

Tests fixed.

commit 0295a1a7ecb2ef57a917ddc9015ff8b71a6ddb14
Author: mcherkasov 
Date:   2017-06-23T18:00:45Z

IGNITE-5521: Large near caches lead to cluster instability with metrics 
enabled.

commit 16fed552fc8f91de550207eeebd5850e685960a8
Author: AMRepo 
Date:   2017-06-29T07:49:34Z

Fix tests.

commit 65d93e48c264f4bfff0a94856fdfeb83375a3976
Author: mcherkasov 
Date:   2017-06-23T18:00:45Z

IGNITE-5521: Large near caches lead to cluster instability with metrics 
enabled

commit ff1afad1278e939aef71b274e959fd4256904971
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Partially reverted GG-12352.

(cherry picked from commit 3668b91)

commit 7fbb95d1698c534957c9f0b7c5558f43985cfe68
Author: Andrey V. Mashenkov 
Date:   2017-06-27T17:43:07Z

GG-12370: Fixed massive NODE_FAILED events lead to excessive momentary 
memory consumption.

(cherry picked from commit 0521b77)

commit 710db327c027d43c0984b7007447cecca71f3cca
Author: Andrey V. Mashenkov 
Date:   2017-06-28T08:47:21Z

Rethrow handshake exceptions as it done for ConnectionException.

(cherry picked from commit 7d52172)

commit 7c619f77009cc6876405839f9f6201d332d94b47
Author: Andrey V. Mashenkov 
Date:   2017-06-28T12:45:42Z

Fixed tests.

(cherry picked from commit 81cdea4)

commit a3717b0cc6d716e3bc966248854334e74b0614e2
Author: Andrey V. Mashenkov 
Date:   2017-06-29T10:06:06Z

Merge remote-tracking branch 'origin/ignite-1.7.12' into ignite-1.7.12

commit 7d41f5da867294befd6cca1de3c945bfd83ae597
Author: Andrey V. Mashenkov 
Date:   2017-06-29T10:15:57Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit 5219a35208b95

[jira] [Created] (IGNITE-7257) Web console: fix reconnection after change profile

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-7257:


 Summary: Web console: fix reconnection after change profile
 Key: IGNITE-7257
 URL: https://issues.apache.org/jira/browse/IGNITE-7257
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7258) BinaryMetadata may be lost if node with outdated metadata becomes a coordinator

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7258:
---

 Summary: BinaryMetadata may be lost if node with outdated metadata 
becomes a coordinator
 Key: IGNITE-7258
 URL: https://issues.apache.org/jira/browse/IGNITE-7258
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Critical
 Fix For: 2.4


Consider the following scenario in PDS-enabled mode:

# Multinode cluster is up and running, BinaryMetadata for some type is created 
and spread across all nodes.
# Node#1 leaves the cluster, then BinaryMetadata is updated one more time.
# All cluster is restarted *and Node#1 becomes a coordinator*.

As in current implementation coordinator is considered to own a master copy of 
BinaryMetadata, it spreads its out-of-date version to all nodes so update from 
step#2 is lost.

We need to improve BinaryMetadata exchange protocol so nodes on join will send 
their version of BinaryMetadata to coordinator so it is able to update its own 
local version.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7259) GridIndexRebuildSelfTest hangs

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7259:
---

 Summary: GridIndexRebuildSelfTest hangs
 Key: IGNITE-7259
 URL: https://issues.apache.org/jira/browse/IGNITE-7259
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Alexander Paschenko
 Fix For: 2.5






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3256: IGNITE-5623: add support for DEFAULT value on CRE...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5623: add support for DEFAULT value on CREATE TABLE



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

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

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

https://github.com/apache/ignite/pull/3256.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 #3256


commit fe658c09727ad7c65bdc2f913c4d33e9f0678613
Author: tledkov-gridgain 
Date:   2017-12-18T09:47:15Z

IGNITE-5623: add support for DEFAULT value on CREATE TABLE




---

[jira] [Created] (IGNITE-7260) DDL needs to support DEFAULT value for ADD COLUMN operation

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-7260:


 Summary: DDL needs to support DEFAULT value for ADD COLUMN 
operation
 Key: IGNITE-7260
 URL: https://issues.apache.org/jira/browse/IGNITE-7260
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.3
Reporter: Taras Ledkov


Constants default value support is added for {{CREATE TABLE}} operation on 
IGNITE-5623.
We have support also:
{{ALTER TABLE  ADD COLUMNDEFAULT }}

NB: all entries already exist in cache must be modified with default value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3257: IGNITE-6803 UriDeployment, find resources fix.

[zstan]

GitHub user zstan opened a pull request:

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

IGNITE-6803 UriDeployment, find resources fix.



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

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

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

https://github.com/apache/ignite/pull/3257.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 #3257


commit 7c7452ec241815d3363448b30dd771d9084ae6ce
Author: Evgeny Stanilovskiy 
Date:   2017-12-20T11:05:14Z

IGNITE-6803 UriDeployment, find resources fix.




---

Re: Time and scope for Apache Ignite 2.4

[Andrey Kuznetsov]

Hi Denis,

As for memory metrics, I'm fixing minor bugs now, and then we'll need some
time for review.

2017-12-19 23:07 GMT+03:00 Denis Magda :

> Igniters,
>
> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#
> ApacheIgnite2.4-RequiredTickets  confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-
> RequiredTickets>
>
> How good are we if to assume 5th of Jan as a code freeze date? Please
> comment:
> - Nikolay Izhikov: Data Frames.
> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
> - Yuri: Machine Learning + neural networks
> - Vladimir Ozerov: Java 9 and Java 7
> - Sergey Kozlov: SQL scope testing
> - etc.: please check the link with the features.
>
> —
> Denis
>
> --
Best regards,
  Andrey Kuznetsov.

[GitHub] ignite pull request #3207: IGNITE-7143: Fixed Decimal serialization issue

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3258: IGNITE-5949: Added limited support for DDL ALTER ...

[skalashnikov]

GitHub user skalashnikov opened a pull request:

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

IGNITE-5949: Added limited support for DDL ALTER TABLE DROP COLUMN



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

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

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

https://github.com/apache/ignite/pull/3258.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 #3258


commit 0b438d9dc1887f2d6ed34aca6fef044edfea2c59
Author: skalashnikov 
Date:   2017-12-20T11:53:44Z

IGNITE-5949: Added limited support for DDL ALTER TABLE DROP COLUMN




---

[GitHub] ignite pull request #3259: Ignite gg 12015m1

[alamar]

GitHub user alamar opened a pull request:

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

Ignite gg 12015m1

IGNITE-7197 Avoid NPE in services() by waiting on latch

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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12015m1

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

https://github.com/apache/ignite/pull/3259.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 #3259


commit dd9c3a81d5ff53bdd88dd83e8f03480912cfbd58
Author: tledkov-gridgain 
Date:   2017-09-15T14:25:26Z

IGNITE-6395: Remove old test. This closes #2673.

commit b6350366fef2a75e9d4eeba9392aec660c0dda0b
Author: devozerov 
Date:   2017-09-16T11:57:55Z

IGNITE-6327: Added thin client configuration. This closes #2672.

commit ecdb3ea74b1d5444c53a043f52e851c840fc7e7b
Author: Alexander Paschenko 
Date:   2017-09-16T14:41:34Z

IGNITE-5620: Implemented SQLSTATE error code for server-side logic and JDBC 
thin client. This closes #2541.

commit d347c2c00b6084c26c640793ea8ba08114022d07
Author: vsisko 
Date:   2017-09-18T07:09:22Z

IGNITE-6417 Fixed missed binary configuration.
(cherry picked from commit 40597a0)

commit 0a878ece75d2b69be92caac0bacb9a7ba866e522
Author: Ilya Kasnacheev 
Date:   2017-09-07T13:41:44Z

Fixed Licenses & Javadoc tests

cherry-pick from aa172573364b3fd91b089df252d884ee9aa8c24f

commit 9f2426ece7a3aab8701902505774627b096ad6e2
Author: Pavel Tupitsyn 
Date:   2017-09-18T09:57:26Z

IGNITE-6404 Fix failures in .NET (NPE in ExceptionUtils, inspections)

commit a2d9d76cbce8658ec42e951432a0e92ee22f46b5
Author: devozerov 
Date:   2017-09-18T10:36:38Z

IGNITE-6413: Improved thin client configuration processing. This closes 
#2680.

commit 9edcd5f7ca5609860b77a8bbb049ad5e805ad967
Author: Sergey Kalashnikov 
Date:   2017-09-18T11:54:40Z

IGNITE-6396: JDBC thin driver: added test for error code for NOT NULL 
violation. This closes #2681.

commit ea2caeb834a100448784c28d49b8d6aca4b3ed51
Author: Alexandr Kuramshin 
Date:   2017-09-18T12:46:46Z

IGNITE-6200 org.dom4j.QName can't be serialized

Signed-off-by: Andrey Gura 

commit bda0b7ce310a24600583869f491326808f07d8bd
Author: tledkov-gridgain 
Date:   2017-09-18T13:01:34Z

IGNITE-6317: JDBC driver: SQLSTATE support. This closes #2682.

commit b74744a0f57cda09bea4c8b303fd7aecbf5e1142
Author: Vitaliy Biryukov 
Date:   2017-09-18T14:15:36Z

ignite-5865 Deadlock detection test for optimistic transactions is fixed

Signed-off-by: Andrey Gura 

commit cde331bf0ebd38993a8720ae0e8e03a26af195fa
Author: dpavlov 
Date:   2017-09-18T15:55:48Z

IGNITE-6427: IgniteOOME in Cache5 test: Increase memory policy size

commit ec4a2229a64e5958ea843704f3c6df88b86a57cb
Author: dpavlov 
Date:   2017-09-15T11:47:03Z

IGNITE-6235 Added ability to handle CacheObject from DataRecord in 
standalone WAL iterator - Fixes #2620.

Signed-off-by: Alexey Goncharuk 

commit a85a67302195351003300838498f8ae90fc40919
Author: Alexey Goncharuk 
Date:   2017-09-18T16:04:36Z

IGNITE-6235 Added ability to handle CacheObject from DataRecord in 
standalone WAL iterator. Fixed compilation

commit f64691636240f026bea929404c15ac1a74f2d8fd
Author: Andrey V. Mashenkov 
Date:   2017-09-18T17:47:47Z

ignite-5839 Fix BinaryObject builder reuse issue.

Signed-off-by: Andrey Gura 

commit 986cf58b724e2c6ba8d76c3fa4f793e369eb6b70
Author: tledkov-gridgain 
Date:   2017-09-18T18:37:35Z

IGNITE-6391: Converted protocol version to local variable in JdbcThinTcpIo. 
This closes #2684.

commit 65d46144bd51583adc9bfa1a5da8bfa8de86aee1
Author: devozerov 
Date:   2017-09-18T20:10:45Z

IGNITE-6403: Fixed a bug causing to early completion of DDL operations on 
client node. This closes #2688. This closes #2691.

commit 2054430bb65c19a4246f234495c9d27fa50c52e5
Author: Dmitriy Govorukhin 
Date:   2017-09-18T14:02:14Z

IGNITE-6210 Fixed inefficient memory consumption by checkpoint buffer.

commit 6393d39454432c9413e19202cff14e38200fb565
Author: Dmitriy Govorukhin 
Date:   2017-09-19T07:46:27Z

IGNITE-6014 Added TX marker records.

commit 7c1b020705f4ea7cbcd050cc3756790c2e8f3169
Author: voipp 
Date:   2017-09-19T08:52:50Z

IGNITE-4931 Fixed cluster deactivation tests - Fixes #2648.

Signed-off-by: Alexey Goncharuk 

commit 8b765b2a7167ec35c4bb0c9b9189ecbcb5560c90
Author: Pavel Tupitsyn 
Date:   2017-09-19T09:09:18Z

IGNITE-6244 .NET: Thin client: ScanQuery

This closes #2693

commit de7d373fedc270344cff9763d7834bf28d97f04d
Author: Pavel Tupitsyn 
Date:   2017-09-19T10:20:25Z

IGNITE-5884 Change default pageSize of page memory to 4KB - fix .NET

commit 6c416d50b0a24f9e3f66e436f6b581b2f70bdc76
Author: Ilya Kasnacheev 
Date:   2017-09-07T13:41:44Z

Fixed Licenses & Javadoc tests.

Signed

[GitHub] ignite pull request #3260: IGNITE-7197 Avoid NPE in services() by waiting on...

[alamar]

GitHub user alamar opened a pull request:

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

 IGNITE-7197 Avoid NPE in services() by waiting on latch 



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12015m3

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

https://github.com/apache/ignite/pull/3260.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 #3260


commit be91bbf8bcb7e9c71fe6d3bea0f79763f9606558
Author: Krzysztof Chmielewski 
Date:   2017-10-10T14:50:59Z

Fixed "IGNITE-6234 Initialize schemaIds to empty set if schemas field is 
null during the deserialization".

Signed-off-by: nikolay_tikhonov 

commit 08389601728512dc4e7fa5b953f5afe34ae4506f
Author: AMRepo 
Date:   2017-10-10T08:57:20Z

IGNITE-6545: Failure during Ignite Service.cancel() can break normal 
shutdown process. This closes #2807.

(cherry picked from commit 8ffa109)

commit 57547b5afae059a0a6dfa13c08b2e0b6c0e96ebd
Author: devozerov 
Date:   2017-10-13T09:34:35Z

Merge branch 'ignite-2.3.1' into ignite-2.3.2

commit 08798f8e47bdfdd68a557385ed2ce98b4bb1609a
Author: devozerov 
Date:   2017-10-13T11:12:44Z

IGNITE-6605: SQL: common backup filter. This closes #2836.

commit 2b59a241de3935a338842b8fc3221aedc8e11e1d
Author: devozerov 
Date:   2017-10-16T07:33:36Z

IGNITE-6631: Minor improvements to GridH2KeyValueRowOnheap. This closes 
#2855.

commit 98438c954c5f9a08634cf3132361268456397864
Author: devozerov 
Date:   2017-10-16T09:38:54Z

IGNITE-6632: SQL: simplified GridH2Row inheritance tree. This closes #2856.

commit 95b7ab518dd3c3db6fcc5142c2ee85da2516c2b6
Author: devozerov 
Date:   2017-10-16T10:37:11Z

IGNITE-6634: Removed IgniteDistributedJoinTestSuite. It's tests are 
distributed between "Query" and "Query 2" suites. This closes #2857.

commit 9c91deff877ebc0eed84559d4abca71408e3cb0a
Author: devozerov 
Date:   2017-10-16T13:46:13Z

Merge branch 'ignite-2.3.1' into ignite-2.3.2

commit 911ab7ab7a8a6968d219b053adb2338477738506
Author: Alexey Popov 
Date:   2017-10-17T11:45:42Z

IGNITE-6627 .NET: Fix serialization of enums within generic collections

* Fix EnumEqualityComparer serialization
* Fix enum arrays serialization
* Fix empty objects missing metadata

This closes #2864

commit 3ba374c319ac7048a05871692060e2f143d6acdf
Author: Alexey Kuznetsov 
Date:   2017-10-06T17:11:37Z

IGNITE-6463 Web Console: Fixed output of big numbers in SQL query results.
(cherry picked from commit 35589a7)

commit b67feb0f175bfbd6ffbefe82a8d693c8ab7d4213
Author: Vasiliy Sisko 
Date:   2017-10-09T10:55:23Z

IGNITE-5767 Web console: Use byte array type instead of java.lang.Object 
for binary JDBC types.
(cherry picked from commit 3184437)

commit 8e1560322b87d79b3d3250832a3969ac4032d6fc
Author: Alexey Kuznetsov 
Date:   2017-10-06T18:10:08Z

IGNITE-6574 Remove pending requests in case STATUS_AUTH_FAILURE && 
credentials == null.
(cherry picked from commit 85261a3)

commit 7a0300ae35894c389b126e95615f720a99a3d360
Author: devozerov 
Date:   2017-10-18T11:18:08Z

Merge branch 'ignite-2.3.1' into ignite-2.3.2

commit ad01f9b099d0bf92537378859ad6d5a52de57748
Author: Alexey Kuznetsov 
Date:   2017-10-19T02:43:20Z

IGNITE-6647 Web Console: Implemented support of schema migration scripts.
(cherry picked from commit c65399c)

commit 0c66344bc752dac98b256dd140fcab95d1662862
Author: Pavel Tupitsyn 
Date:   2017-10-19T09:36:39Z

IGNITE-6627 .NET: Fix repeated known metadata updates

This closes #2876

commit 1b8abd214ed2afcd3fd1f6a4c71a19d6fe1a4b01
Author: Alexey Kuznetsov 
Date:   2017-10-20T04:23:23Z

IGNITE-6647 Added missing Mongo injector.
(cherry picked from commit 173ecef)

commit a221066b3d029afc392be704a810c0e830fc0c49
Author: Alexey Kuznetsov 
Date:   2017-10-20T14:15:02Z

IGNITE-6647 Web Console: Added folder for modules migrations.
(cherry picked from commit 3700717)

commit da8a9d5a968ba071697a28adb01bc59f80d1893c
Author: Pavel Tupitsyn 
Date:   2017-10-23T08:55:33Z

Merge branch 'ignite-2.3.1' into ignite-2.3.2

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Apache.Ignite.Core.Tests.csproj

commit 69fdac3acf768ecb9df80d4412c4de5ffd5bc4f5
Author: Dmitriy Shabalin 
Date:   2017-10-23T09:09:47Z

IGNITE-5909 Added list editable component.
(cherry picked from commit 01daee6)

commit 4a2c38333c112d4956d6394667672c1470503435
Author: apopov 
Date:   2017-10-24T08:56:33Z

IGNITE-6362 NPE in Log4J2Logger

commit 089ebecb3e5962c7a38afd01bd18c77feb23d155
Author: vsisko 
Date:   2017-10-25T04:23:11Z

IGNITE-6671 Web Agent: Fixed data type conversion for Oracle NUMBER(N) data 
types.
(cherry picked from commit 93be8ea)

commit 1e56de86525a79c895eba2d839b

[jira] [Created] (IGNITE-7261) SQL TX: SELECT and DML operations must share the same MVCC version

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7261:
---

 Summary: SQL TX: SELECT and DML operations must share the same 
MVCC version
 Key: IGNITE-7261
 URL: https://issues.apache.org/jira/browse/IGNITE-7261
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Igor Seliverstov
 Fix For: 2.5


Need to make sure that all statements within TX share the same MVCC version 
which is assigned on first read/write. 
Need to add tests for this to confirm REPEATABLE_READ behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3261: Ignite 5804 ScanQuery transformer applies to firs...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

Ignite 5804 ScanQuery transformer applies to first results page only.



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

$ git pull https://github.com/sk0x50/ignite ignite-gg-13232

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

https://github.com/apache/ignite/pull/3261.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 #3261


commit 17b7586a73f6b1179612d601caa38d41924a4fac
Author: Andrey V. Mashenkov 
Date:   2017-06-26T16:38:39Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit ad6add47b29caf44dadfe2e32acd4d245ee256ab
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Fixed tests.

commit 527c71805ac502290a20c631c8d4484f011f77c2
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:57:56Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit 897f4c00c4945eda3f9f4a41d064ded2f6f27ccc
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

commit 90e96db22dbb7a341bfe1a8130b6dc16d5d8ae81
Author: agura 
Date:   2017-06-27T11:43:06Z

Compilation is fixed.

commit 3f33a902ed0d0a3e27be548209fe8e7933da57a9
Author: Andrey V. Mashenkov 
Date:   2017-06-26T09:27:58Z

Minor fix for GG-12197 "Ignore events for discarded update in CLOCK mode".

commit 3668b91817c1da7958cc3d7c4dddf890a2237772
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Partially reverted GG-12352.

commit 172f41c489c0ca5b7613163cd325b0c01d5b28b1
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

(cherry picked from commit 897f4c0)

commit 0521b7780756788d92bfa35ef00f56b5bb01367d
Author: Andrey V. Mashenkov 
Date:   2017-06-27T17:43:07Z

GG-12370: Fixed massive NODE_FAILED events lead to excessive momentary 
memory consumption.

commit 6abe5bf5bd732bf9f79df577e159243520dd5c0b
Author: Andrey V. Mashenkov 
Date:   2017-06-28T06:47:45Z

Fixed compilation.

commit 6b54f991c13efb3630527a3010c4f90105a4fc76
Author: agura 
Date:   2017-06-21T16:09:37Z

ignite-5574 For offheap_tiered cache first try read value from offheap in 
order to avoid redundant synchronization on entry

commit 7d5217260b293b7224340349b5e44792999600f3
Author: Andrey V. Mashenkov 
Date:   2017-06-28T08:47:21Z

Rethrow handshake exceptions as it done for ConnectionException.

commit 81cdea40743131cac9dae49150c1038073595f7e
Author: Andrey V. Mashenkov 
Date:   2017-06-28T10:00:30Z

Fixed tests.

commit 473abcafca568c7c898b0b1ae91fe964084fdf43
Author: agura 
Date:   2017-06-28T11:49:49Z

Tests fixed

commit 4f383ae772631987c3f4ac29bb654b4811fbc407
Author: agura 
Date:   2017-06-28T11:49:49Z

Tests fixed.

commit 4b11bb27d5caeb7ba7bc2929685d7c548f4c327d
Author: Andrey V. Mashenkov 
Date:   2017-06-28T12:45:42Z

Tests fixed.

commit 9b92dac5756619ed5218db269acdae1ef02ef8ae
Author: Andrey V. Mashenkov 
Date:   2017-06-28T15:20:02Z

Tests fixed.

commit 0295a1a7ecb2ef57a917ddc9015ff8b71a6ddb14
Author: mcherkasov 
Date:   2017-06-23T18:00:45Z

IGNITE-5521: Large near caches lead to cluster instability with metrics 
enabled.

commit 16fed552fc8f91de550207eeebd5850e685960a8
Author: AMRepo 
Date:   2017-06-29T07:49:34Z

Fix tests.

commit 65d93e48c264f4bfff0a94856fdfeb83375a3976
Author: mcherkasov 
Date:   2017-06-23T18:00:45Z

IGNITE-5521: Large near caches lead to cluster instability with metrics 
enabled

commit ff1afad1278e939aef71b274e959fd4256904971
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Partially reverted GG-12352.

(cherry picked from commit 3668b91)

commit 7fbb95d1698c534957c9f0b7c5558f43985cfe68
Author: Andrey V. Mashenkov 
Date:   2017-06-27T17:43:07Z

GG-12370: Fixed massive NODE_FAILED events lead to excessive momentary 
memory consumption.

(cherry picked from commit 0521b77)

commit 710db327c027d43c0984b7007447cecca71f3cca
Author: Andrey V. Mashenkov 
Date:   2017-06-28T08:47:21Z

Rethrow handshake exceptions as it done for ConnectionException.

(cherry picked from commit 7d52172)

commit 7c619f77009cc6876405839f9f6201d332d94b47
Author: Andrey V. Mashenkov 
Date:   2017-06-28T12:45:42Z

Fixed tests.

(cherry picked from commit 81cdea4)

commit a3717b0cc6d716e3bc966248854334e74b0614e2
Author: Andrey V. Mashenkov 
Date:   2017-06-29T10:06:06Z

Merge remote-tracking branch 'origin/ignite-1.7.12' into ignite-1.7.12

commit 7d41f5da867294befd6cca1de3c945bfd83ae597
Author: Andrey V. Mashenkov 
Date:   2017-06-29T10:15:57Z

Merge branch 'ignite-1.8.8' into ignite-1.9.4

commit 5219a35208b95a2d7dea3825dd4cb4edc74b3542
Author: Slava Koptilin 
Date:   2017-06-26T12:37:26Z

IGNITE-5076: improved multi-threaded start of node

[jira] [Created] (IGNITE-7262) Most of clients get stuck with "Failed to wait for partition map ..." during load test with 500 logical caches

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-7262:
---

 Summary: Most of clients get stuck with "Failed to wait for 
partition map ..." during load test with 500 logical caches
 Key: IGNITE-7262
 URL: https://issues.apache.org/jira/browse/IGNITE-7262
 Project: Ignite
  Issue Type: Bug
Reporter: Ksenia Rybakova


Load config:




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7263) Daemon-mode Ignite node should not open&listen client port (10800)

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-7263:


 Summary: Daemon-mode Ignite node should not open&listen client 
port (10800)
 Key: IGNITE-7263
 URL: https://issues.apache.org/jira/browse/IGNITE-7263
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 2.1
Reporter: Alexey Popov
Priority: Minor


When I run a Visor console with default configuration file it opens a default 
port (10800) for ODBC driver connection (and for thin JDBC, and for new "thin" 
client).
Then I run several Ignite nodes.

So after that, the ODBC driver with default settings goes directly to a Visor 
(daemon-mode Ignite) and does not able to get any data (daemon-mode Ignite does 
not keep any data)
It is better to avoid such situation.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7264) Caches with forward slash "/" in names cause problems for PDS

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-7264:
---

 Summary: Caches with forward slash "/" in names cause problems for 
PDS
 Key: IGNITE-7264
 URL: https://issues.apache.org/jira/browse/IGNITE-7264
 Project: Ignite
  Issue Type: Bug
  Components: cache, persistence
Affects Versions: 2.3
Reporter: Ilya Kasnacheev


If I am to create cache with name "caches/1", there's no immediate error, but 
nodes fail when trying to rejoin topology with storage already initialized.

I think there should be an immediate exception in case persistence is enabled 
for such case.

Moreover, I suggest first trying to create directory, then making sure it was 
created and that dir.parent == expected parent directory. Because on Windows 
there are more restrictions on FS file names, etc...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7265) BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7265:
---

 Summary: BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails
 Key: IGNITE-7265
 URL: https://issues.apache.org/jira/browse/IGNITE-7265
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
 Fix For: 2.5


{code}
java.lang.AssertionError: Assertion error on row: 26

at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2221)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.put(BPlusTree.java:2156)
at 
org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.iterateConcurrentPutRemove(BPlusTreeSelfTest.java:2202)
at 
org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.testIterateConcurrentPutRemove_1(BPlusTreeSelfTest.java:2169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2008)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1923)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.AssertionError: 27
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.setLevelsCount(BPlusMetaIO.java:98)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.addRoot(BPlusMetaIO.java:155)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:661)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:650)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:241)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$10500(BPlusTree.java:82)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertWithSplit(BPlusTree.java:3073)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:2949)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:2831)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:420)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:401)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5153)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5138)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:342)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:261)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$11100(BPlusTree.java:82)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3143)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7500(BPlusTree.java:2831)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2464)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2185)
... 12 more
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3262: Ignite-1.7.18

[asfedotov]

GitHub user asfedotov opened a pull request:

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

Ignite-1.7.18

CI

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

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

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

https://github.com/apache/ignite/pull/3262.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 #3262


commit f2dc1d71705b86428a04a69c4f2d4ee3a82ed1bd
Author: sboikov 
Date:   2016-11-21T15:12:27Z

Merged ignite-1.6.11 into ignite-1.7.4.

commit d32fa21b673814b060d2362f06ff44838e9c2cdc
Author: sboikov 
Date:   2016-11-22T08:33:55Z

IGNITE-3075 Fixed condition for 'single' request creation

commit d15eba4becf7515b512c1032b193ce75e1589177
Author: Anton Vinogradov 
Date:   2016-11-22T08:56:20Z

IGNITE-4225 DataStreamer can hang on changing topology

commit f80bfbd19e7870554bf3abd13bde89b0f39aaee1
Author: Anton Vinogradov 
Date:   2016-11-22T09:02:57Z

IGNITE-3748 Data rebalancing of large cache can hang out.

commit bc695f8e3306c6d74d4fe53d9a98adedd43ad8f0
Author: Igor Sapego 
Date:   2016-11-22T09:05:15Z

IGNITE-4227: ODBC: Implemented SQLError. This closes #1237.

commit fc9ee6a74fe0bf413ab0643d2776a1a43e6dd5d2
Author: devozerov 
Date:   2016-11-22T09:05:32Z

Merge remote-tracking branch 'upstream/ignite-1.7.4' into ignite-1.7.4

commit 861fab9d0598ca2f06c4a6f293bf2866af31967c
Author: tledkov-gridgain 
Date:   2016-11-22T09:52:03Z

IGNITE-4239: add GridInternal annotaion for tasks instead of jobs. This 
closes #1250.

commit ba99df1554fbd1de2b2367b6ce011a024cd199bd
Author: tledkov-gridgain 
Date:   2016-11-22T10:07:20Z

IGNITE-4239: test cleanup

commit c34d27423a0c45c61341c1fcb3f56727fb91498f
Author: Igor Sapego 
Date:   2016-11-22T11:13:28Z

IGNITE-4100: Fix for DEVNOTES paths.

commit 9d82f2ca06fa6069c1976cc75814874256b24f8c
Author: devozerov 
Date:   2016-11-22T12:05:29Z

IGNITE-4259: Fixed a problem with geospatial indexes and BinaryMarshaller.

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 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 1a2de51f5807a91ce0d5dff28f24ed5bf7abebbc
Author: Konstantin Dudkov 
Date:   2016-11-28T09:59:02Z

IGNITE-4305 marshalling fix

commit c06e4017771603df7118974758d3d6b9cadc41b5
Author: Eduard Shangareev 
Date:   2016-11-30T11:34:47Z

ignite-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations

commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f455

[GitHub] ignite pull request #3263: IGNITE-6615 .NET: Thin client: XML configuration

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-6615 .NET: Thin client: XML configuration



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

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

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

https://github.com/apache/ignite/pull/3263.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 #3263


commit ef418105e0cc4469964f13e4480230be772777aa
Author: Pavel Tupitsyn 
Date:   2017-12-18T15:53:57Z

IGNITE-6615 .NET: Thin client: XML configuration

commit 20550325569336561fd431600e8c81b53e4855d5
Author: Pavel Tupitsyn 
Date:   2017-12-18T15:54:29Z

wip

commit 975e54913bbd3fc09f2e280d12b90f62fca4f1b6
Author: Pavel Tupitsyn 
Date:   2017-12-19T07:26:49Z

Merge branch 'master' into ignite-6615

commit b2392295ac73d03587605f33a3dd5c2b1b901da5
Author: Pavel Tupitsyn 
Date:   2017-12-19T08:13:34Z

fix schema output

commit f57c0aaf5d8ea7a5a26baa3394a8f2a221993c37
Author: Pavel Tupitsyn 
Date:   2017-12-19T09:53:32Z

wip

commit f1b315c4d563b8779392ad96f369902c9477fb18
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:02:24Z

Add startup methods

commit 2244d48c1ac7a1531bc2d47227453d62fb105e50
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:03:17Z

fix docs

commit 39313449ddb8f7938798b562eaa681344d6a6762
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:17:49Z

ToXml / FromXml

commit 707d97dcc6ef17b99ff7b1794d217681fa5fd012
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:19:57Z

wip

commit 286d743fc02cf769b00646deef9c725495a2a79d
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:25:36Z

ToXmlFromXml done

commit d04a06c9716c34257e39da763c96f05b7c929c10
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:26:25Z

wip

commit 66a0f06bdb527fa944c994f54989c6cf12623b07
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:30:02Z

adding tests

commit dd4fdfd5a1644780e60dd4ed0e5ab0e09c83df95
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:31:58Z

wip tests

commit f284472661146b65929e5734f6bd666ce832ec7c
Author: Pavel Tupitsyn 
Date:   2017-12-19T10:37:59Z

wip tests

commit 72f3152978d3e7c6942b4f64ad690e822c33e733
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:00:55Z

wip

commit cf0ae3be5dee6281f044f8de49fe66129439628a
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:08:33Z

Add IIgniteClient.Configuration

commit 073e2450c252d6793d262c5ab7d780233ee2cf6d
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:23:12Z

wip tests

commit 6fedec40b9a00cc3b28b50bb5aba595d58dd6ca4
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:36:08Z

wip

commit b771dd6b0271059d80fa7edf428d5dee8e08aeb3
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:45:19Z

wip tests

commit 2e749e51322f263975359a8db15b466537b55577
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:46:42Z

wip tests

commit 2c5e0959ff3449e1be951472926e6d408e59d7b0
Author: Pavel Tupitsyn 
Date:   2017-12-19T14:54:40Z

wip

commit dc739389af01eec89dcc798dd18474b7a4d75e58
Author: Pavel Tupitsyn 
Date:   2017-12-19T15:01:54Z

wip tests

commit eef2dce5df8caa2e20304d9cc62bf33e12430d86
Author: Pavel Tupitsyn 
Date:   2017-12-19T15:23:15Z

wip tests

commit c59028e9005415a51a23e69f9c88d6363b29dc69
Author: Pavel Tupitsyn 
Date:   2017-12-19T15:51:16Z

wip

commit 30b358e392ac9484e36f799cfe947ac05e5c4337
Author: Pavel Tupitsyn 
Date:   2017-12-19T18:29:09Z

wip tests

commit b41065d424f4910825bc5c2fe70ce339845ca294
Author: Pavel Tupitsyn 
Date:   2017-12-20T07:15:34Z

fix dnc tests

commit 37e2bdebda18d3665db4f3e5d6e18208447c7e42
Author: Pavel Tupitsyn 
Date:   2017-12-20T07:22:30Z

cleanup

commit 9acffa0184a84b45c2d60136e4f169f9baae2cd0
Author: Pavel Tupitsyn 
Date:   2017-12-20T07:46:41Z

wip schema

commit da13aec60c2ba79ac88da7a299ae9ec390093dc0
Author: Pavel Tupitsyn 
Date:   2017-12-20T07:47:33Z

wip

commit bf43c26178cce37f09b23f073f5258409572c227
Author: Pavel Tupitsyn 
Date:   2017-12-20T10:57:19Z

Schema done




---

[GitHub] ignite pull request #3255: Ignite gg 12015

[alamar]

Github user alamar closed the pull request at:

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


---

[GitHub] ignite pull request #3264: IGNITE-7165 Only cancel old rebalance future when...

[alamar]

GitHub user alamar opened a pull request:

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

IGNITE-7165 Only cancel old rebalance future when new rebalance is 
non-trivial.



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

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

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

https://github.com/apache/ignite/pull/3264.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 #3264


commit 2cbf1c5f50bcd301897fd4a1ded681b14e95e795
Author: Ilya Kasnacheev 
Date:   2017-12-20T14:31:16Z

IGNITE-7165 Only cancel old rebalance future when new rebalance is 
non-trivial.




---

[jira] [Created] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7266:
---

 Summary: SQL TX: Joins return duplicated result when MVCC is 
disabled
 Key: IGNITE-7266
 URL: https://issues.apache.org/jira/browse/IGNITE-7266
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Igor Seliverstov
 Fix For: 2.5


Affected tests:
{{IgniteCacheJoinQueryWithAffinityKeyTest}}
{{IgniteCacheCrossCacheJoinRandomTest}}

All tests failed for the same reason: {{expected=X, actual=2*X}}. Looks like we 
return too much results in some cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Transaction classes naming

[Alexey Goncharuk]

Igniters,

As I review transaction-related PRs and communicate with other fellow
Igniters, I realized that our transaction classes naming became
inconsistent and almost impossible to explain to a new contributor. A few
examples:

1) We have a GridNearTxLocal class, but Near in the name does not
necessarily mean that this transaction has to do with the near cache. It
may or may not, depending on the cache configuration. Near in this case
only stands for _originating_ node transaction. This is also reflected in
many messages, such as Near*Request, where near stands for a message sent
from an originating node to the primary node.
2) We have GridNearTxRemote and GridDhtTxRemote classes. First, near here
always means near cache, as near remote transaction will only be created
for near-enabled caches. Second, Remote in the class names stands for
backups (affinity backups or temporarily near-reader backups). On the other
hand, requests sent from primary to backups are named Dht*Request.

All in all, the naming is extremely confusing. For a person who hasn't seen
the evolution of transaction classes over time, it is impossible to infer
or even assume what these classes stand for.

I would like to kick off a discussion on new transaction classes and
messages naming (especially as we started developing MVCC which most likely
will introduce additional TX classes).

How about:
OriginatingTx for transaction created on originating node
PrimaryTx for transaction created on primary nodes, but not the originating
node
BackupTx for transaction created on backup nodes
NearTx for transaction created to update near cache

Thoughts?

Re: Transaction classes naming

[Vladimir Ozerov]

+1

On Wed, Dec 20, 2017 at 6:18 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Igniters,
>
> As I review transaction-related PRs and communicate with other fellow
> Igniters, I realized that our transaction classes naming became
> inconsistent and almost impossible to explain to a new contributor. A few
> examples:
>
> 1) We have a GridNearTxLocal class, but Near in the name does not
> necessarily mean that this transaction has to do with the near cache. It
> may or may not, depending on the cache configuration. Near in this case
> only stands for _originating_ node transaction. This is also reflected in
> many messages, such as Near*Request, where near stands for a message sent
> from an originating node to the primary node.
> 2) We have GridNearTxRemote and GridDhtTxRemote classes. First, near here
> always means near cache, as near remote transaction will only be created
> for near-enabled caches. Second, Remote in the class names stands for
> backups (affinity backups or temporarily near-reader backups). On the other
> hand, requests sent from primary to backups are named Dht*Request.
>
> All in all, the naming is extremely confusing. For a person who hasn't seen
> the evolution of transaction classes over time, it is impossible to infer
> or even assume what these classes stand for.
>
> I would like to kick off a discussion on new transaction classes and
> messages naming (especially as we started developing MVCC which most likely
> will introduce additional TX classes).
>
> How about:
> OriginatingTx for transaction created on originating node
> PrimaryTx for transaction created on primary nodes, but not the originating
> node
> BackupTx for transaction created on backup nodes
> NearTx for transaction created to update near cache
>
> Thoughts?
>

Re: Transaction classes naming

[Ivan Rakov]

As a person who tried to infer transactional behavior from listed 
classes, I completely agree.


Also, I'd like to pay additional attention to:

1) IgniteTxAdapter#near method. It returns true both for GridNearTxLocal 
(where "near" means originating node) and GridNearTxRemote (where "near" 
means near cache). This is extremely confusing, we should rename this 
method as well.


2) GridNear*Request/Response classes (including non-transactional ones). 
They incapsulate requests from originating to primary nodes, so we 
should consider renaming them to GridOriginating*Request/Response.


Best Regards,
Ivan Rakov

On 20.12.2017 18:18, Alexey Goncharuk wrote:

Igniters,

As I review transaction-related PRs and communicate with other fellow
Igniters, I realized that our transaction classes naming became
inconsistent and almost impossible to explain to a new contributor. A few
examples:

1) We have a GridNearTxLocal class, but Near in the name does not
necessarily mean that this transaction has to do with the near cache. It
may or may not, depending on the cache configuration. Near in this case
only stands for _originating_ node transaction. This is also reflected in
many messages, such as Near*Request, where near stands for a message sent
from an originating node to the primary node.
2) We have GridNearTxRemote and GridDhtTxRemote classes. First, near here
always means near cache, as near remote transaction will only be created
for near-enabled caches. Second, Remote in the class names stands for
backups (affinity backups or temporarily near-reader backups). On the other
hand, requests sent from primary to backups are named Dht*Request.

All in all, the naming is extremely confusing. For a person who hasn't seen
the evolution of transaction classes over time, it is impossible to infer
or even assume what these classes stand for.

I would like to kick off a discussion on new transaction classes and
messages naming (especially as we started developing MVCC which most likely
will introduce additional TX classes).

How about:
OriginatingTx for transaction created on originating node
PrimaryTx for transaction created on primary nodes, but not the originating
node
BackupTx for transaction created on backup nodes
NearTx for transaction created to update near cache

Thoughts?

Re: Transaction classes naming

[Andrey Kuznetsov]

Alexey,

And what do you think about 'Adapters' in transaction heirarchy? This term
looks really obfuscating for new contributor, since in fact they are not
adapters for something but abstract superclasses.

2017-12-20 18:18 GMT+03:00 Alexey Goncharuk :

> Igniters,
>
> As I review transaction-related PRs and communicate with other fellow
> Igniters, I realized that our transaction classes naming became
> inconsistent and almost impossible to explain to a new contributor. A few
> examples:
>
> 1) We have a GridNearTxLocal class, but Near in the name does not
> necessarily mean that this transaction has to do with the near cache. It
> may or may not, depending on the cache configuration. Near in this case
> only stands for _originating_ node transaction. This is also reflected in
> many messages, such as Near*Request, where near stands for a message sent
> from an originating node to the primary node.
> 2) We have GridNearTxRemote and GridDhtTxRemote classes. First, near here
> always means near cache, as near remote transaction will only be created
> for near-enabled caches. Second, Remote in the class names stands for
> backups (affinity backups or temporarily near-reader backups). On the other
> hand, requests sent from primary to backups are named Dht*Request.
>
> All in all, the naming is extremely confusing. For a person who hasn't seen
> the evolution of transaction classes over time, it is impossible to infer
> or even assume what these classes stand for.
>
> I would like to kick off a discussion on new transaction classes and
> messages naming (especially as we started developing MVCC which most likely
> will introduce additional TX classes).
>
> How about:
> OriginatingTx for transaction created on originating node
> PrimaryTx for transaction created on primary nodes, but not the originating
> node
> BackupTx for transaction created on backup nodes
> NearTx for transaction created to update near cache
>
> Thoughts?
>



-- 
Best regards,
  Andrey Kuznetsov.

[jira] [Created] (IGNITE-7267) Fix transactional inserts.

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-7267:


 Summary: Fix transactional inserts.
 Key: IGNITE-7267
 URL: https://issues.apache.org/jira/browse/IGNITE-7267
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov
 Fix For: 2.5


Inserts optimisation (IGNITE-4490) breaks transactional inserts. Need to rework 
the feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Transaction classes naming

[Alexey Goncharuk]

Andrey,

Good point. Even though it is not as confusing as near-remote naming, I
agree that this should be fixed as well.

2017-12-20 18:59 GMT+03:00 Andrey Kuznetsov :

> Alexey,
>
> And what do you think about 'Adapters' in transaction heirarchy? This term
> looks really obfuscating for new contributor, since in fact they are not
> adapters for something but abstract superclasses.
>
> 2017-12-20 18:18 GMT+03:00 Alexey Goncharuk :
>
> > Igniters,
> >
> > As I review transaction-related PRs and communicate with other fellow
> > Igniters, I realized that our transaction classes naming became
> > inconsistent and almost impossible to explain to a new contributor. A few
> > examples:
> >
> > 1) We have a GridNearTxLocal class, but Near in the name does not
> > necessarily mean that this transaction has to do with the near cache. It
> > may or may not, depending on the cache configuration. Near in this case
> > only stands for _originating_ node transaction. This is also reflected in
> > many messages, such as Near*Request, where near stands for a message sent
> > from an originating node to the primary node.
> > 2) We have GridNearTxRemote and GridDhtTxRemote classes. First, near here
> > always means near cache, as near remote transaction will only be created
> > for near-enabled caches. Second, Remote in the class names stands for
> > backups (affinity backups or temporarily near-reader backups). On the
> other
> > hand, requests sent from primary to backups are named Dht*Request.
> >
> > All in all, the naming is extremely confusing. For a person who hasn't
> seen
> > the evolution of transaction classes over time, it is impossible to infer
> > or even assume what these classes stand for.
> >
> > I would like to kick off a discussion on new transaction classes and
> > messages naming (especially as we started developing MVCC which most
> likely
> > will introduce additional TX classes).
> >
> > How about:
> > OriginatingTx for transaction created on originating node
> > PrimaryTx for transaction created on primary nodes, but not the
> originating
> > node
> > BackupTx for transaction created on backup nodes
> > NearTx for transaction created to update near cache
> >
> > Thoughts?
> >
>
>
>
> --
> Best regards,
>   Andrey Kuznetsov.
>

Re: Transaction classes naming

[Yakov Zhdanov]

How about we explain it in javadocs and properly document on wiki? Guys, I
would do this at some point when there is no another bigger issue in Ignite
=)

--Yakov

[GitHub] ignite pull request #3265: BinaryMetadata should be merged on coordinator, o...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

BinaryMetadata should be merged on coordinator, otherwise there is a risk 
of data loss



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

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

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

https://github.com/apache/ignite/pull/3265.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 #3265


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

Merge remote-tracking branch 'professional/ignite-2.4.1' into ignite-2.4.1

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

commit edae228c8f55990c15ef3044be987dcb00d6c81a
Author: EdShangGG 
Date:   2017-11-18T10:36:41Z

hack with sleep

commit b5bffc7580a4a8ffbcc06f60c282e73979179578
Author: Ilya Lantukh 
Date:   2017-11-18T12:39:19Z

Fixed Ignite.active(true) returning control too early.

commit 1bcdd76aae78665e2bbd49034fb46a1b91ef8389
Author: Ilya Lantukh 
Date:   2017-11-18T13:33:01Z

Fixed baseline topology changes from client/daemon nodes.

commit e3bbecd9f133251818a4b43afa44f46e66dd0325
Author: Alexey Goncharuk 
Date:   2017-11-18T14:16:39Z

Fix

[jira] [Created] (IGNITE-7268) SQL Tutorials Per Language

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7268:
---

 Summary: SQL Tutorials Per Language
 Key: IGNITE-7268
 URL: https://issues.apache.org/jira/browse/IGNITE-7268
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.5


Create SQL getting started tutorials for major programming languages relying on 
JDBC/ODBC drivers. Have Spanner's tutorials in mind as an example:
https://cloud.google.com/spanner/docs/getting-started/nodejs/

This is an umbrella ticket. Language-specific tutorials will be handled as 
subtasks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7269) .NET: Thin ASP.NET Session State Store Provider

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7269:
--

 Summary: .NET: Thin ASP.NET Session State Store Provider
 Key: IGNITE-7269
 URL: https://issues.apache.org/jira/browse/IGNITE-7269
 Project: Ignite
  Issue Type: New Feature
  Components: platforms, thin client
Reporter: Pavel Tupitsyn


IGNITE-3199 introduced session store provider which works via full .NET API 
that starts JVM in process.

Introduce {{IgniteThinSessionStateStoreProvider}} that uses thin client API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7270) .NET: Thin EntityFramework Second-Level Cache

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7270:
--

 Summary: .NET: Thin EntityFramework Second-Level Cache
 Key: IGNITE-7270
 URL: https://issues.apache.org/jira/browse/IGNITE-7270
 Project: Ignite
  Issue Type: New Feature
  Components: platforms, thin client
Reporter: Pavel Tupitsyn


IGNITE-1915 introduced EF 2nd level cache based on "thick" API.

Introduce {{IgniteThinDbConfiguration}} based on thin client API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Removing "fabric" from Ignite binary package name

[Denis Magda]

Petr, thanks, such a swift turnaround! 

Have you found the one who can asses and review the changes?

Maintainers label might be helpful. Just ping them directly:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers
 



—
Denis

> On Dec 20, 2017, at 12:24 AM, Petr Ivanov  wrote:
> 
> Assigned myself — done the same work while preparing RPM package.
> But for fixing DEVNOTES.txt waiting for review and merge of IGNITE-7107 [1].
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-7107
> 
> 
> 
>> On 19 Dec 2017, at 22:55, Denis Magda  wrote:
>> 
>> All the bids were accepted and the verdict is executed:
>> https://issues.apache.org/jira/browse/IGNITE-7251 
>> 
>> 
>> Who is ready to pick this up?
>> 
>> —
>> Denis
>> 
>>> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov  
>>> wrote:
>>> 
>>> +1б фо шур
>>> 
>>> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov 
>>> wrote:
>>> 
 +1б вуаштшеудн
 
 On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
 valentin.kuliche...@gmail.com> wrote:
 
> +1
> 
> On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
 dsetrak...@apache.org
>> 
> wrote:
> 
>> +1 (completely agree)
>> 
>> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda 
 wrote:
>> 
>>> Igniters,
>>> 
>>> Apache Ignite binary releases still include “fabric” word in their
> names:
>>> https://ignite.apache.org/download.cgi#binaries <
>>> https://ignite.apache.org/download.cgi#binaries>
>>> 
>>> For instance, this is a full name of the previous release -
>>> apache-ignite-fabric-2.3.0-bin.
>>> It’s a little oversight on our side because the project has not been
>>> positioned as a fabric for a while.
>>> 
>>> Proposal! Remove “fabric” from the name and have the binary releases
>> named
>>> as - apache-ignite-{version}-bin.
>>> 
>>> If we’re in consensus then let’s make the change in 2.4.
>>> 
>>> —
>>> Denis
>>> 
>> 
> 
 
>> 
> 

Re: Time and scope for Apache Ignite 2.4

[Denis Magda]

Hi Peter, 

Sorry for confusion, yes, I meant using Java 8 by default in Ignite. Labeled 
the Java 8 ticket with “important” and now it appears in the required tickets 
list:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets

As I see Yuri reviewed the ticket from ML perspective:
https://github.com/apache/ignite/pull/3240 


Do you guys collaborate together making sure the ML build process simplified? 
Do we need to create a sub-task of [1] to make sure it’s not missed?

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


—
Denis

> On Dec 20, 2017, at 12:29 AM, Petr Ivanov  wrote:
> 
> Hi, Denis!
> 
> 
> What about switching to Java 8 by default? [1]
> I guess this task is inseparably connected to Java 7 support drop and Java 9 
> support introducing.
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-7203
> 
> 
> 
>> On 19 Dec 2017, at 23:07, Denis Magda  wrote:
>> 
>> Igniters,
>> 
>> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets
>>  
>> 
>> 
>> How good are we if to assume 5th of Jan as a code freeze date? Please 
>> comment:
>> - Nikolay Izhikov: Data Frames.
>> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
>> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
>> - Yuri: Machine Learning + neural networks
>> - Vladimir Ozerov: Java 9 and Java 7
>> - Sergey Kozlov: SQL scope testing
>> - etc.: please check the link with the features.
>> 
>> —
>> Denis
>>> On Dec 4, 2017, at 1:11 PM, Denis Magda  wrote:
>>> 
>>> Igniters,
>>> 
>>> Basing on the amount of improvements, fixes and features stacked in the 
>>> master branch I think it’s a right time to negotiate the scope and time of 
>>> the next Apache Ignite 2.4 release. I’m ready to step in as a release 
>>> manager if none of the committers wants to try on this role.
>>> 
>>> Here is a release page:
>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 
>>> 
>>> 
>>> Proposed time date: Jan 5 - code freeze -> stabilization and testing -> Jan 
>>> 24 - voting -> Jan 31 release.
>>> 
>>> In my view improvements such Java 9 support and Java 7 discontinuation, 
>>> memory metrics in bytes [1], binary client protocol, etc. needs to get into 
>>> the release. All the features like that are labeled “important” in JIRA. 
>>> Use this label if you are convinced a task has to be release in 2.4.
>>> 
>>> What’s about machine learning, bulk loading [2], internals problems 
>>> resolution [3], metrics [4] related tasks? What goes in 2.4 and what’s 
>>> shifted?
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-6902 
>>> 
>>> [2] 
>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bulk+data+loading+performance+improvements
>>>  
>>> 
>>> [3] 
>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
>>>  
>>> 
>>> [4] 
>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements
>>>  
>>> 
>>> 
>>> —
>>> Denis
>> 
> 

Re: Time and scope for Apache Ignite 2.4

[Denis Magda]

Andrey K., excellent progress! Do you think you will finish the task by the end 
of the year?

Furthermore, I see you are working on Java 9 specific tasks:
https://issues.apache.org/jira/browse/IGNITE-6728 


Is everything alright there? If you need a review try to ping a reviewer 
directly.

—
Denis

> On Dec 20, 2017, at 3:29 AM, Andrey Kuznetsov  wrote:
> 
> Hi Denis,
> 
> As for memory metrics, I'm fixing minor bugs now, and then we'll need some
> time for review.
> 
> 2017-12-19 23:07 GMT+03:00 Denis Magda :
> 
>> Igniters,
>> 
>> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#
>> ApacheIgnite2.4-RequiredTickets > confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-
>> RequiredTickets>
>> 
>> How good are we if to assume 5th of Jan as a code freeze date? Please
>> comment:
>> - Nikolay Izhikov: Data Frames.
>> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
>> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
>> - Yuri: Machine Learning + neural networks
>> - Vladimir Ozerov: Java 9 and Java 7
>> - Sergey Kozlov: SQL scope testing
>> - etc.: please check the link with the features.
>> 
>> —
>> Denis
>> 
>> --
> Best regards,
>  Andrey Kuznetsov.

[jira] [Created] (IGNITE-7271) UPDATE and DELETE statements do not through thin JDBC work in MVCC mode

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7271:
---

 Summary: UPDATE and DELETE statements do not through thin JDBC 
work in MVCC mode
 Key: IGNITE-7271
 URL: https://issues.apache.org/jira/browse/IGNITE-7271
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, sql
Reporter: Vladimir Ozerov
Assignee: Igor Seliverstov
 Fix For: 2.4


See relevant failures JDBC suite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Time and scope for Apache Ignite 2.4

[Andrey Kuznetsov]

Thanks, Denis!

I hope I'll finish the task on memory metrics in a couple of days.

2017-12-20 23:28 GMT+03:00 Denis Magda :

> Andrey K., excellent progress! Do you think you will finish the task by
> the end of the year?
>
> Furthermore, I see you are working on Java 9 specific tasks:
> https://issues.apache.org/jira/browse/IGNITE-6728 <
> https://issues.apache.org/jira/browse/IGNITE-6728>
>
> Is everything alright there? If you need a review try to ping a reviewer
> directly.
>
> —
> Denis
>
> > On Dec 20, 2017, at 3:29 AM, Andrey Kuznetsov  wrote:
> >
> > Hi Denis,
> >
> > As for memory metrics, I'm fixing minor bugs now, and then we'll need
> some
> > time for review.
> >
> > 2017-12-19 23:07 GMT+03:00 Denis Magda :
> >
> >> Igniters,
> >>
> >> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#
> >> ApacheIgnite2.4-RequiredTickets  >> confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-
> >> RequiredTickets>
> >>
> >> How good are we if to assume 5th of Jan as a code freeze date? Please
> >> comment:
> >> - Nikolay Izhikov: Data Frames.
> >> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the
> list.
> >> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
> >> - Yuri: Machine Learning + neural networks
> >> - Vladimir Ozerov: Java 9 and Java 7
> >> - Sergey Kozlov: SQL scope testing
> >> - etc.: please check the link with the features.
> >>
> >> —
> >> Denis
> >>
> >> --
> > Best regards,
> >  Andrey Kuznetsov.
>
>


-- 
Best regards,
  Andrey Kuznetsov.

Re: Time and scope for Apache Ignite 2.4

[Denis Magda]

Please ping me or file a ticket following these rules [1] when this happens so 
that I could update this documentation page:
https://apacheignite.readme.io/docs/memory-metrics

[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document

—
Denis

> On Dec 20, 2017, at 12:56 PM, Andrey Kuznetsov  wrote:
> 
> Thanks, Denis!
> 
> I hope I'll finish the task on memory metrics in a couple of days.
> 
> 2017-12-20 23:28 GMT+03:00 Denis Magda :
> 
>> Andrey K., excellent progress! Do you think you will finish the task by
>> the end of the year?
>> 
>> Furthermore, I see you are working on Java 9 specific tasks:
>> https://issues.apache.org/jira/browse/IGNITE-6728 <
>> https://issues.apache.org/jira/browse/IGNITE-6728>
>> 
>> Is everything alright there? If you need a review try to ping a reviewer
>> directly.
>> 
>> —
>> Denis
>> 
>>> On Dec 20, 2017, at 3:29 AM, Andrey Kuznetsov  wrote:
>>> 
>>> Hi Denis,
>>> 
>>> As for memory metrics, I'm fixing minor bugs now, and then we'll need
>> some
>>> time for review.
>>> 
>>> 2017-12-19 23:07 GMT+03:00 Denis Magda :
>>> 
 Igniters,
 
 It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#
 ApacheIgnite2.4-RequiredTickets 
 
 How good are we if to assume 5th of Jan as a code freeze date? Please
 comment:
 - Nikolay Izhikov: Data Frames.
 - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the
>> list.
 - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
 - Yuri: Machine Learning + neural networks
 - Vladimir Ozerov: Java 9 and Java 7
 - Sergey Kozlov: SQL scope testing
 - etc.: please check the link with the features.
 
 —
 Denis
 
 --
>>> Best regards,
>>> Andrey Kuznetsov.
>> 
>> 
> 
> 
> -- 
> Best regards,
>  Andrey Kuznetsov.

Re: Suppressing "development" warning

[Valentin Kulichenko]

Dmitry,

WARNING_DEV_ONLY actually sounds like a custom *level* name. Unfortunately,
this is not possible because most of the loggers do not support this.

I also don't like having special category for such warnings at least for
these reasons:
- Category does not defines severity of log statement, it defines its
origin (component, piece of code, class, ...).
- Category can have different level statements. WARNING_DEV_ONLY category
will actually allow ERROR or INFO statements.
- Overall, this approach is not in line with typical logger architecture
and therefore can easily confuse our users.

Modern loggers tend to use markers for such tasks [1]. Marker is similar to
level, but it's optional and application can create as many markers as
needed, and then use them for log filtering. I propose to do the following:

   - Add marker support to IgniteLogger interface.
   - Introduce marker for dev only warnings.
   - Loggers that support markers will use them directly (Log4J 2.x,
   Logback, SLF).
   - For other loggers just add a system property to enable/disable dev
   only warnings. Such loggers (e.g. JUL) are not frequently used in large
   production systems anyway, so I think this solution is enough for them.
   Additionally, we can also add option to dynamically enable/disable dev only
   warnings via MBean.

[1]
https://stackoverflow.com/questions/16813032/what-are-markers-in-java-logging-frameworks-and-what-is-a-reason-to-use-them


Thoughts?

-Val

On Mon, Dec 11, 2017 at 4:21 PM, Dmitriy Setrakyan  wrote:

> I actually like the new WARNING_DEV_ONLY category for logging. If we
> provide it in the default logger configuration, then users will not have to
> do anything extra unless they want to change it. Moreover, if it is a
> category, then it can be turned on and off using standard logger
> configuration.
>
> D.
>
> On Mon, Dec 11, 2017 at 3:28 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igniters,
> >
> > We have bunch of warnings in the product which are useful only during
> > development. One of the examples of is "Class ... cannot be serialized
> > using BinaryMarshaller because it either implements Externalizable ...'
> > warning - it is very useful when one is writing code as it warns about
> > possible mistakes and suggest how to fix them, but once implementation is
> > done, it is meaningless. Moreover, in production environments all
> warnings
> > and errors are often automatically monitored, so this introduces an issue
> > of false positive alerts generated by this kind of warnings.
> >
> > I see two possible solutions for this:
> > - Add 'devOnly' flag to IgniteLogger#warning method and ignore them if
> > special system property is set.
> > - Introduce special logger category for such warnings so that user can
> > control if they are logged or not.
> >
> > I think my vote is for the first option as it's more straightforward and
> > doesn't require any additional configuration from a user.
> >
> > Thoughts?
> >
> > -Val
> >
>

[jira] [Created] (IGNITE-7272) SQL TX: incorrect row MVCC version override during CREATE INDEX

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7272:
---

 Summary: SQL TX: incorrect row MVCC version override during CREATE 
INDEX
 Key: IGNITE-7272
 URL: https://issues.apache.org/jira/browse/IGNITE-7272
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
 Fix For: 2.5


Affected tests: {{DynamicIndexServerNodeFIlterBasicSelfTest}} and all siblings.
Root cause: see {{IgniteH2Indexing#dynamicIndexCreate}}

{code}
if (rowDesc.context().mvccEnabled())
row.mvccVersion(1, MVCC_START_CNTR);
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3266: IGNITE-7272

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-7272



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

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

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

https://github.com/apache/ignite/pull/3266.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 #3266


commit f6e982540e65ab17d439dba990794f35616a30dd
Author: sboikov 
Date:   2017-08-30T09:45:40Z

ignite-3478

commit 275a85db5cd6923b36126166ae99b15e876192be
Author: sboikov 
Date:   2017-08-31T07:44:07Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit b7b9089f0102b8cab9942a9c887d93e9f26cc7d2
Author: sboikov 
Date:   2017-08-31T09:00:36Z

disco cache cleanup

commit 855c2d45794c300d41e386b4e6fa40736cc3e40d
Author: sboikov 
Date:   2017-08-31T09:09:58Z

Merge branch 'ignite-3478-1' into ignite-3478

commit 08be7310a93d3ce455215b97cf8ab1a2c3f0ab31
Author: sboikov 
Date:   2017-08-31T09:52:23Z

ignite-3478

commit fce2e31f0fd2f4f6a9944422e40408a0c65cfe90
Author: sboikov 
Date:   2017-09-04T08:13:50Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit d3c049952384750c5543a9f88b383c033ef74096
Author: sboikov 
Date:   2017-09-04T08:52:11Z

ignite-3478

commit e71ce1937a18dd32448e92b1038dc48d4cb6f8ab
Author: sboikov 
Date:   2017-09-04T10:16:03Z

ignite-3478

commit 5fac5b0965e97f8951e16e10ca9229a2e78ddb0c
Author: sboikov 
Date:   2017-09-05T10:16:44Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit 2e0c9c08e046e8d6af1b5358d9053eae999b1fb4
Author: sboikov 
Date:   2017-09-05T11:30:55Z

ignite-3478

commit e1e07ffdf2d711ba3e72f316f5a3970eff27372e
Author: sboikov 
Date:   2017-09-05T11:31:14Z

ignite-3478

commit cbada3934a386668da0b11d4de7d0f58a4d04dfe
Author: sboikov 
Date:   2017-09-05T11:49:49Z

ignite-3484

commit 5a82c68dcd1927bb6fded8b7def38c91ff6e145b
Author: sboikov 
Date:   2017-09-05T11:59:49Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit bc9134c94b7a738dc1664e96ca6eabb059f1c268
Author: sboikov 
Date:   2017-09-05T12:03:39Z

Merge branch 'ignite-3478' into ignite-3484

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/tree/AbstractDataInnerIO.java

commit b4bfcde78825c6517232e49d389bdb5de19f05a9
Author: sboikov 
Date:   2017-09-05T12:27:51Z

ignite-3484

commit 43834aaab9e2c3cd5fdd55289fdc4a9ff8ab6599
Author: sboikov 
Date:   2017-09-05T13:13:00Z

ignite-3478

commit d1b828095713fcadfa260cf94fef01b42a1b12fd
Author: sboikov 
Date:   2017-09-05T13:13:33Z

Merge branch 'ignite-3478' into ignite-3484

commit 6be6779b6336c36cd71eef0a25199a6a877ce6b5
Author: sboikov 
Date:   2017-09-05T13:47:11Z

ignite-3484

commit e3bba83256c1eb53c4b40fbd9ddba47fcf9d58d5
Author: sboikov 
Date:   2017-09-06T07:10:26Z

ignite-3484

commit dd0afb28466094b801506da8afa3601bfaebd853
Author: sboikov 
Date:   2017-09-06T07:30:04Z

ignite-3484

commit 27b87b413348b03986a463551db24b7726321732
Author: sboikov 
Date:   2017-09-06T08:19:18Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit dcaf8801accd6ee089849a82b2ccd558aec81895
Author: sboikov 
Date:   2017-09-06T08:19:30Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java

commit c966451d0bf7059575de92bcfae43d72096ebce4
Author: sboikov 
Date:   2017-09-06T08:27:04Z

Merge branch 'ignite-3478' into ignite-3484

commit 91b9911731a387a3199ddbbc22704bc14af09995
Author: sboikov 
Date:   2017-09-06T09:22:22Z

ignite-3484

commit e40b4d9dcd6fe6c1cd2640bdd7116ca5a08ed781
Author: sboikov 
Date:   2017-09-07T09:12:32Z

ignite-3484

commit 41a1c571e6ba1765941e2f1679dc4ac1582275c4
Author: sboikov 
Date:   2017-09-08T07:55:24Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3484

commit 1626130801dc330bcaf693f46906f6564cce6802
Author: sboikov 
Date:   2017-09-08T08:04:57Z

ignite-3484

commit 91bbb7cd24f38a38e2e65fc3ebf5637572b11b25
Author: sboikov 
Date:   2017-09-08T12:34:52Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-6149

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxPrepareFutureAdapter.java

c

Create cache using thin protocol

[Prachi Garg]

Pavel,

I tried to create a cache with configuration, using the thin protocol.

1. Do I need to provide every configuration as mentioned in the wiki, or I
can just provide a few and the rest can be default?

2. Using the below code:

DataOutputStream out = new DataOutputStream(socket.getOutputStream());

// Message length
writeIntLittleEndian(22, out);

// Op code = OP_CACHE_CREATE_WITH_CONFIGURATION
writeShortLittleEndian(1053, out);

// Request id (can be anything)
long reqId = 1;
writeLongLittleEndian(reqId, out);

// CacheAtomicityMode
writeIntLittleEndian(0, out);

// Backups
writeIntLittleEndian(2, out);

// CacheMode
writeIntLittleEndian(2, out);

// Read result
DataInputStream in = new DataInputStream(socket.getInputStream());

// Response length
final int len = readIntLittleEndian(in);
System.out.println("len: " + len);

// Request id
long resReqId = readLongLittleEndian(in);
System.out.println("resReqId: " + resReqId);

// Success
int statusCode = readIntLittleEndian(in);
System.out.println("status code: " + statusCode);


I get the following error:

[2017-12-20 
16:43:32,800][ERROR][client-connector-#45][ClientListenerNioListener]
Failed to parse client request.
class org.apache.ignite.binary.BinaryObjectException: Not enough data
to read the value [position=22, requiredBytes=4, remainingBytes=0]
at 
org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.ensureEnoughData(BinaryAbstractInputStream.java:305)
at 
org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.readInt(BinaryAbstractInputStream.java:127)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readInt(BinaryReaderExImpl.java:743)
at 
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheConfigurationSerializer.read(ClientCacheConfigurationSerializer.java:125)
at 
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheCreateWithConfigurationRequest.(ClientCacheCreateWithConfigurationRequest.java:45)
at 
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:333)
at 
org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:220)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:119)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Re: Suppressing "development" warning

[Dmitriy Setrakyan]

Sounds good, markers should work.

On Wed, Dec 20, 2017 at 1:00 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Dmitry,
>
> WARNING_DEV_ONLY actually sounds like a custom *level* name. Unfortunately,
> this is not possible because most of the loggers do not support this.
>
> I also don't like having special category for such warnings at least for
> these reasons:
> - Category does not defines severity of log statement, it defines its
> origin (component, piece of code, class, ...).
> - Category can have different level statements. WARNING_DEV_ONLY category
> will actually allow ERROR or INFO statements.
> - Overall, this approach is not in line with typical logger architecture
> and therefore can easily confuse our users.
>
> Modern loggers tend to use markers for such tasks [1]. Marker is similar to
> level, but it's optional and application can create as many markers as
> needed, and then use them for log filtering. I propose to do the following:
>
>- Add marker support to IgniteLogger interface.
>- Introduce marker for dev only warnings.
>- Loggers that support markers will use them directly (Log4J 2.x,
>Logback, SLF).
>- For other loggers just add a system property to enable/disable dev
>only warnings. Such loggers (e.g. JUL) are not frequently used in large
>production systems anyway, so I think this solution is enough for them.
>Additionally, we can also add option to dynamically enable/disable dev
> only
>warnings via MBean.
>
> [1]
> https://stackoverflow.com/questions/16813032/what-are-
> markers-in-java-logging-frameworks-and-what-is-a-reason-to-use-them
>
>
> Thoughts?
>
> -Val
>
> On Mon, Dec 11, 2017 at 4:21 PM, Dmitriy Setrakyan  wrote:
>
> > I actually like the new WARNING_DEV_ONLY category for logging. If we
> > provide it in the default logger configuration, then users will not have
> to
> > do anything extra unless they want to change it. Moreover, if it is a
> > category, then it can be turned on and off using standard logger
> > configuration.
> >
> > D.
> >
> > On Mon, Dec 11, 2017 at 3:28 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Igniters,
> > >
> > > We have bunch of warnings in the product which are useful only during
> > > development. One of the examples of is "Class ... cannot be serialized
> > > using BinaryMarshaller because it either implements Externalizable ...'
> > > warning - it is very useful when one is writing code as it warns about
> > > possible mistakes and suggest how to fix them, but once implementation
> is
> > > done, it is meaningless. Moreover, in production environments all
> > warnings
> > > and errors are often automatically monitored, so this introduces an
> issue
> > > of false positive alerts generated by this kind of warnings.
> > >
> > > I see two possible solutions for this:
> > > - Add 'devOnly' flag to IgniteLogger#warning method and ignore them if
> > > special system property is set.
> > > - Introduce special logger category for such warnings so that user can
> > > control if they are logged or not.
> > >
> > > I think my vote is for the first option as it's more straightforward
> and
> > > doesn't require any additional configuration from a user.
> > >
> > > Thoughts?
> > >
> > > -Val
> > >
> >
>

Re: Transaction classes naming

[Dmitriy Setrakyan]

Will this renaming introduce any issues with supporting previous versions?

On Wed, Dec 20, 2017 at 9:10 AM, Yakov Zhdanov  wrote:

> How about we explain it in javadocs and properly document on wiki? Guys, I
> would do this at some point when there is no another bigger issue in Ignite
> =)
>
> --Yakov
>

[jira] [Created] (IGNITE-7273) Web console: Profile in "main work tab" doesn't see changes of Profile made in another tab

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7273:
--

 Summary: Web console: Profile in "main work tab" doesn't see 
changes of Profile made in another tab
 Key: IGNITE-7273
 URL: https://issues.apache.org/jira/browse/IGNITE-7273
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Pavel Konstantinov
Priority: Minor


# open two tabs with web console
# in the second tab open User\Profile page and make any changes, Save
# open Profile in the first tab - it doesn't show changes you made





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Hello Ignite

[Stanislav Lukyanov]

Hello Ignite Devs,

My name is Stan and I want to contribute to the Apache Ignite project.
I’d like to start by fixing https://issues.apache.org/jira/browse/IGNITE-7217.

I understand that I need additional JIRA access rights to assign the 
IGNITE-7217 to myself.
Could someone please grant me those?

Thanks,
Stanislav Lukyanov

Re: Time and scope for Apache Ignite 2.4

[Petr Ivanov]

Hi, Denis.


Yes, we collaborated with Yuri and are currently waiting for Ignite Tests run 
results (though I’ll be able to start full comparison run only on weekend 
because of extremely high TC load) to be sure that 1) I did not break overall 
build and 2) building and testing on Java 8 produces similar (more or less, 
considering fact that some tests are flaky) result so we can switch to new TC 
test project "Ignite Tests 2.0 (java-8)”.

Hope the changes will see themselves in master on the beginning of the 
following week.



> On 20 Dec 2017, at 23:22, Denis Magda  wrote:
> 
> Hi Peter, 
> 
> Sorry for confusion, yes, I meant using Java 8 by default in Ignite. Labeled 
> the Java 8 ticket with “important” and now it appears in the required tickets 
> list:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets
> 
> As I see Yuri reviewed the ticket from ML perspective:
> https://github.com/apache/ignite/pull/3240 
> 
> 
> Do you guys collaborate together making sure the ML build process simplified? 
> Do we need to create a sub-task of [1] to make sure it’s not missed?
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-7203 
> 
> 
> —
> Denis
> 
>> On Dec 20, 2017, at 12:29 AM, Petr Ivanov  wrote:
>> 
>> Hi, Denis!
>> 
>> 
>> What about switching to Java 8 by default? [1]
>> I guess this task is inseparably connected to Java 7 support drop and Java 9 
>> support introducing.
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-7203
>> 
>> 
>> 
>>> On 19 Dec 2017, at 23:07, Denis Magda  wrote:
>>> 
>>> Igniters,
>>> 
>>> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets
>>>  
>>> 
>>> 
>>> How good are we if to assume 5th of Jan as a code freeze date? Please 
>>> comment:
>>> - Nikolay Izhikov: Data Frames.
>>> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
>>> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
>>> - Yuri: Machine Learning + neural networks
>>> - Vladimir Ozerov: Java 9 and Java 7
>>> - Sergey Kozlov: SQL scope testing
>>> - etc.: please check the link with the features.
>>> 
>>> —
>>> Denis
 On Dec 4, 2017, at 1:11 PM, Denis Magda  wrote:
 
 Igniters,
 
 Basing on the amount of improvements, fixes and features stacked in the 
 master branch I think it’s a right time to negotiate the scope and time of 
 the next Apache Ignite 2.4 release. I’m ready to step in as a release 
 manager if none of the committers wants to try on this role.
 
 Here is a release page:
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 
 
 
 Proposed time date: Jan 5 - code freeze -> stabilization and testing -> 
 Jan 24 - voting -> Jan 31 release.
 
 In my view improvements such Java 9 support and Java 7 discontinuation, 
 memory metrics in bytes [1], binary client protocol, etc. needs to get 
 into the release. All the features like that are labeled “important” in 
 JIRA. Use this label if you are convinced a task has to be release in 2.4.
 
 What’s about machine learning, bulk loading [2], internals problems 
 resolution [3], metrics [4] related tasks? What goes in 2.4 and what’s 
 shifted?
 
 [1] https://issues.apache.org/jira/browse/IGNITE-6902 
 
 [2] 
 https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bulk+data+loading+performance+improvements
  
 
 [3] 
 https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
  
 
 [4] 
 https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements
  
 
 
 —
 Denis
>>> 
>> 
> 

[jira] [Created] (IGNITE-7274) Web Agent: Support multiple statements on Queries screen.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7274:


 Summary: Web Agent: Support multiple statements on Queries screen.
 Key: IGNITE-7274
 URL: https://issues.apache.org/jira/browse/IGNITE-7274
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.4


See IGNITE-6046 for API



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Hello Ignite

[Denis Magda]

Hi Stan,

Please tell me your JIRA id and I’ll add you to the contributors list.

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list sharing 
your JIRA id, so we can add you as a contributor in Jira.

These are the easy tickets to start with:
https://issues.apache.org/jira/browse/IGNITE-4549?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN

While those are more advanced but appealing:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

—
Denis

> On Dec 20, 2017, at 1:23 AM, Stanislav Lukyanov  
> wrote:
> 
> Hello Ignite Devs,
> 
> My name is Stan and I want to contribute to the Apache Ignite project.
> I’d like to start by fixing https://issues.apache.org/jira/browse/IGNITE-7217.
> 
> I understand that I need additional JIRA access rights to assign the 
> IGNITE-7217 to myself.
> Could someone please grant me those?
> 
> Thanks,
> Stanislav Lukyanov

[GitHub] ignite pull request #3266: IGNITE-7272

[devozerov]

Github user devozerov closed the pull request at:

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


---

Re: Transaction classes naming

[ALEKSEY KUZNETSOV]

for renaming +1

> 21 дек. 2017 г., в 5:25, Dmitriy Setrakyan  написал(а):
> 
> Will this renaming introduce any issues with supporting previous versions?
> 
>> On Wed, Dec 20, 2017 at 9:10 AM, Yakov Zhdanov  wrote:
>> 
>> How about we explain it in javadocs and properly document on wiki? Guys, I
>> would do this at some point when there is no another bigger issue in Ignite
>> =)
>> 
>> --Yakov
>> 

IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

[Jason Man, CLSA]

Hi Igniters,

I've got a PR to resolve this JIRA available:

https://issues.apache.org/jira/browse/IGNITE-6853
https://github.com/apache/ignite/pull/3088

The JIRA was tagged previously with fix version = 2.4

May I know what is the process to move things forward?  (The PR has been 
created 3 weeks ago).  I'm hoping this fix would be included in 2.4 release. 

Thanks.
Jason  
The content of this communication is intended for the recipient and is subject 
to CLSA Legal and Regulatory Notices.
These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon 
request.
CLSA is ISO14001 certified and committed to reducing environmental impact.

Re: IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

[Denis Magda]

Hi Jason,

Thanks for fixing the bug! Please assign the ticket on yourself, move it to 
“PATCH AVAILABLE” state and run Cassandra specific tests on TeamCity. More on 
this can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview
 


Igor Rudyak (copied) is a main maintainer. Igor, would you mind checking the 
patch and explain how to test the integration on TeamCity (if needed)?

—
Denis

> On Dec 20, 2017, at 10:08 PM, Jason Man, CLSA  wrote:
> 
> Hi Igniters,
> 
> I've got a PR to resolve this JIRA available:
> 
> https://issues.apache.org/jira/browse/IGNITE-6853
> https://github.com/apache/ignite/pull/3088
> 
> The JIRA was tagged previously with fix version = 2.4
> 
> May I know what is the process to move things forward?  (The PR has been 
> created 3 weeks ago).  I'm hoping this fix would be included in 2.4 release. 
> 
> Thanks.
> Jason  
> The content of this communication is intended for the recipient and is 
> subject to CLSA Legal and Regulatory Notices.
> These can be viewed at https://www.clsa.com/disclaimer.html or sent to you 
> upon request.
> CLSA is ISO14001 certified and committed to reducing environmental impact.

Re: Create cache using thin protocol

[Pavel Tupitsyn]

Hi Prachi,

Yes, you have to provide full configuration. The error is caused by
incomplete request message.

Alternatively, define cache templates on server (configs with * in them)
and then use OP_CACHE_CREATE_WITH_NAME from thin client.

Thanks,
Pavel

On Thu, Dec 21, 2017 at 3:47 AM, Prachi Garg  wrote:

> Pavel,
>
> I tried to create a cache with configuration, using the thin protocol.
>
> 1. Do I need to provide every configuration as mentioned in the wiki, or I
> can just provide a few and the rest can be default?
>
> 2. Using the below code:
>
> DataOutputStream out = new DataOutputStream(socket.getOutputStream());
>
> // Message length
> writeIntLittleEndian(22, out);
>
> // Op code = OP_CACHE_CREATE_WITH_CONFIGURATION
> writeShortLittleEndian(1053, out);
>
> // Request id (can be anything)
> long reqId = 1;
> writeLongLittleEndian(reqId, out);
>
> // CacheAtomicityMode
> writeIntLittleEndian(0, out);
>
> // Backups
> writeIntLittleEndian(2, out);
>
> // CacheMode
> writeIntLittleEndian(2, out);
>
> // Read result
> DataInputStream in = new DataInputStream(socket.getInputStream());
>
> // Response length
> final int len = readIntLittleEndian(in);
> System.out.println("len: " + len);
>
> // Request id
> long resReqId = readLongLittleEndian(in);
> System.out.println("resReqId: " + resReqId);
>
> // Success
> int statusCode = readIntLittleEndian(in);
> System.out.println("status code: " + statusCode);
>
>
> I get the following error:
>
> [2017-12-20 
> 16:43:32,800][ERROR][client-connector-#45][ClientListenerNioListener] Failed 
> to parse client request.
> class org.apache.ignite.binary.BinaryObjectException: Not enough data to read 
> the value [position=22, requiredBytes=4, remainingBytes=0]
>   at 
> org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.ensureEnoughData(BinaryAbstractInputStream.java:305)
>   at 
> org.apache.ignite.internal.binary.streams.BinaryAbstractInputStream.readInt(BinaryAbstractInputStream.java:127)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readInt(BinaryReaderExImpl.java:743)
>   at 
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheConfigurationSerializer.read(ClientCacheConfigurationSerializer.java:125)
>   at 
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheCreateWithConfigurationRequest.(ClientCacheCreateWithConfigurationRequest.java:45)
>   at 
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:333)
>   at 
> org.apache.ignite.internal.processors.platform.client.ClientMessageParser.decode(ClientMessageParser.java:220)
>   at 
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:119)
>   at 
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
>   at 
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>
>
>

Re: List of running Continuous queries or CacheEntryListener per cache or node

[Dmitry Karachentsev]

Crossposting to devlist.

Hi Igniters!

It's might be a nice feature to have - get list of registered continuous 
queries with ability to deregister them.


What do you think?

Thanks!
-Dmitry

20.12.2017 16:59, fefe пишет:

For sanity checks or tests. I want to be sure that I haven't forgot to
deregister any listener.

Its also very important metric to see how many continuous queries/listeners
are currently running.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[GitHub] ignite pull request #3267: IGNITE-6951 .NET: Support pointer serialization

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-6951 .NET: Support pointer serialization



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

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

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

https://github.com/apache/ignite/pull/3267.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 #3267


commit 3691cb937caaf3b78388f46d94c249f5b7246f63
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:22:58Z

wip tests

commit e911a678a6c0030ce4443421dfed850503d86ca1
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:28:45Z

wip

commit 1b6853c292c15d3c4b0ee8b8f27fd3d4d590db2d
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:29:02Z

wip

commit d66f48202048d5a3e4ca077f607dcd79d64e851a
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:30:55Z

wip

commit a2876e6abfef236dd5e401eaa3e3e6b446d44886
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:47:47Z

wip tests

commit fe64981949165e7655a7f2bafc3385d960d9e63c
Author: Pavel Tupitsyn 
Date:   2017-12-20T17:52:31Z

wip tests

commit e418bd0809fe754539c6ee378e32276c7b0581a5
Author: Pavel Tupitsyn 
Date:   2017-12-20T18:30:07Z

wip tests

commit 59cd766236174bf0a57e8ec86f0f13c8a9d58989
Author: Pavel Tupitsyn 
Date:   2017-12-20T18:45:06Z

wip

commit c9bb0c48c55b168f577daec1004c0ee553fe9d89
Author: Pavel Tupitsyn 
Date:   2017-12-20T18:47:31Z

wip

commit 8437a127083b6ba687241736ab2fd6da05119fc8
Author: Pavel Tupitsyn 
Date:   2017-12-20T18:53:21Z

wip

commit 2f4b3b663ee7cd50fb95d3b72d360802509602b0
Author: Pavel Tupitsyn 
Date:   2017-12-20T18:58:34Z

wip

commit c2faaaeceb2df91817f5e17b30f574236452dd81
Author: Pavel Tupitsyn 
Date:   2017-12-20T19:15:11Z

Fix UIntPtr conversion

commit ff0d3e740b416d367ccb3efdc747c0593fccaf34
Author: Pavel Tupitsyn 
Date:   2017-12-20T19:21:01Z

wip tests

commit a5c53df7c9036012676cca538868f5430c16e758
Author: Pavel Tupitsyn 
Date:   2017-12-20T19:22:16Z

wip tests

commit 153b11099a8d08416f6b3f1a31bcf412442b5a7f
Author: Pavel Tupitsyn 
Date:   2017-12-20T19:27:31Z

wip

commit 8ea6e3de0545e8e7ff616ce47b5eabb56b1c9a79
Author: Pavel Tupitsyn 
Date:   2017-12-20T19:37:28Z

wip ptr handling

commit ea6efcbb6d769c93cf272d94ea302b0594811700
Author: Pavel Tupitsyn 
Date:   2017-12-20T20:03:14Z

wip

commit becfada736ab919edb6fb90193c99b249f1d8807
Author: Pavel Tupitsyn 
Date:   2017-12-20T20:23:16Z

some cleanup

commit 1223fef330fdea61a589f3bfc2c9b8fe036a79cc
Author: Pavel Tupitsyn 
Date:   2017-12-20T20:33:12Z

pointers support added

commit 999c99c4ea377b7acaec206f472780174523ccaa
Author: Pavel Tupitsyn 
Date:   2017-12-20T20:35:20Z

Pointers work!

commit 0036af687ebf1545ee2dbf09a9bf87a1859c3fcf
Author: Pavel Tupitsyn 
Date:   2017-12-20T20:41:43Z

raw mode

commit c72aa69e3c1ce501b533794cb0efef40a214a49c
Author: Pavel Tupitsyn 
Date:   2017-12-20T21:41:28Z

fix raw mode

commit a2ff30e0c4bdecf948242a961fc1fdf2861aaed1
Author: Pavel Tupitsyn 
Date:   2017-12-20T21:52:13Z

wip

commit fe35dedb3a875cb01da009ba777e3fe67f0a4298
Author: Pavel Tupitsyn 
Date:   2017-12-20T22:13:02Z

wip

commit 11336b8f4187218616f1d6f37d2def5b06c24748
Author: Pavel Tupitsyn 
Date:   2017-12-20T22:15:32Z

wip

commit b360e30f621d74009de768963f189917ca5e66d4
Author: Pavel Tupitsyn 
Date:   2017-12-20T22:19:21Z

wip

commit 37154035bf4813399cded44d7bcad00636c2a4f7
Author: Pavel Tupitsyn 
Date:   2017-12-21T07:01:37Z

wip tests

commit a4c4d9da27d2c5573b666dc2c24829751ca0dfd6
Author: Pavel Tupitsyn 
Date:   2017-12-21T07:15:06Z

all done




---

[jira] [Created] (IGNITE-7275) Admin panel: Grant\Revoke menu item text doesn't change

[Alexander Kalinin (JIRA)]

Alexander Kalinin created IGNITE-7275:
-

 Summary: Admin panel: Grant\Revoke menu item text doesn't change
 Key: IGNITE-7275
 URL: https://issues.apache.org/jira/browse/IGNITE-7275
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Alexander Kalinin
Assignee: Alexander Kalinin


# select any ordinary user and Grant admin rights - admin rights were 
successfully granted
# open Action menu - menu item text still says 'Grant' but should be 
'Revoke...'
# select another user then select prev user - only after that menu item become 
has right text



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)