[jira] [Created] (IGNITE-7292) Optimize Ignite main page load performance

2017-12-22 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-7292:
---

 Summary: Optimize Ignite main page load performance
 Key: IGNITE-7292
 URL: https://issues.apache.org/jira/browse/IGNITE-7292
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Prachi Garg
Priority: Blocker
 Fix For: 2.4
 Attachments: Screen Shot 2017-12-22 at 9.49.02 AM.png

Ignite main page load performance is poor - takes from 3 to 5 seconds to load 
in completely. That might affect the SEO optimizations we've done so far. These 
are immediate actions to alleviate the situation: 
# Reduce banner and all the images size to 72 ppi resolution and save in the 
JPG format. Use photoshop "Image Size" dialog. The banner and thumbnails of 
screencasts were already changed, just need to regenerate the CSS and merge the 
patch.
# The next fierce contributors to the poor performance are screencasts youtube 
video. It takes 700ms for each screencast to make a roundtrip to YouTube. See 
the screenshot attached where 3 base.js calls are triggered by the video links. 
This has to be done asynchronously.
# Preload GitHub, Twitter butter and feed asynchronously too.

The overall goal of this optimization is to speed up the loading to 2.5 seconds 
(no more).




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


Re: Create cache using thin protocol

2017-12-22 Thread Denis Magda
Pavel, thanks for a quick turnaround. Please ping Prachi when you merge the 
improvement so that she can update the readme doc.

—
Denis

> On Dec 22, 2017, at 4:43 AM, Pavel Tupitsyn  wrote:
> 
> Ticket created: https://issues.apache.org/jira/browse/IGNITE-7288
> I'll implement this next week.
> 
> On Fri, Dec 22, 2017 at 10:06 AM, Pavel Tupitsyn 
> wrote:
> 
>> Hi Denis,
>> 
>> I think we can assign an id to each parameter. It is not difficult to add.
>> 
>>> not to tell about this operation
>> Hiding stuff is not a good approach. Any decent engineer will have a look
>> at the server code and see it.
>> 
>> Pavel
>> 
>> On Fri, Dec 22, 2017 at 3:45 AM, Denis Magda  wrote:
>> 
>>> Hi Pavel,
>>> 
>>> If it’s supposed to be used this way then it’s better not to tell about
>>> this operation at all until it’s simplified from a user standpoint.
>>> 
>>> My suggestion would be to design the operation so that I can pass only
>>> those configuration parameters that need to be different from the defaults.
>>> How difficult is this and can the improvement go into 2.4?
>>> 
>>> —
>>> Denis
>>> 
 On Dec 20, 2017, at 10:48 PM, Pavel Tupitsyn 
>>> wrote:
 
 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-co
>>> nnector-#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.BinaryAbstractInpu
>>> tStream.ensureEnoughData(BinaryAbstractInputStream.java:305)
> at org.apache.ignite.internal.binary.streams.BinaryAbstractInpu
>>> tStream.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(ClientCacheConfigura
>>> tionSerializer.java:125)
> at org.apache.ignite.internal.processors.platform.client.cache.
>>> ClientCacheCreateWithConfigurationRequest.(ClientCache
>>> CreateWithConfigurationRequest.java:45)
> at org.apache.ignite.internal.processors.platform.client.Client
>>> MessageParser.decode(ClientMessageParser.java:333)
> at org.apache.ignite.internal.processors.platform.client.Client
>>> MessageParser.decode(ClientMessageParser.java:220)
> at org.apache.ignite.internal.processors.odbc.ClientListenerNio
>>> Listener.onMessage(ClientListenerNioListener.java:119)
> at org.apache.ignite.internal.processors.odbc.ClientListenerNio
>>> Listener.onMessage(ClientListenerNioListener.java:40)
> at org.apache.ignite.internal.util.nio.GridNioFilterChain$TailF
>>> ilter.onMessageReceived(GridNioFilterChain.java:279)
> at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.pro
>>> ceedMessageReceived(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(GridWo

Re: Ignite Committership Bar Guidance

2017-12-22 Thread Denis Magda
Hi Vyacheslav,

Some common sense, I presume. A committer who will be proposing a candidate can 
use JIRA to see a total number of resolved tickets and Git history to get 
insights on a complexity of every contribution.

Do you have any suggestions on this?

—
Denis

> On Dec 22, 2017, at 12:56 AM, Vyacheslav Daradur  wrote:
> 
> Hi, Denis, how will the complexity of tasks be estimated?
> 
> 
> On Fri, Dec 22, 2017 at 3:16 AM, Denis Magda  wrote:
>> Igniters,
>> 
>> We at Ignite PMC put together a page with rules-of-thumb on when it’s a 
>> right time to promote a contributor to a committer:
>> https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance
>>  
>> 
>> 
>> It’s intended to make “contributor to committer” process more evident and 
>> simplify Ignite PMC voting process on this matter.
>> 
>> Please use it as a reference, comments and suggestions are welcomed!
>> 
>> —
>> Denis
> 
> 
> 
> -- 
> Best Regards, Vyacheslav D.



[jira] [Created] (IGNITE-7291) Apache Ignite "in use at" section

2017-12-22 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-7291:
---

 Summary: Apache Ignite "in use at" section
 Key: IGNITE-7291
 URL: https://issues.apache.org/jira/browse/IGNITE-7291
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 2.4


Put together a list of publicly disclosed Apache Ignite use cases and present 
them on the main page right below the benefits. The "Ignite is in use at" 
section might be like Cassandra's "PROVEN" section:
http://cassandra.apache.org

A list of the known use cases:
* 
https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
* 
https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
* https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
* https://youtu.be/1D8hyLWMtfM
* 
https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations




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


[jira] [Created] (IGNITE-7290) Log when partition is moved to a LOST state

2017-12-22 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-7290:


 Summary: Log when partition is moved to a LOST state
 Key: IGNITE-7290
 URL: https://issues.apache.org/jira/browse/IGNITE-7290
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Priority: Critical
 Fix For: 2.4






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


[jira] [Created] (IGNITE-7289) ODBC: add possibility to reconnect to the cluster after node failing

2017-12-22 Thread Evgenii Zhuravlev (JIRA)
Evgenii Zhuravlev created IGNITE-7289:
-

 Summary: ODBC: add possibility to reconnect to the cluster after 
node failing
 Key: IGNITE-7289
 URL: https://issues.apache.org/jira/browse/IGNITE-7289
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev
Assignee: Igor Sapego






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


[GitHub] ignite pull request #3279: ignite-2.4.2

2017-12-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request:

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

ignite-2.4.2



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

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

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

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


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 

[GitHub] ignite pull request #3246: IGNITE-7174: Local MLP

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] ignite pull request #3278: Ignite 2.1.10

2017-12-22 Thread apopovgg
GitHub user apopovgg opened a pull request:

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

Ignite 2.1.10



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

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

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

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


commit be60c08687f873a278d882666b61d60af7c0205c
Author: dpavlov 
Date:   2017-09-19T12:23:18Z

IGNITE-6428 Fixed IgniteOOME in PDS Indexing suite (increased memory policy 
size) - Fixes #2690.

Signed-off-by: Alexey Goncharuk 

commit 718e365f47bb5c91bc910854a7626b1933c83e59
Author: Igor Sapego 
Date:   2017-09-19T13:23:54Z

IGNITE-6099: ODBC: Implemented SQLGetInfo for all info types. This closes 
#2689.

commit 915682bd5facee9dd62fc5d6dfb35e37ff601db8
Author: Pavel Tupitsyn 
Date:   2017-09-19T13:32:07Z

IGNITE-6399 .NET: Added ClientConnectorConfiguration. This closes #2696.

commit 433879963db63103ba597e67e703f6ab7d3c64e1
Author: vsisko 
Date:   2017-09-19T17:10:46Z

IGNITE-6431 Web console: Fixed duplicate "Partition loss policy" field.
(cherry picked from commit 2299589)

commit 6318c1a15f05e952c22e42e6e238816d7ffdb0ca
Author: vsisko 
Date:   2017-09-20T10:19:58Z

IGNITE-6376 Web console: Enable task and job events in demo mode by default.
(cherry picked from commit ff17783)

commit 668e29fa2766ad5f0fda829e027b777407d9ca4f
Author: vsisko 
Date:   2017-09-20T10:27:14Z

IGNITE-6304 Fixed script execution after throttling interval.
(cherry picked from commit d1f178f)

commit 4e38b792517ff182391b78821937db57353a7388
Author: Dmitriy Shabalin 
Date:   2017-09-20T12:00:09Z

IGNITE-6435 Web Console: Added version to footer.
(cherry picked from commit 3c75184)

commit 1a6461582eac95e1e51faf8acd9b8bd10394dd47
Author: vsisko 
Date:   2017-09-20T12:07:55Z

IGNITE-6449 Added missing cache configuration properties.
(cherry picked from commit 9b2bca7)

commit bd60ab1fa6aaf433849e8a052af41a2a333c7904
Author: Pavel Tupitsyn 
Date:   2017-09-20T13:49:49Z

IGNITE-6250 .NET: Thin client: Basic exception handling

This closes #2698

commit 58ba0d229476b502241940e474c25f0d895c
Author: Ilya Borisov 
Date:   2017-09-21T03:25:19Z

IGNITE-6446 Fix permission transition hook and permissions for basic 
configuration screen.
(cherry picked from commit 0f8a2bf)

commit 3847b47752db7d83c85a76e09964fd154e2f0cc4
Author: Alexey Kuznetsov 
Date:   2017-09-21T07:36:08Z

IGNITE-6461 Web Console: Sanitize user on save.
(cherry picked from commit 1b6873c)

commit 931320f6ded6f927931c6dca2b9ed6795632365c
Author: tledkov-gridgain 
Date:   2017-09-21T11:40:13Z

IGNITE-6457: JDBC thin driver: now schema in URL string is case-insensitive 
by default. This closes #2712.

commit b6d570fb0d5cc5638f857a5aa463600a942fbba0
Author: Alexey Goncharuk 
Date:   2017-09-21T13:37:42Z

IGNITE-6342 Fixed exchange hanging on eviction when partition is lost

commit f5ff60eb72cf6bf55511b2c73f841eb50af59526
Author: Alexey Kuznetsov 
Date:   2017-09-21T14:13:59Z

Web Console: minor refactoring.
(cherry picked from commit abe4ee8)

commit 099d33ceaee8bb8b3edbd1bee91a580572537e45
Author: tledkov-gridgain 
Date:   2017-09-21T14:46:47Z

IGNITE-6448: Fixed a bug causing stale SQL statement to reside in cache 
after ALTER TABLE command. This closes #2702.

commit be8afd4f39599b7e26ad148331c5aa6ba4faf513
Author: tledkov-gridgain 
Date:   2017-09-21T14:51:26Z

IGNITE-6465: JDBC thin driver: added SQLSTATE propagation for 
BatchUpdateException. This closes #2719.

commit 111d8abbe6ec7710c7f0e7ebe6d43f3ccb904dcb
Author: Alexei Scherbakov 
Date:   2017-09-21T14:40:16Z

IGNITE-6228 Avoid closing page store by thread interruption. Fixes #2715

commit aeb4aeaef44ff7abc152f3942dee9e40086bc69c
Author: EdShangGG 
Date:   2017-09-21T15:36:37Z

ignite-6470 Fixed wrong casting og long value to int

Signed-off-by: Andrey Gura 

(cherry picked from commit b98ffab)

commit 21d7fed8a43ba4606eaf850438fc39fcc3223d1c
Author: Alexander Paschenko 
Date:   2017-09-21T15:51:18Z

IGNITE-6316: SQL: fixed CacheConfiguration persistence logic for DDL 
operations. This closes #2701.

commit e82f077df78972a58fdd06917839445711432705
Author: Dmitriy Govorukhin 
Date:   2017-09-21T15:56:40Z

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


[GitHub] ignite pull request #3277: ignite-6952 fix DirectByteBufferStreamImplV2#read...

2017-12-22 Thread dmekhanikov
GitHub user dmekhanikov opened a pull request:

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

ignite-6952 fix DirectByteBufferStreamImplV2#readArrayLE()



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

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

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

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


commit 10a9588fabc9aee5225ae8b32232fe28fc24d9f0
Author: Denis Mekhanikov 
Date:   2017-12-22T14:26:12Z

ignite-6952 fix reading of arrays by DirectByteBufferStreamImplV2 for 
big-endian architectures




---


[GitHub] ignite pull request #3276: Ignite 2.3.2

2017-12-22 Thread AMashenkov
GitHub user AMashenkov opened a pull request:

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

Ignite 2.3.2



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

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

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

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


commit c5d6decfaf4c8be907975531f7d7bd41dda2da4e
Author: dpavlov 
Date:   2017-10-04T06:46:16Z

IGNITE-6285 Enhance persistent store paths handling - Fixes #2775.

Signed-off-by: Alexey Goncharuk 

commit 2e013fbe85da059580e97d57c15e9cbc92c0aa54
Author: dpavlov 
Date:   2017-10-04T12:05:48Z

IGNITE-6554 Atomic cache remove operations are not logged to WAL - Fixes 
#2800.

Signed-off-by: Alexey Goncharuk 

commit 959bf853b1a77fa674ac8115fcf57c31feb0e6c0
Author: oleg-ostanin 
Date:   2017-10-04T14:35:50Z

Removed excluding ML from examples/src

(cherry picked from commit 78f77b1)

commit d4e5d4fd3e989b69f7bfa49986ee8f8d04cac62f
Author: tledkov-gridgain 
Date:   2017-10-05T08:55:26Z

IGNITE-6529 JDBC: support column metadata 'nullable' property. This closes 
#2793.

commit 81d20410205086ff29ac2e66b7cd17909173d642
Author: tledkov-gridgain 
Date:   2017-10-05T13:32:33Z

IGNITE-6358: JDBC thick: support multiple statements. This closes #2777.

commit 2e046d61078874c12e4fd33bba0826f5453b055d
Author: tledkov-gridgain 
Date:   2017-10-05T13:45:31Z

IGNITE-6556: JDBC thin: fixed setSchema() case sensitivity handling. This 
closes #2805.

commit 62b4b5311109af1f4ac0ae84ac47ad885eaa3533
Author: Alexey Goncharuk 
Date:   2017-10-05T14:37:04Z

IGNITE-5739 Fixed Ignite node crash on deactivation

commit b33be44164d4dc4948ab5c27857d53b75ac4a332
Author: Vasiliy Sisko 
Date:   2017-10-06T07:25:42Z

IGNITE-6287 Web Console: Improved DDL support.
(cherry picked from commit 2410f07)

commit 6c4c41d4ce6f2066a399756f60f798507e0553ad
Author: Alexey Kuznetsov 
Date:   2017-10-06T10:00:39Z

IGNITE-6570 Web Console: Move parsing of JSON to pool of workers.
(cherry picked from commit 74f0400)

commit 6efb0cee753eac1289efd21cc773ca372775aa68
Author: Pavel Tupitsyn 
Date:   2017-10-03T15:33:57Z

.NET: Fix TestRecordLocal

commit fca198bf1ecd4eee8bb72233cd59d0ea2e427c7c
Author: Alexander Paschenko 
Date:   2017-10-06T15:04:44Z

IGNITE-6054: SQL: implemented "WRAP_KEY" and "WRAP_VALUE" modes for CREATE 
TABLE. This closes #2784.

commit 73f092df4792bee918083322ee93026dfa95e3b8
Author: devozerov 
Date:   2017-10-09T07:48:06Z

Fixed JavaDoc.

commit 81b16ada108dc497d38f702b7f678de539345705
Author: devozerov 
Date:   2017-10-09T08:34:51Z

Fixed JavaDoc again.

commit d9f0f4e1bec08ab9f52c6c1ba842524f25a4ba19
Author: devozerov 
Date:   2017-10-09T08:57:06Z

IGNITE-6054: Fixed tests.

commit 9358a88538189e48de68ad2d157c2c1ebf9a219e
Author: tledkov-gridgain 
Date:   2017-10-09T12:14:23Z

IGNITE-6529: JDBC thin: fixed driver protocol compatibility. This closes 
#2819.

commit c4acf54413a0e8cb9cedcb7201084f29ee554ee7
Author: Vasiliy Sisko 
Date:   2017-10-09T12:23:23Z

IGNITE-6287 Web Console: Improved DDL support: added checkbox "Use selected 
cache as default schema name".
(cherry picked from commit a45677c)

commit 831c4d9635c911fde3781987f79a28523d6cf15b
Author: Pavel Tupitsyn 
Date:   2017-10-09T14:33:46Z

IGNITE-6397 .NET thin client: basic cache operations. This closes #2725.

commit 1a6bb2bbf513c8a50f81e9f8def1b3f479c08f4b
Author: Andrey Gura 
Date:   2017-09-27T10:50:26Z

ignite-6305 Ignite update checker enabled

commit 72b409cc233919462b3df1547afdec082d8273e1
Author: Alexander Paschenko 
Date:   2017-10-09T19:17:28Z

IGNITE-6569: Fixed hang when trying to execute "DROP TABLE" on the cache 
this table belongs to. This closes #2823.

commit ab384d4b1692538eca6de81c04ec9b720a73308e
Author: Alexander Paschenko 
Date:   2017-10-10T07:05:12Z

IGNITE-6568: Fixed cache configuration persistence logic. This closes #2815.

commit f06927d13303b780bcb9865a3eea9c95b926a25e
Author: Sergey Chugunov 
Date:   2017-10-09T15:35:11Z

IGNITE-6583 Proper getters for rebalance metrics were added; ignite-style 
getters (without get) were deprecated

Signed-off-by: Andrey Gura 

commit 4a782fb8b8f10917addecd70af77049719f908bd
Author: Alexander Belyak 
Date:   2017-10-10T12:09:30Z


[GitHub] ignite pull request #3275: Ignite 2.3 master

2017-12-22 Thread AMashenkov
GitHub user AMashenkov opened a pull request:

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

Ignite 2.3 master



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

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

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

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


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:   

Re: IGNITE-7107 Apache Ignite RPM packages

2017-12-22 Thread Ilya Kasnacheev
Hello!

I have reviewed your code and commented IGNITE-7107 for a list of potential
problem.

I think everything from the first "blocker" section ought to be fixed
before this patch is merged, while "nice to have" things may be spinned out
as separate tickets. I suggest moving scripts that don't work with
non-writable JAVA_HOME to examples section. This will likely include
benchmarks, which I didn't try (but suggest you to).

Regards,
-- 
Ilya Kasnacheev

2017-12-19 13:23 GMT+03:00 vveider :

> Done. See updated PR#3171 [1]
>
>
> [1] https://github.com/apache/ignite/pull/3171
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


[GitHub] ignite pull request #3187: IGNITE-7109 .NET: Thin client: Async cache operat...

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---


Re: Create cache using thin protocol

2017-12-22 Thread Pavel Tupitsyn
Ticket created: https://issues.apache.org/jira/browse/IGNITE-7288
I'll implement this next week.

On Fri, Dec 22, 2017 at 10:06 AM, Pavel Tupitsyn 
wrote:

> Hi Denis,
>
> I think we can assign an id to each parameter. It is not difficult to add.
>
> > not to tell about this operation
> Hiding stuff is not a good approach. Any decent engineer will have a look
> at the server code and see it.
>
> Pavel
>
> On Fri, Dec 22, 2017 at 3:45 AM, Denis Magda  wrote:
>
>> Hi Pavel,
>>
>> If it’s supposed to be used this way then it’s better not to tell about
>> this operation at all until it’s simplified from a user standpoint.
>>
>> My suggestion would be to design the operation so that I can pass only
>> those configuration parameters that need to be different from the defaults.
>> How difficult is this and can the improvement go into 2.4?
>>
>> —
>> Denis
>>
>> > On Dec 20, 2017, at 10:48 PM, Pavel Tupitsyn 
>> wrote:
>> >
>> > 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-co
>> nnector-#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.BinaryAbstractInpu
>> tStream.ensureEnoughData(BinaryAbstractInputStream.java:305)
>> >>  at org.apache.ignite.internal.binary.streams.BinaryAbstractInpu
>> tStream.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(ClientCacheConfigura
>> tionSerializer.java:125)
>> >>  at org.apache.ignite.internal.processors.platform.client.cache.
>> ClientCacheCreateWithConfigurationRequest.(ClientCache
>> CreateWithConfigurationRequest.java:45)
>> >>  at org.apache.ignite.internal.processors.platform.client.Client
>> MessageParser.decode(ClientMessageParser.java:333)
>> >>  at org.apache.ignite.internal.processors.platform.client.Client
>> MessageParser.decode(ClientMessageParser.java:220)
>> >>  at org.apache.ignite.internal.processors.odbc.ClientListenerNio
>> Listener.onMessage(ClientListenerNioListener.java:119)
>> >>  at org.apache.ignite.internal.processors.odbc.ClientListenerNio
>> Listener.onMessage(ClientListenerNioListener.java:40)
>> >>  at org.apache.ignite.internal.util.nio.GridNioFilterChain$TailF
>> ilter.onMessageReceived(GridNioFilterChain.java:279)
>> >>  at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.pro
>> ceedMessageReceived(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(GridWo
>> rker.java:110)
>> >>  at org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(
>> GridWorkerPool.java:70)
>> >>  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> >>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo

[jira] [Created] (IGNITE-7288) Thin client: Allow partial cache configuration

2017-12-22 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-7288:
--

 Summary: Thin client: Allow partial cache configuration
 Key: IGNITE-7288
 URL: https://issues.apache.org/jira/browse/IGNITE-7288
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


{{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
{{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
{{CacheConfiguration}}. User should be able to specify any combination of 
properties in any order, leaving others at default state.

Prefix each property with unique ID, then do a switch in a loop.



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


[GitHub] ignite pull request #3274: Ignite 1.8.17

2017-12-22 Thread dkarachentsev
GitHub user dkarachentsev opened a pull request:

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

Ignite 1.8.17



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

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

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

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


commit a609dc7a0bb2d923ecf79a25fb4c13f48eab5f5b
Author: Andrey V. Mashenkov 
Date:   2017-05-16T12:36:22Z

Merge branch 'ignite-1.8.7.b1' into ignite-1.8.7

commit 9cd7e0f8d132f9b7c496fe64f75f271ef60da5eb
Author: Alexey Kuznetsov 
Date:   2017-02-09T09:44:41Z

IGNITE-4676 Fixed hang if closure executed nested internal task with 
continuation. Added test.
(cherry picked from commit e7a5307)

commit 43bcc15127bd3fd7ac4e277da6da9e5fb6a855c0
Author: Vasiliy Sisko 
Date:   2017-03-30T04:08:10Z

IGNITE-4838 Fixed internal task detection logic. Added tests.
(cherry picked from commit ba68c6c)

commit 72882126c047b937bd5ed93c85e28262530e4977
Author: Vasiliy Sisko 
Date:   2017-03-30T04:08:10Z

IGNITE-4838 Fixed internal task detection logic. Added tests.
(cherry picked from commit ba68c6c)

commit 0d3d93cd4eeb589f1b6a11b48e429defad01c82f
Author: dkarachentsev 
Date:   2017-05-18T16:11:08Z

IGNITE-4842 Now containsKey() respects isReadFromBackup() flag.

(cherry picked from commit d84fd29)

commit 4bf9123a6cff3b1fd17e8772bb0496108fce3f5e
Author: dkarachentsev 
Date:   2017-05-18T16:13:47Z

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

commit 2a818d36395dd1af23acf444adf396b2e2edbede
Author: Konstantin Dudkov 
Date:   2017-05-22T13:28:07Z

Fixed "IGNITE-4205 CassandraCacheStore should start IiteThread threads in 
loadCache() method"

Signed-off-by: nikolay_tikhonov 

commit 04fadd4a499239176ba21c390d93e30809abb4c1
Author: dkarachentsev 
Date:   2017-05-23T12:42:20Z

IGNITE-5223 Allow use local binary metadata cache if it's possible

commit b2040b7a95e421609bcf7ae05b56dc623310b409
Author: dkarachentsev 
Date:   2017-05-23T13:14:08Z

IGNITE-5259 Minor serialization fix

commit b77428d12658b3ab2cdd43ca61ed71d329e83283
Author: sboikov 
Date:   2017-01-10T13:59:17Z

Do not evict removed entries, otherwise removes can be lost.

(cherry picked from commit 55ac6e7)

commit 29187ef6b663eafe67eaaaf38e4c09fc244ac7aa
Author: dkarachentsev 
Date:   2017-05-24T14:31:27Z

Do not evict removed entries, otherwise removes can be lost.

Rollback due to test failings.

commit 442aac2507210d39b7f30ab8f8d9a3dbe2610cae
Author: Andrey V. Mashenkov 
Date:   2017-05-24T15:32:11Z

IGNITE-5225: Fix NPE caused by changes in IGNITE-4577.

(cherry picked from commit d463840)

commit b1736c0bd87d6cfb65f9ef422241e0f1aba04c8d
Author: Andrey V. Mashenkov 
Date:   2017-05-24T15:48:52Z

Fixed thread pools incorrect shutdown.

(cherry picked from commit 66cef22)

commit 15d94b432fdfe458a826df6ad3c30a0408a93f49
Author: Andrey V. Mashenkov 
Date:   2017-05-25T11:27:08Z

Backport of IGNITE-4336: Manual rebalance can't be requested twice.
(cherry picked from commit 9a691c4)

commit 26072dffb8f5b28693731f8367872a8e1e6dfe7e
Author: agura 
Date:   2017-05-18T16:40:09Z

ignite-5203 Simple BLOB support added

commit e105b4e5c9c04f966fa4ffcff0e49dc253f4f050
Author: Andrey V. Mashenkov 
Date:   2017-05-30T13:40:24Z

Merge remote-tracking branch 'origin/ignite-1.7.11' into ignite-1.8.7

# Conflicts:
#   
modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/datasource/DataSource.java
#   
modules/cassandra/store/src/test/java/org/apache/ignite/tests/IgnitePersistentStoreTest.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/service/GridServiceProcessor.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/service/GridServiceProcessorMultiNodeConfigSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/service/GridServiceProcessorMultiNodeSelfTest.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteBinaryObjectsTestSuite.java

Merge remote-tracking branch 'origin/ignite-1.7.11' into ignite-1.8.7

# Conflicts:
#   docs/RELEASE_NOTES.txt
#   docs/community/RELEASE_NOTES.txt
#   

Re: .NET development on Linux & macOS is now possible

2017-12-22 Thread Pavel Tupitsyn
Hi Vyacheslav,

No, porting to .NET Core (actually, libraries should target .NET Standard
instead of .NET Core)
is not planned, since we maintain compatibility with .NET 4 and Visual
Studio 2010.

There is no reason to do the full port, since release binaries already work
on all platforms
(.NET 4+ on Windows, .NET Core 2.0+ on Windows, Linux, macOS).

Pavel

On Fri, Dec 22, 2017 at 2:15 PM, Vyacheslav Daradur 
wrote:

> Hi, Pavel, thanks for this improvement, but as far as I understood it
> is compatibility mode with .NET Сore.
> Are you going to port Ignite to native .NET Core, maybe in the next
> major release?
>
>
> On Fri, Dec 22, 2017 at 1:55 PM, Yakov Zhdanov 
> wrote:
> > Great news, Pavel! As a Linux user I will definitely try that and let you
> > know on results.
> >
> > --Yakov
>
>
>
> --
> Best Regards, Vyacheslav D.
>


Re: .NET development on Linux & macOS is now possible

2017-12-22 Thread Vyacheslav Daradur
Hi, Pavel, thanks for this improvement, but as far as I understood it
is compatibility mode with .NET Сore.
Are you going to port Ignite to native .NET Core, maybe in the next
major release?


On Fri, Dec 22, 2017 at 1:55 PM, Yakov Zhdanov  wrote:
> Great news, Pavel! As a Linux user I will definitely try that and let you
> know on results.
>
> --Yakov



-- 
Best Regards, Vyacheslav D.


Re: .NET development on Linux & macOS is now possible

2017-12-22 Thread Yakov Zhdanov
Great news, Pavel! As a Linux user I will definitely try that and let you
know on results.

--Yakov


[jira] [Created] (IGNITE-7287) Thin client: idle connection timeout

2017-12-22 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-7287:
--

 Summary: Thin client: idle connection timeout
 Key: IGNITE-7287
 URL: https://issues.apache.org/jira/browse/IGNITE-7287
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Add an ability to drop inactive connections on server side, disabled by 
default: introduce {{ClientConnectorConfiguration.idleTimeout}}, default to 
{{long.MAX_VALUE}}.

Currently we set {{GridNioServer.idleTimeout}} to {{MAX_VALUE}} in 
{{ClientListenerProcessor.start()}}.



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


[GitHub] ignite pull request #2632: IGNTIE-6328: in ML examples, class ExampleMatrixS...

2017-12-22 Thread ybabak
Github user ybabak closed the pull request at:

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


---


[GitHub] ignite pull request #3269: IGNITE-6732: Preventing Hadoop module from start ...

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] ignite pull request #3005: IGNITE-6735: Java 9: fix Java version resolution/...

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] ignite pull request #3273: IGNITE-6735

2017-12-22 Thread devozerov
Github user devozerov closed the pull request at:

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


---


.NET development on Linux & macOS is now possible

2017-12-22 Thread Pavel Tupitsyn
Igniters,

I'm glad to announce that it is now possible to do Ignite.NET development
(build from sources, run tests) on Linux and macOS!

Changes are in master, see modules/platforms/dotnet/DEVNOTES.txt for
details.
Let me know if you have any questions.

Thanks,
Pavel


[GitHub] ignite pull request #2748: IGNITE-6015: Rollback on exception in commitIfLoc...

2017-12-22 Thread andrey-kuznetsov
Github user andrey-kuznetsov closed the pull request at:

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


---


[jira] [Created] (IGNITE-7286) Web Console: We can't copy from the tables (in old design)

2017-12-22 Thread Vica Abramova (JIRA)
Vica Abramova created IGNITE-7286:
-

 Summary: Web Console: We can't copy from the tables (in old design)
 Key: IGNITE-7286
 URL: https://issues.apache.org/jira/browse/IGNITE-7286
 Project: Ignite
  Issue Type: Bug
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Alexey Kuznetsov
 Attachments: table.png





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


[GitHub] ignite pull request #3273: IGNITE-6735

2017-12-22 Thread devozerov
GitHub user devozerov opened a pull request:

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

IGNITE-6735



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

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

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

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


commit 6d35794978c6c84001d16293e78031a4aed7d0da
Author: devozerov 
Date:   2017-12-22T09:18:13Z

Done.




---


Re: Ignite Committership Bar Guidance

2017-12-22 Thread Vyacheslav Daradur
Hi, Denis, how will the complexity of tasks be estimated?


On Fri, Dec 22, 2017 at 3:16 AM, Denis Magda  wrote:
> Igniters,
>
> We at Ignite PMC put together a page with rules-of-thumb on when it’s a right 
> time to promote a contributor to a committer:
> https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance 
> 
>
> It’s intended to make “contributor to committer” process more evident and 
> simplify Ignite PMC voting process on this matter.
>
> Please use it as a reference, comments and suggestions are welcomed!
>
> —
> Denis



-- 
Best Regards, Vyacheslav D.


[GitHub] ignite pull request #3232: IGNITE-6731: Dropping unnecessary PerfCounter inv...

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] ignite pull request #3271: IGNITE-7279 .NET: Compile on Linux

2017-12-22 Thread asfgit
Github user asfgit closed the pull request at:

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


---