[GitHub] ignite pull request #4020: IGNITE-8525: Support for IgniteZeroMqStreamer non...

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-8525: Support for IgniteZeroMqStreamer non-multi-part pub-sub.



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

$ git pull https://github.com/shroman/ignite IGNITE-8525

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

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


commit 1e81d413b4f6515160a174fd687ed5f71aea396b
Author: shroman 
Date:   2018-05-18T05:11:00Z

IGNITE-8525: Support for IgniteZeroMqStreamer non-multi-part pub-sub.




---

[jira] [Created] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-8525:


 Summary: Support for IgniteZeroMqStreamer non-multi-part pub-sub
 Key: IGNITE-8525
 URL: https://issues.apache.org/jira/browse/IGNITE-8525
 Project: Ignite
  Issue Type: Improvement
  Components: streaming
Reporter: Roman Shtykh
Assignee: Roman Shtykh
 Fix For: 2.6


Currently only multi-part pub-sub is supported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3967: IGNITE-172

[NSAmelchev]

Github user NSAmelchev closed the pull request at:

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


---

[jira] [Created] (IGNITE-8519) Web Console: Refactor to from Font Awesome to svg icons "Change token" panel on Profile screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8519:


 Summary: Web Console: Refactor to from Font Awesome to svg icons 
"Change token" panel on Profile screen
 Key: IGNITE-8519
 URL: https://issues.apache.org/jira/browse/IGNITE-8519
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Vica Abramova


We are constantly refactoring FontAwesome to svg icons.

Lets refactor "Change token" on Profile screen



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #2962: IGNITE-6679

[NSAmelchev]

Github user NSAmelchev closed the pull request at:

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


---

[GitHub] ignite pull request #3985: IGNITE-8320 Corrupted indexes fix

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8518:


 Summary: Web Console: Auto focus "Confirm" button in Confirmation 
dialog
 Key: IGNITE-8518
 URL: https://issues.apache.org/jira/browse/IGNITE-8518
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4002: IGNITE-8498 JDBC: fix unordered stream compatibil...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4010: IGNITE-8491

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

IGNITE-8491

Add JMX flag: Is the node in baseline or not?

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

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

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

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


commit 714b0b6243f904ceb74bfe5f8c194f6d31b4bf2d
Author: vd-pyatkov 
Date:   2018-05-17T07:35:15Z

IGNITE-8491
Add JMX flag: Is the node in baseline or not?




---

[GitHub] ignite pull request #4016: IGNITE-8320 Backport to 2.4

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-8320 Backport to 2.4



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

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

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

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


commit 79cc7728c87d942316213679f39cfeee46f9bfee
Author: zaleslaw 
Date:   2018-01-30T14:25:08Z

IGNITE-7567: Fixed bug with datasest in examples

this closes #3453

(cherry picked from commit b42a5c5)

commit 915dd2966084d78f7b4f3d482e6bd25f860c1e23
Author: Alexey Goncharuk 
Date:   2018-01-31T08:22:26Z

IGNITE-7569 Fixed index rebuild future - Fixes #3454.

commit 8ea8609259039852ab0c26f26ac528c1ffae7c94
Author: Alexey Goncharuk 
Date:   2018-01-31T08:24:57Z

IGNITE-7577 Fixing public API active flag on baseline changes - Fixes #3455.

commit d1a23c684dfadedf2b28966a223684827f3c5d7b
Author: David Wimsey 
Date:   2018-01-31T08:47:25Z

IGNITE-7576 Scripts: fix version check regexp to handle OpenJDK

This closes #3456

commit c8ce1f66e98b3174d771a3b801a2538499dc2c3d
Author: Ivan Rakov 
Date:   2018-01-31T09:51:09Z

IGNITE-7475 Improved VerifyBackupPartitionsTask to calculate partition 
hashes in parallel - Fixes #3407.

Signed-off-by: Alexey Goncharuk 

commit 258ff4299da20122d7c387cb8579264035c93c18
Author: Alexey Goncharuk 
Date:   2018-01-31T13:52:24Z

IGNITE-7573 Fixed full API tests to be compliant with baseline topology

commit aca3b8c664de8dcbbfeabbb0f8c252194d6ad1b2
Author: Pavel Tupitsyn 
Date:   2018-01-31T16:49:07Z

IGNITE-7473 .NET: Fix ConfigurationManager assembly error on Linux

commit 7bb61dfb1dcbcd759f159618a008bd02f6e6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit 254ed3a9c32d092702a0461509bf867cbd7cdee6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit d5782c53b8beab17ea4f953ad009d71b02fc335c
Author: artemmalykh 
Date:   2018-02-01T09:43:02Z

IGNITE-7590: fixed tree example

this closes #3459

(cherry picked from commit a9d40a7)

commit c1a9c0a404d77fba08170bedf14844f87abe3028
Author: Alexey Goncharuk 
Date:   2018-02-01T10:17:28Z

IGNITE-7569 Fixing index rebuild future

commit e43799ce70cdbe03d9e206381d1d5138b820b075
Author: Alexey Goncharuk 
Date:   2018-02-01T13:39:17Z

IGNITE-7520 Provide util-methods to get baseline from context - Fixes #3431.

commit a54bfd1a0906cee8394a0b495f61549ab63e4346
Author: dpavlov 
Date:   2018-02-01T15:31:12Z

IGNITE-7599 Missed licenses in ignite-direct-io module

Signed-off-by: Anton Vinogradov 

(cherry picked from commit d88af9b)
Signed-off-by: Anton Vinogradov 

commit 8f5fc7cfb0624cf2048efad38dfff32f782116e8
Author: Sergey Chugunov 
Date:   2018-02-02T08:24:29Z

IGNITE-7580 Fix compatibilityMode flag consistency

This closes #3466

(cherry picked from commit 8f2045e)

commit d3ddd50cb2b889173176b6c47c9ff61410e1d909
Author: Ilya Lantukh 
Date:   2018-02-07T10:33:28Z

IGNITE-7514 Affinity assignment should be recalculated when primary node is 
not OWNER

(cherry picked from commit faf50f1)

commit d3745e9d0a3ff5a64fba494889b7e2605f3af6bb
Author: Alexey Goncharuk 
Date:   2018-02-07T18:10:32Z

IGNITE-7639 Fixed NPE

commit 421b2b9554cc0400be3ec95c07efffca409d07dd
Author: Stanislav Lukyanov 
Date:   2018-02-08T22:25:11Z

IGNITE-7464 - Add property to configure time between node connection 
attempts - Fixes #3493

commit f7c16855ba802d9d47048521aec7e14285e4a281
Author: Pavel Kovalenko 
Date:   2018-02-09T13:55:15Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying. - Fixes #3490.

Signed-off-by: Alexey Goncharuk 

commit 2eec607b36186c05f92fae71b30d61d43eda4a69
Author: Nikolay Izhikov 
Date:   2018-02-09T04:00:54Z

IGNITE-7337: Implementation of saving DataFrame to Ignite SQL tables - 
Fixes #3438.

commit c92f167fc491078f02b9f94fe89edafc2902ebc2
Author: ilantukh 
Date:   2018-02-14T12:40:13Z

Updated version in properties.

commit 1ecf348dd429cf7861b414e0e5a7776b72dba281
Author: Sergey 

Re: Apache Ignite 2.5 release

[Ivan Rakov]

Andrey, Igniters,

I bumped into this issue while trying to reproduce another: 
https://issues.apache.org/jira/browse/IGNITE-8320
I think, this fix worth being cherry-picked into 2.5. Possibility of 
AssertionError on persistence level is really undesirable for Ignite as 
a product.


Best Regards,
Ivan Rakov

On 14.05.2018 15:59, Andrey Gura wrote:

Igniters,

we are ready to start process of releasing Apache Ignite 2.5.

So code freeze. No more commits to ignite-2.5 branch.

Thanks!


On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:

Igniters,

Almost all issues for Apache Ignite 2.5 release are fixed. Issues that
are still in Open state will be moved to 2.6 release.

Code freeze for ignite-2.5 branch is planed for tomorrow.

Thanks!

On Tue, May 8, 2018 at 7:09 PM, Andrey Gura  wrote:

Thanks for fast update, Ivan.

On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov  wrote:

Andrey,

Sorry to disturb you again. I have a follow up fix for IGNITE-8429 -
https://issues.apache.org/jira/browse/IGNITE-8453.
Please merge it to master and ignite-2.5.

Best Regards,
Ivan Rakov


On 08.05.2018 15:29, Vladimir Ozerov wrote:

H2 version updated is moved to AI 2.6. There are several serious problems,
main - spatial dependency replacement which is a breaking change.

On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn 
wrote:


IGNITE-8434 merged to master, cherry-picked to ignite-2.5.

Thank you, Andrey!

On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:


Pavel,

issue is targeted to release 2.5 now. Thanks!

On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn 
wrote:

Igniters,

There is an unpleasant bug in .NET [1]:
Services do not work at all on .NET Core and sometimes on classic .NET.

I'm almost done with the fix and I think we should include it in 2.5.

Users

are complaining [2].


[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
http://apache-ignite-users.70518.x6.nabble.com/Re-

Service-Grid-and-net-core-2-td21318.html

On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
wrote:


Andrey,

I realized that we missed one very important thing - H2 version

upgrade

[1]. This is very important thing because new version contain

optimization

to IN clause processing. All we need is to upgrade H2 vesion from

1.4.196

to 1.4.197 and re-run tests. Can we target it to 2.5 release?

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

On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:


Ivan,

ok, targeted to 2.5. Thanks!

On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <

dpavlov@gmail.com>

wrote:

Thank you, Andrey,

I saw 1 more proposal in separate topic
http://apache-ignite-developers.2346864.n4.nabble.

com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-
org-jira-browse-IGNITE-8439-td30161.html

and 1 proposal here related to ML:
http://apache-ignite-developers.2346864.n4.nabble.

com/Apache-Ignite-2-5-release-td28927i20.html#a30155

but here Yuriy Babak probably should share his opinion.

Sincerely,
Dmitriy Pavlov

пн, 7 мая 2018 г. в 17:09, Andrey Gura :

Sergey, Dmitry,

I've targeted your issues to 2.5 release.

Thanks!

On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <

dpavlov@gmail.com>

wrote:

I did not understand process.

Is it required to receive someone reply that issue is agreed to

be

included
into release?

Or because there is no response I can cherry-pick anything to

2.5

hoping

it
is lazy consensus; no one objected.

пт, 4 мая 2018 г. в 17:44, Denis Magda :


Igniters,

I got lost. Were all the bugs reported in this thread fixed

and

merged

into
2.5 branch? Is there any bug which fix is still in progress?

Just want to know when the QA and bugs fixing stage is over.

--
Denis

On Thu, May 3, 2018 at 9:14 AM, Dmitry Pavlov <

dpavlov@gmail.com

wrote:


Hi Andrey, Igniters,

I propose to include
https://issues.apache.org/jira/browse/IGNITE-8347

fix

to 2.5. It is quite isolated.

Memory leak can be reproduced if node in embedded mode is

restarted

under
the same process (thread is alive and cleanup is not

performed).

Sincerely,
Dmitriy Pavlov

сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
 wrote:


Guys,

Consider including this [1] to release.

It's major usability issue and if not fixed now will

lead

to

compatibility

issues in subsequent release.

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

пт, 27 апр. 

[GitHub] ignite pull request #4011: Ignite-2.4.5-p1

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-2.4.5-p1

For test purposes

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

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

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

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


commit 915dd2966084d78f7b4f3d482e6bd25f860c1e23
Author: Alexey Goncharuk 
Date:   2018-01-31T08:22:26Z

IGNITE-7569 Fixed index rebuild future - Fixes #3454.

commit 8ea8609259039852ab0c26f26ac528c1ffae7c94
Author: Alexey Goncharuk 
Date:   2018-01-31T08:24:57Z

IGNITE-7577 Fixing public API active flag on baseline changes - Fixes #3455.

commit c8ce1f66e98b3174d771a3b801a2538499dc2c3d
Author: Ivan Rakov 
Date:   2018-01-31T09:51:09Z

IGNITE-7475 Improved VerifyBackupPartitionsTask to calculate partition 
hashes in parallel - Fixes #3407.

Signed-off-by: Alexey Goncharuk 

commit 258ff4299da20122d7c387cb8579264035c93c18
Author: Alexey Goncharuk 
Date:   2018-01-31T13:52:24Z

IGNITE-7573 Fixed full API tests to be compliant with baseline topology

commit 254ed3a9c32d092702a0461509bf867cbd7cdee6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit c1a9c0a404d77fba08170bedf14844f87abe3028
Author: Alexey Goncharuk 
Date:   2018-02-01T10:17:28Z

IGNITE-7569 Fixing index rebuild future

commit e43799ce70cdbe03d9e206381d1d5138b820b075
Author: Alexey Goncharuk 
Date:   2018-02-01T13:39:17Z

IGNITE-7520 Provide util-methods to get baseline from context - Fixes #3431.

commit 8f5fc7cfb0624cf2048efad38dfff32f782116e8
Author: Sergey Chugunov 
Date:   2018-02-02T08:24:29Z

IGNITE-7580 Fix compatibilityMode flag consistency

This closes #3466

(cherry picked from commit 8f2045e)

commit d3ddd50cb2b889173176b6c47c9ff61410e1d909
Author: Ilya Lantukh 
Date:   2018-02-07T10:33:28Z

IGNITE-7514 Affinity assignment should be recalculated when primary node is 
not OWNER

(cherry picked from commit faf50f1)

commit d3745e9d0a3ff5a64fba494889b7e2605f3af6bb
Author: Alexey Goncharuk 
Date:   2018-02-07T18:10:32Z

IGNITE-7639 Fixed NPE

commit f7c16855ba802d9d47048521aec7e14285e4a281
Author: Pavel Kovalenko 
Date:   2018-02-09T13:55:15Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying. - Fixes #3490.

Signed-off-by: Alexey Goncharuk 

commit c92f167fc491078f02b9f94fe89edafc2902ebc2
Author: ilantukh 
Date:   2018-02-14T12:40:13Z

Updated version in properties.

commit 1ecf348dd429cf7861b414e0e5a7776b72dba281
Author: Sergey Chugunov 
Date:   2018-02-16T13:21:12Z

IGNITE-7699 BinaryMetadata exchange should not be triggered if metadata was 
not updated - Fixes #3523.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit bcd3881)

commit 2458bd08a5b501b3eeb5caf0ae6dcaa2bcccd915
Author: EdShangGG 
Date:   2018-02-16T13:29:49Z

IGNITE-7676 Add affinity version to snapshot plugin stub - Fixes #3510.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit b6d21fb)

commit bfdcda7a2a6b5cf64f15ed169d2beb886f131fac
Author: EdShangGG 
Date:   2018-02-12T16:36:30Z

IGNITE-7626 Unify code in test which cleans up persistence directories - 
Fixes #3477.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit a0997b9)

commit 2e92e0094b270aa8489e66d94bfcf15eadabfb4f
Author: EdShangGG 
Date:   2018-02-12T18:44:10Z

IGNITE-7626 Unify code in test which clean up persistence directories - 
Fixes #3512.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 6f6f8dd)

commit 3f86c127c78065999663a4fc4eaedb5e5d4bee1c
Author: EdShangGG 
Date:   2018-02-12T18:26:31Z

compilation fix

commit 0b9322c566f9b464291854142ac02495bd1817e4
Author: gg-shq 
Date:   2018-02-07T11:28:04Z

IGNITE-6917: Implemented SQL COPY command.

commit c5e386ca96750213bddcd98d0af0c589fee476ca
Author: gg-shq 
Date:   2018-02-07T15:31:27Z

IGNITE-7586: Added COPY command into the JDBC example.

This closes #3485

commit d8203e2d81f8fbf0f7fbe5e710c9908f2fcb8307
Author: shq 
Date:   

[GitHub] ignite pull request #3921: IGNITE-7883 add check property "key configuration...

[a-polyakov]

Github user a-polyakov closed the pull request at:

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


---

[GitHub] ignite pull request #4013: IGNITE-8520 ignite-gce/ignite-shmem is redundant

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-8520 ignite-gce/ignite-shmem is redundant



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

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

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

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


commit 1b6b74c8b626cc4eb9d004435d06f7a12f7402dc
Author: Ivanov Petr 
Date:   2018-05-17T12:20:48Z

IGNITE-8520 ignite-gce/ignite-shmem is redundant




---

[GitHub] ignite pull request #2992: IGNITE-6500 Bug in ignite's CassandraCacheStoreFa...

[kotamrajuyashasvi]

Github user kotamrajuyashasvi closed the pull request at:

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


---

[GitHub] ignite pull request #4015: Ignite 6587

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

Ignite 6587

For test purposes.

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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587

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

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


commit 3b25cb934838feb3300c7088db4b3840ec7f9ab5
Author: Andrey Kuznetsov 
Date:   2018-05-07T12:43:26Z

IGNITE-6587: Refactored ServerImpl.TcpServer to use GridWorker.

commit 665ba863ceb95b643a805d6920f3f384275dae20
Author: Andrey Kuznetsov 
Date:   2018-05-07T13:06:22Z

IGNITE-6587: Refactored ServerImpl.RingMessageWorker to use GridWorker.

commit b10bcd350efb55de95792b369996ba266b3612a9
Author: Andrey Kuznetsov 
Date:   2018-05-07T15:59:56Z

IGNITE-6587: Refactored WAL manager critical threads to use GridWorker.

commit 3154112c8bab70d1ff4fe20639648e8a9c7da373
Author: Andrey Kuznetsov 
Date:   2018-05-07T18:55:25Z

IGNITE-6587: Minor improvements.

commit a44fc8064a9ba8f42e4faacde018ac9bc1193f01
Author: Andrey Kuznetsov 
Date:   2018-05-08T10:52:01Z

IGNITE-6587: Refactored CommunicationWorker to use GridWorker.

commit 0efc5354f33666ac705c738d75955258084091de
Author: Andrey Kuznetsov 
Date:   2018-05-08T15:25:56Z

IGNITE-6587: (WIP) switching to timed waits/polls, updating heartbeats.

commit 48c889441a119ef2192c1ff61485c20f80659e82
Author: Andrey Kuznetsov 
Date:   2018-05-14T13:38:47Z

IGNITE-6587: Heartbeat updates in critical WAL manager workers.

commit 69059bda2071f7d6af0cef30cf8d77b160fc56be
Author: Andrey Kuznetsov 
Date:   2018-05-14T15:55:51Z

IGNITE-6587: (WiP) More heartbeat updates in critical workers.

commit 6fb2edf1fef15bb187481f89eddb3710d5daadba
Author: Andrey Kuznetsov 
Date:   2018-05-15T13:09:16Z

IGNITE-6587: Heartbeat updates in checkpointer.

commit 9cd8cba1fdc8c21d999df4c334daaef7e226aa0f
Author: Andrey Kuznetsov 
Date:   2018-05-15T13:23:17Z

IGNITE-6587: More heartbeat updates in critical workers.

commit 5245abc0c72812c4746127b25638a28dac7af11a
Author: Andrey Kuznetsov 
Date:   2018-05-16T20:14:31Z

IGNITE-6587: Extended StripedExecutor.Stripe from GridWorker.

commit 2eb448f6a7ff7a6be423742336480a7b98793c2d
Author: Andrey Kuznetsov 
Date:   2018-05-17T11:37:08Z

IGNITE-6587: Heartbeat updates in StripedExecutor workers.

commit 8304fa92879fe293f112d1c7ba515b5bd30cc271
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:33:23Z

Merge branch 'master' into ignite-6587

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FileWriteAheadLogManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FsyncModeFileWriteAheadLogManager.java

commit 5051aa4d44e78b5362dd0094bc5a57566eea4855
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:36:23Z

IGNITE-6587: Addition to merge commit.

commit 732d2c25013d94d67188f42b2f96c786eeaf6346
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:42:05Z

IGNITE-6587: Updated WAL FileDecompressors to conform uniform poll style.




---

[GitHub] ignite pull request #3991: IGNITE-8161 Suspend-resume TX test is flaky on TC...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3921: IGNITE-7883 add check property "key configuration...

[a-polyakov]

GitHub user a-polyakov reopened a pull request:

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

IGNITE-7883 add check property "key configuration" in cache configuration

…tions

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

$ git pull https://github.com/a-polyakov/ignite IGNITE-7883

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

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


commit f1e77e4daf9d9389d078954dfaa91cd5bba37494
Author: a-polyakov 
Date:   2018-05-17T13:59:35Z

IGNITE-7883 add check property "key configuration" in cache configurations




---

[GitHub] ignite pull request #3584: IGNITE-7844 Transaction incorrect state after cli...

[voipp]

Github user voipp closed the pull request at:

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


---

[GitHub] ignite pull request #4014: IGNITE-6500

[kotamrajuyashasvi]

GitHub user kotamrajuyashasvi opened a pull request:

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

IGNITE-6500

POJO fields of java wrapper type are not retaining null values from 
Cassandra persistent store, while using ignite's CassandraCacheStoreFactory.

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

$ git pull https://github.com/kotamrajuyashasvi/ignite master

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

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


commit b73a60cafe606d5802776e10e7c19204d0a02450
Author: Unknown 
Date:   2018-05-17T12:40:57Z

IGNITE-6500




---

[GitHub] ignite pull request #4012: IGNITE-8516 checked not null constraint

[dgarus]

GitHub user dgarus opened a pull request:

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

IGNITE-8516 checked not null constraint



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

$ git pull https://github.com/dgarus/ignite ignite-8516

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

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


commit 833cb6e8d39ceb830bf77b5c1c50ebbcc7cb565f
Author: sbt-garus-dg 
Date:   2018-05-17T12:06:24Z

IGNITE-8516 checked not null constraint




---

Re: Apache Ignite 2.4+ Go language client

[Igor Sapego]

By the way, Alexandr,

Do you want to donate your client to Apache Ignite, so we
are going to include it in our release, or would you prefer
keep it separate?


Best Regards,
Igor

On Thu, May 10, 2018 at 1:09 PM, Igor Sapego  wrote:

> Aleksandr,
> I'm currently working on the improvement of the doc, so please,
> feel free to participate with review and proposals here - [1].
>
> [1] -https://issues.apache.org/jira/browse/IGNITE-8039
>
> Best Regards,
> Igor
>
> On Tue, May 8, 2018 at 3:47 PM, Aleksandr Sokolovskii 
> wrote:
>
>> Hi Alexey,
>>
>> I spent some time and fully implemented OP_QUERY_SQL and
>> OP_QUERY_SQL_CURSOR_GET_PAGE including unit tests.
>> The OP_QUERY_SQL returns value as complex object (code=103) wrapped by
>> array (code=27).
>> But it’s not the end of the story. )))
>> Complex object is marshalled in different way than described in
>> documentation.
>>
>> Example how to unmarshall complex object of several formats:
>> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> ry/v1/types.go#L969
>>
>> Unit test for OP_QUERY_SQL:
>> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> ry/v1/client-sql-and-scan-queries_test.go#L9
>>
>> Unit test for OP_QUERY_SQL_CURSOR_GET_PAGE:
>> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> ry/v1/client-sql-and-scan-queries_test.go#L80
>>
>> Thanks,
>> Aleksandr
>>
>> From: Alexey Kosenchuk
>> Sent: 25 апреля 2018 г. 16:33
>> To: dev@ignite.apache.org
>> Subject: Re: Apache Ignite 2.4+ Go language client
>>
>> No problem with OP_QUERY_SQL_FIELDS.
>> I mean OP_QUERY_SQL.
>> But I overlooked "OP_QUERY_SQL - Done without unit test. Need help to
>> develop unit test."
>> Sorry. I remove my question so far)))
>>
>> Thanks,
>> -Alexey
>>
>> 25.04.2018 15:40, Aleksandr Sokolovskii пишет:
>> > Hi Alexey,
>> >
>> >> Seems an important missed part is complex objects support.
>> >> And it's the most difficult part.
>> > Yes, you are absolutely right.
>> > Complex object and binary types are not supported by my client now.
>> > That’s why I’m here.
>> > I plan to come back to this subject in the beginning of May.
>> > I very much count on the community help.
>> >
>> >> Also, do you have a working example for SQL Query which first inserts
>> >> cache entries and then selects them and successfully get the same
>> values
>> >> which were inserted ?
>> > Yes, it works fine.
>> > This one:
>> > https://github.com/amsokol/ignite-go-client/blob/master/bina
>> ry/v1/client-sql-and-scan-queries_test.go#L89
>> > It’s OP_QUERY_SQL_FIELDS operation unit test.
>> > It you are familiar with Go it’s easy to run in debug mode.
>> >
>> > If you explain me your problem I can try to help you.
>> > There some mistakes in binary protocol documentation.
>> > So I spent a lot of time in Apache Ignite server source code analyzing
>> )))
>> >
>> > Thanks,
>> > Aleksandr
>> >
>> > From: Alexey Kosenchuk
>> > Sent: 25 апреля 2018 г. 12:05
>> > To: dev@ignite.apache.org
>> > Subject: Re: Apache Ignite 2.4+ Go language client
>> >
>> > Hi Aleksandr,
>> >
>> > Seems an important missed part is complex objects support.
>> > And it's the most difficult part.
>> > Actually, it is not possible to implement it correctly basing on the
>> > current protocol spec only.
>> > If you decide to support it, you should either wait for an updated spec
>> > or ask for help.
>> >
>> > The issues against the current protocol spec are summarized in
>> > IGNITE-8039 [1] and IGNITE-8212 [2]. One more jira with the issues
>> > against the rest of the spec will be submitted soon.
>> > If you see more issues, please feel free to added them as comments to
>> > that jiras.
>> >
>> > Also, do you have a working example for SQL Query which first inserts
>> > cache entries and then selects them and successfully get the same values
>> > which were inserted ?
>> >
>> > Thanks,
>> > -Alexey
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-8039
>> > [2] https://issues.apache.org/jira/browse/IGNITE-8212
>> >
>> > 25.04.2018 0:11, Aleksandr Sokolovskii пишет:
>> >> ...forgot OP_RESOURCE_CLOSE that is implemented also.
>> >>
>> >> Thanks,
>> >> Aleksandr
>> >>
>> >> Thanks,
>> >> Aleksandr
>> >>
>> >> On 25 April 2018 at 00:06, Aleksandr Sokolovskii 
>> wrote:
>> >>
>> >>> Hello All,
>> >>>
>> >>> Besides the SQL driver I implemented the following operations also:
>> >>> OP_CACHE_GET_NAMES
>> >>> OP_CACHE_CREATE_WITH_NAME
>> >>> OP_CACHE_GET_OR_CREATE_WITH_NAME
>> >>> OP_CACHE_CREATE_WITH_CONFIGURATION
>> >>> OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION
>> >>> OP_CACHE_GET_CONFIGURATION
>> >>> OP_CACHE_DESTROY
>> >>> OP_CACHE_GET
>> >>> OP_CACHE_PUT
>> >>> OP_CACHE_PUT_IF_ABSENT
>> >>> OP_CACHE_GET_ALL
>> >>> OP_CACHE_PUT_ALL
>> >>> OP_CACHE_GET_AND_PUT
>> >>> OP_CACHE_GET_AND_REPLACE
>> >>> OP_CACHE_GET_AND_REMOVE
>> >>> OP_CACHE_GET_AND_PUT_IF_ABSENT
>> >>> OP_CACHE_REPLACE
>> >>> OP_CACHE_REPLACE_IF_EQUALS
>> >>> 

[GitHub] ignite pull request #3990: IGNITE-8474 skipForExchangeMerge property changed...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-8520) ignite-gce/ignite-shmem

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-8520:
-

 Summary: ignite-gce/ignite-shmem
 Key: IGNITE-8520
 URL: https://issues.apache.org/jira/browse/IGNITE-8520
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sergey Kozlov
 Fix For: 2.5


{{ignite-shmem}} is already included in {{libs}} and thus should  be excluded 
from {{libs/optional/ignite-gce}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4017: IGNITE-8461 Scala-2.10 modules compilation failur...

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-8461 Scala-2.10 modules compilation failure under JDK 9

 * fixed Scala 2.10 compilation on JDK9
 * updated other Scala versions

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

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

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

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


commit 83c5423b649386d109c57c0260824849b9163daa
Author: Ivanov Petr 
Date:   2018-05-17T13:46:59Z

IGNITE-8461 Scala-2.10 modules compilation failure under JDK 9
 * fixed Scala 2.10 compilation on JDK9
 * updated other Scala versions




---

[GitHub] ignite pull request #4019: IGNITE-8405 Backport to 2.4

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-8405 Backport to 2.4



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

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

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

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


commit 47d05b2eb1ecfef225b4f3460b0eca5122f96b15
Author: Ivanov Petr 
Date:   2018-01-29T20:17:41Z

IGNITE-7534: Removed ClusterGroupExample duplicate. Fixes #3446.

Signed-off-by: Valentin Kulichenko 

commit 79cc7728c87d942316213679f39cfeee46f9bfee
Author: zaleslaw 
Date:   2018-01-30T14:25:08Z

IGNITE-7567: Fixed bug with datasest in examples

this closes #3453

(cherry picked from commit b42a5c5)

commit 915dd2966084d78f7b4f3d482e6bd25f860c1e23
Author: Alexey Goncharuk 
Date:   2018-01-31T08:22:26Z

IGNITE-7569 Fixed index rebuild future - Fixes #3454.

commit 8ea8609259039852ab0c26f26ac528c1ffae7c94
Author: Alexey Goncharuk 
Date:   2018-01-31T08:24:57Z

IGNITE-7577 Fixing public API active flag on baseline changes - Fixes #3455.

commit d1a23c684dfadedf2b28966a223684827f3c5d7b
Author: David Wimsey 
Date:   2018-01-31T08:47:25Z

IGNITE-7576 Scripts: fix version check regexp to handle OpenJDK

This closes #3456

commit c8ce1f66e98b3174d771a3b801a2538499dc2c3d
Author: Ivan Rakov 
Date:   2018-01-31T09:51:09Z

IGNITE-7475 Improved VerifyBackupPartitionsTask to calculate partition 
hashes in parallel - Fixes #3407.

Signed-off-by: Alexey Goncharuk 

commit 258ff4299da20122d7c387cb8579264035c93c18
Author: Alexey Goncharuk 
Date:   2018-01-31T13:52:24Z

IGNITE-7573 Fixed full API tests to be compliant with baseline topology

commit aca3b8c664de8dcbbfeabbb0f8c252194d6ad1b2
Author: Pavel Tupitsyn 
Date:   2018-01-31T16:49:07Z

IGNITE-7473 .NET: Fix ConfigurationManager assembly error on Linux

commit 7bb61dfb1dcbcd759f159618a008bd02f6e6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit 254ed3a9c32d092702a0461509bf867cbd7cdee6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit d5782c53b8beab17ea4f953ad009d71b02fc335c
Author: artemmalykh 
Date:   2018-02-01T09:43:02Z

IGNITE-7590: fixed tree example

this closes #3459

(cherry picked from commit a9d40a7)

commit c1a9c0a404d77fba08170bedf14844f87abe3028
Author: Alexey Goncharuk 
Date:   2018-02-01T10:17:28Z

IGNITE-7569 Fixing index rebuild future

commit e43799ce70cdbe03d9e206381d1d5138b820b075
Author: Alexey Goncharuk 
Date:   2018-02-01T13:39:17Z

IGNITE-7520 Provide util-methods to get baseline from context - Fixes #3431.

commit a54bfd1a0906cee8394a0b495f61549ab63e4346
Author: dpavlov 
Date:   2018-02-01T15:31:12Z

IGNITE-7599 Missed licenses in ignite-direct-io module

Signed-off-by: Anton Vinogradov 

(cherry picked from commit d88af9b)
Signed-off-by: Anton Vinogradov 

commit 8f5fc7cfb0624cf2048efad38dfff32f782116e8
Author: Sergey Chugunov 
Date:   2018-02-02T08:24:29Z

IGNITE-7580 Fix compatibilityMode flag consistency

This closes #3466

(cherry picked from commit 8f2045e)

commit d3ddd50cb2b889173176b6c47c9ff61410e1d909
Author: Ilya Lantukh 
Date:   2018-02-07T10:33:28Z

IGNITE-7514 Affinity assignment should be recalculated when primary node is 
not OWNER

(cherry picked from commit faf50f1)

commit d3745e9d0a3ff5a64fba494889b7e2605f3af6bb
Author: Alexey Goncharuk 
Date:   2018-02-07T18:10:32Z

IGNITE-7639 Fixed NPE

commit 421b2b9554cc0400be3ec95c07efffca409d07dd
Author: Stanislav Lukyanov 
Date:   2018-02-08T22:25:11Z

IGNITE-7464 - Add property to configure time between node connection 
attempts - Fixes #3493

commit f7c16855ba802d9d47048521aec7e14285e4a281
Author: Pavel Kovalenko 
Date:   2018-02-09T13:55:15Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying. - Fixes #3490.

Signed-off-by: Alexey Goncharuk 

commit 2eec607b36186c05f92fae71b30d61d43eda4a69
Author: Nikolay Izhikov 
Date:   2018-02-09T04:00:54Z

IGNITE-7337: Implementation of saving 

Re: Apache Ignite 2.5 release

[Denis Magda]

We keep facing the issues that postpone the release over and over again
which seems like a never-ending story.

What are the changes the users come across the 2 latest bugs you've
mentioned (any special conditions)?

What's the overall state of our testing cycles? When would we send the
release for vote if include the abovementioned bugs or move them to the
next release?

--
Denis

On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Another issue that may lead to incorrect recovery on node startup is
> https://issues.apache.org/jira/browse/IGNITE-8464 which is already in PA.
> I
> suggest we also include it to 2.5 given that fix improves stability of the
> persistence layer. Any objections?
>
> 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
>
> > Andrey, Igniters,
> >
> > I bumped into this issue while trying to reproduce another:
> > https://issues.apache.org/jira/browse/IGNITE-8320
> > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > AssertionError on persistence level is really undesirable for Ignite as a
> > product.
> >
> > Best Regards,
> > Ivan Rakov
> >
> >
> > On 14.05.2018 15:59, Andrey Gura wrote:
> >
> >> Igniters,
> >>
> >> we are ready to start process of releasing Apache Ignite 2.5.
> >>
> >> So code freeze. No more commits to ignite-2.5 branch.
> >>
> >> Thanks!
> >>
> >>
> >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:
> >>
> >>> Igniters,
> >>>
> >>> Almost all issues for Apache Ignite 2.5 release are fixed. Issues that
> >>> are still in Open state will be moved to 2.6 release.
> >>>
> >>> Code freeze for ignite-2.5 branch is planed for tomorrow.
> >>>
> >>> Thanks!
> >>>
> >>> On Tue, May 8, 2018 at 7:09 PM, Andrey Gura  wrote:
> >>>
>  Thanks for fast update, Ivan.
> 
>  On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov 
>  wrote:
> 
> > Andrey,
> >
> > Sorry to disturb you again. I have a follow up fix for IGNITE-8429 -
> > https://issues.apache.org/jira/browse/IGNITE-8453.
> > Please merge it to master and ignite-2.5.
> >
> > Best Regards,
> > Ivan Rakov
> >
> >
> > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> >
> >> H2 version updated is moved to AI 2.6. There are several serious
> >> problems,
> >> main - spatial dependency replacement which is a breaking change.
> >>
> >> On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn <
> ptupit...@apache.org
> >> >
> >> wrote:
> >>
> >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> >>>
> >>> Thank you, Andrey!
> >>>
> >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
> >>> wrote:
> >>>
> >>> Pavel,
> 
>  issue is targeted to release 2.5 now. Thanks!
> 
>  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
>  ptupit...@apache.org>
>  wrote:
> 
> > Igniters,
> >
> > There is an unpleasant bug in .NET [1]:
> > Services do not work at all on .NET Core and sometimes on classic
> > .NET.
> >
> > I'm almost done with the fix and I think we should include it in
> > 2.5.
> >
>  Users
> 
> > are complaining [2].
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > [2]
> > http://apache-ignite-users.70518.x6.nabble.com/Re-
> >
>  Service-Grid-and-net-core-2-td21318.html
> 
> > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > voze...@gridgain.com>
> > wrote:
> >
> > Andrey,
> >>
> >> I realized that we missed one very important thing - H2 version
> >>
> > upgrade
> >>>
>  [1]. This is very important thing because new version contain
> >>
> > optimization
> 
> > to IN clause processing. All we need is to upgrade H2 vesion from
> >>
> > 1.4.196
> 
> > to 1.4.197 and re-run tests. Can we target it to 2.5 release?
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-4150
> >>
> >> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura 
> >> wrote:
> >>
> >> Ivan,
> >>>
> >>> ok, targeted to 2.5. Thanks!
> >>>
> >>> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
> >>>
> >> dpavlov@gmail.com>
> >>>
>  wrote:
> >>>
>  Thank you, Andrey,
> 
>  I saw 1 more proposal in separate topic
>  http://apache-ignite-developers.2346864.n4.nabble.
> 
> >>> com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-
> >>> org-jira-browse-IGNITE-8439-td30161.html
> >>>
> 

Re: Apache Ignite 2.5 release

[Alexey Goncharuk]

Another issue that may lead to incorrect recovery on node startup is
https://issues.apache.org/jira/browse/IGNITE-8464 which is already in PA. I
suggest we also include it to 2.5 given that fix improves stability of the
persistence layer. Any objections?

2018-05-17 16:55 GMT+03:00 Ivan Rakov :

> Andrey, Igniters,
>
> I bumped into this issue while trying to reproduce another:
> https://issues.apache.org/jira/browse/IGNITE-8320
> I think, this fix worth being cherry-picked into 2.5. Possibility of
> AssertionError on persistence level is really undesirable for Ignite as a
> product.
>
> Best Regards,
> Ivan Rakov
>
>
> On 14.05.2018 15:59, Andrey Gura wrote:
>
>> Igniters,
>>
>> we are ready to start process of releasing Apache Ignite 2.5.
>>
>> So code freeze. No more commits to ignite-2.5 branch.
>>
>> Thanks!
>>
>>
>> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:
>>
>>> Igniters,
>>>
>>> Almost all issues for Apache Ignite 2.5 release are fixed. Issues that
>>> are still in Open state will be moved to 2.6 release.
>>>
>>> Code freeze for ignite-2.5 branch is planed for tomorrow.
>>>
>>> Thanks!
>>>
>>> On Tue, May 8, 2018 at 7:09 PM, Andrey Gura  wrote:
>>>
 Thanks for fast update, Ivan.

 On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov 
 wrote:

> Andrey,
>
> Sorry to disturb you again. I have a follow up fix for IGNITE-8429 -
> https://issues.apache.org/jira/browse/IGNITE-8453.
> Please merge it to master and ignite-2.5.
>
> Best Regards,
> Ivan Rakov
>
>
> On 08.05.2018 15:29, Vladimir Ozerov wrote:
>
>> H2 version updated is moved to AI 2.6. There are several serious
>> problems,
>> main - spatial dependency replacement which is a breaking change.
>>
>> On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn > >
>> wrote:
>>
>> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
>>>
>>> Thank you, Andrey!
>>>
>>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
>>> wrote:
>>>
>>> Pavel,

 issue is targeted to release 2.5 now. Thanks!

 On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
 ptupit...@apache.org>
 wrote:

> Igniters,
>
> There is an unpleasant bug in .NET [1]:
> Services do not work at all on .NET Core and sometimes on classic
> .NET.
>
> I'm almost done with the fix and I think we should include it in
> 2.5.
>
 Users

> are complaining [2].
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8434
> [2]
> http://apache-ignite-users.70518.x6.nabble.com/Re-
>
 Service-Grid-and-net-core-2-td21318.html

> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> wrote:
>
> Andrey,
>>
>> I realized that we missed one very important thing - H2 version
>>
> upgrade
>>>
 [1]. This is very important thing because new version contain
>>
> optimization

> to IN clause processing. All we need is to upgrade H2 vesion from
>>
> 1.4.196

> to 1.4.197 and re-run tests. Can we target it to 2.5 release?
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-4150
>>
>> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura 
>> wrote:
>>
>> Ivan,
>>>
>>> ok, targeted to 2.5. Thanks!
>>>
>>> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
>>>
>> dpavlov@gmail.com>
>>>
 wrote:
>>>
 Thank you, Andrey,

 I saw 1 more proposal in separate topic
 http://apache-ignite-developers.2346864.n4.nabble.

>>> com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-
>>> org-jira-browse-IGNITE-8439-td30161.html
>>>
 and 1 proposal here related to ML:
 http://apache-ignite-developers.2346864.n4.nabble.

>>> com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>>>
 but here Yuriy Babak probably should share his opinion.

 Sincerely,
 Dmitriy Pavlov

 пн, 7 мая 2018 г. в 17:09, Andrey Gura :

> Sergey, Dmitry,
>
> I've targeted your issues to 2.5 release.
>
> Thanks!
>
> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
>
 dpavlov@gmail.com>

> wrote:
>
>> I did not understand 

[jira] [Created] (IGNITE-8522) Transaction incorrect state after cache closed

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8522:


 Summary: Transaction incorrect state after cache closed
 Key: IGNITE-8522
 URL: https://issues.apache.org/jira/browse/IGNITE-8522
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


When we started transaction on client node and closed cache , transaction is 
rolled back.
But tx state is still ACTIVE which causes unexpected exception when we try to 
commit it.
The expected exception is TransactionRollbackException.

Look at the following code:

{code:java}
public void testTxRollbackWhenCacheClosed() throws Exception {
startGrid(0);// server node started

client = true;

IgniteEx clientNode = startGrid(1);

IgniteCache cache = clientNode.createCache();// transactional cache is 
started

IgniteTransactions transactions = clientNode.transactions();

Transaction tx = transactions.txStart();

cache.put(1, 1);

multithreaded(cache::close, 1);

tx.commit();// TransactionRollbackException expected, but NPE is thrown.
}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4018: IGNITE-8423 Control utility may block when joinin...

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

IGNITE-8423 Control utility may block when joining node is watiting f…

…or partition map exchange.

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

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

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

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


commit 9962d6a767ccacd34d5cc9375e930a6119efc78f
Author: Aleksei Scherbakov 
Date:   2018-05-17T15:08:45Z

IGNITE-8423 Control utility may block when joining node is watiting for 
partition map exchange.




---

Re: Apache Ignite 2.5 release

[Alexey Goncharuk]

Denis,

The issue with page corruption may manifest itself when a node is stopped
during partition eviction (basically, a random chance on topology change
scenario).

The issue with WAL iterator can manifest during historical rebalancing
(this is less likely than the previous issue).

2018-05-17 18:07 GMT+03:00 Denis Magda :

> We keep facing the issues that postpone the release over and over again
> which seems like a never-ending story.
>
> What are the changes the users come across the 2 latest bugs you've
> mentioned (any special conditions)?
>
> What's the overall state of our testing cycles? When would we send the
> release for vote if include the abovementioned bugs or move them to the
> next release?
>
> --
> Denis
>
> On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > Another issue that may lead to incorrect recovery on node startup is
> > https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
> PA.
> > I
> > suggest we also include it to 2.5 given that fix improves stability of
> the
> > persistence layer. Any objections?
> >
> > 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
> >
> > > Andrey, Igniters,
> > >
> > > I bumped into this issue while trying to reproduce another:
> > > https://issues.apache.org/jira/browse/IGNITE-8320
> > > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > > AssertionError on persistence level is really undesirable for Ignite
> as a
> > > product.
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > >
> > > On 14.05.2018 15:59, Andrey Gura wrote:
> > >
> > >> Igniters,
> > >>
> > >> we are ready to start process of releasing Apache Ignite 2.5.
> > >>
> > >> So code freeze. No more commits to ignite-2.5 branch.
> > >>
> > >> Thanks!
> > >>
> > >>
> > >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
> wrote:
> > >>
> > >>> Igniters,
> > >>>
> > >>> Almost all issues for Apache Ignite 2.5 release are fixed. Issues
> that
> > >>> are still in Open state will be moved to 2.6 release.
> > >>>
> > >>> Code freeze for ignite-2.5 branch is planed for tomorrow.
> > >>>
> > >>> Thanks!
> > >>>
> > >>> On Tue, May 8, 2018 at 7:09 PM, Andrey Gura 
> wrote:
> > >>>
> >  Thanks for fast update, Ivan.
> > 
> >  On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov 
> >  wrote:
> > 
> > > Andrey,
> > >
> > > Sorry to disturb you again. I have a follow up fix for IGNITE-8429
> -
> > > https://issues.apache.org/jira/browse/IGNITE-8453.
> > > Please merge it to master and ignite-2.5.
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > >
> > > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> > >
> > >> H2 version updated is moved to AI 2.6. There are several serious
> > >> problems,
> > >> main - spatial dependency replacement which is a breaking change.
> > >>
> > >> On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn <
> > ptupit...@apache.org
> > >> >
> > >> wrote:
> > >>
> > >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> > >>>
> > >>> Thank you, Andrey!
> > >>>
> > >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
> > >>> wrote:
> > >>>
> > >>> Pavel,
> > 
> >  issue is targeted to release 2.5 now. Thanks!
> > 
> >  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
> >  ptupit...@apache.org>
> >  wrote:
> > 
> > > Igniters,
> > >
> > > There is an unpleasant bug in .NET [1]:
> > > Services do not work at all on .NET Core and sometimes on
> classic
> > > .NET.
> > >
> > > I'm almost done with the fix and I think we should include it
> in
> > > 2.5.
> > >
> >  Users
> > 
> > > are complaining [2].
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > > [2]
> > > http://apache-ignite-users.70518.x6.nabble.com/Re-
> > >
> >  Service-Grid-and-net-core-2-td21318.html
> > 
> > > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > > voze...@gridgain.com>
> > > wrote:
> > >
> > > Andrey,
> > >>
> > >> I realized that we missed one very important thing - H2
> version
> > >>
> > > upgrade
> > >>>
> >  [1]. This is very important thing because new version contain
> > >>
> > > optimization
> > 
> > > to IN clause processing. All we need is to upgrade H2 vesion
> from
> > >>
> > > 1.4.196
> > 
> > > to 1.4.197 and re-run tests. Can we target it to 2.5 release?
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-4150
> > >>
> > >> On Mon, May 7, 2018 at 

[jira] [Created] (IGNITE-8523) Java and Scala spark examples are mixed

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-8523:
-

 Summary: Java and Scala spark examples are mixed
 Key: IGNITE-8523
 URL: https://issues.apache.org/jira/browse/IGNITE-8523
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Sergey Kozlov
 Fix For: 2.5


Now {{ignite-example}} project has two locations to store spark examples:
{{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}} - single 
spark example on Scala
{{examples/src/main/spark/org/apache/ignite/examples/spark}} - mix of java and 
scala examples

Moreover the profile {{scala}} activates spark folder but that folder has Java 
examples as well. Thus I can't run java spark examples without {{scala}} 
profile.

The current implementation is weird and should be fixed by following way:
1. Make two locations where collect java and scala examples separately:
{{examples/src/main/java/org/apache/ignite/examples/spark}} for java examples
{{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}} for scala 
examples
2. Remove {{scala}} profile



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Apache Ignite 2.4+ Go language client

[Vyacheslav Daradur]

Hi, there is such GitHub profile:
https://github.com/apacheignite

But I don't know who manage that.

On Thu, May 17, 2018 at 9:22 PM, Aleksandr Sokolovskii
 wrote:
> Hi Igor,
>
> Of course I am ready to donate code.
>
> You have to know that GitHub is source code repo and package repo for build
> for Go lang.
> I see that .NET client is deep inside Apache Ignite source code structure.
> It's not very comfortable for Go lang developers.
> It's best practice when each Go lang library/project has own GitHub repo.
>
> What do you think to create Apache Ignite "organization" in GitHub and
> consolidate all source code.
> Here is example of CockroachDB project:
> https://github.com/cockroachdb
>
>
> Thanks,
> Aleksandr
>
> On 17 May 2018 at 17:21, Igor Sapego  wrote:
>
>> By the way, Alexandr,
>>
>> Do you want to donate your client to Apache Ignite, so we
>> are going to include it in our release, or would you prefer
>> keep it separate?
>>
>>
>> Best Regards,
>> Igor
>>
>> On Thu, May 10, 2018 at 1:09 PM, Igor Sapego  wrote:
>>
>> > Aleksandr,
>> > I'm currently working on the improvement of the doc, so please,
>> > feel free to participate with review and proposals here - [1].
>> >
>> > [1] -https://issues.apache.org/jira/browse/IGNITE-8039
>> >
>> > Best Regards,
>> > Igor
>> >
>> > On Tue, May 8, 2018 at 3:47 PM, Aleksandr Sokolovskii > >
>> > wrote:
>> >
>> >> Hi Alexey,
>> >>
>> >> I spent some time and fully implemented OP_QUERY_SQL and
>> >> OP_QUERY_SQL_CURSOR_GET_PAGE including unit tests.
>> >> The OP_QUERY_SQL returns value as complex object (code=103) wrapped by
>> >> array (code=27).
>> >> But it’s not the end of the story. )))
>> >> Complex object is marshalled in different way than described in
>> >> documentation.
>> >>
>> >> Example how to unmarshall complex object of several formats:
>> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> >> ry/v1/types.go#L969
>> >>
>> >> Unit test for OP_QUERY_SQL:
>> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> >> ry/v1/client-sql-and-scan-queries_test.go#L9
>> >>
>> >> Unit test for OP_QUERY_SQL_CURSOR_GET_PAGE:
>> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
>> >> ry/v1/client-sql-and-scan-queries_test.go#L80
>> >>
>> >> Thanks,
>> >> Aleksandr
>> >>
>> >> From: Alexey Kosenchuk
>> >> Sent: 25 апреля 2018 г. 16:33
>> >> To: dev@ignite.apache.org
>> >> Subject: Re: Apache Ignite 2.4+ Go language client
>> >>
>> >> No problem with OP_QUERY_SQL_FIELDS.
>> >> I mean OP_QUERY_SQL.
>> >> But I overlooked "OP_QUERY_SQL - Done without unit test. Need help to
>> >> develop unit test."
>> >> Sorry. I remove my question so far)))
>> >>
>> >> Thanks,
>> >> -Alexey
>> >>
>> >> 25.04.2018 15:40, Aleksandr Sokolovskii пишет:
>> >> > Hi Alexey,
>> >> >
>> >> >> Seems an important missed part is complex objects support.
>> >> >> And it's the most difficult part.
>> >> > Yes, you are absolutely right.
>> >> > Complex object and binary types are not supported by my client now.
>> >> > That’s why I’m here.
>> >> > I plan to come back to this subject in the beginning of May.
>> >> > I very much count on the community help.
>> >> >
>> >> >> Also, do you have a working example for SQL Query which first inserts
>> >> >> cache entries and then selects them and successfully get the same
>> >> values
>> >> >> which were inserted ?
>> >> > Yes, it works fine.
>> >> > This one:
>> >> > https://github.com/amsokol/ignite-go-client/blob/master/bina
>> >> ry/v1/client-sql-and-scan-queries_test.go#L89
>> >> > It’s OP_QUERY_SQL_FIELDS operation unit test.
>> >> > It you are familiar with Go it’s easy to run in debug mode.
>> >> >
>> >> > If you explain me your problem I can try to help you.
>> >> > There some mistakes in binary protocol documentation.
>> >> > So I spent a lot of time in Apache Ignite server source code analyzing
>> >> )))
>> >> >
>> >> > Thanks,
>> >> > Aleksandr
>> >> >
>> >> > From: Alexey Kosenchuk
>> >> > Sent: 25 апреля 2018 г. 12:05
>> >> > To: dev@ignite.apache.org
>> >> > Subject: Re: Apache Ignite 2.4+ Go language client
>> >> >
>> >> > Hi Aleksandr,
>> >> >
>> >> > Seems an important missed part is complex objects support.
>> >> > And it's the most difficult part.
>> >> > Actually, it is not possible to implement it correctly basing on the
>> >> > current protocol spec only.
>> >> > If you decide to support it, you should either wait for an updated
>> spec
>> >> > or ask for help.
>> >> >
>> >> > The issues against the current protocol spec are summarized in
>> >> > IGNITE-8039 [1] and IGNITE-8212 [2]. One more jira with the issues
>> >> > against the rest of the spec will be submitted soon.
>> >> > If you see more issues, please feel free to added them as comments to
>> >> > that jiras.
>> >> >
>> >> > Also, do you have a working example for SQL Query which first inserts
>> >> > cache entries and then selects them and 

[GitHub] ignite pull request #3651: IGNITE-7963 Update JavaDoc on data streamer

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4018: IGNITE-8423 Control utility may block when joinin...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Apache Ignite 2.5 release

[Denis Magda]

Alexey,

Makes sense to merge.

--
Denis

On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Denis,
>
> The issue with page corruption may manifest itself when a node is stopped
> during partition eviction (basically, a random chance on topology change
> scenario).
>
> The issue with WAL iterator can manifest during historical rebalancing
> (this is less likely than the previous issue).
>
> 2018-05-17 18:07 GMT+03:00 Denis Magda :
>
> > We keep facing the issues that postpone the release over and over again
> > which seems like a never-ending story.
> >
> > What are the changes the users come across the 2 latest bugs you've
> > mentioned (any special conditions)?
> >
> > What's the overall state of our testing cycles? When would we send the
> > release for vote if include the abovementioned bugs or move them to the
> > next release?
> >
> > --
> > Denis
> >
> > On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > Another issue that may lead to incorrect recovery on node startup is
> > > https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
> > PA.
> > > I
> > > suggest we also include it to 2.5 given that fix improves stability of
> > the
> > > persistence layer. Any objections?
> > >
> > > 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
> > >
> > > > Andrey, Igniters,
> > > >
> > > > I bumped into this issue while trying to reproduce another:
> > > > https://issues.apache.org/jira/browse/IGNITE-8320
> > > > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > > > AssertionError on persistence level is really undesirable for Ignite
> > as a
> > > > product.
> > > >
> > > > Best Regards,
> > > > Ivan Rakov
> > > >
> > > >
> > > > On 14.05.2018 15:59, Andrey Gura wrote:
> > > >
> > > >> Igniters,
> > > >>
> > > >> we are ready to start process of releasing Apache Ignite 2.5.
> > > >>
> > > >> So code freeze. No more commits to ignite-2.5 branch.
> > > >>
> > > >> Thanks!
> > > >>
> > > >>
> > > >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
> > wrote:
> > > >>
> > > >>> Igniters,
> > > >>>
> > > >>> Almost all issues for Apache Ignite 2.5 release are fixed. Issues
> > that
> > > >>> are still in Open state will be moved to 2.6 release.
> > > >>>
> > > >>> Code freeze for ignite-2.5 branch is planed for tomorrow.
> > > >>>
> > > >>> Thanks!
> > > >>>
> > > >>> On Tue, May 8, 2018 at 7:09 PM, Andrey Gura 
> > wrote:
> > > >>>
> > >  Thanks for fast update, Ivan.
> > > 
> > >  On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov  >
> > >  wrote:
> > > 
> > > > Andrey,
> > > >
> > > > Sorry to disturb you again. I have a follow up fix for
> IGNITE-8429
> > -
> > > > https://issues.apache.org/jira/browse/IGNITE-8453.
> > > > Please merge it to master and ignite-2.5.
> > > >
> > > > Best Regards,
> > > > Ivan Rakov
> > > >
> > > >
> > > > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> > > >
> > > >> H2 version updated is moved to AI 2.6. There are several serious
> > > >> problems,
> > > >> main - spatial dependency replacement which is a breaking
> change.
> > > >>
> > > >> On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn <
> > > ptupit...@apache.org
> > > >> >
> > > >> wrote:
> > > >>
> > > >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> > > >>>
> > > >>> Thank you, Andrey!
> > > >>>
> > > >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  >
> > > >>> wrote:
> > > >>>
> > > >>> Pavel,
> > > 
> > >  issue is targeted to release 2.5 now. Thanks!
> > > 
> > >  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
> > >  ptupit...@apache.org>
> > >  wrote:
> > > 
> > > > Igniters,
> > > >
> > > > There is an unpleasant bug in .NET [1]:
> > > > Services do not work at all on .NET Core and sometimes on
> > classic
> > > > .NET.
> > > >
> > > > I'm almost done with the fix and I think we should include it
> > in
> > > > 2.5.
> > > >
> > >  Users
> > > 
> > > > are complaining [2].
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > > > [2]
> > > > http://apache-ignite-users.70518.x6.nabble.com/Re-
> > > >
> > >  Service-Grid-and-net-core-2-td21318.html
> > > 
> > > > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > > > voze...@gridgain.com>
> > > > wrote:
> > > >
> > > > Andrey,
> > > >>
> > > >> I realized that we missed one very important thing - H2
> > version
> > > >>
> > > > upgrade
> > > >>>
> > >  [1]. This is very 

Re: Apache Ignite 2.4+ Go language client

[Aleksandr Sokolovskii]

Hi Igor,

Of course I am ready to donate code.

You have to know that GitHub is source code repo and package repo for build
for Go lang.
I see that .NET client is deep inside Apache Ignite source code structure.
It's not very comfortable for Go lang developers.
It's best practice when each Go lang library/project has own GitHub repo.

What do you think to create Apache Ignite "organization" in GitHub and
consolidate all source code.
Here is example of CockroachDB project:
https://github.com/cockroachdb


Thanks,
Aleksandr

On 17 May 2018 at 17:21, Igor Sapego  wrote:

> By the way, Alexandr,
>
> Do you want to donate your client to Apache Ignite, so we
> are going to include it in our release, or would you prefer
> keep it separate?
>
>
> Best Regards,
> Igor
>
> On Thu, May 10, 2018 at 1:09 PM, Igor Sapego  wrote:
>
> > Aleksandr,
> > I'm currently working on the improvement of the doc, so please,
> > feel free to participate with review and proposals here - [1].
> >
> > [1] -https://issues.apache.org/jira/browse/IGNITE-8039
> >
> > Best Regards,
> > Igor
> >
> > On Tue, May 8, 2018 at 3:47 PM, Aleksandr Sokolovskii  >
> > wrote:
> >
> >> Hi Alexey,
> >>
> >> I spent some time and fully implemented OP_QUERY_SQL and
> >> OP_QUERY_SQL_CURSOR_GET_PAGE including unit tests.
> >> The OP_QUERY_SQL returns value as complex object (code=103) wrapped by
> >> array (code=27).
> >> But it’s not the end of the story. )))
> >> Complex object is marshalled in different way than described in
> >> documentation.
> >>
> >> Example how to unmarshall complex object of several formats:
> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> ry/v1/types.go#L969
> >>
> >> Unit test for OP_QUERY_SQL:
> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> ry/v1/client-sql-and-scan-queries_test.go#L9
> >>
> >> Unit test for OP_QUERY_SQL_CURSOR_GET_PAGE:
> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> ry/v1/client-sql-and-scan-queries_test.go#L80
> >>
> >> Thanks,
> >> Aleksandr
> >>
> >> From: Alexey Kosenchuk
> >> Sent: 25 апреля 2018 г. 16:33
> >> To: dev@ignite.apache.org
> >> Subject: Re: Apache Ignite 2.4+ Go language client
> >>
> >> No problem with OP_QUERY_SQL_FIELDS.
> >> I mean OP_QUERY_SQL.
> >> But I overlooked "OP_QUERY_SQL - Done without unit test. Need help to
> >> develop unit test."
> >> Sorry. I remove my question so far)))
> >>
> >> Thanks,
> >> -Alexey
> >>
> >> 25.04.2018 15:40, Aleksandr Sokolovskii пишет:
> >> > Hi Alexey,
> >> >
> >> >> Seems an important missed part is complex objects support.
> >> >> And it's the most difficult part.
> >> > Yes, you are absolutely right.
> >> > Complex object and binary types are not supported by my client now.
> >> > That’s why I’m here.
> >> > I plan to come back to this subject in the beginning of May.
> >> > I very much count on the community help.
> >> >
> >> >> Also, do you have a working example for SQL Query which first inserts
> >> >> cache entries and then selects them and successfully get the same
> >> values
> >> >> which were inserted ?
> >> > Yes, it works fine.
> >> > This one:
> >> > https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> ry/v1/client-sql-and-scan-queries_test.go#L89
> >> > It’s OP_QUERY_SQL_FIELDS operation unit test.
> >> > It you are familiar with Go it’s easy to run in debug mode.
> >> >
> >> > If you explain me your problem I can try to help you.
> >> > There some mistakes in binary protocol documentation.
> >> > So I spent a lot of time in Apache Ignite server source code analyzing
> >> )))
> >> >
> >> > Thanks,
> >> > Aleksandr
> >> >
> >> > From: Alexey Kosenchuk
> >> > Sent: 25 апреля 2018 г. 12:05
> >> > To: dev@ignite.apache.org
> >> > Subject: Re: Apache Ignite 2.4+ Go language client
> >> >
> >> > Hi Aleksandr,
> >> >
> >> > Seems an important missed part is complex objects support.
> >> > And it's the most difficult part.
> >> > Actually, it is not possible to implement it correctly basing on the
> >> > current protocol spec only.
> >> > If you decide to support it, you should either wait for an updated
> spec
> >> > or ask for help.
> >> >
> >> > The issues against the current protocol spec are summarized in
> >> > IGNITE-8039 [1] and IGNITE-8212 [2]. One more jira with the issues
> >> > against the rest of the spec will be submitted soon.
> >> > If you see more issues, please feel free to added them as comments to
> >> > that jiras.
> >> >
> >> > Also, do you have a working example for SQL Query which first inserts
> >> > cache entries and then selects them and successfully get the same
> values
> >> > which were inserted ?
> >> >
> >> > Thanks,
> >> > -Alexey
> >> >
> >> > [1] https://issues.apache.org/jira/browse/IGNITE-8039
> >> > [2] https://issues.apache.org/jira/browse/IGNITE-8212
> >> >
> >> > 25.04.2018 0:11, Aleksandr Sokolovskii пишет:
> >> >> ...forgot OP_RESOURCE_CLOSE that is implemented 

Re: Apache Ignite 2.4+ Go language client

[Aleksandr Sokolovskii]

Hi,

This guy had made last commit in https://github.com/apacheignite repo Nov
2017:
https://github.com/TikhonovNikolay?tab=repositories

May be hi is from GridGane...

Thanks,
Aleksandr

On 17 May 2018 at 21:27, Vyacheslav Daradur  wrote:

> Hi, there is such GitHub profile:
> https://github.com/apacheignite
>
> But I don't know who manage that.
>
> On Thu, May 17, 2018 at 9:22 PM, Aleksandr Sokolovskii
>  wrote:
> > Hi Igor,
> >
> > Of course I am ready to donate code.
> >
> > You have to know that GitHub is source code repo and package repo for
> build
> > for Go lang.
> > I see that .NET client is deep inside Apache Ignite source code
> structure.
> > It's not very comfortable for Go lang developers.
> > It's best practice when each Go lang library/project has own GitHub repo.
> >
> > What do you think to create Apache Ignite "organization" in GitHub and
> > consolidate all source code.
> > Here is example of CockroachDB project:
> > https://github.com/cockroachdb
> >
> >
> > Thanks,
> > Aleksandr
> >
> > On 17 May 2018 at 17:21, Igor Sapego  wrote:
> >
> >> By the way, Alexandr,
> >>
> >> Do you want to donate your client to Apache Ignite, so we
> >> are going to include it in our release, or would you prefer
> >> keep it separate?
> >>
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Thu, May 10, 2018 at 1:09 PM, Igor Sapego 
> wrote:
> >>
> >> > Aleksandr,
> >> > I'm currently working on the improvement of the doc, so please,
> >> > feel free to participate with review and proposals here - [1].
> >> >
> >> > [1] -https://issues.apache.org/jira/browse/IGNITE-8039
> >> >
> >> > Best Regards,
> >> > Igor
> >> >
> >> > On Tue, May 8, 2018 at 3:47 PM, Aleksandr Sokolovskii <
> amso...@gmail.com
> >> >
> >> > wrote:
> >> >
> >> >> Hi Alexey,
> >> >>
> >> >> I spent some time and fully implemented OP_QUERY_SQL and
> >> >> OP_QUERY_SQL_CURSOR_GET_PAGE including unit tests.
> >> >> The OP_QUERY_SQL returns value as complex object (code=103) wrapped
> by
> >> >> array (code=27).
> >> >> But it’s not the end of the story. )))
> >> >> Complex object is marshalled in different way than described in
> >> >> documentation.
> >> >>
> >> >> Example how to unmarshall complex object of several formats:
> >> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> >> ry/v1/types.go#L969
> >> >>
> >> >> Unit test for OP_QUERY_SQL:
> >> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> >> ry/v1/client-sql-and-scan-queries_test.go#L9
> >> >>
> >> >> Unit test for OP_QUERY_SQL_CURSOR_GET_PAGE:
> >> >> https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> >> ry/v1/client-sql-and-scan-queries_test.go#L80
> >> >>
> >> >> Thanks,
> >> >> Aleksandr
> >> >>
> >> >> From: Alexey Kosenchuk
> >> >> Sent: 25 апреля 2018 г. 16:33
> >> >> To: dev@ignite.apache.org
> >> >> Subject: Re: Apache Ignite 2.4+ Go language client
> >> >>
> >> >> No problem with OP_QUERY_SQL_FIELDS.
> >> >> I mean OP_QUERY_SQL.
> >> >> But I overlooked "OP_QUERY_SQL - Done without unit test. Need help to
> >> >> develop unit test."
> >> >> Sorry. I remove my question so far)))
> >> >>
> >> >> Thanks,
> >> >> -Alexey
> >> >>
> >> >> 25.04.2018 15:40, Aleksandr Sokolovskii пишет:
> >> >> > Hi Alexey,
> >> >> >
> >> >> >> Seems an important missed part is complex objects support.
> >> >> >> And it's the most difficult part.
> >> >> > Yes, you are absolutely right.
> >> >> > Complex object and binary types are not supported by my client now.
> >> >> > That’s why I’m here.
> >> >> > I plan to come back to this subject in the beginning of May.
> >> >> > I very much count on the community help.
> >> >> >
> >> >> >> Also, do you have a working example for SQL Query which first
> inserts
> >> >> >> cache entries and then selects them and successfully get the same
> >> >> values
> >> >> >> which were inserted ?
> >> >> > Yes, it works fine.
> >> >> > This one:
> >> >> > https://github.com/amsokol/ignite-go-client/blob/master/bina
> >> >> ry/v1/client-sql-and-scan-queries_test.go#L89
> >> >> > It’s OP_QUERY_SQL_FIELDS operation unit test.
> >> >> > It you are familiar with Go it’s easy to run in debug mode.
> >> >> >
> >> >> > If you explain me your problem I can try to help you.
> >> >> > There some mistakes in binary protocol documentation.
> >> >> > So I spent a lot of time in Apache Ignite server source code
> analyzing
> >> >> )))
> >> >> >
> >> >> > Thanks,
> >> >> > Aleksandr
> >> >> >
> >> >> > From: Alexey Kosenchuk
> >> >> > Sent: 25 апреля 2018 г. 12:05
> >> >> > To: dev@ignite.apache.org
> >> >> > Subject: Re: Apache Ignite 2.4+ Go language client
> >> >> >
> >> >> > Hi Aleksandr,
> >> >> >
> >> >> > Seems an important missed part is complex objects support.
> >> >> > And it's the most difficult part.
> >> >> > Actually, it is not possible to implement it correctly basing on
> the
> >> >> > current protocol spec only.
> >> >> > If you 

Baseline topology documentation clarified: usage scenarios and definition

[Denis Magda]

Igniters,

With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
baseline topology documentation much better and vivid. Check up the new
sections that did a better job explaining the topology, cover common usage
scenarious and explain how to trigger the rebalancing programmatically if
it's not expected that the baseline topology's node count to be recovered
soon:

   -
   
https://apacheignite.readme.io/v2.4/docs/cluster-activation#section-baseline-topology
   -
   
https://apacheignite.readme.io/v2.4/docs/cluster-activation#section-usage-scenarios
   -
   
https://apacheignite.readme.io/v2.4/docs/cluster-activation#section-triggering-rebalancing-programmatically

--
Denis

Fwd: control.bat authentication support

[Denis Magda]

That's a good point.

Taras, Vladimir, as those who contributed the authentication could you
schedule this improvement for future releases?

Oleksandr, as for now, please use your own version of the script. Moreover,
you can update the existing scripts and ask the community to accept your
changes to the main repository.

--
Denis
-- Forwarded message --
From: Olexandr K 
Date: Thu, May 17, 2018 at 7:09 AM
Subject: control.bat authentication support
To: u...@ignite.apache.org


Hi guys,

I configured Ignite user/password authentication by adding custom plugin.
It works fine in server/client nodes and visor but I can't find any auth
support in control.bat
I checked it's source code and don't see any place where I can provide
credentials.

Should I write my own control tool or how can I solve this?

BR, Oleksandr

[jira] [Created] (IGNITE-8524) Document consistency check utilities

[Denis Magda (JIRA)]

Denis Magda created IGNITE-8524:
---

 Summary: Document consistency check utilities
 Key: IGNITE-8524
 URL: https://issues.apache.org/jira/browse/IGNITE-8524
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.5


Ignite 2.5 will go with special consistency check utilities that, for instance, 
ensure that the data stays consistent across backups, indexes are correct and 
many other things. More details can be taken from here:
* https://issues.apache.org/jira/browse/IGNITE-8277
* https://issues.apache.org/jira/browse/IGNITE-7467

Here is an empty page that is created for the documentation: 
https://apacheignite.readme.io/docs/consistency-check-utilities



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)