[jira] [Commented] (IGNITE-4799) Remove TcpDiscoverySpi.heartbeatsFrequency parameter

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-4799:
--

Create ignite-4799-2.0 branch from ignite-2.0 and move all commits. Please 
commit changes from IGNITE-5062 to it.

> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> 
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Semen Boikov
>  Labels: important
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the 
> heartbeats frequence. It affects the frequency of metrics messages sent over 
> the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of 
> metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics 
> messages are not participated in the failure detection process. We have to 
> clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
>  



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

[jira] [Comment Edited] (IGNITE-4539) RocketMQ data streamer

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-4539 at 4/25/17 2:39 AM:
---

[~agoncharuk] [~dmagda] Can we include it into 2.0 release? Any objections?


was (Author: roman_s):
[~agoncharuk] Can we include it into 2.0 release?

> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: important
> Fix For: 2.1
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



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

[jira] [Commented] (IGNITE-4970) Document all transactional methods

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4970:
-

Documented. See "Transactional Methods" callout here:
https://apacheignite.readme.io/docs/transactions-20

> Document all transactional methods
> --
>
> Key: IGNITE-4970
> URL: https://issues.apache.org/jira/browse/IGNITE-4970
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 2.0
>
>
> Refer to IGNITE-4795 to get a list of transactional methods that have to be 
> documented on: 
> https://dash.readme.io/project/apacheignite/v1.9/docs/transactions-20



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

[jira] [Closed] (IGNITE-4970) Document all transactional methods

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-4970.
---

> Document all transactional methods
> --
>
> Key: IGNITE-4970
> URL: https://issues.apache.org/jira/browse/IGNITE-4970
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 2.0
>
>
> Refer to IGNITE-4795 to get a list of transactional methods that have to be 
> documented on: 
> https://dash.readme.io/project/apacheignite/v1.9/docs/transactions-20



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

[jira] [Resolved] (IGNITE-4970) Document all transactional methods

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-4970.
-
Resolution: Fixed

> Document all transactional methods
> --
>
> Key: IGNITE-4970
> URL: https://issues.apache.org/jira/browse/IGNITE-4970
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 2.0
>
>
> Refer to IGNITE-4795 to get a list of transactional methods that have to be 
> documented on: 
> https://dash.readme.io/project/apacheignite/v1.9/docs/transactions-20



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

[jira] [Created] (IGNITE-5071) Web Console: Support custom table names on model import

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5071:


 Summary: Web Console: Support custom table names on model import
 Key: IGNITE-5071
 URL: https://issues.apache.org/jira/browse/IGNITE-5071
 Project: Ignite
  Issue Type: Test
  Components: wizards
Affects Versions: 1.9
Reporter: Alexey Kuznetsov
Assignee: Vasiliy Sisko
 Fix For: 2.0


We need to support table aliases aka custom table name on models import from 
RDBMS.

See QueryEntity.TableName property.



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

[jira] [Commented] (IGNITE-5070) Update Affinity Functions Documentation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5070:
-

In addition, provide an example on how to configure the function.

> Update Affinity Functions Documentation
> ---
>
> Key: IGNITE-5070
> URL: https://issues.apache.org/jira/browse/IGNITE-5070
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.0
>
>
> Review and update the existing documentation on the affinity functions:
> https://apacheignite.readme.io/docs/affinity-collocation#affinity-function
> At least the fair affinity function has to be removed from there and 
> mentioned in the migration guide.



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

[jira] [Created] (IGNITE-5070) Update Affinity Functions Documentation

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5070:
---

 Summary: Update Affinity Functions Documentation
 Key: IGNITE-5070
 URL: https://issues.apache.org/jira/browse/IGNITE-5070
 Project: Ignite
  Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Denis Magda
Priority: Critical


Review and update the existing documentation on the affinity functions:
https://apacheignite.readme.io/docs/affinity-collocation#affinity-function

At least the fair affinity function has to be removed from there and mentioned 
in the migration guide.



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

[jira] [Closed] (IGNITE-4966) Document SQL index hints and merge sort capabilities

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4966.
---

Reviewed.

> Document SQL index hints and merge sort capabilities
> 
>
> Key: IGNITE-4966
> URL: https://issues.apache.org/jira/browse/IGNITE-4966
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> Document the following:
> * SQL hints usage (IGNITE-4594)
> * Merge sort (IGNITE-3013)
> Readme page:
> https://dash.readme.io/project/apacheignite/v1.9/docs/distributed-queries-20



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

[jira] [Updated] (IGNITE-5065) DSL/scripting support

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-5065:
---
Summary: DSL/scripting support  (was: DSL/scription support)

> DSL/scripting support
> -
>
> Key: IGNITE-5065
> URL: https://issues.apache.org/jira/browse/IGNITE-5065
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>
> The goal is introduce JS(using Nashorn) support as scripting language. Also 
> we should make investigation about using Scala as DSL.



--
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=15981446#comment-15981446
 ] 

ASF GitHub Bot commented on IGNITE-4575:


Github user skalashnikov closed the pull request at:

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


> 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: Task
>  Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>




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

[jira] [Assigned] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

[neeraj (JIRA)]

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

neeraj reassigned IGNITE-5046:
--

Assignee: neeraj

> TcpDiscoverySpi.toString() method miss some fields.
> ---
>
> Key: IGNITE-5046
> URL: https://issues.apache.org/jira/browse/IGNITE-5046
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: neeraj
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> We have a number of protected fields that is missed by toString method.
> Looks like we should annotate these fields with @GridToStringInclude.
> locAddr, locPort, locPortRange, netTimeout and others.



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

[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3487:


GitHub user skalashnikov opened a pull request:

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

IGNITE-3487: hidden _key and _val columns



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

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

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

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






> _key and _val fields should be excluded from 'select * from' queries
> 
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}} 
> fields are returned when query like {{select * from}} is executed. First of 
> all, this is counterintuitive because user never defines or configures these 
> fields. Second of all, they actually duplicate all other fields. And finally, 
> they cause serialization exceptions because classes for key and value are not 
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a 
> compatibility breaking change. It should be done in 2.0.



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

[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3487:


Github user skalashnikov closed the pull request at:

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


> _key and _val fields should be excluded from 'select * from' queries
> 
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}} 
> fields are returned when query like {{select * from}} is executed. First of 
> all, this is counterintuitive because user never defines or configures these 
> fields. Second of all, they actually duplicate all other fields. And finally, 
> they cause serialization exceptions because classes for key and value are not 
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a 
> compatibility breaking change. It should be done in 2.0.



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

[jira] [Commented] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5050:


Dev list thread created, waiting for the decision: 
http://apache-ignite-developers.2346864.n4.nabble.com/MemoryMetrics-interface-inconsistencies-td17156.html

> .NET: IIgnite.GetMemoryMetrics
> --
>
> Key: IGNITE-5050
> URL: https://issues.apache.org/jira/browse/IGNITE-5050
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Add {{IIgnite.GetMemoryMetrics()}} in .NET which delegates to 
> {{Ignite.memoryMetrics()}} in Java



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

[jira] [Created] (IGNITE-5069) QueryWords example fails with exception

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5069:
-

 Summary: QueryWords example fails with exception
 Key: IGNITE-5069
 URL: https://issues.apache.org/jira/browse/IGNITE-5069
 Project: Ignite
  Issue Type: Bug
Reporter: Yakov Zhdanov
Priority: Blocker
 Fix For: 2.0


[~sergi.vladykin], please have a look. It may happen so that avg(cnt) in former 
Ignite versions was returned as double for long column. For current master it 
is returned as long and causes exception in formatter. I was able to reproduce 
it on 1.9 also, but did not try other versions.

Steps to reproduce
# start {{ExampleNodeStartup}}
# start {{QueryWords}}
# start {{StreamWords}}

{noformat}
/opt/jdk/jdk1.8.0_121/bin/java...
org.apache.ignite.examples.streaming.wordcount.QueryWords
[18:20:17]__   
[18:20:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
[18:20:17]  _/ // (7 7// /  / / / _/   
[18:20:17] /___/\___/_/|_/___/ /_/ /___/  
[18:20:17] 
[18:20:17] ver. 2.1.0-SNAPSHOT#19700101-sha1:DEV
[18:20:17] 2017 Copyright(C) Apache Software Foundation
[18:20:17] 
[18:20:17] Ignite documentation: http://ignite.apache.org
[18:20:17] 
[18:20:17] Quiet mode.
[18:20:17]   ^-- Logging to file 
'/home/yzhdanov/projects/incubator-ignite/work/log/ignite-dbfdab2d.log'
[18:20:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[18:20:17] 
[18:20:17] OS: Linux 4.8.0-46-generic amd64
[18:20:17] VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
[18:20:17] Initial heap size is 246MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[18:20:17] Configured plugins:
[18:20:17]   ^-- None
[18:20:17] 
[18:20:17] Message queue limit is set to 0 which may lead to potential OOMEs 
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
message queues growth on sender and receiver sides.
[18:20:17] Security status [authentication=off, tls/ssl=off]
[18:20:18] REST protocols do not start on client node. To start the protocols 
on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system property.
[18:20:20] Performance suggestions for grid  (fix if possible)
[18:20:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[18:20:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[18:20:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[18:20:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
JVM options)
[18:20:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[18:20:20]   ^-- Disable processing of calls to System.gc() (add 
'-XX:+DisableExplicitGC' to JVM options)
[18:20:20] Refer to this page for more performance suggestions: 
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[18:20:20] 
[18:20:20] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[18:20:20] 
[18:20:20] Ignite node started OK (id=dbfdab2d)
[18:20:20] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]
Query result set is empty.
Query result set is empty.
[18:20:27] Topology snapshot [ver=3, servers=1, clients=2, CPUs=4, heap=10.0GB]
Query results [avg=[18:20:33] Ignite node stopped OK [uptime=00:00:12:733]
Exception in thread "main" java.util.IllegalFormatConversionException: f != 
java.lang.Long
at 
java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302)
at java.util.Formatter$FormatSpecifier.printFloat(Formatter.java:2806)
at java.util.Formatter$FormatSpecifier.print(Formatter.java:2753)
at java.util.Formatter.format(Formatter.java:2520)
at java.io.PrintStream.format(PrintStream.java:970)
at java.io.PrintStream.printf(PrintStream.java:871)
at 
org.apache.ignite.examples.streaming.wordcount.QueryWords.main(QueryWords.java:78)

Process finished with exit code 1

{noformat}



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

[jira] [Commented] (IGNITE-5036) Disallow @QuerySqlField and @QueryTextField on methods

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5036:
--

[~irudyak], please review the changes at the {{cassandra store}} modules.

> Disallow @QuerySqlField and @QueryTextField on methods
> --
>
> Key: IGNITE-5036
> URL: https://issues.apache.org/jira/browse/IGNITE-5036
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Resolved] (IGNITE-795) IgniteCacheTxMessageRecoveryTest fails from time to time on TC

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-795.
-
Resolution: Cannot Reproduce
  Assignee: (was: Semen Boikov)

> IgniteCacheTxMessageRecoveryTest fails from time to time on TC
> --
>
> Key: IGNITE-795
> URL: https://issues.apache.org/jira/browse/IGNITE-795
> Project: Ignite
>  Issue Type: Test
>  Components: cache
>Reporter: Semen Boikov
>
> IgniteCacheTxMessageRecoveryTest fails from time to time on TC (assert at 
> line 165: 'assertTrue(clients.size() > 0);').



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

[jira] [Assigned] (IGNITE-3362) Event EVT_CACHE_REBALANCE_STOPPED fires prematurely.

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-3362:


Assignee: (was: Semen Boikov)

> Event EVT_CACHE_REBALANCE_STOPPED fires prematurely.
> 
>
> Key: IGNITE-3362
> URL: https://issues.apache.org/jira/browse/IGNITE-3362
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
>
> EVT_CACHE_REBALANCE_STOPPED fires earlier then the partiotions has been 
> rebalanced.
> You can see detail here: 
> [How do I know the cache rebalance is 
> finished?|http://apache-ignite-users.70518.x6.nabble.com/How-do-I-know-the-cache-rebalance-is-finished-tc5219.html#a5746]



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

[jira] [Assigned] (IGNITE-2254) Need append nodeId for sql-query command in REST API

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2254:


Assignee: (was: Semen Boikov)

> Need append nodeId for sql-query command in REST API
> 
>
> Key: IGNITE-2254
> URL: https://issues.apache.org/jira/browse/IGNITE-2254
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Reporter: Andrey Novikov
>
> Query execute command should return nodeId for node where QueryCursor stored 
> in nodeLocal
> https://apacheignite.readme.io/v1.6/docs/rest-api#sql-query-execute
> Query fetch command should resend job to node with nodeId
> https://apacheignite.readme.io/v1.6/docs/rest-api#sql-query-fetch



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

[jira] [Commented] (IGNITE-1439) CPP: Implement futures.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1439:


Github user isapego closed the pull request at:

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


> CPP: Implement futures.
> ---
>
> Key: IGNITE-1439
> URL: https://issues.apache.org/jira/browse/IGNITE-1439
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>




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

[jira] [Commented] (IGNITE-5036) Disallow @QuerySqlField and @QueryTextField on methods

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5036:
--

Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1863%2Fhead]

> Disallow @QuerySqlField and @QueryTextField on methods
> --
>
> Key: IGNITE-5036
> URL: https://issues.apache.org/jira/browse/IGNITE-5036
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-5036) Disallow @QuerySqlField and @QueryTextField on methods

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5036:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5036  Disallow @QuerySqlField and @QueryTextField on methods



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

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

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

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


commit 2d505817cef677c523dc27a521a709d983cc26e5
Author: devozerov 
Date:   2017-04-20T08:31:14Z

WIP.

commit 668be3703cedad20c3440f3b6c050e909ad85e38
Author: tledkov-gridgain 
Date:   2017-04-20T09:50:57Z

Merge branch 'ignite-2.0' into ignite-5036

commit 214c665beec3e50ec78ed1f6aa1f5a8a7f07bd57
Author: tledkov-gridgain 
Date:   2017-04-20T10:32:51Z

IGNITE-5036: save the progress

commit b2a420f04075822682e1101d7776041e62dbf88b
Author: tledkov-gridgain 
Date:   2017-04-20T10:41:33Z

IGNITE-5036: save the progress

commit c92e3090be6aa9a2fff881d71b32df185fcae82d
Author: tledkov-gridgain 
Date:   2017-04-20T15:23:54Z

Merge branch 'ignite-2.0' into ignite-5036

commit 564e59f71482ef0791c4a6d18b50b12cb463d516
Author: tledkov-gridgain 
Date:   2017-04-21T08:34:55Z

IGNITE-5036: save the progress

commit 2861a904d6c8429627cb49e34c247de380fe7b9b
Author: tledkov-gridgain 
Date:   2017-04-21T13:41:10Z

Merge branch 'ignite-2.0' into ignite-5036

commit cc54788c586782110ecf6ed2b673142acef7af40
Author: tledkov-gridgain 
Date:   2017-04-24T09:15:37Z

Merge branch 'ignite-2.0' into ignite-5036

commit 53e07627f1e72dbe3e7594e805a56d9fa3522e42
Author: tledkov-gridgain 
Date:   2017-04-24T12:28:39Z

IGNITE-5036: cassandra: save the progress

commit e27054f9cc430ce8d3541129efffe5b7e0ea523f
Author: tledkov-gridgain 
Date:   2017-04-24T13:28:10Z

IGNITE-5036: cassandra: save the progress

commit 732b6c8850a84a12536ff2b38964010e1c3d20ea
Author: tledkov-gridgain 
Date:   2017-04-24T14:16:11Z

IGNITE-5036: cassandra: save the progress

commit 504890f3182085b304166a88c4c965e1d5a12cbb
Author: tledkov-gridgain 
Date:   2017-04-24T14:37:41Z

IGNITE-5036: the progress




> Disallow @QuerySqlField and @QueryTextField on methods
> --
>
> Key: IGNITE-5036
> URL: https://issues.apache.org/jira/browse/IGNITE-5036
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-1439) CPP: Implement futures.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-1439:


Looks good to me.

> CPP: Implement futures.
> ---
>
> Key: IGNITE-1439
> URL: https://issues.apache.org/jira/browse/IGNITE-1439
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-5068) Redesign GridDhtPartitionTopologyImpl.part2node map to store only diff from affinity assignment

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh updated IGNITE-5068:
-
Summary: Redesign GridDhtPartitionTopologyImpl.part2node map to store only 
diff from affinity assignment  (was: Redesign usage of 
GridDhtPartitionTopologyImpl.part2node map to store only diff from affinity 
assignment)

> Redesign GridDhtPartitionTopologyImpl.part2node map to store only diff from 
> affinity assignment
> ---
>
> Key: IGNITE-5068
> URL: https://issues.apache.org/jira/browse/IGNITE-5068
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>
> This map can become very huge on large topologies, and rebuilding it on each 
> update is also costly. Some beneficial changes were made in the scope of 
> IGNITE-4626, but further improvement requires complete redesign.
> This map always stores affinity nodes + some additional "temporary owners". 
> Those owners are only needed to complete rebalancing and they will evict 
> partition when rebalancing is finished. It seems that storing only those 
> non-affinity owners can greatly reduce memory required by this map (it will 
> be empty on stable topology) and effort needed to keep it consistent with 
> node2part.



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

[jira] [Created] (IGNITE-5068) Redesign usage of GridDhtPartitionTopologyImpl.part2node map to store only diff from affinity assignment

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5068:


 Summary: Redesign usage of GridDhtPartitionTopologyImpl.part2node 
map to store only diff from affinity assignment
 Key: IGNITE-5068
 URL: https://issues.apache.org/jira/browse/IGNITE-5068
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh


This map can become very huge on large topologies, and rebuilding it on each 
update is also costly. Some beneficial changes were made in the scope of 
IGNITE-4626, but further improvement requires complete redesign.
This map always stores affinity nodes + some additional "temporary owners". 
Those owners are only needed to complete rebalancing and they will evict 
partition when rebalancing is finished. It seems that storing only those 
non-affinity owners can greatly reduce memory required by this map (it will be 
empty on stable topology) and effort needed to keep it consistent with 
node2part.



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

[jira] [Created] (IGNITE-5067) Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir path

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5067:
---

 Summary: Absolute swapFilePath for MemoryPolicy is merged 
incorrectly with working dir path
 Key: IGNITE-5067
 URL: https://issues.apache.org/jira/browse/IGNITE-5067
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.0
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.1


h2. Steps to reproduce
* Create *MemoryPolicyConfiguration* with swapFilePath specified to some 
*absolute* path
* Start Ignite node with this configuration.

h2. Expected outcome
Swap file is allocated by absolute path specified by configuration.

h2. Actual outcome
Swap file is allocated by path where current working directory is merged with 
swapFilePath.




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

[jira] [Comment Edited] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5050 at 4/24/17 1:32 PM:
-

Main difficulty here is that {{MemoryMetrics}} is not a read-only snapshot like 
all other metrics, it is a living object which is constantly updated.

I think for .NET we should still go with a snapshot approach to avoid frequent 
native calls.

To enable and disable metrics there should be a separate 
{{IIgnite.EnableMemoryMetrics(string policyName, bool enable)}} method.


was (Author: ptupitsyn):
Main difficulty here is that {{MemoryMetrics}} is not a read-only snapshot like 
all other metrics, it is a living object which is constantly updated.

I think for .NET we should still go with a snapshot approach to avoid frequent 
native calls.

> .NET: IIgnite.GetMemoryMetrics
> --
>
> Key: IGNITE-5050
> URL: https://issues.apache.org/jira/browse/IGNITE-5050
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Add {{IIgnite.GetMemoryMetrics()}} in .NET which delegates to 
> {{Ignite.memoryMetrics()}} in Java



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

[jira] [Commented] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5050:


Main difficulty here is that {{MemoryMetrics}} is not a read-only snapshot like 
all other metrics, it is a living object which is constantly updated.

I think for .NET we should still go with a snapshot approach to avoid frequent 
native calls.

> .NET: IIgnite.GetMemoryMetrics
> --
>
> Key: IGNITE-5050
> URL: https://issues.apache.org/jira/browse/IGNITE-5050
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Add {{IIgnite.GetMemoryMetrics()}} in .NET which delegates to 
> {{Ignite.memoryMetrics()}} in Java



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

[jira] [Assigned] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set

[Alexei Kaigorodov (JIRA)]

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

Alexei Kaigorodov reassigned IGNITE-4991:
-

Assignee: Alexei Kaigorodov

> Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is 
> set
> -
>
> Key: IGNITE-4991
> URL: https://issues.apache.org/jira/browse/IGNITE-4991
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alexei Kaigorodov
>  Labels: newbie
> Fix For: 2.1
>
>
> {{IgniteKernal#ackSystemProperties}} and {{IgniteKernal#ackVmArguments}} 
> print out system properties that can contain sensitive data. This print outs 
> should be disabled when {{IGNITE_TO_STRING_INCLUDE_SENSITIVE}} system 
> property is set to {{true}}.



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

[jira] [Commented] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5046:
-

[~neeraj.bhatt], I added you to committers list. Please try again.

> TcpDiscoverySpi.toString() method miss some fields.
> ---
>
> Key: IGNITE-5046
> URL: https://issues.apache.org/jira/browse/IGNITE-5046
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> We have a number of protected fields that is missed by toString method.
> Looks like we should annotate these fields with @GridToStringInclude.
> locAddr, locPort, locPortRange, netTimeout and others.



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

[jira] [Commented] (IGNITE-5041) NPE during deadlock detection because cache isn't started on node

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-5041:
--

Hi Andrey,

Reviewed, did some minor changes, please take a look. Good to merge.

Thanks!

> NPE during deadlock detection because cache isn't started on node
> -
>
> Key: IGNITE-5041
> URL: https://issues.apache.org/jira/browse/IGNITE-5041
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>
> NPE is possible during deadlock detection process in case when one of 
> participating cache isn't started on node that initiates transaction:
> {noformat}
> Exception in thread "sys-#66%transactions.TxDeadlockNpeClientTest1%" 
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxKey.finishUnmarshal(IgniteTxKey.java:92)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.TxLocksResponse.finishUnmarshal(TxLocksResponse.java:190)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.unmarshall(IgniteTxManager.java:2588)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.onMessage(IgniteTxManager.java:2478)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> *Steps to reproduce:*
> # Start server node with two caches.
> # Start two transactions on server node that involve both caches and lead to 
> deadlock.
> # Start client node and create only one cache
> # Start transaction on client node that will try to update key that involved 
> into deadlock
> As result transaction on client node will hang until deadlock detection 
> timeout happens.
> The same result could be achived using node filters for caches.
> *Workaround:*
> Start all caches on node if possible.
> Another way is deadlock detection disabling using JVM parameter 
> {{-DIGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS=0}}
> *Possible solution:*
> Try to create {{CacheObjectContext}} without starting of the cache.



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

[jira] [Commented] (IGNITE-5057) .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5057:


Fixed in {{ignite-2.0}}: {{7c249d7bbb3c6f65e2781e0da3cd21c62d2ce078}}

> .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower
> 
>
> Key: IGNITE-5057
> URL: https://issues.apache.org/jira/browse/IGNITE-5057
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> {{MSBUILD : error MSB1008: Only one project can be specified. Switch: CPU}}



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

[jira] [Resolved] (IGNITE-5057) .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5057.

Resolution: Fixed

> .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower
> 
>
> Key: IGNITE-5057
> URL: https://issues.apache.org/jira/browse/IGNITE-5057
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> {{MSBUILD : error MSB1008: Only one project can be specified. Switch: CPU}}



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

[jira] [Updated] (IGNITE-5044) JVM crash

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5044:

Fix Version/s: (was: 2.0)
   2.1

> JVM crash
> -
>
> Key: IGNITE-5044
> URL: https://issues.apache.org/jira/browse/IGNITE-5044
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 2.1
>
> Attachments: grid.2.node.1.0.out.log, hs_err_pid4079.log
>
>
> Sometimes testing Apache Hadoop +  Apache Hive kills JVM
> Take a look on the attached file



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

[jira] [Commented] (IGNITE-5044) JVM crash

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5044:
-

Moving to {{2.1}}. Will merge to {{2.0}} if fix is ready before vote.

> JVM crash
> -
>
> Key: IGNITE-5044
> URL: https://issues.apache.org/jira/browse/IGNITE-5044
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 2.1
>
> Attachments: grid.2.node.1.0.out.log, hs_err_pid4079.log
>
>
> Sometimes testing Apache Hadoop +  Apache Hive kills JVM
> Take a look on the attached file



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

[jira] [Assigned] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-5046:


Assignee: Andrew Mashenkov

> TcpDiscoverySpi.toString() method miss some fields.
> ---
>
> Key: IGNITE-5046
> URL: https://issues.apache.org/jira/browse/IGNITE-5046
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> We have a number of protected fields that is missed by toString method.
> Looks like we should annotate these fields with @GridToStringInclude.
> locAddr, locPort, locPortRange, netTimeout and others.



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

[jira] [Assigned] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-5046:


Assignee: (was: Andrew Mashenkov)

> TcpDiscoverySpi.toString() method miss some fields.
> ---
>
> Key: IGNITE-5046
> URL: https://issues.apache.org/jira/browse/IGNITE-5046
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> We have a number of protected fields that is missed by toString method.
> Looks like we should annotate these fields with @GridToStringInclude.
> locAddr, locPort, locPortRange, netTimeout and others.



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

[jira] [Commented] (IGNITE-5046) TcpDiscoverySpi.toString() method miss some fields.

[neeraj (JIRA)]

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

neeraj commented on IGNITE-5046:


[~amashenkov] it seems I don't have rights to assign the issues. Can you please 
give proper rights?

> TcpDiscoverySpi.toString() method miss some fields.
> ---
>
> Key: IGNITE-5046
> URL: https://issues.apache.org/jira/browse/IGNITE-5046
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> We have a number of protected fields that is missed by toString method.
> Looks like we should annotate these fields with @GridToStringInclude.
> locAddr, locPort, locPortRange, netTimeout and others.



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

[jira] [Commented] (IGNITE-4799) Remove TcpDiscoverySpi.heartbeatsFrequency parameter

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4799:


[~sbberkov] please merge from 2.0 so I can work on .NET in IGNITE-5062 subtask

> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> 
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Semen Boikov
>  Labels: important
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the 
> heartbeats frequence. It affects the frequency of metrics messages sent over 
> the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of 
> metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics 
> messages are not participated in the failure detection process. We have to 
> clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
>  



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

[jira] [Commented] (IGNITE-5018) review and improve javadocs in ML module

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-5018:


Thank you [Anton 
Vinogradov|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=avinogradov]
 - reference to [commit 
7378bc3|https://github.com/apache/ignite/commit/7378bc38abf8ec6ed8aca9c3608eec00f1a86fb2]
 was really helpful. I see now that it would be possible to find the issue by 
checking the code against 
[guidelines|https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines]
 but that would probably take much more time.

[Denis 
Magda|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dmagda] just 
letting you know that this was merged as you asked.

> review and improve javadocs in ML module
> 
>
> Key: IGNITE-5018
> URL: https://issues.apache.org/jira/browse/IGNITE-5018
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Minor
> Fix For: 2.0
>
>
> Review and improve javadocs in Ignite ML module (added per IGNITE-4572). To 
> name a few, add descriptions for constructor parameters in classes 
> {{CacheMatrix}}, {{CacheMatrixStorage}}, {{RandomVector}}. Etc.



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

[jira] [Commented] (IGNITE-5025) null name for default MemoryPolicy must be replaced with 'default'

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5025:


Fixed on .NET side.

> null name for default MemoryPolicy must be replaced with 'default'
> --
>
> Key: IGNITE-5025
> URL: https://issues.apache.org/jira/browse/IGNITE-5025
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Critical
> Fix For: 2.0
>
>
> Corresponding changes must be applied on .NET side as well.



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

[jira] [Assigned] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko reassigned IGNITE-4991:
---

Assignee: (was: Valentin Kulichenko)

> Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is 
> set
> -
>
> Key: IGNITE-4991
> URL: https://issues.apache.org/jira/browse/IGNITE-4991
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>  Labels: newbie
> Fix For: 2.1
>
>
> {{IgniteKernal#ackSystemProperties}} and {{IgniteKernal#ackVmArguments}} 
> print out system properties that can contain sensitive data. This print outs 
> should be disabled when {{IGNITE_TO_STRING_INCLUDE_SENSITIVE}} system 
> property is set to {{true}}.



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

[jira] [Comment Edited] (IGNITE-5066) .NET: Continuous query fails with exception on Java side

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5066 at 4/24/17 11:10 AM:
--

Added a test ({{TestSameQueryMultipleNodes}}) that reproduces the problem in 
{{ignite-1.9}}. It does not fail in {{ignite-2.0}}, so the problem seems to be 
fixed.

Merged to {{ignite-2.0}}.


was (Author: ptupitsyn):
Added a test that reproduces the problem in {{ignite-1.9}}. It does not fail in 
{{ignite-2.0}}, so the problem seems to be fixed.

Merged to {{ignite-2.0}}.

> .NET: Continuous query fails with exception on Java side
> 
>
> Key: IGNITE-5066
> URL: https://issues.apache.org/jira/browse/IGNITE-5066
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Reported by the user, simple program being run twice:
> {code}
> using (IIgnite ignite = Ignition.Start(config))
> {
> var cache = ignite.GetOrCreateCache(nameof(Data));
> cache.QueryContinuous(new ContinuousQuery(new 
> Listener()));
> 
> // Pressing any key in the console will add a value to the 
> cache
> while (true)
> {
> Console.ReadKey();
> var entry = new Data() { Id = Guid.NewGuid(), Value = "a 
> value" };
> cache.Put(entry.Id, entry);
> }
> }
> {code}
> Causes exceptions on Java side:
> {code}
> Exception in thread "sys-#44%null%" 
> javax.cache.event.CacheEntryListenerException: Failed resolve class for ID: 
> 3076010
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.toCacheEntryListenerException(PlatformUtils.java:593)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:551)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformContinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:705)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1089)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1222)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2000(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2443)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1182)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2300(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1151)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed 
> resolve class for ID: 3076010
> at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:699)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1491)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
> 

[jira] [Commented] (IGNITE-5066) .NET: Continuous query fails with exception on Java side

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5066:


Added a test that reproduces the problem in {{ignite-1.9}}. It does not fail in 
{{ignite-2.0}}, so the problem seems to be fixed.

Merged to {{ignite-2.0}}.

> .NET: Continuous query fails with exception on Java side
> 
>
> Key: IGNITE-5066
> URL: https://issues.apache.org/jira/browse/IGNITE-5066
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Reported by the user, simple program being run twice:
> {code}
> using (IIgnite ignite = Ignition.Start(config))
> {
> var cache = ignite.GetOrCreateCache(nameof(Data));
> cache.QueryContinuous(new ContinuousQuery(new 
> Listener()));
> 
> // Pressing any key in the console will add a value to the 
> cache
> while (true)
> {
> Console.ReadKey();
> var entry = new Data() { Id = Guid.NewGuid(), Value = "a 
> value" };
> cache.Put(entry.Id, entry);
> }
> }
> {code}
> Causes exceptions on Java side:
> {code}
> Exception in thread "sys-#44%null%" 
> javax.cache.event.CacheEntryListenerException: Failed resolve class for ID: 
> 3076010
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.toCacheEntryListenerException(PlatformUtils.java:593)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:551)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformContinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:705)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1089)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1222)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2000(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2443)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1182)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2300(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1151)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed 
> resolve class for ID: 3076010
> at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:699)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1491)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryEvent.getValue(CacheContinuousQueryEvent.java:73)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.writeCacheEntryEvent(PlatformUtils.java:606)
> 

[jira] [Resolved] (IGNITE-5066) .NET: Continuous query fails with exception on Java side

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5066.

Resolution: Fixed

> .NET: Continuous query fails with exception on Java side
> 
>
> Key: IGNITE-5066
> URL: https://issues.apache.org/jira/browse/IGNITE-5066
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Reported by the user, simple program being run twice:
> {code}
> using (IIgnite ignite = Ignition.Start(config))
> {
> var cache = ignite.GetOrCreateCache(nameof(Data));
> cache.QueryContinuous(new ContinuousQuery(new 
> Listener()));
> 
> // Pressing any key in the console will add a value to the 
> cache
> while (true)
> {
> Console.ReadKey();
> var entry = new Data() { Id = Guid.NewGuid(), Value = "a 
> value" };
> cache.Put(entry.Id, entry);
> }
> }
> {code}
> Causes exceptions on Java side:
> {code}
> Exception in thread "sys-#44%null%" 
> javax.cache.event.CacheEntryListenerException: Failed resolve class for ID: 
> 3076010
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.toCacheEntryListenerException(PlatformUtils.java:593)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:551)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformContinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:705)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1089)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
> at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1222)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2000(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2443)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1182)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2300(GridIoManager.java:108)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1151)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed 
> resolve class for ID: 3076010
> at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:699)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1491)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryEvent.getValue(CacheContinuousQueryEvent.java:73)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.writeCacheEntryEvent(PlatformUtils.java:606)
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:539)
> ... 15 more
> Caused by: class 

[jira] [Updated] (IGNITE-5066) .NET: Continuous query fails with exception on Java side

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5066:
---
Description: 
Reported by the user, simple program being run twice:
{code}
using (IIgnite ignite = Ignition.Start(config))
{
var cache = ignite.GetOrCreateCache(nameof(Data));
cache.QueryContinuous(new ContinuousQuery(new 
Listener()));

// Pressing any key in the console will add a value to the cache
while (true)
{
Console.ReadKey();

var entry = new Data() { Id = Guid.NewGuid(), Value = "a 
value" };
cache.Put(entry.Id, entry);
}
}
{code}

Causes exceptions on Java side:
{code}
Exception in thread "sys-#44%null%" 
javax.cache.event.CacheEntryListenerException: Failed resolve class for ID: 
3076010
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.toCacheEntryListenerException(PlatformUtils.java:593)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:551)
at 
org.apache.ignite.internal.processors.platform.cache.query.PlatformContinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:705)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1089)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1222)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2000(GridIoManager.java:108)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2443)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1182)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2300(GridIoManager.java:108)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1151)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed resolve 
class for ID: 3076010
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:699)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1491)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryEvent.getValue(CacheContinuousQueryEvent.java:73)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.writeCacheEntryEvent(PlatformUtils.java:606)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:539)
... 15 more
Caused by: class org.apache.ignite.IgniteCheckedException: Class definition was 
not found at marshaller cache and local file. [id=3076010, 
file=C:\Users\USER\AppData\Local\Temp\ignite\work\marshaller\3076010.classname]
at 
org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:218)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:683)
{code}

For some reason Java tries to deserialize .NET value.
There is no exception on .NET side, but events are not delivered.

  

[jira] [Created] (IGNITE-5066) .NET: Continuous query fails with exception on Java side

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5066:
--

 Summary: .NET: Continuous query fails with exception on Java side
 Key: IGNITE-5066
 URL: https://issues.apache.org/jira/browse/IGNITE-5066
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.9
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


Reported by the user, simple program being run twice:
{code}
using (IIgnite ignite = Ignition.Start(config))
{
var cache = ignite.GetOrCreateCache(nameof(Data));
cache.QueryContinuous(new ContinuousQuery(new 
Listener()));

// Pressing any key in the console will add a value to the cache
while (true)
{
Console.ReadKey();

var entry = new Data() { Id = Guid.NewGuid(), Value = "a 
value" };
cache.Put(entry.Id, entry);
}
}
{code}

Causes exceptions on Java side:
{code}
Exception in thread "sys-#44%null%" 
javax.cache.event.CacheEntryListenerException: Failed resolve class for ID: 
3076010
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.toCacheEntryListenerException(PlatformUtils.java:593)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:551)
at 
org.apache.ignite.internal.processors.platform.cache.query.PlatformContinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:705)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1089)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1222)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2000(GridIoManager.java:108)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2443)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1182)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2300(GridIoManager.java:108)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1151)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed resolve 
class for ID: 3076010
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:699)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1491)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryEvent.getValue(CacheContinuousQueryEvent.java:73)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.writeCacheEntryEvent(PlatformUtils.java:606)
at 
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.applyContinuousQueryEvents(PlatformUtils.java:539)
... 15 more
Caused by: class org.apache.ignite.IgniteCheckedException: Class definition was 
not found at marshaller cache and local file. [id=3076010, 
file=C:\Users\USER\AppData\Local\Temp\ignite\work\marshaller\3076010.classname]
at 
org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:218)
at 

[jira] [Created] (IGNITE-5065) DSL/scription support

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5065:
--

 Summary: DSL/scription support
 Key: IGNITE-5065
 URL: https://issues.apache.org/jira/browse/IGNITE-5065
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Yury Babak
Assignee: Yury Babak


The goal is introduce JS(using Nashorn) support as scripting language. Also we 
should make investigation about using Scala as DSL.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4575:

Fix Version/s: (was: 2.0)
   2.1

> 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: Task
>  Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>




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

[jira] [Comment Edited] (IGNITE-5018) review and improve javadocs in ML module

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-5018 at 4/24/17 10:26 AM:


[~oignatenko]
I've merged pullrequest, looks good to me. 
Only one thing I've fixed - is imports, see commit 
7378bc38abf8ec6ed8aca9c3608eec00f1a86fb2 for details.
Thanks for contribution. Merged to ignite-2.0.


was (Author: avinogradov):
[~oignatenko]
I've merged pullrequest, looks good to me. 
Only one thing I've fixes - is imports, see commit 
7378bc38abf8ec6ed8aca9c3608eec00f1a86fb2 for details.
Thanks for contribution. Merged to ignite-2.0.

> review and improve javadocs in ML module
> 
>
> Key: IGNITE-5018
> URL: https://issues.apache.org/jira/browse/IGNITE-5018
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Minor
> Fix For: 2.0
>
>
> Review and improve javadocs in Ignite ML module (added per IGNITE-4572). To 
> name a few, add descriptions for constructor parameters in classes 
> {{CacheMatrix}}, {{CacheMatrixStorage}}, {{RandomVector}}. Etc.



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

[jira] [Assigned] (IGNITE-5052) Implement CREATE/DROP table parsing and execution

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-5052:
---

Assignee: Alexander Paschenko

> Implement CREATE/DROP table parsing and execution
> -
>
> Key: IGNITE-5052
> URL: https://issues.apache.org/jira/browse/IGNITE-5052
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.1
>
>
> Convert SQL string to relevant Igntie command. This could be:
> - {{createCache}}
> - {{getOrCreateCache}} (for {{IF NOT EXISTS}} case)
> - {{destroyCache}}



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

[jira] [Resolved] (IGNITE-5018) review and improve javadocs in ML module

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-5018.
--
Resolution: Fixed

[~oignatenko]
I've merged pullrequest, looks good to me. 
Only one thing I've fixes - is imports, see commit 
7378bc38abf8ec6ed8aca9c3608eec00f1a86fb2 for details.
Thanks for contribution. Merged to ignite-2.0.

> review and improve javadocs in ML module
> 
>
> Key: IGNITE-5018
> URL: https://issues.apache.org/jira/browse/IGNITE-5018
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Minor
> Fix For: 2.0
>
>
> Review and improve javadocs in Ignite ML module (added per IGNITE-4572). To 
> name a few, add descriptions for constructor parameters in classes 
> {{CacheMatrix}}, {{CacheMatrixStorage}}, {{RandomVector}}. Etc.



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

[jira] [Created] (IGNITE-5064) Obsolete EventTypes to be removed

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5064:
---

 Summary: Obsolete EventTypes to be removed
 Key: IGNITE-5064
 URL: https://issues.apache.org/jira/browse/IGNITE-5064
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Sergey Chugunov
Assignee: Alexey Kuznetsov


The following list of EventTypes were removed as part of 
[IGNITE-4952|https://issues.apache.org/jira/browse/IGNITE-4952]:

* *EventType#EVT_CACHE_OBJECT_SWAPPED*
* *EventType#EVT_CACHE_OBJECT_UNSWAPPED*
* *EventType#EVT_SWAP_SPACE_DATA_READ*
* *EventType#EVT_SWAP_SPACE_DATA_STORED*
* *EventType#EVT_SWAP_SPACE_DATA_REMOVED*
* *EventType#EVT_SWAP_SPACE_CLEARED*
* *EventType#EVT_SWAP_SPACE_DATA_EVICTED*
* *EventType#EVT_CACHE_OBJECT_TO_OFFHEAP*
* *EventType#EVT_CACHE_OBJECT_FROM_OFFHEAP*

Corresponding array of swap events was also removed: *EventType#EVTS_SWAPSPACE*.

All references to these events must be removed from sources of web-console.



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

[jira] [Updated] (IGNITE-5063) Dynamic cache start hangs if validation fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5063:

Summary: Dynamic cache start hangs if validation fails  (was: Dynamic cache 
start hangs in validation fails)

> Dynamic cache start hangs if validation fails
> -
>
> Key: IGNITE-5063
> URL: https://issues.apache.org/jira/browse/IGNITE-5063
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> When cache is started dynamically, it's validation occur in exchange thread. 
> If exception is thrown at this point, operation hangs forever.



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

[jira] [Commented] (IGNITE-5058) Improve QueryEntity validation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5058:


Github user devozerov closed the pull request at:

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


> Improve QueryEntity validation
> --
>
> Key: IGNITE-5058
> URL: https://issues.apache.org/jira/browse/IGNITE-5058
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> Currently {{QueryEntity.setIndexes}} mutates provided index in order to set 
> missing index name if needed. This is fundamentally wrong because validation 
> must occur after everything is set, not before. 
> This faulty approach worked fine before, when index name was not dependent on 
> type name. But recent DDL changes broken it further, so now it is impossible 
> to set indexes with null names before setting {{QueryEntity.typeName}}.



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

[jira] [Resolved] (IGNITE-5063) Dynamic cache start hangs in validation fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-5063.
-
Resolution: Duplicate

> Dynamic cache start hangs in validation fails
> -
>
> Key: IGNITE-5063
> URL: https://issues.apache.org/jira/browse/IGNITE-5063
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> When cache is started dynamically, it's validation occur in exchange thread. 
> If exception is thrown at this point, operation hangs forever.



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

[jira] [Closed] (IGNITE-5063) Dynamic cache start hangs in validation fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-5063.
---

> Dynamic cache start hangs in validation fails
> -
>
> Key: IGNITE-5063
> URL: https://issues.apache.org/jira/browse/IGNITE-5063
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> When cache is started dynamically, it's validation occur in exchange thread. 
> If exception is thrown at this point, operation hangs forever.



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

[jira] [Assigned] (IGNITE-5063) Dynamic cache start hangs in validation fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5063:
---

Assignee: (was: Semen Boikov)

> Dynamic cache start hangs in validation fails
> -
>
> Key: IGNITE-5063
> URL: https://issues.apache.org/jira/browse/IGNITE-5063
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> When cache is started dynamically, it's validation occur in exchange thread. 
> If exception is thrown at this point, operation hangs forever.



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5062:
---
Issue Type: Sub-task  (was: Improvement)
Parent: IGNITE-4799

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Created] (IGNITE-5063) Dynamic cache start hangs in validation fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5063:
---

 Summary: Dynamic cache start hangs in validation fails
 Key: IGNITE-5063
 URL: https://issues.apache.org/jira/browse/IGNITE-5063
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.0


When cache is started dynamically, it's validation occur in exchange thread. If 
exception is thrown at this point, operation hangs forever.



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5062:
---
Issue Type: Improvement  (was: Bug)

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5062:
---
Fix Version/s: 2.0

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

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

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5062:
---
Summary: .NET: Support new communication parameters in configuration  (was: 
Support new parameters in .Net)

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Updated] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5062:
---
Component/s: platforms

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



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

[jira] [Commented] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2578:


Merged to {{ignite-2.0}}: {{09b65075b12ff6ea0a54a404e0f339a6538143f1}}

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Resolved] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-2578.

Resolution: Fixed

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Comment Edited] (IGNITE-3521) IGFS: Remove "max space" notion.

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3521 at 4/24/17 9:08 AM:
---

Tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1854%2Fhead]
 are OK with me.

[~vozerov], please review the changes.


was (Author: tledkov-gridgain):
Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1854%2Fhead]

> IGFS: Remove "max space" notion.
> 
>
> Key: IGNITE-3521
> URL: https://issues.apache.org/jira/browse/IGNITE-3521
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We have "max space" concept in IGFS which governs maximum amount of local 
> data available for IGFS. This concept looks a bit weird because we do not 
> have the same thing in caches. 
> Moreover, we have several conflicting configuration parameters:
> 1) {{IgfsPerBlockLruEvictionPolicy}} where we also can specify maximum size.
> 2) {{CacheConfiguration.offheapMaxMemory}} which also governs evictions.
> It looks like we should simply remove "max space" property from IGFS 
> configuration and do not control it anyhow.



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

[jira] [Commented] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2578:


* {{Object.GetHashCode}} is no longer used by Ignite. Hash codes and equality 
are handled by {{BinaryArrayEqualityComparer}} always (IGNITE-4919).
* Un-ignored {{AtomicReferenceTest}} tests, they work as expected.

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Updated] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2578:
---
Fix Version/s: 2.0

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Assigned] (IGNITE-3521) IGFS: Remove "max space" notion.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3521:


Assignee: Taras Ledkov  (was: Alexey Kuznetsov)

> IGFS: Remove "max space" notion.
> 
>
> Key: IGNITE-3521
> URL: https://issues.apache.org/jira/browse/IGNITE-3521
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We have "max space" concept in IGFS which governs maximum amount of local 
> data available for IGFS. This concept looks a bit weird because we do not 
> have the same thing in caches. 
> Moreover, we have several conflicting configuration parameters:
> 1) {{IgfsPerBlockLruEvictionPolicy}} where we also can specify maximum size.
> 2) {{CacheConfiguration.offheapMaxMemory}} which also governs evictions.
> It looks like we should simply remove "max space" property from IGFS 
> configuration and do not control it anyhow.



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

[jira] [Created] (IGNITE-5062) Support new parameters in .Net

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5062:


 Summary: Support new parameters in .Net
 Key: IGNITE-5062
 URL: https://issues.apache.org/jira/browse/IGNITE-5062
 Project: Ignite
  Issue Type: Bug
Reporter: Alexander Belyak
Assignee: Pavel Tupitsyn


Need to support new value and remove old ones:
In TcpDiscoverySpi:
remove maxMissedHeartbeats
remove maxMissedClientHeartbeats
remove heartbeatFrequency
rename hbFreq to metricsUpdateFrequency
In IgniteConfiguration:
add clientFailureDetectionTimeout (long with bounds from metricsUpdateFrequency 
to Integer.MAX_VALUE)



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

[jira] [Assigned] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-2578:
--

Assignee: Pavel Tupitsyn

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Resolved] (IGNITE-4984) AssertionError GridNearAtomicSingleUpdateFuture.onAllReceived on node left

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-4984.
--
   Resolution: Fixed
 Assignee: (was: Semen Boikov)
Fix Version/s: (was: 2.1)
   2.0

It was possible that node left could be processed twice, fixed.

> AssertionError GridNearAtomicSingleUpdateFuture.onAllReceived on node left
> --
>
> Key: IGNITE-4984
> URL: https://issues.apache.org/jira/browse/IGNITE-4984
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Priority: Critical
> Fix For: 2.0
>
>
> Observed this assertion:
> {noformat}
> [17:36:35]W:   [org.apache.ignite:ignite-core] 
> [14:36:35,825][ERROR][disco-event-worker-#15603%atomic.IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest0%][GridEventStorageManager]
>  Unexpected exception in listener notification for event: DiscoveryEvent 
> [evtNode=TcpDiscoveryNode [id=aad85fba-82f7-4e2e-9e88-002251f3, 
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=22, 
> intOrder=13, lastExchangeTime=1492094195733, loc=false, 
> ver=2.0.0#19700101-sha1:, isClient=false], topVer=23, 
> nodeId8=23f2fe27, msg=Node left: TcpDiscoveryNode 
> [id=aad85fba-82f7-4e2e-9e88-002251f3, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=22, intOrder=13, 
> lastExchangeTime=1492094195733, loc=false, ver=2.0.0#19700101-sha1:, 
> isClient=false], type=NODE_LEFT, tstamp=1492094195813]
> [17:36:35]W:   [org.apache.ignite:ignite-core] 
> java.lang.AssertionError
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onAllReceived(GridNearAtomicSingleUpdateFuture.java:336)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:176)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1311)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:892)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:340)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:307)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2277)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2474)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2306)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> java.lang.Thread.run(Thread.java:745)
> [17:36:35]W:   [org.apache.ignite:ignite-core] 
> [14:36:35,826][ERROR][disco-event-worker-#15603%atomic.IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest0%][GridDiscoveryManager]
>  Unexpected exception in discovery worker thread (ignored).
> [17:36:35]W:   [org.apache.ignite:ignite-core] 
> java.lang.AssertionError
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onAllReceived(GridNearAtomicSingleUpdateFuture.java:336)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:176)
> [17:36:35]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Assigned] (IGNITE-5061) Add ability to enable and disable rebalancing per-node

[Alexander Belyak (JIRA)]

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

Alexander Belyak reassigned IGNITE-5061:


Assignee: Alexander Belyak

> Add ability to enable and disable rebalancing per-node
> --
>
> Key: IGNITE-5061
> URL: https://issues.apache.org/jira/browse/IGNITE-5061
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexander Belyak
> Fix For: 2.1
>
>
> It would be nice to have an ability to enable and disable rebalancing per 
> node. 
> First of all, we need to come up with a simple API to allow this. 
> Corresponding methods most likely should be also added to Ignite MBean.
> We need to discuss on the dev-list whether it is enough to have this setting 
> per-node, or this needs to be done on a per-cache basis.



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

[jira] [Created] (IGNITE-5061) Add ability to enable and disable rebalancing per-node

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5061:


 Summary: Add ability to enable and disable rebalancing per-node
 Key: IGNITE-5061
 URL: https://issues.apache.org/jira/browse/IGNITE-5061
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Alexey Goncharuk
 Fix For: 2.1


It would be nice to have an ability to enable and disable rebalancing per node. 
First of all, we need to come up with a simple API to allow this. Corresponding 
methods most likely should be also added to Ignite MBean.
We need to discuss on the dev-list whether it is enough to have this setting 
per-node, or this needs to be done on a per-cache basis.



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

[jira] [Created] (IGNITE-5060) Check configuration parameters on the Integer overflowing

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5060:


 Summary: Check configuration parameters on the Integer overflowing
 Key: IGNITE-5060
 URL: https://issues.apache.org/jira/browse/IGNITE-5060
 Project: Ignite
  Issue Type: Bug
Reporter: Alexander Belyak


Time related configuration parameters using long data type (and expect value in 
ms), but standard java.net.Socket class expect integer for soDelay and usually 
long timeouts from configuration cast to ineter with simple (int) method with 
overflow if configuration timeout > Integer.MAX_VALUE.
Need to add configuration check for:
* IgniteConfiguration.failureDetectionTimeout
* IgniteConfiguration.clientFailureDetectionTimeout
* TcpDiscoverySpi.ackTimeout
* TcpDiscoverySpi.netTimeout




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

[jira] [Assigned] (IGNITE-4799) Remove TcpDiscoverySpi.heartbeatsFrequency parameter

[Alexander Belyak (JIRA)]

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

Alexander Belyak reassigned IGNITE-4799:


Assignee: Semen Boikov  (was: Alexander Belyak)

> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> 
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Semen Boikov
>  Labels: important
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the 
> heartbeats frequence. It affects the frequency of metrics messages sent over 
> the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of 
> metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics 
> messages are not participated in the failure detection process. We have to 
> clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
>  



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

[jira] [Commented] (IGNITE-4539) RocketMQ data streamer

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4539:
--

[~agoncharuk] Can we include it into 2.0 release?

> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: important
> Fix For: 2.1
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



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