[jira] [Assigned] (IGNITE-5655) Introduce pluggable string encoder/decoder

[Andrey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Kuznetsov reassigned IGNITE-5655:


Assignee: Andrey Kuznetsov

> Introduce pluggable string encoder/decoder
> --
>
> Key: IGNITE-5655
> URL: https://issues.apache.org/jira/browse/IGNITE-5655
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Andrey Kuznetsov
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it 
> makes sense to serialize strings with different encodings to save space. 
> Let's add global property to control String encoding and customize our binary 
> protocol to support it. For instance, we can add another flag 
> {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]



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

[jira] [Updated] (IGNITE-5706) Redis FLUSHDB command support

[Roman Shtykh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Shtykh updated IGNITE-5706:
-
Fix Version/s: 2.2

> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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

[jira] [Assigned] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-5345:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



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

[jira] [Commented] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099319#comment-16099319
 ] 

Denis Magda commented on IGNITE-5345:
-

[~vozerov], thanks for the documentation. I've merged it with the previously 
existing page cleaning it out:
https://apacheignite.readme.io/v2.1/docs/jdbc-driver

(remove the page created by you).

Current version of the page distinguishes the thin driver from the "client 
node" one and looks pretty vivid to me. I would leave it this way for now.

[~pgarg], please review the page below and close the ticket:
https://apacheignite.readme.io/v2.1/docs/jdbc-driver

> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



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

[jira] [Closed] (IGNITE-5351) Document K-means clustering algorithm

[Prachi Garg (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prachi Garg closed IGNITE-5351.
---

Reviewed.

> Document K-means clustering algorithm
> -
>
> Key: IGNITE-5351
> URL: https://issues.apache.org/jira/browse/IGNITE-5351
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Someone should document K-means algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Closed] (IGNITE-5349) Document C++ Compute Grid

[Prachi Garg (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prachi Garg closed IGNITE-5349.
---

Reviewed. Made minor edits.

> Document C++ Compute Grid
> -
>
> Key: IGNITE-5349
> URL: https://issues.apache.org/jira/browse/IGNITE-5349
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Prachi Garg
>  Labels: cpp, documentation
> Fix For: 2.1
>
>
> In 2.1 we're introducing compute grid support for C++. It has to be properly 
> documented.



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

[jira] [Assigned] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-5682:


Assignee: Dmitriy Pavlov  (was: Semen Boikov)

[~dpavlov], please merge from latest master, there are conflicts.

Thanks!

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Assigned] (IGNITE-5542) Assertion failure in IgniteBasic test IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-5542:


Assignee: Sergey Chugunov  (was: Semen Boikov)

Reviewed changes, my comments:

- there is already method validating 
ClusterCachesInfo.validateCacheGroupConfiguration, I think we need move all 
checks there instead of adding new method 'validateLocalSpecificConfigurations'
- please add in test case when CacheConfiguration.groupName  is not null

Thanks

> Assertion failure in IgniteBasic test 
> IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed
>  
> -
>
> Key: IGNITE-5542
> URL: https://issues.apache.org/jira/browse/IGNITE-5542
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Sergey Chugunov
>  Labels: test-fail
>
>  
> http://ci.ignite.apache.org/viewLog.html?buildId=674131=buildResultsDiv=Ignite20Tests_IgniteBasic#testNameId-720637123828878
> org.apache.ignite.internal.processors.cache.IgniteCacheP2pUnmarshallingRebalanceErrorTest#testResponseMessageOnUnmarshallingFailed
> assertion failed, 
> *stable reproducable locally*



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

[jira] [Updated] (IGNITE-5739) JVM crash on node deactivation

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-5739:
-
Fix Version/s: (was: 2.1)
   2.2

> JVM crash on node deactivation
> --
>
> Key: IGNITE-5739
> URL: https://issues.apache.org/jira/browse/IGNITE-5739
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
> Attachments: hs_err_pid16076.log, ignite-c43368bb.log
>
>
> Start one node (with persistence).
> Activate
> Deactivate - node crashed.



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

[jira] [Assigned] (IGNITE-5739) JVM crash on node deactivation

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-5739:


Assignee: Alexey Kuznetsov  (was: Semen Boikov)

> JVM crash on node deactivation
> --
>
> Key: IGNITE-5739
> URL: https://issues.apache.org/jira/browse/IGNITE-5739
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
> Attachments: hs_err_pid16076.log, ignite-c43368bb.log
>
>
> Start one node (with persistence).
> Activate
> Deactivate - node crashed.



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

[jira] [Commented] (IGNITE-5805) Fix some alerts identified by lgtm.com

[Semen Boikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099104#comment-16099104
 ] 

Semen Boikov commented on IGNITE-5805:
--

Fixed some alerts in commit 301943361bd29c9c33b7ba15e9567a0e05bf27e2.

> Fix some alerts identified by lgtm.com
> --
>
> Key: IGNITE-5805
> URL: https://issues.apache.org/jira/browse/IGNITE-5805
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Malcolm Taylor
>Assignee: Semen Boikov
> Fix For: 2.2
>
>
> A number of issues have been identified by lgtm.com, detailed at 
> https://lgtm.com/projects/g/apache/ignite/alerts/
> This issue is to address some of the straightforward ones, such as resources 
> not being closed and results of int multiplication being cast to long (with 
> risk of overflow).



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

[jira] [Commented] (IGNITE-5597) Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache

[Konstantin Boudnik (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098981#comment-16098981
 ] 

Konstantin Boudnik commented on IGNITE-5597:


Thanks for committing the patch, [~dkarachentsev]dkarachentsev!
Please note, that patches need to be applied with {{git am -s}} command to 
preserve the original author's name in the interest of giving the credit where 
is due.

> Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache
> ---
>
> Key: IGNITE-5597
> URL: https://issues.apache.org/jira/browse/IGNITE-5597
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Evgenii Zhuravlev
>Assignee: Andrei Yakushin
>  Labels: javadoc
> Fix For: 2.2
>
>
> RendezvousAffinityFunction.getPartitions() Javadoc says:
> {code:java}
>  * Note that for fully replicated caches this method should always
>  * return {@code 1}.
> {code}
> but it's not true, it works the same as PARTITIONED cache.
> Affinity.mapKeyToNode(K key) javadoc says:
> {code:java}
>  * 
>  *  For fully replicated caches first node ID returned by {@link 
> AffinityFunction}
>  *  is returned.
>  * 
>  * For partitioned caches, primary node for the given key is 
> returned.
> {code}
> it looks confusing, while REPLICATED cache has primary nodes for keys as 
> PRATITIONED.
> Also,  
> {code:java}
> * Provides affinity information to detect which node is primary and which 
> nodes are
>  * backups for a partitioned cache.
> {code}
> Affinity matter for REPLICATED cache too.



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

[jira] [Created] (IGNITE-5819) SQL: add support for TRUNCATE TABLE command.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5819:


 Summary: SQL: add support for TRUNCATE TABLE command.
 Key: IGNITE-5819
 URL: https://issues.apache.org/jira/browse/IGNITE-5819
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Andrew Mashenkov
 Fix For: 2.3


Add support for  "TRUNCATE TABLE" command syntax.



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

[jira] [Updated] (IGNITE-5819) SQL: add support for TRUNCATE TABLE command.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5819:
-
Issue Type: New Feature  (was: Bug)

> SQL: add support for TRUNCATE TABLE command.
> 
>
> Key: IGNITE-5819
> URL: https://issues.apache.org/jira/browse/IGNITE-5819
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
>
> Add support for  "TRUNCATE TABLE" command syntax.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: (was: DecimalPrecisionSqlTest.java)

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Attachment: DecimalKeyTest.java

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
> compared incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Attachment: (was: DecimalKeyTest.java)

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
> compared incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: (was: DecimalPrecisionSqlTest.java)

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Attachment: (was: DecimalKeyTest.java)

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
> compared incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Attachment: DecimalKeyTest.java

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
> compared incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Commented] (IGNITE-5770) Refactor PlatformProcessor to PlatformTarget mechanism

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098556#comment-16098556
 ] 

Pavel Tupitsyn commented on IGNITE-5770:


[~isapego] please have a look.

> Refactor PlatformProcessor to PlatformTarget mechanism
> --
>
> Key: IGNITE-5770
> URL: https://issues.apache.org/jira/browse/IGNITE-5770
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> {{PlatformProcessor}} has a number of methods that are called over JNI 
> ({{createCache}} and so on). All other JNI calls (for {{PlatformCache}}, etc) 
> go through {{PlatformTarget}} mechanism.
> To avoid code duplication in JNI and ThinClient code all platform calls 
> should use the same mechanism.



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Fix Version/s: 2.2

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization [1] makes some kind of keys to be compared 
> incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Description: 
Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
compared incorrectly.
E.g. Decimal key. PFA repro.

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

  was:
Looks like query optimization [1] makes some kind of keys to be compared 
incorrectly.
E.g. Decimal key. PFA repro.

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


> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization IGNITE-4509 [1] makes some kind of keys to be 
> compared incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Updated] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5818:
-
Attachment: DecimalKeyTest.java

> SQL: query with condition on affinity column works incorrect in some cases.
> ---
>
> Key: IGNITE-5818
> URL: https://issues.apache.org/jira/browse/IGNITE-5818
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Attachments: DecimalKeyTest.java
>
>
> Looks like query optimization [1] makes some kind of keys to be compared 
> incorrectly.
> E.g. Decimal key. PFA repro.
> [1] https://issues.apache.org/jira/browse/IGNITE-4509



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

[jira] [Created] (IGNITE-5818) SQL: query with condition on affinity column works incorrect in some cases.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5818:


 Summary: SQL: query with condition on affinity column works 
incorrect in some cases.
 Key: IGNITE-5818
 URL: https://issues.apache.org/jira/browse/IGNITE-5818
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Andrew Mashenkov


Looks like query optimization [1] makes some kind of keys to be compared 
incorrectly.
E.g. Decimal key. PFA repro.

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



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: (was: DecimalPrecisionSqlTest.java)

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Commented] (IGNITE-5770) Refactor PlatformProcessor to PlatformTarget mechanism

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098537#comment-16098537
 ] 

Pavel Tupitsyn commented on IGNITE-5770:


* {{PlatformProcessor}} refactored to implement {{PlatformTarget}} and use 
methods such as {{processInLongOutLong}} to handle all interop
* All PlatformProcessor-specific methods removed from JNI project
* Cluster-related methods (such as {{GetCompute}}) moved to 
{{PlatformClusterGroup}}
* Usages fixed in C++ & .NET

As a result, interop code is simpler, shorter, and universal across all 
operations.

> Refactor PlatformProcessor to PlatformTarget mechanism
> --
>
> Key: IGNITE-5770
> URL: https://issues.apache.org/jira/browse/IGNITE-5770
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> {{PlatformProcessor}} has a number of methods that are called over JNI 
> ({{createCache}} and so on). All other JNI calls (for {{PlatformCache}}, etc) 
> go through {{PlatformTarget}} mechanism.
> To avoid code duplication in JNI and ThinClient code all platform calls 
> should use the same mechanism.



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

[jira] [Commented] (IGNITE-4181) The several runs of ServicesExample causes NPE

[Dmitriy Sorokin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098501#comment-16098501
 ] 

Dmitriy Sorokin commented on IGNITE-4181:
-

This issue seems resolved by:

commit 7e45010b4848d0a570995e6dc938875710d846d8
Author: sboikov 
Date: 2017-06-04T08:02:31Z

ignite-5075 'logical' caches sharing the same 'physical' cache group

> The several runs of ServicesExample causes NPE
> --
>
> Key: IGNITE-4181
> URL: https://issues.apache.org/jira/browse/IGNITE-4181
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6, 1.7, 2.0
> Environment: Windows 10, Oracle JDK 7
>Reporter: Sergey Kozlov
>Assignee: Andrey Kuznetsov
>  Labels: newbie
> Fix For: 2.2
>
>
> 0. Open example project in IDEA
> 1. Start 2-3 {{ExampleNodeStartup}}
> 2. Run {{ServicesExample}} several times.
> Sometimes it causes NullPointerException:
> {noformat}
> Executing closure [mapSize=10]
> Service was cancelled: myNodeSingletonService
> [15:37:20,020][INFO ][srvc-deploy-#24%null%][GridServiceProcessor] Cancelled 
> service instance [name=myNodeSingletonService, 
> execId=88a92a4d-c1cb-4a9b-8930-c67ac7f42bf3]
> [15:37:20,032][INFO ][sys-#33%null%][GridCacheProcessor] Stopped cache: 
> myNodeSingletonService
> [15:37:20,033][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=4], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,045][INFO ][sys-#39%null%][GridCacheProcessor] Stopped cache: 
> myClusterSingletonService
> [15:37:20,046][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=5], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,062][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Node left topology: TcpDiscoveryNode 
> [id=4f9cbc67-d756-4c25-9ee4-aee6528da024, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.107, 2001:0:9d38:6ab8:34b2:9f3e:3c6f:269], 
> sockAddrs=[/2001:0:9d38:6ab8:34b2:9f3e:3c6f:269:0, /127.0.0.1:0, 
> /0:0:0:0:0:0:0:1:0, work-pc/172.25.4.107:0], discPort=0, order=10, 
> intOrder=7, lastExchangeTime=1478522239236, loc=false, 
> ver=1.7.3#20161107-sha1:5132ac87, isClient=true]
> [15:37:20,063][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=11.0GB]
> [15:37:20,064][INFO ][sys-#44%null%][GridCacheProcessor] Stopped cache: 
> myMultiService
> [15:37:20,066][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=6], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,076][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myClusterSingletonService, mode=PARTITIONED]
> [15:37:20,115][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=7], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,121][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=11, 
> minorTopVer=0], evt=NODE_LEFT, node=4f9cbc67-d756-4c25-9ee4-aee6528da024]
> [15:37:20,133][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myMultiService, mode=PARTITIONED]
> [15:37:20,135][ERROR][exchange-worker-#23%null%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=11, 
> minorTopVer=1], nodeId=5faac72a, evt=DISCOVERY_CUSTOM_EVT]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedCacheOnCoordinator(CacheAffinitySharedManager.java:743)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:413)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:565)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:448)
>   at 
> 

[jira] [Updated] (IGNITE-5803) IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, stable reproducible locally

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5803:
---
Description: 
http://ci.ignite.apache.org/viewLog.html?buildId=738392=buildResultsDiv=Ignite20Tests_IgniteCache4

org.apache.ignite.testsuites.IgniteCacheTestSuite4: 
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughAtomicReplicated
  
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx0
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx1
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx2
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTxReplicated

All failed with 
{noformat}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.fail(Assert.java:64)
at junit.framework.TestCase.fail(TestCase.java:235)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughAbstractTest$TestEntryProcessor.process(IgniteCacheInvokeReadThroughAbstractTest.java:362)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.applyTransformClosures(IgniteTxAdapter.java:1465)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.batchStoreCommit(IgniteTxAdapter.java:1221)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:501)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3030)
{noformat}

  was:
org.apache.ignite.testsuites.IgniteCacheTestSuite4: 
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughAtomicReplicated
  
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx0
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx1
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx2
   
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTxReplicated




> IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, 
> stable reproducible locally
> ---
>
> Key: IGNITE-5803
> URL: https://issues.apache.org/jira/browse/IGNITE-5803
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=738392=buildResultsDiv=Ignite20Tests_IgniteCache4
> org.apache.ignite.testsuites.IgniteCacheTestSuite4: 
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughAtomicReplicated
> 
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx0
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx1
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx2
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTxReplicated
> All failed with 
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.fail(Assert.java:64)
> at junit.framework.TestCase.fail(TestCase.java:235)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughAbstractTest$TestEntryProcessor.process(IgniteCacheInvokeReadThroughAbstractTest.java:362)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.applyTransformClosures(IgniteTxAdapter.java:1465)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.batchStoreCommit(IgniteTxAdapter.java:1221)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:501)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3030)
> {noformat}



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

[jira] [Commented] (IGNITE-5806) IgniteCache5 suite timed out, assertions in sessions close logic

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098495#comment-16098495
 ] 

Alexey Goncharuk commented on IGNITE-5806:
--

Dmitriy,

I whink a more correct fix would be 
{code}
if (!sesHolder.get().ended(store))
   store.sessionEnd(commit);
{code}

Please re-run the TC with this change.

> IgniteCache5 suite timed out, assertions in sessions close logic
> 
>
> Key: IGNITE-5806
> URL: https://issues.apache.org/jira/browse/IGNITE-5806
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
> Attachments: Ignite_2.0_Tests_Ignite_Cache_5_748.log.zip
>
>
> Ignite Cache 5 timeouts observed in master
> http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5_Ignite20Tests=%3Cdefault%3E=buildTypeStatusDiv
> Reproduced for builds 725, 740 and 748 
> Log contains assertion coming from 
> {code}
> !sesHolder.get().ended(store); 
> {code}
> at
> {noformat} [2017-07-21 
> 07:59:44,774][ERROR][sys-stripe-3-#117%cache.CacheSerializableTransactionsTest2%][G]
>  Failed to execute runnable.
>  
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionEnd0(GridCacheStoreManagerAdapter.java:878)
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:335)
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> {noformat}
> First time assertion came from test 
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest#testRandomOperations
> Assertion is reproducible locally. But test is considered passed



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

[jira] [Created] (IGNITE-5817) Changing checksum calculation methods

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5817:


 Summary: Changing checksum calculation methods
 Key: IGNITE-5817
 URL: https://issues.apache.org/jira/browse/IGNITE-5817
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Neither sha1 nor md5 are trustful checksum calculation methods. We should be 
switching to at least sha265 or higher.



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

[jira] [Commented] (IGNITE-5810) Implement configuration import to xml

[Max Shonichev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098487#comment-16098487
 ] 

Max Shonichev commented on IGNITE-5810:
---

If that would return settings modified run-time - ok for me.

As of Mbeans interface: is there exist any limitation for RMI result size ? 
Configuration can be very big, e.g. for 1000 caches around ~800k - is that OK 
for JMX?

> Implement configuration import to xml
> -
>
> Key: IGNITE-5810
> URL: https://issues.apache.org/jira/browse/IGNITE-5810
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Yakov Zhdanov
>  Labels: usability
>
> When investigating failures having the entire grid configuration is a must. 
> Now Ignite lacks this feature which would be very cool for deployments 
> configured from code.
> I suggest to implement {{public String Ignite.configurationAsXml();}} and add 
> ability to output files and gather them to MBeans and web console.



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

[jira] [Commented] (IGNITE-4181) The several runs of ServicesExample causes NPE

[Dmitriy Sorokin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098485#comment-16098485
 ] 

Dmitriy Sorokin commented on IGNITE-4181:
-

This issue was caused by mechanics which uses GridCacheProcessor's cache 
descriptors map concurrently by event handlers at TCP discovery workers and 
exchange processors at exchange worker. Cache creation event puts newly created 
cache descriptor into GCP's cache descriptors map, then emits exchange, and 
processing of one try take cache descriptor, which already can be removed by 
cache deletion event, processed later then cache creation event but earlier 
then cache creation exchange.

> The several runs of ServicesExample causes NPE
> --
>
> Key: IGNITE-4181
> URL: https://issues.apache.org/jira/browse/IGNITE-4181
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6, 1.7, 2.0
> Environment: Windows 10, Oracle JDK 7
>Reporter: Sergey Kozlov
>Assignee: Andrey Kuznetsov
>  Labels: newbie
> Fix For: 2.2
>
>
> 0. Open example project in IDEA
> 1. Start 2-3 {{ExampleNodeStartup}}
> 2. Run {{ServicesExample}} several times.
> Sometimes it causes NullPointerException:
> {noformat}
> Executing closure [mapSize=10]
> Service was cancelled: myNodeSingletonService
> [15:37:20,020][INFO ][srvc-deploy-#24%null%][GridServiceProcessor] Cancelled 
> service instance [name=myNodeSingletonService, 
> execId=88a92a4d-c1cb-4a9b-8930-c67ac7f42bf3]
> [15:37:20,032][INFO ][sys-#33%null%][GridCacheProcessor] Stopped cache: 
> myNodeSingletonService
> [15:37:20,033][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=4], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,045][INFO ][sys-#39%null%][GridCacheProcessor] Stopped cache: 
> myClusterSingletonService
> [15:37:20,046][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=5], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,062][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Node left topology: TcpDiscoveryNode 
> [id=4f9cbc67-d756-4c25-9ee4-aee6528da024, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.107, 2001:0:9d38:6ab8:34b2:9f3e:3c6f:269], 
> sockAddrs=[/2001:0:9d38:6ab8:34b2:9f3e:3c6f:269:0, /127.0.0.1:0, 
> /0:0:0:0:0:0:0:1:0, work-pc/172.25.4.107:0], discPort=0, order=10, 
> intOrder=7, lastExchangeTime=1478522239236, loc=false, 
> ver=1.7.3#20161107-sha1:5132ac87, isClient=true]
> [15:37:20,063][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=11.0GB]
> [15:37:20,064][INFO ][sys-#44%null%][GridCacheProcessor] Stopped cache: 
> myMultiService
> [15:37:20,066][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=6], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,076][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myClusterSingletonService, mode=PARTITIONED]
> [15:37:20,115][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=7], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,121][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=11, 
> minorTopVer=0], evt=NODE_LEFT, node=4f9cbc67-d756-4c25-9ee4-aee6528da024]
> [15:37:20,133][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myMultiService, mode=PARTITIONED]
> [15:37:20,135][ERROR][exchange-worker-#23%null%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=11, 
> minorTopVer=1], nodeId=5faac72a, evt=DISCOVERY_CUSTOM_EVT]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedCacheOnCoordinator(CacheAffinitySharedManager.java:743)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:413)
>   at 
> 

[jira] [Updated] (IGNITE-5816) Race in WAL segment leading to ClosedChannelException

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk updated IGNITE-5816:
-
Description: 
In current flushOrWait() code we acquire writtenBytes before we try to flush. 
If flush fails, we wait for written be equal to expWritten.
When a segment is being closed, this leads to one thread returning from 
flushOrWait early because written is updated, but expWritten does not match the 
last record position.

> Race in WAL segment leading to ClosedChannelException
> -
>
> Key: IGNITE-5816
> URL: https://issues.apache.org/jira/browse/IGNITE-5816
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.2
>
>
> In current flushOrWait() code we acquire writtenBytes before we try to flush. 
> If flush fails, we wait for written be equal to expWritten.
> When a segment is being closed, this leads to one thread returning from 
> flushOrWait early because written is updated, but expWritten does not match 
> the last record position.



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

[jira] [Created] (IGNITE-5816) Race in WAL segment leading to ClosedChannelException

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5816:


 Summary: Race in WAL segment leading to ClosedChannelException
 Key: IGNITE-5816
 URL: https://issues.apache.org/jira/browse/IGNITE-5816
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.2






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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: (was: DecimalPrecisionSqlTest.java)

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Assigned] (IGNITE-5815) Web Console: Improve Zero Configuration Politics

[Vica Abramova (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vica Abramova reassigned IGNITE-5815:
-

Assignee: Alexey Kuznetsov

> Web Console: Improve Zero Configuration Politics
> 
>
> Key: IGNITE-5815
> URL: https://issues.apache.org/jira/browse/IGNITE-5815
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
>
> If the user enters a value in the field and it matches the default value, 
> then we generate a string.



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

[jira] [Created] (IGNITE-5815) Web Console: Improve Zero Configuration Politics

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5815:
-

 Summary: Web Console: Improve Zero Configuration Politics
 Key: IGNITE-5815
 URL: https://issues.apache.org/jira/browse/IGNITE-5815
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Vica Abramova


If the user enters a value in the field and it matches the default value, then 
we generate a string.



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

[jira] [Assigned] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reassigned IGNITE-5682:
--

Assignee: Semen Boikov  (was: Dmitriy Pavlov)

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Comment Edited] (IGNITE-5806) IgniteCache5 suite timed out, assertions in sessions close logic

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098409#comment-16098409
 ] 

Dmitriy Pavlov edited comment on IGNITE-5806 at 7/24/17 1:54 PM:
-

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

All failures from 20 runs ( 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5_Ignite20Tests=pull%2F2335%2Fhead=buildTypeStatusDiv
 ) came from [IGNITE-5759].



was (Author: dpavlov):
https://github.com/apache/ignite/pull/2335

All failures from 20 runs (see above) came from [IGNITE-5759].


> IgniteCache5 suite timed out, assertions in sessions close logic
> 
>
> Key: IGNITE-5806
> URL: https://issues.apache.org/jira/browse/IGNITE-5806
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
> Attachments: Ignite_2.0_Tests_Ignite_Cache_5_748.log.zip
>
>
> Ignite Cache 5 timeouts observed in master
> http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5_Ignite20Tests=%3Cdefault%3E=buildTypeStatusDiv
> Reproduced for builds 725, 740 and 748 
> Log contains assertion coming from 
> {code}
> !sesHolder.get().ended(store); 
> {code}
> at
> {noformat} [2017-07-21 
> 07:59:44,774][ERROR][sys-stripe-3-#117%cache.CacheSerializableTransactionsTest2%][G]
>  Failed to execute runnable.
>  
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionEnd0(GridCacheStoreManagerAdapter.java:878)
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:335)
> at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> {noformat}
> First time assertion came from test 
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest#testRandomOperations
> Assertion is reproducible locally. But test is considered passed



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

[jira] [Updated] (IGNITE-4181) The several runs of ServicesExample causes NPE

[Dmitriy Sorokin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Sorokin updated IGNITE-4181:

Affects Version/s: 2.0

> The several runs of ServicesExample causes NPE
> --
>
> Key: IGNITE-4181
> URL: https://issues.apache.org/jira/browse/IGNITE-4181
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6, 1.7, 2.0
> Environment: Windows 10, Oracle JDK 7
>Reporter: Sergey Kozlov
>Assignee: Andrey Kuznetsov
>  Labels: newbie
> Fix For: 2.2
>
>
> 0. Open example project in IDEA
> 1. Start 2-3 {{ExampleNodeStartup}}
> 2. Run {{ServicesExample}} several times.
> Sometimes it causes NullPointerException:
> {noformat}
> Executing closure [mapSize=10]
> Service was cancelled: myNodeSingletonService
> [15:37:20,020][INFO ][srvc-deploy-#24%null%][GridServiceProcessor] Cancelled 
> service instance [name=myNodeSingletonService, 
> execId=88a92a4d-c1cb-4a9b-8930-c67ac7f42bf3]
> [15:37:20,032][INFO ][sys-#33%null%][GridCacheProcessor] Stopped cache: 
> myNodeSingletonService
> [15:37:20,033][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=4], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,045][INFO ][sys-#39%null%][GridCacheProcessor] Stopped cache: 
> myClusterSingletonService
> [15:37:20,046][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=5], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,062][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Node left topology: TcpDiscoveryNode 
> [id=4f9cbc67-d756-4c25-9ee4-aee6528da024, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.107, 2001:0:9d38:6ab8:34b2:9f3e:3c6f:269], 
> sockAddrs=[/2001:0:9d38:6ab8:34b2:9f3e:3c6f:269:0, /127.0.0.1:0, 
> /0:0:0:0:0:0:0:1:0, work-pc/172.25.4.107:0], discPort=0, order=10, 
> intOrder=7, lastExchangeTime=1478522239236, loc=false, 
> ver=1.7.3#20161107-sha1:5132ac87, isClient=true]
> [15:37:20,063][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager] 
> Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=11.0GB]
> [15:37:20,064][INFO ][sys-#44%null%][GridCacheProcessor] Stopped cache: 
> myMultiService
> [15:37:20,066][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=6], evt=DISCOVERY_CUSTOM_EVT, 
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,076][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myClusterSingletonService, mode=PARTITIONED]
> [15:37:20,115][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10, 
> minorTopVer=7], evt=DISCOVERY_CUSTOM_EVT, 
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,121][INFO 
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping 
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=11, 
> minorTopVer=0], evt=NODE_LEFT, node=4f9cbc67-d756-4c25-9ee4-aee6528da024]
> [15:37:20,133][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started 
> cache [name=myMultiService, mode=PARTITIONED]
> [15:37:20,135][ERROR][exchange-worker-#23%null%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=11, 
> minorTopVer=1], nodeId=5faac72a, evt=DISCOVERY_CUSTOM_EVT]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedCacheOnCoordinator(CacheAffinitySharedManager.java:743)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:413)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:565)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:448)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1447)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> 

[jira] [Created] (IGNITE-5814) Service deploy fails with NPE if it implements ExecutorService interface

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-5814:
-

 Summary: Service deploy fails with NPE if it implements 
ExecutorService interface
 Key: IGNITE-5814
 URL: https://issues.apache.org/jira/browse/IGNITE-5814
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.9
Reporter: Evgenii Zhuravlev






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

[jira] [Updated] (IGNITE-5814) Service deploy fails with NPE if it implements ExecutorService interface

[Evgenii Zhuravlev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgenii Zhuravlev updated IGNITE-5814:
--
Description: 
Caused by: class org.apache.ignite.IgniteCheckedException: null
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7239)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
at 
org.apache.ignite.internal.AsyncSupportAdapter.saveOrGet(AsyncSupportAdapter.java:112)
at 
org.apache.ignite.internal.IgniteServicesImpl.deployNodeSingleton(IgniteServicesImpl.java:83)
... 6 more
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:244)
at 
org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:227)
at 
org.apache.ignite.internal.processors.resource.GridResourceProcessor.injectGeneric(GridResourceProcessor.java:208)
at 
org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:487)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1188)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1107)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1758)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1435)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:118)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1402)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1805)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

> Service deploy fails with NPE if it implements ExecutorService interface
> 
>
> Key: IGNITE-5814
> URL: https://issues.apache.org/jira/browse/IGNITE-5814
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Evgenii Zhuravlev
>
> Caused by: class org.apache.ignite.IgniteCheckedException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7239)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
>   at 
> org.apache.ignite.internal.AsyncSupportAdapter.saveOrGet(AsyncSupportAdapter.java:112)
>   at 
> org.apache.ignite.internal.IgniteServicesImpl.deployNodeSingleton(IgniteServicesImpl.java:83)
>   ... 6 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:244)
>   at 
> org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:227)
>   at 
> org.apache.ignite.internal.processors.resource.GridResourceProcessor.injectGeneric(GridResourceProcessor.java:208)
>   at 
> org.apache.ignite.internal.processors.resource.GridResourceProcessor.inject(GridResourceProcessor.java:487)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1188)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1107)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1758)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1435)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:118)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1402)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1805)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> 

[jira] [Commented] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098410#comment-16098410
 ] 

Dmitriy Pavlov commented on IGNITE-5759:


See also 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5_Ignite20Tests=pull%2F2335%2Fhead=buildTypeStatusDiv

10% probablity than test is failed (master)

> IgniteCache5 suite timed out probably by 
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was 
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
>  TcpCommunicationSpi failed to establish connection to node, node will be 
> dropped from cluster [rmtNode=TcpDiscoveryNode 
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4, 
> lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
> [23:19:11]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node 
> still alive?). Make sure that each ComputeTask and cache Transaction has a 
> timeout set in order to prevent parties from waiting forever in case of 
> network issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93, 
> addrs=[/127.0.0.1:45273]]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [23:19:11]W:   [org.apache.ignite:ignite-core]Suppressed: 
> class org.apache.ignite.IgniteCheckedException: Failed to connect to address 
> [addr=/127.0.0.1:45273, err=Connection refused]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> [23:19:11]W:   [org.apache.ignite:ignite-core]Caused by: 
> java.net.ConnectException: Connection refused
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3024)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> {noformat}
> and then
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,895][WARN ][main][root] Interrupting threads started so far: 5
> 

[jira] [Updated] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5759:
---
Priority: Critical  (was: Major)

> IgniteCache5 suite timed out probably by 
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was 
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
>  TcpCommunicationSpi failed to establish connection to node, node will be 
> dropped from cluster [rmtNode=TcpDiscoveryNode 
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4, 
> lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
> [23:19:11]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node 
> still alive?). Make sure that each ComputeTask and cache Transaction has a 
> timeout set in order to prevent parties from waiting forever in case of 
> network issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93, 
> addrs=[/127.0.0.1:45273]]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [23:19:11]W:   [org.apache.ignite:ignite-core]Suppressed: 
> class org.apache.ignite.IgniteCheckedException: Failed to connect to address 
> [addr=/127.0.0.1:45273, err=Connection refused]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> [23:19:11]W:   [org.apache.ignite:ignite-core]Caused by: 
> java.net.ConnectException: Connection refused
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3024)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> {noformat}
> and then
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,895][WARN ][main][root] Interrupting threads started so far: 5
> [23:19:11] :   [Step 4/5] [2017-07-14 20:19:11,895][INFO ][main][root] >>> 
> Stopping test class: GridCachePartitionEvictionDuringReadThroughSelfTest <<<
> [23:19:11]W:   

[jira] [Updated] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5759:
---
Labels: MakeTeamcityGreenAgain test-fail  (was: test-fail)

> IgniteCache5 suite timed out probably by 
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was 
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
>  TcpCommunicationSpi failed to establish connection to node, node will be 
> dropped from cluster [rmtNode=TcpDiscoveryNode 
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4, 
> lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
> [23:19:11]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node 
> still alive?). Make sure that each ComputeTask and cache Transaction has a 
> timeout set in order to prevent parties from waiting forever in case of 
> network issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93, 
> addrs=[/127.0.0.1:45273]]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [23:19:11]W:   [org.apache.ignite:ignite-core]Suppressed: 
> class org.apache.ignite.IgniteCheckedException: Failed to connect to address 
> [addr=/127.0.0.1:45273, err=Connection refused]
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> [23:19:11]W:   [org.apache.ignite:ignite-core]Caused by: 
> java.net.ConnectException: Connection refused
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
> [23:19:11]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3024)
> [23:19:11]W:   [org.apache.ignite:ignite-core]... 6 
> more
> {noformat}
> and then
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,895][WARN ][main][root] Interrupting threads started so far: 5
> [23:19:11] :   [Step 4/5] [2017-07-14 20:19:11,895][INFO ][main][root] >>> 
> Stopping test class: GridCachePartitionEvictionDuringReadThroughSelfTest <<<
> [23:19:11]W:   

[jira] [Updated] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5682:
---
Labels: MakeTeamcityGreenAgain Muted_test test-fail  (was: Make Muted_test 
test-fail)

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5682:
---
Labels: Make Muted_test test-fail  (was: MakeTeamcityGreenAgain Muted_test 
test-fail)

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Comment Edited] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098399#comment-16098399
 ] 

Dmitriy Pavlov edited comment on IGNITE-5759 at 7/24/17 1:25 PM:
-

Problems is still found for recent runs:  buildId737186; buildId737181


was (Author: dpavlov):
Problems is still found for recent runs: 
{noformat}
2017-07-21 
20:52:03,988][ERROR][sys-#87168%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest0%][GridNearGetFuture]
 Failed to get values from dht cache [fut=GridCompoundIdentityFuture 
[super=GridCompoundFuture [rdc=Collection reducer: null, initFlag=1, 
lsnrCalls=0, done=true, cancelled=false, err=class 
o.a.i.IgniteCheckedException: null, futs=[false
[23:52:03]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteCheckedException: null
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:484)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAll(GridCacheStoreManagerAdapter.java:389)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$15.call(GridCacheAdapter.java:2024)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$15.call(GridCacheAdapter.java:2022)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6625)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:959)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
[23:52:03]W: [org.apache.ignite:ignite-core] Caused by: 
javax.cache.integration.CacheLoaderException
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridCachePartitionEvictionDuringReadThroughSelfTest$HangingCacheStore.load(GridCachePartitionEvictionDuringReadThroughSelfTest.java:146)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridCachePartitionEvictionDuringReadThroughSelfTest$HangingCacheStore.load(GridCachePartitionEvictionDuringReadThroughSelfTest.java:139)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.cache.store.CacheStoreAdapter.loadAll(CacheStoreAdapter.java:62)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheStoreBalancingWrapper.loadAll(CacheStoreBalancingWrapper.java:173)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:476)
[23:52:03]W: [org.apache.ignite:ignite-core]... 9 more

{noformat}

> IgniteCache5 suite timed out probably by 
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was 
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
>  TcpCommunicationSpi failed to establish connection to node, node will be 
> dropped from cluster [rmtNode=TcpDiscoveryNode 
> 

[jira] [Commented] (IGNITE-5759) IgniteCache5 suite timed out probably by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098399#comment-16098399
 ] 

Dmitriy Pavlov commented on IGNITE-5759:


Problems is still found for recent runs: 
{noformat}
2017-07-21 
20:52:03,988][ERROR][sys-#87168%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest0%][GridNearGetFuture]
 Failed to get values from dht cache [fut=GridCompoundIdentityFuture 
[super=GridCompoundFuture [rdc=Collection reducer: null, initFlag=1, 
lsnrCalls=0, done=true, cancelled=false, err=class 
o.a.i.IgniteCheckedException: null, futs=[false
[23:52:03]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteCheckedException: null
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:484)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAll(GridCacheStoreManagerAdapter.java:389)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$15.call(GridCacheAdapter.java:2024)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$15.call(GridCacheAdapter.java:2022)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6625)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:959)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
[23:52:03]W: [org.apache.ignite:ignite-core] Caused by: 
javax.cache.integration.CacheLoaderException
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridCachePartitionEvictionDuringReadThroughSelfTest$HangingCacheStore.load(GridCachePartitionEvictionDuringReadThroughSelfTest.java:146)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridCachePartitionEvictionDuringReadThroughSelfTest$HangingCacheStore.load(GridCachePartitionEvictionDuringReadThroughSelfTest.java:139)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.cache.store.CacheStoreAdapter.loadAll(CacheStoreAdapter.java:62)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheStoreBalancingWrapper.loadAll(CacheStoreBalancingWrapper.java:173)
[23:52:03]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:476)
[23:52:03]W: [org.apache.ignite:ignite-core]... 9 more

{noformat}

> IgniteCache5 suite timed out probably by 
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=727951=Ignite20Tests_IgniteCache5
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was 
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W:   [org.apache.ignite:ignite-core] [2017-07-14 
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
>  TcpCommunicationSpi failed to establish connection to node, node will be 
> dropped from cluster [rmtNode=TcpDiscoveryNode 
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4, 
> lastExchangeTime=1500063443391, 

[jira] [Updated] (IGNITE-4784) Web Console: Revise demo mode

[Vica Abramova (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vica Abramova updated IGNITE-4784:
--
Description: 
Let's add animated blue line.
Demo: https://marvelapp.com/32e928b

Link 'Close Demo' should be red onhover.

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> Link 'Close Demo' should be red onhover.



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

[jira] [Commented] (IGNITE-5123) Ignite.cache(String) returns null in PluginProvider.onIgniteStart()

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098340#comment-16098340
 ] 

ASF GitHub Bot commented on IGNITE-5123:


Github user YevIgn closed the pull request at:

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


> Ignite.cache(String) returns null in PluginProvider.onIgniteStart()
> ---
>
> Key: IGNITE-5123
> URL: https://issues.apache.org/jira/browse/IGNITE-5123
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nick Pordash
>Assignee: Yevgeniy Ignatyev
> Fix For: 2.2
>
> Attachments: ignite-plugin-failure.zip
>
>
> Given an Ignite node that has pre-configured caches (via 
> IgniteConfiguration.setCacheConfiguration) if you try to obtain a reference 
> to the cache instance in PluginProvider.onIgniteStart() you'll get a null 
> reference.
> @Override
> public void onIgniteStart() throws IgniteCheckedException {
> ignite.cacheNames().forEach(name -> {
> assert ignite.cache(name) != null : "Cache is null: " + name;
> });
> }



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

[jira] [Commented] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098338#comment-16098338
 ] 

Andrew Mashenkov commented on IGNITE-5813:
--

Seems, we should force cache entries eviction on transaction rollback if Store 
with writeThrough ("and readThrough" possibly ?) configured.

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: IgniteTxOriginatingNodeFailsAfterStoreCommitSelfTest.java
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Updated] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5813:
-
Attachment: IgniteTxOriginatingNodeFailsAfterStoreCommitSelfTest.java

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: IgniteTxOriginatingNodeFailsAfterStoreCommitSelfTest.java
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Commented] (IGNITE-5810) Implement configuration import to xml

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098327#comment-16098327
 ] 

Pavel Tupitsyn commented on IGNITE-5810:


[~mshonichev] {{Ignite.configuration()}} already exists, so you can call 
{{Ignite.configuration().toXml()}}. Is that what you mean?

> Implement configuration import to xml
> -
>
> Key: IGNITE-5810
> URL: https://issues.apache.org/jira/browse/IGNITE-5810
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Yakov Zhdanov
>  Labels: usability
>
> When investigating failures having the entire grid configuration is a must. 
> Now Ignite lacks this feature which would be very cool for deployments 
> configured from code.
> I suggest to implement {{public String Ignite.configurationAsXml();}} and add 
> ability to output files and gather them to MBeans and web console.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: (was: DecimalPrecisionSqlTest.java)

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Commented] (IGNITE-5123) Ignite.cache(String) returns null in PluginProvider.onIgniteStart()

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098258#comment-16098258
 ] 

Dmitriy Pavlov commented on IGNITE-5123:


[~avinogradov], could you please merge this fix? 
See also 
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5123-Review-td19813.html
 for more details on this issue

> Ignite.cache(String) returns null in PluginProvider.onIgniteStart()
> ---
>
> Key: IGNITE-5123
> URL: https://issues.apache.org/jira/browse/IGNITE-5123
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nick Pordash
>Assignee: Yevgeniy Ignatyev
> Fix For: 2.2
>
> Attachments: ignite-plugin-failure.zip
>
>
> Given an Ignite node that has pre-configured caches (via 
> IgniteConfiguration.setCacheConfiguration) if you try to obtain a reference 
> to the cache instance in PluginProvider.onIgniteStart() you'll get a null 
> reference.
> @Override
> public void onIgniteStart() throws IgniteCheckedException {
> ignite.cacheNames().forEach(name -> {
> assert ignite.cache(name) != null : "Cache is null: " + name;
> });
> }



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

[jira] [Created] (IGNITE-5812) Implement decorator to auto adjust dopdown width to parent

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-5812:


 Summary: Implement decorator to auto adjust dopdown width to parent
 Key: IGNITE-5812
 URL: https://issues.apache.org/jira/browse/IGNITE-5812
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin
 Fix For: 2.2






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

[jira] [Updated] (IGNITE-5811) Detect java-level deadlock and act according to a policy configured.

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-5811:
--
Labels: usability  (was: )

> Detect java-level deadlock and act according to a policy configured.
> 
>
> Key: IGNITE-5811
> URL: https://issues.apache.org/jira/browse/IGNITE-5811
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Yakov Zhdanov
>  Labels: usability
>
> This has something in common with segmentation policy we currently have. User 
> should get notified on a deadlock problem and node should take an action 
> (stop by default)



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

[jira] [Created] (IGNITE-5811) Detect java-level deadlock and act according to a policy configured.

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5811:
-

 Summary: Detect java-level deadlock and act according to a policy 
configured.
 Key: IGNITE-5811
 URL: https://issues.apache.org/jira/browse/IGNITE-5811
 Project: Ignite
  Issue Type: New Feature
Reporter: Yakov Zhdanov


This has something in common with segmentation policy we currently have. User 
should get notified on a deadlock problem and node should take an action (stop 
by default)



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

[jira] [Comment Edited] (IGNITE-5734) Web Console: update npm dependensies

[Andrey Novikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098180#comment-16098180
 ] 

Andrey Novikov edited comment on IGNITE-5734 at 7/24/17 10:35 AM:
--

[~vsisko], can you please check transition between states, state restoring, 
project download, tables?


was (Author: anovikov):
[~vsisko], can you please check transition between states, state restoring?

> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Commented] (IGNITE-5123) Ignite.cache(String) returns null in PluginProvider.onIgniteStart()

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098183#comment-16098183
 ] 

Alexey Goncharuk commented on IGNITE-5123:
--

I'm ok with the changes as long as TC is ok

> Ignite.cache(String) returns null in PluginProvider.onIgniteStart()
> ---
>
> Key: IGNITE-5123
> URL: https://issues.apache.org/jira/browse/IGNITE-5123
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nick Pordash
>Assignee: Yevgeniy Ignatyev
> Fix For: 2.2
>
> Attachments: ignite-plugin-failure.zip
>
>
> Given an Ignite node that has pre-configured caches (via 
> IgniteConfiguration.setCacheConfiguration) if you try to obtain a reference 
> to the cache instance in PluginProvider.onIgniteStart() you'll get a null 
> reference.
> @Override
> public void onIgniteStart() throws IgniteCheckedException {
> ignite.cacheNames().forEach(name -> {
> assert ignite.cache(name) != null : "Cache is null: " + name;
> });
> }



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

[jira] [Comment Edited] (IGNITE-5810) Implement configuration import to xml

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098182#comment-16098182
 ] 

Pavel Tupitsyn edited comment on IGNITE-5810 at 7/24/17 10:25 AM:
--

I think {{String IgniteConfiguration.toXml()}} is better - can be called on any 
config instance and does not require started node.


was (Author: ptupitsyn):
I think `String IgniteConfiguration.toXml()` is better - can be called on any 
config instance and does not require started node.

> Implement configuration import to xml
> -
>
> Key: IGNITE-5810
> URL: https://issues.apache.org/jira/browse/IGNITE-5810
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Yakov Zhdanov
>  Labels: usability
>
> When investigating failures having the entire grid configuration is a must. 
> Now Ignite lacks this feature which would be very cool for deployments 
> configured from code.
> I suggest to implement {{public String Ignite.configurationAsXml();}} and add 
> ability to output files and gather them to MBeans and web console.



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

[jira] [Commented] (IGNITE-5810) Implement configuration import to xml

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098182#comment-16098182
 ] 

Pavel Tupitsyn commented on IGNITE-5810:


I think `String IgniteConfiguration.toXml()` is better - can be called on any 
config instance and does not require started node.

> Implement configuration import to xml
> -
>
> Key: IGNITE-5810
> URL: https://issues.apache.org/jira/browse/IGNITE-5810
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Yakov Zhdanov
>  Labels: usability
>
> When investigating failures having the entire grid configuration is a must. 
> Now Ignite lacks this feature which would be very cool for deployments 
> configured from code.
> I suggest to implement {{public String Ignite.configurationAsXml();}} and add 
> ability to output files and gather them to MBeans and web console.



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

[jira] [Commented] (IGNITE-5734) Web Console: update npm dependensies

[Andrey Novikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098180#comment-16098180
 ] 

Andrey Novikov commented on IGNITE-5734:


[~vsisko], can you please check transition between states, state restoring?

> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Assigned] (IGNITE-5734) Web Console: update npm dependensies

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-5734:
--

Assignee: Andrey Novikov  (was: Ilya Borisov)

> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Created] (IGNITE-5810) Implement configuration import to xml

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5810:
-

 Summary: Implement configuration import to xml
 Key: IGNITE-5810
 URL: https://issues.apache.org/jira/browse/IGNITE-5810
 Project: Ignite
  Issue Type: New Feature
Reporter: Yakov Zhdanov


When investigating failures having the entire grid configuration is a must. Now 
Ignite lacks this feature which would be very cool for deployments configured 
from code.

I suggest to implement {{public String Ignite.configurationAsXml();}} and add 
ability to output files and gather them to MBeans and web console.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Fix Version/s: (was: 2.2)
   2.3

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.3
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Updated] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-5809:
-
Attachment: DecimalPrecisionSqlTest.java

> SQL: Add precision and scale support for table fields.
> --
>
> Key: IGNITE-5809
> URL: https://issues.apache.org/jira/browse/IGNITE-5809
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: DecimalPrecisionSqlTest.java
>
>
> PFA test.



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

[jira] [Commented] (IGNITE-5807) Fixing signing artifacts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098170#comment-16098170
 ] 

ASF GitHub Bot commented on IGNITE-5807:


GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOT…

…ES.txt

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

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

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

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


commit 6ea8a8262b847d4180e16567d5a8a0973bed6562
Author: oleg-ostanin 
Date:   2017-07-22T10:08:41Z

IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOTES.txt




> Fixing signing artifacts
> 
>
> Key: IGNITE-5807
> URL: https://issues.apache.org/jira/browse/IGNITE-5807
> Project: Ignite
>  Issue Type: Bug
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>
> We need to fix pom.xml file to allow gpg plugin to sign .zip artifacts after 
> assembly.



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

[jira] [Created] (IGNITE-5809) SQL: Add precision and scale support for table fields.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5809:


 Summary: SQL: Add precision and scale support for table fields.
 Key: IGNITE-5809
 URL: https://issues.apache.org/jira/browse/IGNITE-5809
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Andrew Mashenkov
 Fix For: 2.2


PFA test.



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

[jira] [Commented] (IGNITE-5734) Web Console: update npm dependensies

[Ilya Borisov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098162#comment-16098162
 ] 

Ilya Borisov commented on IGNITE-5734:
--

[~anovikov] I've fixed some regressions, removed unnecessary commented out code 
and disabled debug messages for $trace service. The rest looks OK.

> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Ilya Borisov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Resolved] (IGNITE-5093) Better heap usage during exchange on large topologies and cache numbers/partitions.

[Alexei Scherbakov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Scherbakov resolved IGNITE-5093.
---
Resolution: Duplicate

Major fixes were done for other tickes, including:

1. store difference with topology version

2. GridPartitionStateMap

> Better heap usage during exchange on large topologies and cache 
> numbers/partitions.
> ---
>
> Key: IGNITE-5093
> URL: https://issues.apache.org/jira/browse/IGNITE-5093
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.2
>
>
> I observed huge heap occupation on large grid installation including 136 
> nodes/1k caches.
> Example from machine with 64g heap:
> {noformat}
>  num #instances #bytes  class name
> --
>1:   89728797743069822896  java.util.HashMap$Node
>2:   927316214866180592  [Ljava.util.HashMap$Node;
>3:   2012822924830775008java.lang.Integer
>4:   6247215983811096  [Ljava.lang.Object;
>5:   3383402767741664  [C
>6:   12188669411952   [B
>7:   9923859   635126976   java.util.HashMap
> ...
> {noformat}
> Further investigation had showed the heap is polluted during exchange 
> process, which involves creating many hashmaps occupying large amounts of 
> memory.
> Proposal: use other datastructures to help keep heap usage low.



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

[jira] [Assigned] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock

[Vyacheslav Daradur (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Daradur reassigned IGNITE-9:
---

Assignee: Alexey Kuznetsov  (was: Vyacheslav Daradur)

> Need to implement IngniteReentrantReadWriteLock
> ---
>
> Key: IGNITE-9
> URL: https://issues.apache.org/jira/browse/IGNITE-9
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Alexey Kuznetsov
>
> See org.apache.ignite.IgniteLock for reference



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

[jira] [Assigned] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock

[Vyacheslav Daradur (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Daradur reassigned IGNITE-9:
---

Assignee: Vyacheslav Daradur  (was: Alexey Kuznetsov)

> Need to implement IngniteReentrantReadWriteLock
> ---
>
> Key: IGNITE-9
> URL: https://issues.apache.org/jira/browse/IGNITE-9
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vyacheslav Daradur
>
> See org.apache.ignite.IgniteLock for reference



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

[jira] [Assigned] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-5767:
--

Assignee: Vasiliy Sisko  (was: Andrey Novikov)

> Web console: use byte array type instead of java.lang.Object for binary JDBC 
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
>
> Schema importer should use {{[B}} query entity field type instead of 
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}} 
> and {{LONGVARBINARY}}.



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

[jira] [Commented] (IGNITE-5467) Exception in communication SPI can stall the cluster

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098075#comment-16098075
 ] 

ASF GitHub Bot commented on IGNITE-5467:


Github user ezhuravl closed the pull request at:

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


> Exception in communication SPI can stall the cluster
> 
>
> Key: IGNITE-5467
> URL: https://issues.apache.org/jira/browse/IGNITE-5467
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
> Fix For: 2.2
>
> Attachments: MessageSendExceptionTest.java
>
>
> Test attached.
> If there is an exception in {{CommunicationSpi#sendMessage}} while sending 
> response for a cache operation, it can stall whole cluster forever (operation 
> doesn't complete, new nodes can't join, etc.).



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

[jira] [Updated] (IGNITE-4775) Web Console: Implement role-based access control

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4775:
-
Fix Version/s: 2.2

> Web Console: Implement role-based access control
> 
>
> Key: IGNITE-4775
> URL: https://issues.apache.org/jira/browse/IGNITE-4775
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
> Fix For: 2.2
>
>




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

[jira] [Commented] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098009#comment-16098009
 ] 

Vladimir Ozerov commented on IGNITE-5345:
-

[~dmagda], I added separate page for the driver, please review: 
https://apacheignite.readme.io/v2.1/docs/jdbc-thin-driver
Looks like we need to restructure the whole JDBC section somehow. Previous page 
contains a lot of unnecessary information.

> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



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

[jira] [Assigned] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-5345:
---

Assignee: Denis Magda  (was: Vladimir Ozerov)

> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



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