[jira] [Commented] (IGNITE-6701) Do not deserialize previous value during indexes update

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6701:
-

Benchmarks shown ~10% performance gain in case of multiple indexes.

> Do not deserialize previous value during indexes update
> ---
>
> Key: IGNITE-6701
> URL: https://issues.apache.org/jira/browse/IGNITE-6701
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Roman Kondakov
>  Labels: iep-1, performance
> Fix For: 2.4
>
>
> In GridH2Table.doUpdate all indexes are updated using BPlusTree.put method 
> which deserializes previous value, actually previous value is already 
> available in GridQueryProcessor.store/remove methods. Need try to change 
> GridH2Table.doUpdate to use BPlusTree.putx instead of BPlusTree.put.



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

[jira] [Assigned] (IGNITE-6437) DataStructure can not be obtained on client if it is created on server node.

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny reassigned IGNITE-6437:
--

Assignee: Alexey Goncharuk  (was: Stanilovsky Evgeny)

> DataStructure can not be obtained on client if it is created on server node.
> 
>
> Key: IGNITE-6437
> URL: https://issues.apache.org/jira/browse/IGNITE-6437
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.1, 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.4
>
> Attachments: NoQueueOnClientNodeTest.java, tc_111.png
>
>
> DataStructure can not be obtained on client if it is created on server node.



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

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-6005:
-

[~ezhuravl] Thank you!

Please, see my answers and fixes in review.

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> 

[jira] [Commented] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny commented on IGNITE-5955:


[TC seems 
ok|https://ci.ignite.apache.org/viewLog.html?buildId=932284=buildResultsDiv=Ignite20Tests_RunAll]


> Ignite Continuous Query (Queries 3): 
> IgniteCacheContinuousQueryClientReconnectTest fails
> 
>
> Key: IGNITE-5955
> URL: https://issues.apache.org/jira/browse/IGNITE-5955
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>  Labels: MakeTeamcityGreenAgain, test-failure
>
> Reproducible locally with the same exception as on TC.
> In test log there is the following exception:
> {noformat}
> [2017-08-07 
> 03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
>  Failed to stop grid 
> [igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0,
>  cancel=true]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node 
> disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
> at 
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> According to [TC 
> history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
>  is failing since mid of April.
> Last commit where test has been passing is *b6b3d3754849*.



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

[jira] [Commented] (IGNITE-6701) Do not deserialize previous value during indexes update

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6701:


Github user asfgit closed the pull request at:

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


> Do not deserialize previous value during indexes update
> ---
>
> Key: IGNITE-6701
> URL: https://issues.apache.org/jira/browse/IGNITE-6701
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Roman Kondakov
>  Labels: iep-1, performance
> Fix For: 2.4
>
>
> In GridH2Table.doUpdate all indexes are updated using BPlusTree.put method 
> which deserializes previous value, actually previous value is already 
> available in GridQueryProcessor.store/remove methods. Need try to change 
> GridH2Table.doUpdate to use BPlusTree.putx instead of BPlusTree.put.



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

[jira] [Commented] (IGNITE-5635) Web Console: Show query execution progress

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin commented on IGNITE-5635:
---

Progress indication to Export\Export btn's has been added

> Web Console: Show query execution progress
> --
>
> Key: IGNITE-5635
> URL: https://issues.apache.org/jira/browse/IGNITE-5635
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexander Kalinin
>
> Show query execution progress, some progress or spinning wheel.



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

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-6824:


Assignee: Pavel Konstantinov  (was: Ilya Borisov)

Please test as much screens as possible, the changes in this issue affect whole 
app.

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



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

[jira] [Commented] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-6824:
--

[~alexdel] looks good to me.

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



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

[jira] [Commented] (IGNITE-6687) SQL Error Codes Documentation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6687:
-

[~isapego], could you provide a small example showing how to catch and process 
an exception depending on an error code? Please see how it was done for JDBC: 
https://apacheignite-sql.readme.io/v2.3/docs/jdbc-error-codes

> SQL Error Codes Documentation
> -
>
> Key: IGNITE-6687
> URL: https://issues.apache.org/jira/browse/IGNITE-6687
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.4
>
>
> Presently we have JDBC error codes documented:
> https://apacheignite-sql.readme.io/docs/jdbc-error-codes
> Two things have to be done:
> * If there are similar error codes shared between the ODBC and JDBC drivers, 
> and native APIs then let's put them under SQL reference category below Data 
> Types: https://apacheignite-sql.readme.io/docs/sql-reference-overview
> * ODBC specific error codes with an example of an error handling need to be 
> listed in ODBC category [~isapego], please assist with this: 
> https://apacheignite-sql.readme.io/docs/odbc-driver
> Discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-error-codes-td23415.html



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

[jira] [Commented] (IGNITE-6686) Document SQL Data Types

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6686:
-

[~vozerov], I've adopted the H2 format. Looks clear right now. Please check it 
up.

In addition, please spare some time for the following:
* What's Java/JDBC type used for DATE? Is it from sql or utils package? 
Presently Java/JDBC part is blank: 
https://apacheignite-sql.readme.io/v2.3/docs/data-types#section-date
* Skim through all the types documented confirming the description's 
correctness.
* Do we support any of the types listed below? If yes then please add a missing 
type to our documentation.
http://www.h2database.com/html/datatypes.html#identity_type
http://www.h2database.com/html/datatypes.html#binary_type
http://www.h2database.com/html/datatypes.html#other_type
http://www.h2database.com/html/datatypes.html#varchar_ignorecase_type
http://www.h2database.com/html/datatypes.html#blob_type
http://www.h2database.com/html/datatypes.html#clob_type
http://www.h2database.com/html/datatypes.html#array_type
http://www.h2database.com/html/datatypes.html#enum_type


> Document SQL Data Types
> ---
>
> Key: IGNITE-6686
> URL: https://issues.apache.org/jira/browse/IGNITE-6686
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> The data types page should include all SQL types supported and how they 
> mapped to a language or driver specific type. Presently the types are 
> represented in a tabular format:
> https://apacheignite-sql.readme.io/v2.3/docs/data-types
> Guys, please help to fill out langage/drivers specific columns:
> # [~ptupitsyn] - .NET data types.
> # [~isapego] - C++ and ODBC data type.
> # [~al.psc] - JDBC and JAVA data types.
> [~vozerov], please suggest what to do with these few types below. They 
> supported by H2 but I'm not sure how Ignite deals with them:
> http://www.h2database.com/html/datatypes.html#identity_type
> http://www.h2database.com/html/datatypes.html#binary_type
> http://www.h2database.com/html/datatypes.html#other_type
> http://www.h2database.com/html/datatypes.html#varchar_ignorecase_type
> http://www.h2database.com/html/datatypes.html#blob_type
> http://www.h2database.com/html/datatypes.html#clob_type
> http://www.h2database.com/html/datatypes.html#array_type
> http://www.h2database.com/html/datatypes.html#enum_type



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

[jira] [Assigned] (IGNITE-6607) Thin client: protocol documentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6607:
---

Assignee: Prachi Garg  (was: Pavel Tupitsyn)

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



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

[jira] [Updated] (IGNITE-6607) Thin client: protocol documentation

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6607:

Description: 
Document thin client protocol on Apache Ignite readme.op:

* Common message format (length, flags)
* Data types (endianness, strings, etc)
* Request/Response format for each message type
* How to connect

A list of supported commands can be taken from here:
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java

The protocol documentation format can be similar to REST API:
https://apacheignite.readme.io/docs/rest-api

  was:
Document thin client protocol on Ignite wiki: 
https://cwiki.apache.org/confluence/display/IGNITE/Design+Documents

* Common message format (length, flags)
* Data types (endianness, strings, etc)
* Request/Response format for each message type
* How to connect


> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



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

[jira] [Commented] (IGNITE-6500) POJO fields of java wrapper type are not retaining null values from Cassandra persistent store, while using ignite's CassandraCacheStoreFactory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6500:


GitHub user kotamrajuyashasvi opened a pull request:

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

IGNITE-6500 Bug in ignite's CassandraCacheStoreFactory

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

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

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

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

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


commit 1c9c4abd03f3ff47dfdfbf651fcae87df9a0506b
Author: kotamrajuyashasvi 
Date:   2017-09-28T20:10:41Z

IGNITE-6500

commit f452f1c3d83986a7ea72e36da36730ae3b7b73bf
Author: kotamrajuyashasvi 
Date:   2017-09-28T20:29:53Z

IGNITE-6500




> POJO fields of java wrapper type are not retaining null values from Cassandra 
> persistent store, while using ignite's CassandraCacheStoreFactory
> ---
>
> Key: IGNITE-6500
> URL: https://issues.apache.org/jira/browse/IGNITE-6500
> Project: Ignite
>  Issue Type: Bug
>  Components: cassandra
>Affects Versions: 2.1
>Reporter: Yashasvi Kotamraju
>Assignee: Yashasvi Kotamraju
>Priority: Minor
> Fix For: 2.4
>
>
> While using  ignite's CassandraCacheStoreFactory(part of 
> ignite-cassandra-store.jar) as cacheStoreFactory for a cache, if a POJO field 
> is of wrapper class type, and the column value mapped in Cassandra persistent 
> store is null then the POJO field is getting set to default primitive type 
> instead of null.
> For Example: Assume a table 'person' in a Cassandra persistent store with the 
> following structure and data.
> *table person:*
> *column*person_no(int)phno(text) address(text)  age(int)  
> name(text)   
> *data* 1 12353   null 
>  nullyash 
> person_no is the PRIMARY_KEY.
> This table is mapped to person POJO  for ignite cache.
> public class person{
>   private int person_no;
>   private String name;
>   private Integer age=null;
>   private String phno;
>   private String address;
> .getters and setters etc..
> }
> Now we load the row from Cassandra into ignite cache using cache.get(1) or 
> cache.load(..) And we are using ignite's CassandraCacheStoreFactory for this 
> cache.
> Let person p1 = cache.get(1);
> now p1.getName returns "yash", p1.getAddress returns null.
> But  p1.getAge returns 0 instead of null. It is expected null value since the 
> value is null in Cassandra persistent store.
> Hence if the value is 0 for the age field there is no way differentiate if it 
> was null or it was actually 0. The similar problem exists for other wrapper 
> types -> Long, Float, Double, Boolean.
> This problem cause is as follows. 
> In 
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(..)
>  method first the Cassandra field value is obtained by using the method 
> PropertyMappingHelper.getCassandraColumnValue(..). This method calls DataStax 
> Driver methods Row.getInt() or Row.getFloat() or Row.getDouble() etc.. 
> depending upon the column. This value obtained from this method is then set 
> to the respective POJO field. But According to Datastax documentation getInt 
> returns 0 if column value is null and similarly getLong returns 0L , 
> getDouble return 0.0 etc. Hence PropertyMappingHelper. 
> getCassandraColumnValue returns 0 or 0L or 0.0 or false even if the value is 
> null. And then this value is set to the wrapper type POJO fields. The problem 
> only persists with the primitive data types in Cassandra mapped to wrapper 
> type fields in POJO. For other types like String , Date etc.. the null values 
> are retained in the POJO fields. 



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

[jira] [Commented] (IGNITE-6649) Add EvictionPolicy factory support in IgniteConfiguration.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-6649:
--

[~agura],
TC tests looks fine. 
Would you please review once again?

> Add EvictionPolicy factory support in IgniteConfiguration.
> --
>
> Key: IGNITE-6649
> URL: https://issues.apache.org/jira/browse/IGNITE-6649
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: EvictionPolicyTest.java
>
>
> For now the only way to set EvictionPolicy to IgniteConfiguration is to use 
> EvictionPolicy instance. 
> That looks error prone as user can easily share instance between caches or 
> cache reincarnations and got unexpected results.
> E.g. it can cause an AssertionError if EvictionPolicy is reused.
> Steps to reproduce.
> 1. Create CacheConfiguration object that will be reused.
> 2. Create and fill a cache.
> 3. Destroy cache and create cache again with same CacheConfiguration object.
> 4. One of next put can fails with stacktrace below.
> The error is throws when EvictionPolicy tries to evict entries from cache 
> that has just been destroyed.
> Also, EvictionPolicy object can be implicitly holds by some user objects 
> (together with IgniteConfiguration) that can cause memory leak.
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.CacheEvictableEntryImpl.evict(CacheEvictableEntryImpl.java:71)
>   at 
> org.apache.ignite.cache.eviction.lru.LruEvictionPolicy.shrink0(LruEvictionPolicy.java:275)
>   at 
> org.apache.ignite.cache.eviction.lru.LruEvictionPolicy.shrink(LruEvictionPolicy.java:250)
>   at 
> org.apache.ignite.cache.eviction.lru.LruEvictionPolicy.onEntryAccessed(LruEvictionPolicy.java:161)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.notifyPolicy(GridCacheEvictionManager.java:1393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(GridCacheEvictionManager.java:825)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3058)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1952)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1730)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.mapSingle(GridNearAtomicAbstractUpdateFuture.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:494)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:436)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1245)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:680)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2328)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2305)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1379)
>  
> UPD: See discussion here [1].
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/CacheConfiguration-reusage-issues-with-EvictionPolicy-enabled-td23437.html



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

[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-425:


Hello, [~avinogradov].

Did you have a chance to review the ticket?

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: 2.2
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
> Fix For: 2.4
>
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



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

[jira] [Updated] (IGNITE-6835) ODBC driver should handle ungraceful tcp disconnects

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-6835:

Description: 
It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
recv().
Ungraceful TCP disconnect could be caused:
1. Network failure (or new firewall rules)
2. Remote party shutdown (Half Closed Connection)

So, the proposal is:
setup socket  options: 
1) SO_KEEPALIVE enabled
2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
3) TCP_KEEPINTVL to 5 (\?) sec. It is 1 sec at Win and 75 sec at Linux by 
default.
4) send/receive buffers to some greater value (8k by default)


  was:
It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
recv().
Ungraceful TCP disconnect could be caused:
1. Network failure (or new firewall rules)
2. Remote party shutdown (Half Closed Connection)

So, the proposal is:
setup socket  options: 
1) SO_KEEPALIVE enabled
2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
3) TCP_KEEPINTVL to 5 (?) sec. It is 1 sec at Win and 75 sec at Linux by 
default.
4) send/receive buffers to some greater value (8k by default)



> ODBC driver should handle ungraceful tcp disconnects
> 
>
> Key: IGNITE-6835
> URL: https://issues.apache.org/jira/browse/IGNITE-6835
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: odbc
>Affects Versions: 2.1
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>
> It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
> recv().
> Ungraceful TCP disconnect could be caused:
> 1. Network failure (or new firewall rules)
> 2. Remote party shutdown (Half Closed Connection)
> So, the proposal is:
> setup socket  options: 
> 1) SO_KEEPALIVE enabled
> 2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
> 3) TCP_KEEPINTVL to 5 (\?) sec. It is 1 sec at Win and 75 sec at Linux by 
> default.
> 4) send/receive buffers to some greater value (8k by default)



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

[jira] [Commented] (IGNITE-6687) SQL Error Codes Documentation

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-6687:
-

[~dmagda], [~vozerov], I've added errors for the ODBC driver. Check it out - 
https://apacheignite-sql.readme.io/v2.3/docs/error-codes

> SQL Error Codes Documentation
> -
>
> Key: IGNITE-6687
> URL: https://issues.apache.org/jira/browse/IGNITE-6687
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.4
>
>
> Presently we have JDBC error codes documented:
> https://apacheignite-sql.readme.io/docs/jdbc-error-codes
> Two things have to be done:
> * If there are similar error codes shared between the ODBC and JDBC drivers, 
> and native APIs then let's put them under SQL reference category below Data 
> Types: https://apacheignite-sql.readme.io/docs/sql-reference-overview
> * ODBC specific error codes with an example of an error handling need to be 
> listed in ODBC category [~isapego], please assist with this: 
> https://apacheignite-sql.readme.io/docs/odbc-driver
> Discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-error-codes-td23415.html



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

[jira] [Commented] (IGNITE-6837) Create a CREATE INDEX benchmark

[Roman Kondakov (JIRA)]

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

Roman Kondakov commented on IGNITE-6837:


[~vozerov], please review the patch: 
[https://github.com/apache/ignite/pull/2991]

> Create a CREATE INDEX benchmark
> ---
>
> Key: IGNITE-6837
> URL: https://issues.apache.org/jira/browse/IGNITE-6837
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: yardstick
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>  Labels: benchmark
> Fix For: 2.4
>
>
> We need to implement a benchmark for the dynamically created indexes build 
> time in order to test our optimizations.



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

[jira] [Commented] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6839:


GitHub user dspavlov opened a pull request:

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

IGNITE-6839: delete binary meta before tests, PDS compatibility tests 



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

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

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

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


commit e6dcb4af579aeb3e01bcd3555098e2ad49b28040
Author: dpavlov 
Date:   2017-11-07T16:13:42Z

IGNITE-6839: delete binary meta before tests, PDS compatibility tests 
improved




> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> 
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Ignite Compatibility: 2 test are flaky:
>   
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
>  (fails: 2/55): 
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta, 
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in 
> https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Created] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-6839:
--

 Summary: Ignite Compatibility: flaky test 
testFoldersReuseCompatibility_2_1 & 2_2
 Key: IGNITE-6839
 URL: https://issues.apache.org/jira/browse/IGNITE-6839
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: persistence
Affects Versions: 2.3
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
 Fix For: 2.4


Ignite Compatibility: 2 test are flaky:
  org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
 (fails: 2/55): 

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E

{noformat}
junit.framework.AssertionFailedError: Directory [binary_meta, 
135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
[/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
at 
org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
{noformat}

Test probaly indicates a bug in 
https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Updated] (IGNITE-6838) .NET: Add CacheConfiguration.EvictionPolicyFactory

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-6838:
---
Labels: .NET  (was: )

> .NET: Add CacheConfiguration.EvictionPolicyFactory
> --
>
> Key: IGNITE-6838
> URL: https://issues.apache.org/jira/browse/IGNITE-6838
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Andrew Mashenkov
>  Labels: .NET
>
> Add EvictionPolicyFactory support to cache configuration.



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

[jira] [Updated] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5885:
---
Description: 
Just copy a configuration and change NUnit bitness.
We should probably run only a subset of tests (introduce "BASIC_TEST" category 
or something).

  was:Just copy a configuration and change NUnit bitness.


> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.
> We should probably run only a subset of tests (introduce "BASIC_TEST" 
> category or something).



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

[jira] [Updated] (IGNITE-6838) .NET: Add CacheConfiguration.EvictionPolicyFactory

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-6838:
-
Description: Add EvictionPolicyFactory support to cache configuration.  
(was: Add EvictionPolicyFactory support in configuration.)

> .NET: Add CacheConfiguration.EvictionPolicyFactory
> --
>
> Key: IGNITE-6838
> URL: https://issues.apache.org/jira/browse/IGNITE-6838
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Andrew Mashenkov
>
> Add EvictionPolicyFactory support to cache configuration.



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

[jira] [Updated] (IGNITE-6838) .NET: Add CacheConfiguration.EvictionPolicyFactory

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-6838:
-
Description: Add EvictionPolicyFactory support in configuration.

> .NET: Add CacheConfiguration.EvictionPolicyFactory
> --
>
> Key: IGNITE-6838
> URL: https://issues.apache.org/jira/browse/IGNITE-6838
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Andrew Mashenkov
>
> Add EvictionPolicyFactory support in configuration.



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

[jira] [Created] (IGNITE-6838) .NET: Add CacheConfiguration.EvictionPolicyFactory

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-6838:


 Summary: .NET: Add CacheConfiguration.EvictionPolicyFactory
 Key: IGNITE-6838
 URL: https://issues.apache.org/jira/browse/IGNITE-6838
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: platforms
Reporter: Andrew Mashenkov






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

[jira] [Commented] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5343:


All done, waiting for TC run.

> .NET: Interoperate with JVM directly, get rid of C++ layer
> --
>
> Key: IGNITE-5343
> URL: https://issues.apache.org/jira/browse/IGNITE-5343
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> We can work with JNI directly using P/Invoke, there is no real need for C++ 
> layer.
> Advantages of removing C++ layer:
> * *No MSVC++ 2010 dependency*
> * *No build tools required for development*
> * Simplify and speed up the build procedure
> * No embedded libraries
> * Easier crossplatform support (IGNITE-2662)



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

[jira] [Commented] (IGNITE-5846) Add support of distributed matrices for OLS regression.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5846:


GitHub user zaleslaw opened a pull request:

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

IGNITE-5846: Add support of distributed matrices for OLS regression.



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

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

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

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


commit e4450ed14cd0b27b00351afd3356383cfbcf9eb4
Author: zaleslaw 
Date:   2017-10-04T17:51:31Z

Renamed variables for readability

commit 5ef823b3a735d09261b545f21d1c576ebbe4baf0
Author: zaleslaw 
Date:   2017-10-04T17:52:17Z

Renamed method according javadoc

commit 5ed2047d6a9990597c2c8f17ec901296eeb486b8
Author: zaleslaw 
Date:   2017-10-04T17:52:47Z

Created skeleton for distributed version

commit 69508d52339834db98fcac781f86823da208bc9b
Author: zaleslaw 
Date:   2017-10-04T19:27:14Z

Fixed example

commit 38480ca561a92ef154ca767b24d28847863ed900
Author: zaleslaw 
Date:   2017-10-04T19:27:47Z

Added distributed skeleton for QR decomposition

commit 3040e8f6b3950de67990cd9ddc8e09cf42bcb802
Author: zaleslaw 
Date:   2017-10-04T19:28:13Z

Deleted strange behaviour of like method

commit 39e61dcfff285d26fb517c87fc2777cc4077cca9
Author: zaleslaw 
Date:   2017-10-05T09:54:09Z

Removed local matrix creation for distributed matrix in like operator

commit 93c2f78db3e8d0221f2281af6b34173239d5ae21
Author: zaleslaw 
Date:   2017-10-05T10:09:01Z

Removed local matrix creation for distributed matrix in like operator 
(correct version)

commit abebeb186c1949114be9b26c9cefa3684651bf29
Author: zaleslaw 
Date:   2017-10-05T12:17:54Z

Added review of copy-paste class

commit 667a37601f3e64e256a6d172ece1cca4e0b9c7b3
Author: zaleslaw 
Date:   2017-10-05T12:22:15Z

Added review of copy-paste class (for QR)

commit 62a21f14379eb43c5195286a16cd96ede57197a6
Author: zaleslaw 
Date:   2017-10-05T18:50:25Z

Added draft of SparseDistributedVectorStorage and SparseDistributedVector 
with tests

commit 6cc85e63a8c086a6afb5976e548b78f30b1a45e3
Author: zaleslaw 
Date:   2017-10-14T14:43:12Z

Finished SparseDistributedVector initial design

commit 62ddd46972de5c7c5873438f81c7b35d33b6427b
Author: zaleslaw 
Date:   2017-10-14T15:56:21Z

Added draft of distributed regression test

commit a8b998ddeb297249b501f211ef088c5076b1c003
Author: zaleslaw 
Date:   2017-10-15T15:59:49Z

Implemented copy, like and other useful functions for distributed structures

commit 5ad808486e8fe876cc3f665c56845ab7275ecdcf
Author: zaleslaw 
Date:   2017-10-15T16:00:43Z

Fixed small bugs in regression

commit 5ed519902eac0754adb3c84bf532e987cd76d7be
Author: zaleslaw 
Date:   2017-10-15T16:01:14Z

Fixed Distributed Regression Test and Suite

commit d95ffaab178d79747ed1e8371899f54892dc1f02
Author: zaleslaw 
Date:   2017-10-15T17:17:18Z

Fixed NewSampleDataXNull test

commit f56c08d729781ff3298efefba5412b81044e3343
Author: zaleslaw 
Date:   2017-10-15T19:08:22Z

Added debug messages

commit 31835c50a3aa0f80dc26cedf6014c0eda7ace2c4
Author: zaleslaw 
Date:   2017-10-17T17:01:15Z

Change SDM on SDBM

commit 76bdc3dd8fd09b385a8de91f9862808b8d4e90c9
Author: zaleslaw 
Date:   2017-10-21T12:48:44Z

Finished SDV and SDBM with storages

commit 6c99b486fb5a1e2cf0ff630893a8e3cadf3c1604
Author: zaleslaw 
Date:   2017-10-21T12:49:50Z

Changed test according adding support for the operation

commit d172d35e627e92b065ce65451ef1b21acb6a9e8a
Author: zaleslaw 
Date:   2017-10-21T12:51:20Z

Added test for Matrix-Vector multiplication and fixed failed test

commit 1df2a12c14b032d10f1ab1e718140a8bb0a11056
Author: zaleslaw 
Date:   2017-10-31T15:32:57Z

Added debug changes before merge

commit df9b35a3000966a3f9c3dfeb735dd93d11e5bee7
Author: zaleslaw 
Date:   2017-10-31T15:49:38Z

Merge with last master updates

commit 4af3a85bf55d62a24f566b84e29bb243af5eb3a3
Author: zaleslaw 
Date:   

[jira] [Assigned] (IGNITE-6687) SQL Error Codes Documentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6687:
---

Assignee: Igor Sapego  (was: Vladimir Ozerov)

> SQL Error Codes Documentation
> -
>
> Key: IGNITE-6687
> URL: https://issues.apache.org/jira/browse/IGNITE-6687
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.4
>
>
> Presently we have JDBC error codes documented:
> https://apacheignite-sql.readme.io/docs/jdbc-error-codes
> Two things have to be done:
> * If there are similar error codes shared between the ODBC and JDBC drivers, 
> and native APIs then let's put them under SQL reference category below Data 
> Types: https://apacheignite-sql.readme.io/docs/sql-reference-overview
> * ODBC specific error codes with an example of an error handling need to be 
> listed in ODBC category [~isapego], please assist with this: 
> https://apacheignite-sql.readme.io/docs/odbc-driver
> Discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-error-codes-td23415.html



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

[jira] [Updated] (IGNITE-6687) SQL Error Codes Documentation

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6687:

Fix Version/s: (was: 2.3)
   2.4

> SQL Error Codes Documentation
> -
>
> Key: IGNITE-6687
> URL: https://issues.apache.org/jira/browse/IGNITE-6687
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.4
>
>
> Presently we have JDBC error codes documented:
> https://apacheignite-sql.readme.io/docs/jdbc-error-codes
> Two things have to be done:
> * If there are similar error codes shared between the ODBC and JDBC drivers, 
> and native APIs then let's put them under SQL reference category below Data 
> Types: https://apacheignite-sql.readme.io/docs/sql-reference-overview
> * ODBC specific error codes with an example of an error handling need to be 
> listed in ODBC category [~isapego], please assist with this: 
> https://apacheignite-sql.readme.io/docs/odbc-driver
> Discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-error-codes-td23415.html



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

[jira] [Comment Edited] (IGNITE-5218) Decision trees

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-5218 at 11/7/17 3:26 PM:
-

Example provided for decision trees 
([MNISTExample|https://github.com/gridgain/apache-ignite/blob/ignite-5218/examples/src/main/ml/org/apache/ignite/examples/ml/math/trees/MNISTExample.java])
 looks sufficiently documented and runs fine on my machine.

Unit tests run successfully on my machine 
([DecisionTreesTestSuite|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/DecisionTreesTestSuite.java]),
 as well as "internal" benchmark 
[ColumnDecisionTreeTrainerBenchmark|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/performance/ColumnDecisionTreeTrainerBenchmark.java].
 Worth noting that yesterday Yury did a [trial run on 
TC|https://ci.ignite.apache.org/viewLog.html?buildId=927458=Ignite20Tests_IgniteMl=buildResultsDiv]
 for this pull request and it came out all green.

Code formatting looks right in both main and test parts.

Code inspections results are okay in both main and test parts.

(!) [~amalykh] - prior to passing this PR to committer for merge please re-run 
PR on TeamCity in order to make sure that changes made during review didn't 
introduce failures. Add the link of TC results to this ticket so that it's 
easier to check for the committer.


was (Author: oignatenko):
Example provided for decision trees 
([MNISTExample|https://github.com/gridgain/apache-ignite/blob/ignite-5218/examples/src/main/ml/org/apache/ignite/examples/ml/math/trees/MNISTExample.java])
 looks sufficiently documented and runs fine on my machine.

Unit tests run successfully on my machine 
([DecisionTreesTestSuite|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/DecisionTreesTestSuite.java]),
 as well as "internal" benchmark 
[ColumnDecisionTreeTrainerBenchmark|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/performance/ColumnDecisionTreeTrainerBenchmark.java].
 Worth noting that yesterday Yury did a [trial run on 
TC|https://ci.ignite.apache.org/viewLog.html?buildId=927458=Ignite20Tests_IgniteMl=buildResultsDiv]
 for this pull request and it came out all green.

Code formatting looks right in both main and test parts.

Code inspections results are okay in both main and test parts.

> Decision trees
> --
>
> Key: IGNITE-5218
> URL: https://issues.apache.org/jira/browse/IGNITE-5218
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
>
> We want to implement Decision trees for Ignite ML because it's really common 
> one for ML.



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

[jira] [Comment Edited] (IGNITE-5218) Decision trees

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-5218 at 11/7/17 3:17 PM:
-

Example provided for decision trees 
([MNISTExample|https://github.com/gridgain/apache-ignite/blob/ignite-5218/examples/src/main/ml/org/apache/ignite/examples/ml/math/trees/MNISTExample.java])
 looks sufficiently documented and runs fine on my machine.

Unit tests run successfully on my machine 
([DecisionTreesTestSuite|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/DecisionTreesTestSuite.java]),
 as well as "internal" benchmark 
[ColumnDecisionTreeTrainerBenchmark|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/performance/ColumnDecisionTreeTrainerBenchmark.java].
 Worth noting that yesterday Yury did a [trial run on 
TC|https://ci.ignite.apache.org/viewLog.html?buildId=927458=Ignite20Tests_IgniteMl=buildResultsDiv]
 for this pull request and it came out all green.

Code formatting looks right in both main and test parts.

Code inspections results are okay in both main and test parts.


was (Author: oignatenko):
Example provided for decision trees 
([MNISTExample|https://github.com/gridgain/apache-ignite/blob/ignite-5218/examples/src/main/ml/org/apache/ignite/examples/ml/math/trees/MNISTExample.java])
 looks sufficiently documented and runs fine on my machine.

Unit tests run successfully on my machine 
([DecisionTreesTestSuite|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/DecisionTreesTestSuite.java]),
 as well as "internal" benchmark 
[ColumnDecisionTreeTrainerBenchmark|https://github.com/gridgain/apache-ignite/blob/ignite-5218/modules/ml/src/test/java/org/apache/ignite/ml/trees/performance/ColumnDecisionTreeTrainerBenchmark.java].
 Worth noting that yesterday Yury did a [trial run on 
TC|https://ci.ignite.apache.org/viewLog.html?buildId=927458=Ignite20Tests_IgniteMl=buildResultsDiv]
 for this pull request and it came out all green.

Code formatting looks right in both main and test parts.

Code inspections results for main part are mostly okay, I commented on few 
remaining minor issues in pull request. (x) Code inspections for test part are 
yet to be fixed.

> Decision trees
> --
>
> Key: IGNITE-5218
> URL: https://issues.apache.org/jira/browse/IGNITE-5218
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
>
> We want to implement Decision trees for Ignite ML because it's really common 
> one for ML.



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

[jira] [Assigned] (IGNITE-6437) DataStructure can not be obtained on client if it is created on server node.

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-6437:


Assignee: Stanilovsky Evgeny  (was: Ilya Lantukh)

> DataStructure can not be obtained on client if it is created on server node.
> 
>
> Key: IGNITE-6437
> URL: https://issues.apache.org/jira/browse/IGNITE-6437
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Attachments: NoQueueOnClientNodeTest.java, tc_111.png
>
>
> DataStructure can not be obtained on client if it is created on server node.



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

[jira] [Commented] (IGNITE-6437) DataStructure can not be obtained on client if it is created on server node.

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-6437:
--

Looks good.

> DataStructure can not be obtained on client if it is created on server node.
> 
>
> Key: IGNITE-6437
> URL: https://issues.apache.org/jira/browse/IGNITE-6437
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Ilya Lantukh
>Priority: Critical
> Attachments: NoQueueOnClientNodeTest.java, tc_111.png
>
>
> DataStructure can not be obtained on client if it is created on server node.



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

[jira] [Updated] (IGNITE-6837) Create a CREATE INDEX benchmark

[Roman Kondakov (JIRA)]

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

Roman Kondakov updated IGNITE-6837:
---
Component/s: yardstick

> Create a CREATE INDEX benchmark
> ---
>
> Key: IGNITE-6837
> URL: https://issues.apache.org/jira/browse/IGNITE-6837
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: yardstick
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>  Labels: benchmark
> Fix For: 2.4
>
>
> We need to implement a benchmark for the dynamically created indexes build 
> time in order to test our optimizations.



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

[jira] [Updated] (IGNITE-6837) Create a CREATE INDEX benchmark

[Roman Kondakov (JIRA)]

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

Roman Kondakov updated IGNITE-6837:
---
Fix Version/s: 2.4

> Create a CREATE INDEX benchmark
> ---
>
> Key: IGNITE-6837
> URL: https://issues.apache.org/jira/browse/IGNITE-6837
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>  Labels: benchmark
> Fix For: 2.4
>
>
> We need to implement a benchmark for the dynamically created indexes build 
> time in order to test our optimizations.



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

[jira] [Created] (IGNITE-6837) Create a CREATE INDEX benchmark

[Roman Kondakov (JIRA)]

Roman Kondakov created IGNITE-6837:
--

 Summary: Create a CREATE INDEX benchmark
 Key: IGNITE-6837
 URL: https://issues.apache.org/jira/browse/IGNITE-6837
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Roman Kondakov
Assignee: Roman Kondakov


We need to implement a benchmark for the dynamically created indexes build time 
in order to test our optimizations.



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

[jira] [Assigned] (IGNITE-6835) ODBC driver should handle ungraceful tcp disconnects

[Alexey Popov (JIRA)]

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

Alexey Popov reassigned IGNITE-6835:


Assignee: Alexey Popov

> ODBC driver should handle ungraceful tcp disconnects
> 
>
> Key: IGNITE-6835
> URL: https://issues.apache.org/jira/browse/IGNITE-6835
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: odbc
>Affects Versions: 2.1
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>
> It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
> recv().
> Ungraceful TCP disconnect could be caused:
> 1. Network failure (or new firewall rules)
> 2. Remote party shutdown (Half Closed Connection)
> So, the proposal is:
> setup socket  options: 
> 1) SO_KEEPALIVE enabled
> 2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
> 3) TCP_KEEPINTVL to 5 (?) sec. It is 1 sec at Win and 75 sec at Linux by 
> default.
> 4) send/receive buffers to some greater value (8k by default)



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

[jira] [Created] (IGNITE-6836) ODBC: Add support for SQL_ATTR_QUERY_TIMEOUT

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-6836:


 Summary: ODBC: Add support for SQL_ATTR_QUERY_TIMEOUT
 Key: IGNITE-6836
 URL: https://issues.apache.org/jira/browse/IGNITE-6836
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: odbc
Affects Versions: 2.1
Reporter: Alexey Popov


It would be great if we can support SQL_ATTR_QUERY_TIMEOUT at ODBC.

That gives a flexibility to end-user code to handle long-running/timeouted 
queries.



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

[jira] [Created] (IGNITE-6835) ODBC driver should handle ungraceful tcp disconnects

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-6835:


 Summary: ODBC driver should handle ungraceful tcp disconnects
 Key: IGNITE-6835
 URL: https://issues.apache.org/jira/browse/IGNITE-6835
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: odbc
Affects Versions: 2.1
Reporter: Alexey Popov


It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
recv().
Ungraceful TCP disconnect could be caused:
1. Network failure (or new firewall rules)
2. Remote party shutdown (Half Closed Connection)

So, the proposal is:
setup socket  options: 
1) SO_KEEPALIVE enabled
2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
3) TCP_KEEPINTVL to 5 (?) sec. It is 1 sec at Win and 75 sec at Linux by 
default.
4) send/receive buffers to some greater value (8k by default)




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

[jira] [Resolved] (IGNITE-6805) Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32)

[Aleksey Zinoviev (JIRA)]

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

Aleksey Zinoviev resolved IGNITE-6805.
--
   Resolution: Fixed
Fix Version/s: 2.4

> Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32)
> --
>
> Key: IGNITE-6805
> URL: https://issues.apache.org/jira/browse/IGNITE-6805
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: ml
>Affects Versions: 2.4
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
> Fix For: 2.4
>
>
> In SparseDistributedBlockMatrixTest are red next tests
> * testCacheBehaviour
> * testSquareMatrixTimes
> with another value of constant MAX_BLOCK_SIZE (4 or 8, for example)
> In my opinion, it means that algorithm is incorrect for matrices with large 
> number of blocks



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

[jira] [Commented] (IGNITE-6686) Document SQL Data Types

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6686:
-

[~dmagda], or may be it makes sense to has separate paragraph for every type. 
Current table is almost unreadable. See H2 for reference: 
http://www.h2database.com/html/datatypes.html

> Document SQL Data Types
> ---
>
> Key: IGNITE-6686
> URL: https://issues.apache.org/jira/browse/IGNITE-6686
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> The data types page should include all SQL types supported and how they 
> mapped to a language or driver specific type. Presently the types are 
> represented in a tabular format:
> https://apacheignite-sql.readme.io/v2.3/docs/data-types
> Guys, please help to fill out langage/drivers specific columns:
> # [~ptupitsyn] - .NET data types.
> # [~isapego] - C++ and ODBC data type.
> # [~al.psc] - JDBC and JAVA data types.
> [~vozerov], please suggest what to do with these few types below. They 
> supported by H2 but I'm not sure how Ignite deals with them:
> http://www.h2database.com/html/datatypes.html#identity_type
> http://www.h2database.com/html/datatypes.html#binary_type
> http://www.h2database.com/html/datatypes.html#other_type
> http://www.h2database.com/html/datatypes.html#varchar_ignorecase_type
> http://www.h2database.com/html/datatypes.html#blob_type
> http://www.h2database.com/html/datatypes.html#clob_type
> http://www.h2database.com/html/datatypes.html#array_type
> http://www.h2database.com/html/datatypes.html#enum_type



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

[jira] [Commented] (IGNITE-6686) Document SQL Data Types

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6686:
-

[~dmagda], I do not think that mixing all platforms on the same page is a good 
idea. It is better to have one page for languages (Java, .NET, CPP), one for 
JDBC and another for ODBC. Makes sense?

> Document SQL Data Types
> ---
>
> Key: IGNITE-6686
> URL: https://issues.apache.org/jira/browse/IGNITE-6686
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> The data types page should include all SQL types supported and how they 
> mapped to a language or driver specific type. Presently the types are 
> represented in a tabular format:
> https://apacheignite-sql.readme.io/v2.3/docs/data-types
> Guys, please help to fill out langage/drivers specific columns:
> # [~ptupitsyn] - .NET data types.
> # [~isapego] - C++ and ODBC data type.
> # [~al.psc] - JDBC and JAVA data types.
> [~vozerov], please suggest what to do with these few types below. They 
> supported by H2 but I'm not sure how Ignite deals with them:
> http://www.h2database.com/html/datatypes.html#identity_type
> http://www.h2database.com/html/datatypes.html#binary_type
> http://www.h2database.com/html/datatypes.html#other_type
> http://www.h2database.com/html/datatypes.html#varchar_ignorecase_type
> http://www.h2database.com/html/datatypes.html#blob_type
> http://www.h2database.com/html/datatypes.html#clob_type
> http://www.h2database.com/html/datatypes.html#array_type
> http://www.h2database.com/html/datatypes.html#enum_type



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

[jira] [Commented] (IGNITE-6687) SQL Error Codes Documentation

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6687:
-

[~dmagda], there is no similar error code for native API.
[~isapego], could you please add missing bits for ODBC?

> SQL Error Codes Documentation
> -
>
> Key: IGNITE-6687
> URL: https://issues.apache.org/jira/browse/IGNITE-6687
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Presently we have JDBC error codes documented:
> https://apacheignite-sql.readme.io/docs/jdbc-error-codes
> Two things have to be done:
> * If there are similar error codes shared between the ODBC and JDBC drivers, 
> and native APIs then let's put them under SQL reference category below Data 
> Types: https://apacheignite-sql.readme.io/docs/sql-reference-overview
> * ODBC specific error codes with an example of an error handling need to be 
> listed in ODBC category [~isapego], please assist with this: 
> https://apacheignite-sql.readme.io/docs/odbc-driver
> Discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-error-codes-td23415.html



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

[jira] [Commented] (IGNITE-6701) Do not deserialize previous value during indexes update

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6701:
-

Test run with latest changes: 
https://ci.ignite.apache.org/viewQueued.html?itemId=932473

> Do not deserialize previous value during indexes update
> ---
>
> Key: IGNITE-6701
> URL: https://issues.apache.org/jira/browse/IGNITE-6701
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Semen Boikov
>Assignee: Roman Kondakov
>  Labels: iep-1, performance
> Fix For: 2.4
>
>
> In GridH2Table.doUpdate all indexes are updated using BPlusTree.put method 
> which deserializes previous value, actually previous value is already 
> available in GridQueryProcessor.store/remove methods. Need try to change 
> GridH2Table.doUpdate to use BPlusTree.putx instead of BPlusTree.put.



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

[jira] [Issue Comment Deleted] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5343:
---
Comment: was deleted

(was: All done. Need to make sure we still work properly both in x86 and x64 
modes.
New TeamCity config created: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNetX86)

> .NET: Interoperate with JVM directly, get rid of C++ layer
> --
>
> Key: IGNITE-5343
> URL: https://issues.apache.org/jira/browse/IGNITE-5343
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> We can work with JNI directly using P/Invoke, there is no real need for C++ 
> layer.
> Advantages of removing C++ layer:
> * *No MSVC++ 2010 dependency*
> * *No build tools required for development*
> * Simplify and speed up the build procedure
> * No embedded libraries
> * Easier crossplatform support (IGNITE-2662)



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

[jira] [Comment Edited] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5885 at 11/7/17 2:00 PM:
-

Turns out there is no x86 JVM on the agents, or it does not get detected. Need 
to fiddle with JAVA_HOME before running tests? Putting this aside for now.


was (Author: ptupitsyn):
Turns out there is no x86 JVM on the agents.

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Commented] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5885:


Turns out there is no x86 JVM on the agents.

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Reopened] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reopened IGNITE-5885:


> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-6005:
---

[~NIzhikov], I've added my thoughts to the review for this PR.

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> 

[jira] [Resolved] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5885.

Resolution: Fixed

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Commented] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5885:


Config added: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNetX86

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Updated] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5885:
---
Fix Version/s: 2.4

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Assigned] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5885:
--

Assignee: Pavel Tupitsyn

> .NET: Add x86 tests on TeamCity
> ---
>
> Key: IGNITE-5885
> URL: https://issues.apache.org/jira/browse/IGNITE-5885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Just copy a configuration and change NUnit bitness.



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

[jira] [Commented] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5343:


All done. Need to make sure we still work properly both in x86 and x64 modes.
New TeamCity config created: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformNetX86

> .NET: Interoperate with JVM directly, get rid of C++ layer
> --
>
> Key: IGNITE-5343
> URL: https://issues.apache.org/jira/browse/IGNITE-5343
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> We can work with JNI directly using P/Invoke, there is no real need for C++ 
> layer.
> Advantages of removing C++ layer:
> * *No MSVC++ 2010 dependency*
> * *No build tools required for development*
> * Simplify and speed up the build procedure
> * No embedded libraries
> * Easier crossplatform support (IGNITE-2662)



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

[jira] [Commented] (IGNITE-6722) Marshaller mappings and binary metadata must be merged and written to disk on registerLocally

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6722:
-

LGTM. Merged to master branch.
Thanks!

> Marshaller mappings and binary metadata must be merged and written to disk on 
> registerLocally
> -
>
> Key: IGNITE-6722
> URL: https://issues.apache.org/jira/browse/IGNITE-6722
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.4
>
>
> Each mapping/metadata register operation must result in creating/updating 
> corresponding file in file system.
> Methods for local register ({{MarshallerContext::registerClassNameLocally}} 
> and {{CacheObjectBinaryProcessor::addMetaLocally}}) lack this part.



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

[jira] [Commented] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5955:


GitHub user zstan opened a pull request:

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

IGNITE-5955: IgniteCacheContinuousQueryClientReconnectTest fix



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

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

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

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


commit 4fc98a238ce3d7f1b42dec1911a8ad73f39cba47
Author: Evgeny Stanilovskiy 
Date:   2017-11-07T12:10:16Z

IGNITE-5955: IgniteCacheContinuousQueryClientReconnectTest fix




> Ignite Continuous Query (Queries 3): 
> IgniteCacheContinuousQueryClientReconnectTest fails
> 
>
> Key: IGNITE-5955
> URL: https://issues.apache.org/jira/browse/IGNITE-5955
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>  Labels: MakeTeamcityGreenAgain, test-failure
>
> Reproducible locally with the same exception as on TC.
> In test log there is the following exception:
> {noformat}
> [2017-08-07 
> 03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
>  Failed to stop grid 
> [igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0,
>  cancel=true]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node 
> disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
> at 
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> According to [TC 
> history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
>  is failing since mid of April.
> Last commit where test has been passing is *b6b3d3754849*.



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

[jira] [Assigned] (IGNITE-6611) Optionally disable binary metadata for type

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov reassigned IGNITE-6611:
--

Assignee: Sergey Kalashnikov  (was: Alexander Paschenko)

> Optionally disable binary metadata for type
> ---
>
> Key: IGNITE-6611
> URL: https://issues.apache.org/jira/browse/IGNITE-6611
> Project: Ignite
>  Issue Type: Task
>  Components: binary, sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Fix For: 2.4
>
>
> We need to introduce special metadata mode for type - without metadata. This 
> way we will have a kind of "flexible" type with no restrictions. This will be 
> especially useful for SQL-related types where schema changes are possible 
> (e.g. ADD COLUMN -> DROP COLUMN).
> Public part should be exposed to:
> 1) {{BinaryTypeConfiguration}}
> 2) {{BinaryType}} - add a flag here.



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

[jira] [Updated] (IGNITE-2662) .NET Standard support

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2662:
---
Description: 
Ignite.NET should target .NET Standard so it is available on maximum number of 
platforms, see
https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
https://github.com/dotnet/core/blob/master/roadmap.md

Make sure that all used APIs are supported on all platforms, see API Analyzer 
tool:
https://channel9.msdn.com/coding4fun/blog/Your-New-Virtual-API-Review-Assistant

This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
additional to good old regular .NET.

Possible difficulties:
* JNI interop. Core has dllImport and it works on linux, and our C++ client 
works on linux, so it should be possible
* Reflection. We use it a lot, and API has changed.

  was:
Ignite.NET should target .NET Standard so it is available on maximum number of 
platforms, see
https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
https://github.com/dotnet/core/blob/master/roadmap.md

This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
additional to good old regular .NET.

Possible difficulties:
* JNI interop. Core has dllImport and it works on linux, and our C++ client 
works on linux, so it should be possible
* Reflection. We use it a lot, and API has changed.


> .NET Standard support
> -
>
> Key: IGNITE-2662
> URL: https://issues.apache.org/jira/browse/IGNITE-2662
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net, xplat
>
> Ignite.NET should target .NET Standard so it is available on maximum number 
> of platforms, see
> https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
> https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
> https://github.com/dotnet/core/blob/master/roadmap.md
> Make sure that all used APIs are supported on all platforms, see API Analyzer 
> tool:
> https://channel9.msdn.com/coding4fun/blog/Your-New-Virtual-API-Review-Assistant
> This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
> additional to good old regular .NET.
> Possible difficulties:
> * JNI interop. Core has dllImport and it works on linux, and our C++ client 
> works on linux, so it should be possible
> * Reflection. We use it a lot, and API has changed.



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

[jira] [Commented] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5343:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5343 .NET: Work with JNI directly, get rid of C++ layer



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

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

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

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


commit 3cd6bebc271b0c6e4238cc60a7fc6fd844add76c
Author: Pavel Tupitsyn 
Date:   2017-11-07T11:51:56Z

IGNITE-5343 .NET: Work with JNI directly, get rid of C++ layer




> .NET: Interoperate with JVM directly, get rid of C++ layer
> --
>
> Key: IGNITE-5343
> URL: https://issues.apache.org/jira/browse/IGNITE-5343
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> We can work with JNI directly using P/Invoke, there is no real need for C++ 
> layer.
> Advantages of removing C++ layer:
> * *No MSVC++ 2010 dependency*
> * *No build tools required for development*
> * Simplify and speed up the build procedure
> * No embedded libraries
> * Easier crossplatform support (IGNITE-2662)



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

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-6824:
-

Assignee: Ilya Borisov  (was: Alexander Kalinin)

Please review. angular-touch deps removed

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



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

[jira] [Updated] (IGNITE-6787) Simplifying and optimising GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-6787:
-
Attachment: IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch

> Simplifying and optimising GridNioServer
> 
>
> Key: IGNITE-6787
> URL: https://issues.apache.org/jira/browse/IGNITE-6787
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
> Attachments: 
> IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch
>
>
> Seems we are able to improve communication model using Mpsc queues, NIO task 
> abstractions and reducing concurrent operations.



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

[jira] [Resolved] (IGNITE-6787) Simplifying and optimising GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov resolved IGNITE-6787.
--
Resolution: Won't Fix

> Simplifying and optimising GridNioServer
> 
>
> Key: IGNITE-6787
> URL: https://issues.apache.org/jira/browse/IGNITE-6787
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
> Attachments: 
> IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch
>
>
> Seems we are able to improve communication model using Mpsc queues, NIO task 
> abstractions and reducing concurrent operations.



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

[jira] [Resolved] (IGNITE-4646) Try to unmarshall direct messages in striped pool

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov resolved IGNITE-4646.
--
Resolution: Won't Fix

> Try to unmarshall direct messages in striped pool
> -
>
> Key: IGNITE-4646
> URL: https://issues.apache.org/jira/browse/IGNITE-4646
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Attachments: client_serialization.patch
>
>
> During marshalling in NIO thread the following should be added to the write 
> buffer and sent to peer:
> 1. chunk size - 16 bits (this probably puts limitation on max write buffer 
> size of 64k or will require some changes to direct writer)
> 2. last  chunk - 1 bit
> 3. pool policy - 8 bits
> Here is the scheme to explain how this should work.
> {noformat}
> [chunk size] [pool policy] [partition] [last flag] [chunk data] X <-- no more 
> space in write buffer
> [next chunk size] [last flag] [chunk data] <<-- we write next chunk once some 
> space is available in write buffer, but we skip partition and policy flags 
> and maybe others that should be sent only once.
> ...
> ...
> [next chunk size] [last flag] [chunk data] <<-- last flag is true here
> {noformat}
> Examples
> Write buffer - 64k
> Message - 84k
> # sender reserves space for chunk size
> # reserves space for policy and last chunk flag
> # marshalls message to buffer while it has free space (64k - SPACE will be 
> written to buffer)
> # puts size and flags to reserved space in the beginning
> # sends buffer or part of it which makes some space available to further 
> writes
> # reserves space for next chunk size and flags
> # marshalls message to buffer while it has free space (lets assume the rest 
> of message fits)
> # puts size and last=true to the reserved space and sends
> Receiver:
> # reads chunk size, stores the target pool and partition
> # allocates heap buffer and copies chunk data to it from read buffer
> # once all message chunks are fully read message should be submitted to a 
> pool where it will be unmarshalled and processed



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

[jira] [Updated] (IGNITE-6787) Simplifying and optimising GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-6787:
-
Attachment: (was: 
IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch)

> Simplifying and optimising GridNioServer
> 
>
> Key: IGNITE-6787
> URL: https://issues.apache.org/jira/browse/IGNITE-6787
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> Seems we are able to improve communication model using Mpsc queues, NIO task 
> abstractions and reducing concurrent operations.



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

[jira] [Commented] (IGNITE-4646) Try to unmarshall direct messages in striped pool

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-4646:
--

Seems there is no performance increase

> Try to unmarshall direct messages in striped pool
> -
>
> Key: IGNITE-4646
> URL: https://issues.apache.org/jira/browse/IGNITE-4646
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Attachments: client_serialization.patch
>
>
> During marshalling in NIO thread the following should be added to the write 
> buffer and sent to peer:
> 1. chunk size - 16 bits (this probably puts limitation on max write buffer 
> size of 64k or will require some changes to direct writer)
> 2. last  chunk - 1 bit
> 3. pool policy - 8 bits
> Here is the scheme to explain how this should work.
> {noformat}
> [chunk size] [pool policy] [partition] [last flag] [chunk data] X <-- no more 
> space in write buffer
> [next chunk size] [last flag] [chunk data] <<-- we write next chunk once some 
> space is available in write buffer, but we skip partition and policy flags 
> and maybe others that should be sent only once.
> ...
> ...
> [next chunk size] [last flag] [chunk data] <<-- last flag is true here
> {noformat}
> Examples
> Write buffer - 64k
> Message - 84k
> # sender reserves space for chunk size
> # reserves space for policy and last chunk flag
> # marshalls message to buffer while it has free space (64k - SPACE will be 
> written to buffer)
> # puts size and flags to reserved space in the beginning
> # sends buffer or part of it which makes some space available to further 
> writes
> # reserves space for next chunk size and flags
> # marshalls message to buffer while it has free space (lets assume the rest 
> of message fits)
> # puts size and last=true to the reserved space and sends
> Receiver:
> # reads chunk size, stores the target pool and partition
> # allocates heap buffer and copies chunk data to it from read buffer
> # once all message chunks are fully read message should be submitted to a 
> pool where it will be unmarshalled and processed



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

[jira] [Updated] (IGNITE-4646) Try to unmarshall direct messages in striped pool

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-4646:
-
Attachment: client_serialization.patch

> Try to unmarshall direct messages in striped pool
> -
>
> Key: IGNITE-4646
> URL: https://issues.apache.org/jira/browse/IGNITE-4646
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Attachments: client_serialization.patch
>
>
> During marshalling in NIO thread the following should be added to the write 
> buffer and sent to peer:
> 1. chunk size - 16 bits (this probably puts limitation on max write buffer 
> size of 64k or will require some changes to direct writer)
> 2. last  chunk - 1 bit
> 3. pool policy - 8 bits
> Here is the scheme to explain how this should work.
> {noformat}
> [chunk size] [pool policy] [partition] [last flag] [chunk data] X <-- no more 
> space in write buffer
> [next chunk size] [last flag] [chunk data] <<-- we write next chunk once some 
> space is available in write buffer, but we skip partition and policy flags 
> and maybe others that should be sent only once.
> ...
> ...
> [next chunk size] [last flag] [chunk data] <<-- last flag is true here
> {noformat}
> Examples
> Write buffer - 64k
> Message - 84k
> # sender reserves space for chunk size
> # reserves space for policy and last chunk flag
> # marshalls message to buffer while it has free space (64k - SPACE will be 
> written to buffer)
> # puts size and flags to reserved space in the beginning
> # sends buffer or part of it which makes some space available to further 
> writes
> # reserves space for next chunk size and flags
> # marshalls message to buffer while it has free space (lets assume the rest 
> of message fits)
> # puts size and last=true to the reserved space and sends
> Receiver:
> # reads chunk size, stores the target pool and partition
> # allocates heap buffer and copies chunk data to it from read buffer
> # once all message chunks are fully read message should be submitted to a 
> pool where it will be unmarshalled and processed



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

[jira] [Assigned] (IGNITE-5635) Web Console: Show query execution progress

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-5635:
-

Assignee: Alexander Kalinin  (was: Andrey Novikov)

> Web Console: Show query execution progress
> --
>
> Key: IGNITE-5635
> URL: https://issues.apache.org/jira/browse/IGNITE-5635
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexander Kalinin
>
> Show query execution progress, some progress or spinning wheel.



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

[jira] [Assigned] (IGNITE-6535) Web Console: Set IGNITE_HOME for Web Agent

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-6535:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

> Web Console: Set IGNITE_HOME for Web Agent
> --
>
> Key: IGNITE-6535
> URL: https://issues.apache.org/jira/browse/IGNITE-6535
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.3
>
>
> Add initialization logic for IGNITE_HOME for ignite-web-agent.{bat | sh}.
> IGNITE_HOME is required for correct work of demo mode.



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

[jira] [Assigned] (IGNITE-6535) Web Console: Set IGNITE_HOME for Web Agent

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-6535:
-

Assignee: Alexander Kalinin  (was: Pavel Konstantinov)

> Web Console: Set IGNITE_HOME for Web Agent
> --
>
> Key: IGNITE-6535
> URL: https://issues.apache.org/jira/browse/IGNITE-6535
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Alexey Kuznetsov
>Assignee: Alexander Kalinin
> Fix For: 2.3
>
>
> Add initialization logic for IGNITE_HOME for ignite-web-agent.{bat | sh}.
> IGNITE_HOME is required for correct work of demo mode.



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

[jira] [Resolved] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-5917.

Resolution: Won't Fix

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Closed] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-5917.
--

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Commented] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5917:


Will be re-worked in new UI. Closed.

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Commented] (IGNITE-5635) Web Console: Show query execution progress

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5635:


Also please add progress to Export\Export All button on Queries screen

> Web Console: Show query execution progress
> --
>
> Key: IGNITE-5635
> URL: https://issues.apache.org/jira/browse/IGNITE-5635
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
>
> Show query execution progress, some progress or spinning wheel.



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

[jira] [Assigned] (IGNITE-6795) Web console: Make default file name for saving scan results more informative

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6795:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: Make default file name for saving scan results more informative
> 
>
> Key: IGNITE-6795
> URL: https://issues.apache.org/jira/browse/IGNITE-6795
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently file name is '' + '-all' in case if I want to save all 
> result set. (export all)
> I suggest to use 'scan--all'



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

[jira] [Commented] (IGNITE-6795) Web console: Make default file name for saving scan results more informative

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6795:


Successfully tested in branch

> Web console: Make default file name for saving scan results more informative
> 
>
> Key: IGNITE-6795
> URL: https://issues.apache.org/jira/browse/IGNITE-6795
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently file name is '' + '-all' in case if I want to save all 
> result set. (export all)
> I suggest to use 'scan--all'



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

[jira] [Closed] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6398.
--

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-6824:
-

Assignee: Alexander Kalinin  (was: Ilya Borisov)

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Alexander Kalinin
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



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

[jira] [Updated] (IGNITE-6787) Simplifying and optimising GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-6787:
-
Attachment: IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch

There is no performance increase.

> Simplifying and optimising GridNioServer
> 
>
> Key: IGNITE-6787
> URL: https://issues.apache.org/jira/browse/IGNITE-6787
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
> Attachments: 
> IGNITE_6787_Simplifying_and_optimising_GridNioServer.patch
>
>
> Seems we are able to improve communication model using Mpsc queues, NIO task 
> abstractions and reducing concurrent operations.



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

[jira] [Commented] (IGNITE-6786) Refactoring of GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-6786:
--

Seems all the changes have no effect on overall performance.

> Refactoring of GridNioServer
> 
>
> Key: IGNITE-6786
> URL: https://issues.apache.org/jira/browse/IGNITE-6786
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2, 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: None
>
> Attachments: IGNITE_6786_Refactoring_of_GridNioServer.patch
>
>
> Currently {{org.apache.ignite.internal.util.nio.GridNioServer}} is too 
> complex to change or even maintain. 
> Try to move all nested classes outside {{GridNioServer}} before changing the 
> communication model.



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

[jira] [Updated] (IGNITE-6786) Refactoring of GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-6786:
-
Attachment: IGNITE_6786_Refactoring_of_GridNioServer.patch

> Refactoring of GridNioServer
> 
>
> Key: IGNITE-6786
> URL: https://issues.apache.org/jira/browse/IGNITE-6786
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2, 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: None
>
> Attachments: IGNITE_6786_Refactoring_of_GridNioServer.patch
>
>
> Currently {{org.apache.ignite.internal.util.nio.GridNioServer}} is too 
> complex to change or even maintain. 
> Try to move all nested classes outside {{GridNioServer}} before changing the 
> communication model.



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

[jira] [Updated] (IGNITE-6786) Refactoring of GridNioServer

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-6786:
-
Fix Version/s: (was: 2.4)
   None

> Refactoring of GridNioServer
> 
>
> Key: IGNITE-6786
> URL: https://issues.apache.org/jira/browse/IGNITE-6786
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2, 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: None
>
> Attachments: IGNITE_6786_Refactoring_of_GridNioServer.patch
>
>
> Currently {{org.apache.ignite.internal.util.nio.GridNioServer}} is too 
> complex to change or even maintain. 
> Try to move all nested classes outside {{GridNioServer}} before changing the 
> communication model.



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

[jira] [Commented] (IGNITE-6805) Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6805:


Github user asfgit closed the pull request at:

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


> Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 32)
> --
>
> Key: IGNITE-6805
> URL: https://issues.apache.org/jira/browse/IGNITE-6805
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: ml
>Affects Versions: 2.4
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>
> In SparseDistributedBlockMatrixTest are red next tests
> * testCacheBehaviour
> * testSquareMatrixTimes
> with another value of constant MAX_BLOCK_SIZE (4 or 8, for example)
> In my opinion, it means that algorithm is incorrect for matrices with large 
> number of blocks



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

[jira] [Commented] (IGNITE-6809) Use MPSC queue in striped pool

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6809:


Github user asfgit closed the pull request at:

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


> Use MPSC queue in striped pool
> --
>
> Key: IGNITE-6809
> URL: https://issues.apache.org/jira/browse/IGNITE-6809
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>  Labels: performance
> Fix For: 2.4
>
>
> Use MPSC queue in striped pool
> Let's start from [MP-SC concurrent linked queue implementation based on 
> Dmitry 
> Vyukov's|http://www.1024cores.net/home/lock-free-algorithms/queues/non-intrusive-mpsc-node-based-queue]



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

[jira] [Closed] (IGNITE-4466) Web console - Admin panel: show different message for 'Grant\Revoke admin' actions

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4466.
--

> Web console - Admin panel: show different message for 'Grant\Revoke admin' 
> actions
> --
>
> Key: IGNITE-4466
> URL: https://issues.apache.org/jira/browse/IGNITE-4466
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
>
> Currently we show the same message for these two different actions. It is not 
> clear what exactly was performed.



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

[jira] [Commented] (IGNITE-4466) Web console - Admin panel: show different message for 'Grant\Revoke admin' actions

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4466:


Confirmed.

> Web console - Admin panel: show different message for 'Grant\Revoke admin' 
> actions
> --
>
> Key: IGNITE-4466
> URL: https://issues.apache.org/jira/browse/IGNITE-4466
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
>
> Currently we show the same message for these two different actions. It is not 
> clear what exactly was performed.



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

[jira] [Commented] (IGNITE-5343) .NET: Interoperate with JVM directly, get rid of C++ layer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5343:


[~ManiGandham] thanks, got it. See IGNITE-1417 and IGNITE-6834, these are 
planned, but for now blocked by IGNITE-2701.

> .NET: Interoperate with JVM directly, get rid of C++ layer
> --
>
> Key: IGNITE-5343
> URL: https://issues.apache.org/jira/browse/IGNITE-5343
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> We can work with JNI directly using P/Invoke, there is no real need for C++ 
> layer.
> Advantages of removing C++ layer:
> * *No MSVC++ 2010 dependency*
> * *No build tools required for development*
> * Simplify and speed up the build procedure
> * No embedded libraries
> * Easier crossplatform support (IGNITE-2662)



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

[jira] [Created] (IGNITE-6834) .NET: Distributed Set

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6834:
--

 Summary: .NET: Distributed Set
 Key: IGNITE-6834
 URL: https://issues.apache.org/jira/browse/IGNITE-6834
 Project: Ignite
  Issue Type: New Feature
  Security Level: Public (Viewable by anyone)
  Components: platforms
Reporter: Pavel Tupitsyn


See {{IgniteSet}} in Java.



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

[jira] [Updated] (IGNITE-1417) .NET: Implement distributed queue

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1417:
---
Description: See {{IgnitQueue}} in Java.

> .NET: Implement distributed queue
> -
>
> Key: IGNITE-1417
> URL: https://issues.apache.org/jira/browse/IGNITE-1417
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>  Labels: .net
>
> See {{IgnitQueue}} in Java.



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

[jira] [Updated] (IGNITE-1417) .NET: Implement distributed queue

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1417:
---
Description: See {{IgniteQueue}} in Java.  (was: See {{IgnitQueue}} in 
Java.)

> .NET: Implement distributed queue
> -
>
> Key: IGNITE-1417
> URL: https://issues.apache.org/jira/browse/IGNITE-1417
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>  Labels: .net
>
> See {{IgniteQueue}} in Java.



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

[jira] [Updated] (IGNITE-1417) .NET: Implement distributed queue

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1417:
---
Summary: .NET: Implement distributed queue  (was: .Net: Implement 
distributed queue.)

> .NET: Implement distributed queue
> -
>
> Key: IGNITE-1417
> URL: https://issues.apache.org/jira/browse/IGNITE-1417
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>  Labels: .net
>




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

[jira] [Commented] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6398:


Tested

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Closed] (IGNITE-6670) Web console: Check demo node configuration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6670.
--

> Web console: Check demo node configuration
> --
>
> Key: IGNITE-6670
> URL: https://issues.apache.org/jira/browse/IGNITE-6670
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> On start of demo the Web agent shows a lot of debug messages in log. 
> Configuration should be changed to reduce information shown on start.



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

[jira] [Commented] (IGNITE-6670) Web console: Check demo node configuration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6670:


Tested

> Web console: Check demo node configuration
> --
>
> Key: IGNITE-6670
> URL: https://issues.apache.org/jira/browse/IGNITE-6670
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> On start of demo the Web agent shows a lot of debug messages in log. 
> Configuration should be changed to reduce information shown on start.



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

[jira] [Commented] (IGNITE-6737) GridDeploymentPerVersionStore retries loading class infinitely

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov commented on IGNITE-6737:
---

Looks to, TC passed
https://ci.ignite.apache.org/viewModification.html?modId=442914=false==vcsModificationTests

> GridDeploymentPerVersionStore retries loading class infinitely
> --
>
> Key: IGNITE-6737
> URL: https://issues.apache.org/jira/browse/IGNITE-6737
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Vladislav Pyatkov
> Fix For: 2.4
>
>
> {noformat}
> 2017-10-24 14:34:06 [DEBUG] 
> [org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
> [pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment meta for local deployment: 
> GridDeploymentMetadata [depMode=SHARED, 
> alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
> clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
> sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b16, clsLdrId=null, clsLdr=null, 
> participants=null, parentLdr=null, record=true, nodeFilter=null, seqNum=n/a]
> 2017-10-24 14:34:06 [DEBUG] 
> [org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
> [pub-#5258%DPL_GRID%DplGridNodeName%] - Failed to load class for local 
> auto-deployment 
> [ldr=grid:com.sbt.core.envelope.container.FileClassLoader@3e4327dc, 
> meta=GridDeploymentMetadata [depMode=SHARED, 
> alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
> clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
> sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b16, clsLdrId=null, clsLdr=null, 
> participants=null, parentLdr=null, record=true, nodeFilter=null, seqNum=n/a]]
> 2017-10-24 14:34:06 [DEBUG] 
> [org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore]
>  [pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (class 
> does not exist on participating nodes) [dep=SharedDeployment [rmv=false, 
> super=GridDeployment [ts=1508810401226, depMode=SHARED, 
> clsLdr=GridDeploymentClassLoader 
> [id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
> nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
>  
> 3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
>  
> f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
>  
> 5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
>  
> 65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
>  
> 045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
>  
> afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
>  
> 4b2662e9-d525-4d96-936c-8cc645464e65=591541c4f51-4b2662e9-d525-4d96-936c-8cc645464e65},
>  p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false], 
> clsLdrId=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, userVer=0, 
> loc=false, 
> sampleClsName=com.sbt.fea_cc.services.business.autoStopTurnkeySettings.AutoStopTurnkeySettingsService$FindOrderTurnkeyForSuspend,
>  pendingUndeploy=false, undeployed=false, usage=0]], 
> meta=GridDeploymentMetadata [depMode=SHARED, 
> alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
> clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=0, 
> sndNodeId=4457016c-5f93-450f-b2a7-86bd25f536cf, 
> clsLdrId=898962c4f51-4457016c-5f93-450f-b2a7-86bd25f536cf, clsLdr=null, 
> participants=null, parentLdr=null, record=true, nodeFilter=null, 
> seqNum=150888744]]
> 2017-10-24 14:34:06 [DEBUG] 
> [org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore]
>  [pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (random 
> class could not be loaded from sender node) [dep=SharedDeployment [rmv=false, 
> super=GridDeployment [ts=1508810401226, depMode=SHARED, 
> clsLdr=GridDeploymentClassLoader 
> [id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
> nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
>  
> 3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
>  
> f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
>  
> 5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
>  
> 65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
>  
> 045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
>  
> afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
>  
> 

[jira] [Commented] (IGNITE-6789) Web Console: Rework sorting of caches list on Queries screen to ignore case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6789:


Tested.

> Web Console: Rework sorting of caches list on Queries screen to ignore case
> ---
>
> Key: IGNITE-6789
> URL: https://issues.apache.org/jira/browse/IGNITE-6789
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> Currently caches are sorted case sensitive that is not very useful



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

[jira] [Closed] (IGNITE-6789) Web Console: Rework sorting of caches list on Queries screen to ignore case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6789.
--

> Web Console: Rework sorting of caches list on Queries screen to ignore case
> ---
>
> Key: IGNITE-6789
> URL: https://issues.apache.org/jira/browse/IGNITE-6789
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> Currently caches are sorted case sensitive that is not very useful



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

[jira] [Assigned] (IGNITE-6824) Web Console: migrate from angularjs 1.5 to angular 1.6

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-6824:


Assignee: Ilya Borisov  (was: Andrey Novikov)

> Web Console: migrate from angularjs 1.5 to angular 1.6
> --
>
> Key: IGNITE-6824
> URL: https://issues.apache.org/jira/browse/IGNITE-6824
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> angularjs 1.5 version is legacy, let's migrate to last stable version 1.6



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