[jira] [Assigned] (IGNITE-4838) NPE on execution of unknown internal task by name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-4838:
-

Assignee: Yakov Zhdanov  (was: Vasiliy Sisko)

Yakov. Please review fix.

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Yakov Zhdanov
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches

[Saikat Maitra (JIRA)]

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

Saikat Maitra reassigned IGNITE-3303:
-

Assignee: Anton Vinogradov  (was: Saikat Maitra)

> Apache Flink Integration - Flink source to run a continuous query against one 
> or multiple caches
> 
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Saikat Maitra
>Assignee: Anton Vinogradov
> Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, 
> testFlinkIgniteSourceWithLargeBatch.log, win7.PNG
>
>
> Apache Flink integration 
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion : 
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-3303:
---

[~avinogradov]

Please review the changes and let me know if you have any feedback.

> Apache Flink Integration - Flink source to run a continuous query against one 
> or multiple caches
> 
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
> Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, 
> testFlinkIgniteSourceWithLargeBatch.log, win7.PNG
>
>
> Apache Flink integration 
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion : 
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4838) NPE on execution of unknown internal task by name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-4838 at 3/28/17 3:16 AM:


http://reviews.ignite.apache.org/ignite/review/IGNT-CR-136


was (Author: vsisko):
http://reviews.ignite.apache.org/ignite/branch/PR%201673

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4838) NPE on execution of unknown internal task by name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-4838:
---

http://reviews.ignite.apache.org/ignite/branch/PR%201673

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4802) Create separate thread pool for services

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-4802.
---

> Create separate thread pool for services
> 
>
> Key: IGNITE-4802
> URL: https://issues.apache.org/jira/browse/IGNITE-4802
> Project: Ignite
>  Issue Type: Improvement
>  Components: managed services
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 2.0
>
>
> Currently if a service is invoked via service proxy, it will be executed on a 
> remote node in its public thread pool. This means that it's unsafe to execute 
> a compute job or closure from a service as it can cause starvation.
> Need to create a separate pool for services to overcome this limitation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Rishi (JIRA)]

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

Rishi reassigned IGNITE-2786:
-

Assignee: Rishi

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Rishi
> Fix For: 2.0
>
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4575:


GitHub user skalashnikov opened a pull request:

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

IGNITE-4575: Added enum support to SQL queries



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

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

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

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


commit 60dd521b09d23aeed77acc70adda67c8e19a2db1
Author: skalashnikov 
Date:   2017-03-27T20:01:26Z

IGNITE-4575: Added enum support to SQL queries




> Implement in Ignite wrapper for enums based on H2 user value type
> -
>
> Key: IGNITE-4575
> URL: https://issues.apache.org/jira/browse/IGNITE-4575
> Project: Ignite
>  Issue Type: Sub-task
>  Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-1925) Test HadoopSkipListSelfTest.testLevel flakily fails

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-1925:
-

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

> Test HadoopSkipListSelfTest.testLevel flakily fails
> ---
>
> Key: IGNITE-1925
> URL: https://issues.apache.org/jira/browse/IGNITE-1925
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.6
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
>Priority: Minor
>
> Test HadoopSkipListSelfTest.testLevel fails from time to time with ~ 3% 
> probability.
>  
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at 
> org.apache.ignite.internal.processors.hadoop.shuffle.collections.HadoopSkipListSelfTest.testLevel(HadoopSkipListSelfTest.java:83)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4868:
-
Attachment: SqlIndexTest.java

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
> Attachments: SqlIndexTest.java
>
>
> Using Object.class as index key type cause an unexpected behaviour. Entry 
> won't be removed from index due to inconsistent value type of entry and of 
> table type descriptor.
> Startpoints are IgniteH2Indexing.remove() and 
> GridQueryProcessor.initializeCache()



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4868:
-
Attachment: (was: TestRemoveAll.java)

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
> Attachments: SqlIndexTest.java
>
>
> Using Object.class as index key type cause an unexpected behaviour. Entry 
> won't be removed from index due to inconsistent value type of entry and of 
> table type descriptor.
> Startpoints are IgniteH2Indexing.remove() and 
> GridQueryProcessor.initializeCache()



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-2231.
---

> 'Put' cache event treats entry created at lock acquisition time as old value
> 
>
> Key: IGNITE-2231
> URL: https://issues.apache.org/jira/browse/IGNITE-2231
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
> Fix For: 2.0
>
> Attachments: EventsProcessingTest.java
>
>
> Subscribe for EVT_CACHE_OBJECT_PUT event on one node and perform 'put' 
> operations from the other to an empty transnational cache.
> The subscriber will receive a notification saying that there was an old value 
> for a key at the time the new was being inserted. In fact the was no an old 
> value, the entry with a {{null}} as a value was generated as a part of 
> implicit lock acquisition.
> This snippet of the code in {{GridCacheMapEntry}} generates a wrong event 
> (innerSet function)
> {noformat}
> if (evt && newVer != null && 
> cctx.events().isRecordable(EVT_CACHE_OBJECT_PUT)) {
> CacheObject evtOld = cctx.unwrapTemporary(old);
> cctx.events().addEvent(partition(),
> key,
> evtNodeId,
> tx == null ? null : tx.xid(),
> newVer,
> EVT_CACHE_OBJECT_PUT,
> val,
> val != null,
> evtOld,
> evtOld != null || hasValueUnlocked(),
> subjId, null, taskName,
> keepBinary);
> }
> {noformat}
> Attached the test that lets reproduce the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-2231.
-
Resolution: Fixed

> 'Put' cache event treats entry created at lock acquisition time as old value
> 
>
> Key: IGNITE-2231
> URL: https://issues.apache.org/jira/browse/IGNITE-2231
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
> Fix For: 2.0
>
> Attachments: EventsProcessingTest.java
>
>
> Subscribe for EVT_CACHE_OBJECT_PUT event on one node and perform 'put' 
> operations from the other to an empty transnational cache.
> The subscriber will receive a notification saying that there was an old value 
> for a key at the time the new was being inserted. In fact the was no an old 
> value, the entry with a {{null}} as a value was generated as a part of 
> implicit lock acquisition.
> This snippet of the code in {{GridCacheMapEntry}} generates a wrong event 
> (innerSet function)
> {noformat}
> if (evt && newVer != null && 
> cctx.events().isRecordable(EVT_CACHE_OBJECT_PUT)) {
> CacheObject evtOld = cctx.unwrapTemporary(old);
> cctx.events().addEvent(partition(),
> key,
> evtNodeId,
> tx == null ? null : tx.xid(),
> newVer,
> EVT_CACHE_OBJECT_PUT,
> val,
> val != null,
> evtOld,
> evtOld != null || hasValueUnlocked(),
> subjId, null, taskName,
> keepBinary);
> }
> {noformat}
> Attached the test that lets reproduce the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4863) Log4jLogger can change RootLogger logging level unexpectedly.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-4863:


Assignee: Andrew Mashenkov

> Log4jLogger can change RootLogger logging level unexpectedly.
> -
>
> Key: IGNITE-4863
> URL: https://issues.apache.org/jira/browse/IGNITE-4863
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>
> Setting System property "IGNITE_CONSOLE_APPENDER" to true will set rootLogger 
> level to OFF that can be unexpectedly as well.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/Logging-ignite-log4j-jar-td11400.html
> Seems, we should check if there is no other loggers configured which can 
> inherits rootLogger logging level before raising level or turning rootLogger 
> off.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4868:
-
Description: 
Using Object.class as index key type cause an unexpected behaviour. Entry won't 
be removed from index due to inconsistent value type of entry and of table type 
descriptor.

Startpoints are IgniteH2Indexing.remove() and 
GridQueryProcessor.initializeCache()

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
> Attachments: TestRemoveAll.java
>
>
> Using Object.class as index key type cause an unexpected behaviour. Entry 
> won't be removed from index due to inconsistent value type of entry and of 
> table type descriptor.
> Startpoints are IgniteH2Indexing.remove() and 
> GridQueryProcessor.initializeCache()



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4868:
-
Attachment: TestRemoveAll.java

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
> Attachments: TestRemoveAll.java
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4869) Unnecessary benchmarks for legacy binary identity

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-4869:
---

PR: https://github.com/apache/ignite/pull/1677

> Unnecessary benchmarks for legacy binary identity
> -
>
> Key: IGNITE-4869
> URL: https://issues.apache.org/jira/browse/IGNITE-4869
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 2.0
>
>
> IgniteLegacyBinaryIdentityPutBenchmark & 
> IgniteLegacyBinaryIdentityGetBenchmark isn't needed after removing 
> BinaryObjectBuilder.hashCode(int) method 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4870) .NET: QueryEntity.TableName

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4870:
--

 Summary: .NET: QueryEntity.TableName
 Key: IGNITE-4870
 URL: https://issues.apache.org/jira/browse/IGNITE-4870
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Add {{QueryEntity.TableName}} property and propagate to Java configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4870) .NET: QueryEntity.TableName

[Pavel Tupitsyn (JIRA)]

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

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

> .NET: QueryEntity.TableName
> ---
>
> Key: IGNITE-4870
> URL: https://issues.apache.org/jira/browse/IGNITE-4870
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Add {{QueryEntity.TableName}} property and propagate to Java configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4564) Ensure that builder approach is used for all setters in public API

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4564:

Labels: important  (was: )

> Ensure that builder approach is used for all setters in public API
> --
>
> Key: IGNITE-4564
> URL: https://issues.apache.org/jira/browse/IGNITE-4564
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> *Problem*
> We employed "builder" approach for some configuration classes:
> {code}
> class Configuration {
> Configuration setSomething(Something);
> }
> {code}
> This is very convenient for users. However, only part of our configs employ 
> this approach.
> *Task*
> Let's make sure that all other parts of our API follow this rule.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4564) Ensure that builder approach is used for all setters in public API

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4564:
---

Assignee: Vladimir Ozerov  (was: Andrew Mashenkov)

> Ensure that builder approach is used for all setters in public API
> --
>
> Key: IGNITE-4564
> URL: https://issues.apache.org/jira/browse/IGNITE-4564
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> *Problem*
> We employed "builder" approach for some configuration classes:
> {code}
> class Configuration {
> Configuration setSomething(Something);
> }
> {code}
> This is very convenient for users. However, only part of our configs employ 
> this approach.
> *Task*
> Let's make sure that all other parts of our API follow this rule.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4869) Unnecessary benchmarks for legacy binary identity

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-4869:
--
Summary: Unnecessary benchmarks for legacy binary identity  (was: 
Unnecessary benchmarcs for legacy binary identity)

> Unnecessary benchmarks for legacy binary identity
> -
>
> Key: IGNITE-4869
> URL: https://issues.apache.org/jira/browse/IGNITE-4869
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 2.0
>
>
> IgniteLegacyBinaryIdentityPutBenchmark & 
> IgniteLegacyBinaryIdentityGetBenchmark isn't needed after removing 
> BinaryObjectBuilder.hashCode(int) method 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4869) Unnecessary benchmarcs for legacy binary identity

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-4869:
--
Summary: Unnecessary benchmarcs for legacy binary identity  (was: 
Unnecessary benchmarcs for legacy minary identity)

> Unnecessary benchmarcs for legacy binary identity
> -
>
> Key: IGNITE-4869
> URL: https://issues.apache.org/jira/browse/IGNITE-4869
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 2.0
>
>
> IgniteLegacyBinaryIdentityPutBenchmark & 
> IgniteLegacyBinaryIdentityGetBenchmark isn't needed after removing 
> BinaryObjectBuilder.hashCode(int) method 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4869) Unnecessary benchmarcs for legacy minary identity

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-4869:
-

 Summary: Unnecessary benchmarcs for legacy minary identity
 Key: IGNITE-4869
 URL: https://issues.apache.org/jira/browse/IGNITE-4869
 Project: Ignite
  Issue Type: Bug
Reporter: Evgenii Zhuravlev
Assignee: Evgenii Zhuravlev
Priority: Critical
 Fix For: 2.0


IgniteLegacyBinaryIdentityPutBenchmark & IgniteLegacyBinaryIdentityGetBenchmark 
isn't needed after removing BinaryObjectBuilder.hashCode(int) method 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4868:
-
Fix Version/s: 2.0

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-4868:


Assignee: Alexander Paschenko

> SQL: Entry can't be removed from index with 'Object.class' key type 
> configured.
> ---
>
> Key: IGNITE-4868
> URL: https://issues.apache.org/jira/browse/IGNITE-4868
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4868) SQL: Entry can't be removed from index with 'Object.class' key type configured.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4868:


 Summary: SQL: Entry can't be removed from index with 
'Object.class' key type configured.
 Key: IGNITE-4868
 URL: https://issues.apache.org/jira/browse/IGNITE-4868
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Reporter: Andrew Mashenkov






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4501) Improvement of connection in a cluster of new node

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov edited comment on IGNITE-4501 at 3/27/17 2:04 PM:
--

[~yzhdanov]

I recreate PR: https://github.com/apache/ignite/pull/1676/files


was (Author: sharpler):
[~yzhdanov]

I reopen PR: https://github.com/apache/ignite/pull/1676/files

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4501) Improvement of connection in a cluster of new node

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-4501:
-

[~yzhdanov]

I reopen PR: https://github.com/apache/ignite/pull/1676/files

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4501) Improvement of connection in a cluster of new node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4501:


GitHub user SharplEr opened a pull request:

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

IGNITE-4501: Improvement of connection in a cluster of new node

Reopen that PR: https://github.com/apache/ignite/pull/1436

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

$ git pull https://github.com/SharplEr/ignite ignite-4501

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

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


commit 0e7768224e8ae26797460e2b750d04979c49c92f
Author: Alexander Menshikov 
Date:   2017-01-20T12:35:05Z

Add using CLUSTER_REGION_ID for ordering nodes in ring

commit c43894854a2bdcb5d39d92552f0e105c70a10198
Author: Alexander Menshikov 
Date:   2017-01-20T12:35:53Z

Add tests for RegionNodeComparator

commit 5a7d5e395c00ab7e6eafa03ed29ae4eea754cbc1
Author: Alexander Menshikov 
Date:   2017-01-20T12:44:28Z

Add test to suite

commit cdcda327773b61beb90539e7c11130906d0525dc
Author: Alexander Menshikov 
Date:   2017-01-21T10:57:54Z

A little clean up code

commit 620be443f3ef7bd4730ba755fb4e110d8dcd4918
Author: Alexander Menshikov 
Date:   2017-01-25T12:26:42Z

Change ordering inside nodes field, and add maxNode field to avoid using 
old ordering. Add method variant of serverNodes method which return only 
necessary part of ring. That make complexity of nextNode equals O(log n + k), 
which better then O(n). n is number of nodes, k is number of client nodes.

commit b45bad8b5dcf9d3904805503b1c327d4a6686d60
Author: Alexander Menshikov 
Date:   2017-01-25T13:03:27Z

Add filed to TcpDiscoveryNode for faster getting cluster_region_id

commit d9b68dd3cc4f546d73c475c7adf82ea797d851f2
Author: Alexander Menshikov 
Date:   2017-01-27T15:01:38Z

Fix bug in RegionNodeComparator

commit f36f07da21ca51bf2585fb80b82239541a3a16d6
Author: Alexander Menshikov 
Date:   2017-01-27T15:02:30Z

Cleanup code in RegionNodeComparatorTest

commit 145394cb5c10e5f1127071f1cb7957a3c1307a9d
Author: Alexander Menshikov 
Date:   2017-01-27T15:09:55Z

Add catch NumberFormatException

commit eeaf244788bd957a2b8f1e3b33d00338072edde1
Author: Alexander Menshikov 
Date:   2017-01-27T15:34:37Z

cleanup TcpDiscoveryNodesRing

commit a3431dec0103f815803af744ec3c75b7188c19fb
Author: Alexander Menshikov 
Date:   2017-01-30T10:37:16Z

Code cleanup

commit a41ee660eb275714bd924dfae7bf01c3274300f1
Author: Alexander Menshikov 
Date:   2017-01-30T11:58:26Z

Add @NotNull to RegionNodeComparator.compare

commit 8ebd887797cba7adf3ca08ea8af8ac43e29be221
Author: Alexander Menshikov 
Date:   2017-01-30T12:06:09Z

Add @Nullable to TcpDiscoveryNode.getClusterRegionId

commit fd91a18a421e951638c9f9078c34169916adde5e
Author: Alexander Menshikov 
Date:   2017-01-30T12:07:57Z

cleanup 
modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/internal/TcpDiscoveryNodesRing.java

commit f4652c888d07c1f52945c801be3e220d55895860
Author: Alexander Menshikov 
Date:   2017-01-30T16:31:44Z

Remove using cast to Nubmer

commit 6a3ac2eccd7a01bfde73def424f94d80da0c75c1
Author: Alexander Menshikov 
Date:   2017-01-30T16:37:20Z

restore code format

commit ecb82ffd908cf3de8618c8d557d4077f9341e3cc
Author: Alexander Menshikov 
Date:   2017-01-30T16:45:14Z

restore code format2

commit 2e3ec7797327d722160bdee1b0803508ce9b4058
Author: Alexander Menshikov 
Date:   2017-02-01T17:55:24Z

fix reusing variable

commit 77055549e20248c0f22eefc43e839ba82a3f3ecc
Author: Alexander Menshikov 
Date:   2017-02-01T17:57:55Z

Fix lost regionId after deserialization

commit 30d3cd992d0c4cf76b2b368c7a336863eb3b5e2d
Author: Alexander Menshikov 
Date:   2017-02-01T17:58:57Z

Add test for save sorting

commit 3e204be6d14d356d6cda6c11f2cd8d730348f44d
Author: Alexander Menshikov 
Date:   2017-02-02T11:25:24Z

Add RegionTcpDiscoverySelfTest

commit f1bdd6c936f7feae2535ab3f4dae8dddc9a4cde0
Author: Alexander Menshikov 
Date:   2017-02-02T11:31:08Z

Add license

commit 5e9343b96ecdcf25f0bdabf7468a2bd503ec7773
Author: Alexander Menshikov 
Date:   

[jira] [Assigned] (IGNITE-4838) NPE on execution of unknown internal task by name

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4838:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Vasiliy, I reviewed your changes. Please fix my comments that I made in 
Upsource.

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-2703) .NET: Dynamically registered classes must use binary serialization if possible

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2703:


Merged from master

> .NET: Dynamically registered classes must use binary serialization if possible
> --
>
> Key: IGNITE-2703
> URL: https://issues.apache.org/jira/browse/IGNITE-2703
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .net, breaking-api, important
> Fix For: 2.0
>
>
> At present we support dynamic class registration in .NET, but they are 
> written using deafult .NET mechanism. This is counterintuitive for users and 
> not consistent with Java, where such classes are written in binary form.
> Proposed implementation plan:
> 1) For each dynamically registered class we must understand whether it could 
> be serialized through binary or not. If not - print a warning and fallback to 
> .NET.
> 2) Before writing a class we must ensure that it's [typeId -> name] pair is 
> known to the cluster. If not - write full class name instead of type ID. Java 
> already do that.
> 3) Last, to support backward compatibility we must be able to fallback to 
> current mode with help of some boolean flag.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4102) .NET: Generic ICacheStore methods

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4102:


Merged to master.

> .NET: Generic ICacheStore methods
> -
>
> Key: IGNITE-4102
> URL: https://issues.apache.org/jira/browse/IGNITE-4102
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Current interface causes boxing on primitive types in LoadCache action 
> parameter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4102) .NET: Generic ICacheStore methods

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4102:


Github user asfgit closed the pull request at:

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


> .NET: Generic ICacheStore methods
> -
>
> Key: IGNITE-4102
> URL: https://issues.apache.org/jira/browse/IGNITE-4102
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Current interface causes boxing on primitive types in LoadCache action 
> parameter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-3575) CPP: Support continuous queries remote filters.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-3575 at 3/27/17 1:03 PM:
--

[~isapego], public part looks good to me. It would be cool if someone else with 
good CPP background throw a glance as well, as I don't feel I understand 
implementation details good enough.


was (Author: vozerov):
[~isapego], public part looks good to me. It would be cool if someone else with 
good CPP background thrown a glance as well, as I don't feel I understand 
implementation details good enough.

> CPP: Support continuous queries remote filters.
> ---
>
> Key: IGNITE-3575
> URL: https://issues.apache.org/jira/browse/IGNITE-3575
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp, important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3575) CPP: Support continuous queries remote filters.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3575:
-

[~isapego], public part looks good to me. It would be cool if someone else with 
good CPP background thrown a glance as well, as I don't feel I understand 
implementation details good enough.

> CPP: Support continuous queries remote filters.
> ---
>
> Key: IGNITE-3575
> URL: https://issues.apache.org/jira/browse/IGNITE-3575
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp, important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3018 at 3/27/17 12:09 PM:


Core review with partitions balancer: 
[IGNT-CR-137|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-137]


was (Author: tledkov-gridgain):
Core review with partitions balancer: 
[IGNT-CR-116|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-116]

> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
> Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 
> 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, 
> balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, 
> balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, 
> balanced.400.png, balanced.600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4477) Fix IgniteFuture.listen() and IgniteFuture.chain() semantics

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev reassigned IGNITE-4477:
---

Assignee: Dmitry Karachentsev

> Fix IgniteFuture.listen() and IgniteFuture.chain() semantics
> 
>
> Key: IGNITE-4477
> URL: https://issues.apache.org/jira/browse/IGNITE-4477
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> *Problem*
> We allow users to pass continuations to {{IgniteFuture}} which will be 
> executed on future completion. This can be done through {{listen}} or 
> {{chain}} methods.
> However, continuation semantics is broken intrinsically:
> 1) If future is already completed, user code executed in the same thread;
> 2) If future is not completed yet, it will be executed in completion thread.
> Neither of this options are valid because it easily leads to starvation. E.g.:
> {code}
> IgniteFuture fut = cache.getAsync(key2);
> fut.listen(fut0 -> {
>  cache.put(key2, val2); // Possible deadlock, because invoked in sys pool;
> });
> {code}
> *Solution*
> 1) By default callbacks must be executed asynchronously in some common pool 
> (public pool? new "callback pool"? FJP?)
> 2) It should be possible to specify where to execute a callback explicitly:
> {code}
> IgniteFuture.listen(IgniteClosure, ExecutorService);
> {code}
> 3) We may want to expose our public pool on API for convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4758) Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple memory policies

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4758:


Assignee: Sergey Chugunov  (was: Alexey Kuznetsov)

I've fixed Visor DTO objects.

> Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple 
> memory policies
> -
>
> Key: IGNITE-4758
> URL: https://issues.apache.org/jira/browse/IGNITE-4758
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>   Original Estimate: 336h
>  Time Spent: 32h
>
> h2. Acceptance Criteria
> # For each named *MemoryPolicy* described in configuration new named 
> *PageMemory* is created.
> # Each cache on startup is assigned to corresponding *PageMemory* instance 
> which is stored in context of the cache.
> # A default *PageMemory* is used to store content of caches with no 
> *MemoryPolicy* configured.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4351) .NET: Use BinaryArrayIdentityResolver by default

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4351:


Github user asfgit closed the pull request at:

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


> .NET: Use BinaryArrayIdentityResolver by default
> 
>
> Key: IGNITE-4351
> URL: https://issues.apache.org/jira/browse/IGNITE-4351
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET, breaking-api
> Fix For: 2.0
>
>
> Current legacy behavior calculates hash codes by calling 
> Object.GetHashCode(), but equality comparison is performed by comparing byte 
> arrays in binary form, which is inconsistent and can lead to unexpected 
> behavior with user-defined keys.
> In 2.0 we should replace default behavior with ArrayResolver so that Equals 
> and GetHashCode are consistent.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4838) NPE on execution of unknown internal task by name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-4838:
---

Added Check task class on null when task name is invalid. Added test.

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4838) NPE on execution of unknown internal task by name

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-4838:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> NPE on execution of unknown internal task by name
> -
>
> Key: IGNITE-4838
> URL: https://issues.apache.org/jira/browse/IGNITE-4838
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>
> Caused by: java.lang.NullPointerException
>   at org.jsr166.ConcurrentHashMap8.get(ConcurrentHashMap8.java:2619)
>   at 
> org.apache.ignite.internal.managers.deployment.GridDeployment.internalTask(GridDeployment.java:373)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:624)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:447)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:267)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4867) CacheMetricsSnapshot ignores 'size' and 'keySize' fields

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-4867:

Labels: newbie  (was: )

> CacheMetricsSnapshot ignores 'size' and 'keySize' fields
> 
>
> Key: IGNITE-4867
> URL: https://issues.apache.org/jira/browse/IGNITE-4867
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Karachentsev
>  Labels: newbie
>
> 'size' and 'keySize' fields in CacheMetricsSnapshot must be serialized and 
> properly processed to show correct values in CacheClusterMetricsMXBeanImpl.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4867) CacheMetricsSnapshot ignores 'size' and 'keySize' fields

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-4867:
---

 Summary: CacheMetricsSnapshot ignores 'size' and 'keySize' fields
 Key: IGNITE-4867
 URL: https://issues.apache.org/jira/browse/IGNITE-4867
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitry Karachentsev


'size' and 'keySize' fields in CacheMetricsSnapshot must be serialized and 
properly processed to show correct values in CacheClusterMetricsMXBeanImpl.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3579) Message type should be short.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3579:


Github user asfgit closed the pull request at:

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


> Message type should be short.
> -
>
> Key: IGNITE-3579
> URL: https://issues.apache.org/jira/browse/IGNITE-3579
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Currently we encode internal messages with {{byte}}. It turns out that we 
> almost exhausted possible IDs. 
> We should change {{byte}} to {{short}} for message ID.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4475) Simplify async API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4475:


Github user asfgit closed the pull request at:

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


> Simplify async API
> --
>
> Key: IGNITE-4475
> URL: https://issues.apache.org/jira/browse/IGNITE-4475
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> *Problem*
> We need to simplify our async API. It is to complex and verbose at the moment:
> {code}
> IgniteCache asyncCache = cache.withAsync();
> asyncCache.get(key);
> IgniteFuture fut = asyncCache.future();
> {code}
> *Proposed solution*
> 1) Deprecate {{IgniteAsyncSupport}} interface.
> 2) Make async operations more straightforward:
> {code}
> IgniteFuture fut = cache.getAsync(key);
> {code}
> *Scope*
> ~80 async methods in all public interfaces.
> Base branch: {{ignite-4475-async}}
> Migration guide has to be updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin reassigned IGNITE-4865:
--

Assignee: Vladimir Ozerov  (was: Alexandr Kuramshin)

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

> Non-informative error message on using GridClientOptimizedMarshaller with 
> unknown task classes
> --
>
> Key: IGNITE-4865
> URL: https://issues.apache.org/jira/browse/IGNITE-4865
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Vladimir Ozerov
>
> Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
> class is not present in {{classnames.properties}}. It occurs when 
> {{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.
> {noformat}
> Closing NIO session because of unhandled exception [cls=class 
> o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
> Failed to deserialize object with given class loader: null]
> {noformat}
> There is two problems:
> * Actual problem was hidden
> {noformat}
> Caused by: java.lang.UnsupportedOperationException
> at 
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
> at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
> {noformat}
> * Even reading the cause we don't understand what is wrong
> What to do:
> * Log stacktrace every time
> * Throw UnsupportedOperationException with informative message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4865:


GitHub user akuramshingg opened a pull request:

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

IGNITE-4865 Verbose logging, informative messages



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

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

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

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


commit c66889a45ae2b38d03fd06e3f437b551bd7906ab
Author: Alexandr Kuramshin 
Date:   2017-03-27T10:16:22Z

IGNITE-4865 Verbose logging, informative messages




> Non-informative error message on using GridClientOptimizedMarshaller with 
> unknown task classes
> --
>
> Key: IGNITE-4865
> URL: https://issues.apache.org/jira/browse/IGNITE-4865
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
>
> Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
> class is not present in {{classnames.properties}}. It occurs when 
> {{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.
> {noformat}
> Closing NIO session because of unhandled exception [cls=class 
> o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
> Failed to deserialize object with given class loader: null]
> {noformat}
> There is two problems:
> * Actual problem was hidden
> {noformat}
> Caused by: java.lang.UnsupportedOperationException
> at 
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
> at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
> {noformat}
> * Even reading the cause we don't understand what is wrong
> What to do:
> * Log stacktrace every time
> * Throw UnsupportedOperationException with informative message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4866) Add lazy value deserialization in GridCacheRawVersionedEntry

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-4866:
---

 Summary: Add lazy value deserialization in 
GridCacheRawVersionedEntry
 Key: IGNITE-4866
 URL: https://issues.apache.org/jira/browse/IGNITE-4866
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4534) Implement offheap eviction policies based on page memory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4534:


GitHub user glukos opened a pull request:

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

IGNITE-4534: Implement offheap eviction policies based on page memory

Per-page eviction policies are implemented, algorithm (random-LRU or 
random-K-LRU) can be configured in MemoryPolicyConfiguration.

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

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

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

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


commit 60ea031ebf19a7b6b8a205d762ae3b96ef2ed1ba
Author: Ivan Rakov 
Date:   2017-02-28T10:56:40Z

IGNITE-4534: First approach to evict by page index

commit c5d45a4fa575a444537db7a933a8f489574ccf83
Author: Ivan Rakov 
Date:   2017-02-28T11:35:36Z

IGNITE-4534: First approach to evict by page index

commit 27d024048bf6689e59548bfdf67461665b9ee06b
Author: Ivan Rakov 
Date:   2017-03-02T17:34:19Z

IGNITE-4534: Random-LRU implemented

commit 0b7c770e4e12826e45a7716ec408129f68cf6ebb
Author: Ivan Rakov 
Date:   2017-03-03T12:04:00Z

IGNITE-4534: Bugs fixed. Works fine for small objects, found bug with big 
objects (size > pageSize)

commit a8d74454f6e0c67632c5a2f2a10a41e8e2fcbe12
Author: Ivan Rakov 
Date:   2017-03-03T13:02:13Z

IGNITE-4534: Smoke test added

commit f5ff54a9945477768bf74161c8c51d4ce83d4b62
Author: Sergey Chugunov 
Date:   2017-03-02T16:24:20Z

IGNITE-4758 multiple MemoryPolicies were implemented

commit 5479f947f672e28fc39f92e8a489c016f96d10f0
Author: Sergey Chugunov 
Date:   2017-03-09T10:17:45Z

Merge branch 'ignite-3477' into ignite-4758

commit db1087e28f438c494d96afea92de2b454f369c46
Author: Sergey Chugunov 
Date:   2017-03-09T12:13:17Z

IGNITE-4758 added back 'freeList' parameter on RowStore constructor

commit 4cd7cfab87f385fd6633f866d7f63625c010b649
Author: Ivan Rakov 
Date:   2017-03-13T12:17:24Z

IGNITE-4534: Fixed bug with reading fragmented data row

commit 26458a89bef395325232172dfcc20403c8d00eaa
Author: Ivan Rakov 
Date:   2017-03-13T12:39:23Z

Merge branch 'ignite-4758' into ignite-4534

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/CacheDataRowAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/IgniteCacheDatabaseSharedManager.java

commit a0ae590e0411a1d029dfc515edf66fe45eb7635b
Author: Ivan Rakov 
Date:   2017-03-13T15:00:22Z

IGNITE-4578: Refactoring - configuration is now available from policy; 
memory policy map is introduced.

commit df92f49048905a0245cf1daa0499cf96dd3c7238
Author: Ivan Rakov 
Date:   2017-03-13T15:01:13Z

Merge branch 'ignite-4758' into ignite-4534

commit 9a5a4f17940ee902b27cd06998fb235553e4dea9
Author: Ivan Rakov 
Date:   2017-03-13T16:54:14Z

IGNITE-4534: Integrated memory policy changes

commit 9eaa00ef1a0d0124a23b59ef1245fa4e6df25478
Author: Sergey Chugunov 
Date:   2017-03-13T16:20:12Z

IGNITE-4758 Indexing SPI tests fix, CPP tests configs refactoring, 
documentation improvements

commit 89ce9b672223110b7f3b2ab36117772e9ddae06b
Author: Sergey Chugunov 
Date:   2017-03-15T08:40:41Z

IGNITE-4758 some tests were added, code was improved to avoid NPE on client 
nodes, documentation was detailed

commit bf491b3a2fe94d05ff77d812809c02ce908036cf
Author: Sergey Chugunov 
Date:   2017-03-16T11:16:51Z

IGNITE-4758 NPE on metrics gathering on client node was fixed

commit a4cbde0cfe25e9e40ba06882dc97b5d815cb4cf6
Author: Sergey Chugunov 
Date:   2017-03-20T14:27:53Z

IGNITE-4758 bug with initializing default memory pool was fixed

commit 1faea11b1e3f360b592cecd88149d86d8ba30e3a
Author: Ivan Rakov 
Date:   2017-03-20T17:14:53Z

Merge branch 'ignite-4758' into ignite-4534

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

commit df37f1f04d73a70ffd80c4bc6022a395ca7846ce
Author: Ivan Rakov 
Date:   2017-03-20T17:16:52Z

Fixing after merging ignite-4758

commit 

[jira] [Created] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-4865:
--

 Summary: Non-informative error message on using 
GridClientOptimizedMarshaller with unknown task classes
 Key: IGNITE-4865
 URL: https://issues.apache.org/jira/browse/IGNITE-4865
 Project: Ignite
  Issue Type: Improvement
  Components: rest
Affects Versions: 2.0
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
class is not present in {{classnames.properties}}. It occurs when 
{{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.

{noformat}
Closing NIO session because of unhandled exception [cls=class 
o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
Failed to deserialize object with given class loader: null]
{noformat}

There is two problems:
* Actual problem was hidden
{noformat}
Caused by: java.lang.UnsupportedOperationException
at 
org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
{noformat}
* Even reading the cause we don't understand what is wrong

What to do:
* Log stacktrace every time
* Throw UnsupportedOperationException with informative message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4535) Add option to store deserialized values on-heap

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-4535:
--

Please review.

> Add option to store deserialized values on-heap
> ---
>
> Key: IGNITE-4535
> URL: https://issues.apache.org/jira/browse/IGNITE-4535
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Ilya Lantukh
>  Labels: important
> Fix For: 2.0
>
>
> Now cache data is always stored in offheap (pagememory). Need implement 
> option to also store deserialised values in heap memory, this should be 
> replacement for existing CacheConfiguration.memoryMode configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4535) Add option to store deserialized values on-heap

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-4535:


Assignee: Alexey Goncharuk  (was: Ilya Lantukh)

> Add option to store deserialized values on-heap
> ---
>
> Key: IGNITE-4535
> URL: https://issues.apache.org/jira/browse/IGNITE-4535
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Now cache data is always stored in offheap (pagememory). Need implement 
> option to also store deserialised values in heap memory, this should be 
> replacement for existing CacheConfiguration.memoryMode configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3474) Grid hung during load test with warning "Failed to wait for partition map exchange"

[Anuj Kumar (JIRA)]

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

Anuj Kumar commented on IGNITE-3474:


I am facing this issue in 1.9. Second node couldn't join the cluster gives this 
error.
Failed to wait for partition map exchange

> Grid hung during load test with warning "Failed to wait for partition map 
> exchange"
> ---
>
> Key: IGNITE-3474
> URL: https://issues.apache.org/jira/browse/IGNITE-3474
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Semen Boikov
>Priority: Critical
> Attachments: 132548_id2_172.25.1.33_part.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml
>
>
> During load test grid hung:
> {noformat}
> [09:22:17,688][WARN 
> ][exchange-worker-#137%null%][GridCachePartitionExchangeManager] Failed to 
> wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=97, 
> minorTopVer=0], node=0fe0c0f2-65e1-4ad5-a8c9-92db997fcb7d]. Dumpin
> g pending objects that might be the cause:
> ...
> {noformat}
> See attached file with more info from logs.
> Notes:
> The issue was also reproduced with IGNITE-3239 fixed. So, IGNITE-3239 doesn't 
> seem to be a root cause. 
> Configs:
> 1)
>  - Benchmark name: IgniteCacheRandomOperationBenchmark 
>  - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, 
> remove_all, put_if_absent, replace
> - Heap: 4Gb for servers, 1Gb for clients
> - 80 clients, 20 servers, 8 hosts
> - Number of caches: 100
> - Preload amount 250K
> - Key range 500K
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, 
> onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> 2) 
> - Benchmark name: IgniteCacheRandomOperationBenchmark 
> - Operations: scan_query, sql_query, continuous_query
> - Heap: 4Gb for servers, 1Gb for clients
> - 20 clients, 80 servers, 8 hosts
> - Number of caches: 12
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, 
> onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> Attachments:
> - part of log with the problem (for one of the servers) for config #2
> - xml configs and property file that were used to run yardstick for config #2
> Complete logs can be provided on demand.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4862) NPE in reading data from IGFS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4862:

Priority: Minor  (was: Critical)

> NPE in reading data from IGFS
> -
>
> Key: IGNITE-4862
> URL: https://issues.apache.org/jira/browse/IGNITE-4862
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.9
>Reporter: Dmitry Karachentsev
>Priority: Minor
> Fix For: 2.0
>
>
> {noformat}
> D:\app\CodexRT.CodexRT_20170314-1>hadoop\bin\hadoop fs -copyToLocal 
> igfs:///cacheLink/test3.orc D:\test3.orc
> -copyToLocal: Fatal internal error
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$FetchBufferPart.flatten(HadoopIgfsInputStream.java:458)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$DoubleFetchBuffer.flatten(HadoopIgfsInputStream.java:511)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream.read(HadoopIgfsInputStream.java:177)
> at java.io.DataInputStream.read(DataInputStream.java:100)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:91)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:59)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:119)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination$TargetFileSystem.writeStreamToFile(CommandWithDestination.java:466)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.copyStreamToTarget(CommandWithDestination.java:391)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.copyFileToTarget(CommandWithDestination.java:328)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPath(CommandWithDestination.java:263)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPath(CommandWithDestination.java:248)
> at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:317)
> at 
> org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:289)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPathArgument(CommandWithDestination.java:243)
> at 
> org.apache.hadoop.fs.shell.Command.processArgument(Command.java:271)
> at 
> org.apache.hadoop.fs.shell.Command.processArguments(Command.java:255)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processArguments(CommandWithDestination.java:220)
> at 
> org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:201)
> at org.apache.hadoop.fs.shell.Command.run(Command.java:165)
> at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
> {noformat}
> Details in discussion: 
> [http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-when-using-IGFS-td11328.html]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4864) .NET: Support arrays in SQL

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4864:
--

 Summary: .NET: Support arrays in SQL
 Key: IGNITE-4864
 URL: https://issues.apache.org/jira/browse/IGNITE-4864
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Ignite SQL supports arrays, for example, string array can be configured via 
{{QueryEntity.ValueTypeName = "L[java.lang.String;";}} and then queried with 
{{WHERE array_contains(ABC, ?);}}.

* Update {{JavaTypes}} with array mappings
* Add tests to make sure results and arguments are passed properly
* Add support in LINQ (separate ticket?)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)