[jira] [Comment Edited] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-4244 at 11/26/16 3:02 AM:


[~anovikov]
Andrey, an error message starting with ERR.
This is covered by the unit test in RedisProtocolSelfTest#testIncrDecr lines 
299-307.

Do you think this fix can be merged to the master branch? I would like to see 
it in 1.8.0 release.


was (Author: roman_s):
[~anovikov]
Andrey, an error message starting with ERR.
This is covered by the unit test in RedisProtocolSelfTest#testIncrDecr lines 
299-307.

> Redis INCR/DECR to operate on AtomicLong.
> -
>
> Key: IGNITE-4244
> URL: https://issues.apache.org/jira/browse/IGNITE-4244
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> "The INCR command parses the string value as an integer, increments it by 
> one, and finally sets the obtained value as the new value. " 
> http://redis.io/topics/data-types-intro



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4244:
--

[~anovikov]
Andrey, an error message starting with ERR.
This is covered by the unit test in RedisProtocolSelfTest#testIncrDecr lines 
299-307.

> Redis INCR/DECR to operate on AtomicLong.
> -
>
> Key: IGNITE-4244
> URL: https://issues.apache.org/jira/browse/IGNITE-4244
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> "The INCR command parses the string value as an integer, increments it by 
> one, and finally sets the obtained value as the new value. " 
> http://redis.io/topics/data-types-intro



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4282) Javadoc broken

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4282:


Github user asfgit closed the pull request at:

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


> Javadoc broken 
> ---
>
> Key: IGNITE-4282
> URL: https://issues.apache.org/jira/browse/IGNITE-4282
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.8
>Reporter: Ilya Suntsov
>Assignee: Roman Shtykh
> Fix For: 1.8
>
> Attachments: javadoc
>
>
> Broken javadoc here:
> {noformat}incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/rest/handlers/redis/server/GridRedisDbSizeCommandHandler.java{noformat}
> Warning text:
> {noformat}Tag @inheritDoc cannot be used in constructor documentation.  It 
> can only be used in the following types of documentation: method, inline 
> text.{noformat}
> Log you can find in attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4243) Add examples of using Redis

[Roman Shtykh (JIRA)]

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

Roman Shtykh closed IGNITE-4243.


Merged to the master branch.

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-4303.
-

fixed

> CacheClientBinaryQueryExample returns wrong result
> --
>
> Key: IGNITE-4303
> URL: https://issues.apache.org/jira/browse/IGNITE-4303
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
> employees must be not empty.
> {noformat}
> >>> Employees working for GridGain:
> >>> Employee names and their salaries:
> >>> [Name=Allison Mathis, salary=25300]
> >>> [Name=Breana Robbin, salary=6500]
> >>> [Name=Philip Horsley, salary=19800]
> >>> [Name=Brian Peters, salary=10600]
> >>> [Name=James Wilson, salary=12500]
> >>> [Name=Daniel Adams, salary=11000]
> >>> [Name=Cristian Moss, salary=12500]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-4304.
-

fixed

> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following exception after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, order=1480016808989, nodeOrder=1]], 
> super=GridCacheMessage [msgId=-1, depInfo=null, err=null, skipPrepare=false, 
> cacheId=0, cacheId=0]]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov reassigned IGNITE-4304:
-

Assignee: Sergey Kozlov  (was: Vladimir Ozerov)

> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following exception after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, order=1480016808989, nodeOrder=1]], 
> super=GridCacheMessage [msgId=-1, depInfo=null, err=null, skipPrepare=false, 
> cacheId=0, cacheId=0]]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3169) .NET: Provide error messages for incorrect Apache.Ignite.exe command line arguments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3169:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-3169 .NET: Provide error messages for incorrect Apache.Ignite.exe 
command line arguments



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

$ git pull https://github.com/ptupitsyn/ignite ignite-3169

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

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


commit 06c21e5c93c7f2b02c5e681bfe02feac854a27d7
Author: Pavel Tupitsyn 
Date:   2016-11-25T12:02:32Z

Add failure on unknown argument

commit cbcc6dd219df309f798fa9cd6ea56c035610af57
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:11:54Z

Add empty args validation

commit d99ebe4493b1e180f783a6290b272574392cc21a
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:30:14Z

wip tests

commit b1c65cc4a4aa117604c12295099dc6eb4a12bd67
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:52:27Z

wip tests

commit d7dc96c6718091a6f223e4fdf9464a29d877792d
Author: Pavel Tupitsyn 
Date:   2016-11-25T14:55:05Z

tests

commit b804326ede37e7421275eed1a4c7bf972a83cce2
Author: Pavel Tupitsyn 
Date:   2016-11-25T15:02:03Z

wip

commit 62460472b4860a81c35ad943020881168dd3c69d
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:36:44Z

wip test

commit 9fd8166b5e3cb1d2ff6c9e890de299731aa0c2c7
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:45:35Z

more tests

commit b1d453ea870d030e32f21fabff5de98c285a341c
Author: Pavel Tupitsyn 
Date:   2016-11-25T16:55:30Z

wip

commit dc760dce03fb19ec2145a30f5bcd63a971b0419f
Author: Pavel Tupitsyn 
Date:   2016-11-25T17:00:32Z

Tests done




> .NET: Provide error messages for incorrect Apache.Ignite.exe command line 
> arguments
> ---
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.9
>
>
> Make sure invalid argument names and values are not ignored/swallowed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (IGNITE-4243) Add examples of using Redis

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov updated IGNITE-4243:
-
Comment: was deleted

(was: Ok, thanks!)

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4243) Add examples of using Redis

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-4243:
--

Ok, thanks!

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4243) Add examples of using Redis

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-4243:
--

Ok, thanks!

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4263) Hadoop: abstract out offheap/heap memory management.

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4263 at 11/25/16 4:18 PM:


I'll create the interface {{MemoryManager}} that provide all necessary 
operation with the memory.
The off heap implementation is based on {{GridUnsafeMemory}} and heap the dummy 
implementation is based on the list of pages that contains {{byte[]}}.
The more efficient implementation of the on-heap memory manager may be 
implemented later.


was (Author: tledkov-gridgain):
I'll create the interface {{MemoryManager}} that provide all necessary 
operation with the memory.
The off heap implementation is based on {{GridUnsafeMemory}} and heap the dummy 
implementation is based on the pages that contains {{byte[]}}.
The more efficient implementation of the on-heap memory manager may be 
implemented later.

> Hadoop: abstract out offheap/heap memory management.
> 
>
> Key: IGNITE-4263
> URL: https://issues.apache.org/jira/browse/IGNITE-4263
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4263) Hadoop: abstract out offheap/heap memory management.

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4263:
--

I'll create the interface {{MemoryManager}} that provide all necessary 
operation with the memory.
The off heap implementation is based on {{GridUnsafeMemory}} and heap the dummy 
implementation is based on the pages that contains {{byte[]}}.
The more efficient implementation of the on-heap memory manager may be 
implemented later.

> Hadoop: abstract out offheap/heap memory management.
> 
>
> Key: IGNITE-4263
> URL: https://issues.apache.org/jira/browse/IGNITE-4263
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4308) Make QueryEntity.keyFields optional for caches having SQL types as keys

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4308:

Fix Version/s: 1.8

> Make QueryEntity.keyFields optional for caches having SQL types as keys
> ---
>
> Key: IGNITE-4308
> URL: https://issues.apache.org/jira/browse/IGNITE-4308
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> Initial implementation of DML requires the user to specify keyFields in 
> configuration explicitly, even if it's empty, in cases when DML is used and 
> binary marshaller is used. As [~vozerov] noted, it could affect usability, if 
> even a little, so this should be fixed - when a primitive/simple SQL type is 
> used as a key, it's obvious that there's no key fields and hence it's not 
> necessary to specify empty keyFields in this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4287:

Assignee: Sergey Kozlov  (was: Sergi Vladykin)

> DML: DELETE statement failed: Invalid number of query parameters. Cannot find 
> 2 parameter.
> --
>
> Key: IGNITE-4287
> URL: https://issues.apache.org/jira/browse/IGNITE-4287
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> {code:title=test.java|borderStyle=solid}
>   IgniteCache orgCache = 
> Ignition.ignite().cache(ORG_CACHE);
> orgCache.clear();
> for (int z=100; z < 10; z++) {
> orgCache.query(new SqlFieldsQuery("insert into Organization 
> (_key, name) values (?, ?)").setArgs(z, "Org " + Integer.toString(z)));
> }
> for (int z=100; z < 10; z++) {
> if (z > 0 && z % 10 == 0)
> System.out.println("Delete " + z);
> orgCache.query(new SqlFieldsQuery("delete from Organization where 
> _key >= ?").setArgs(z));
> }
> {code}
> The code above failed with IgniteException
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid number of query parameters. Cannot 
> find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:336)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:110)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:818)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid number of 
> query parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1789)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   ... 8 more
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:634)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:604)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:403)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:184)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1277)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:813)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:811)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> 

[jira] [Commented] (IGNITE-4243) Add examples of using Redis

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4243:
--

I will tomorrow after removing the version from the link.

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4243) Add examples of using Redis

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-4243:
--

[~roman_s]
Did you merge this PR master?

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4314) Cache.clear should not destroy offheap map

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4314:


 Summary: Cache.clear should not destroy offheap map
 Key: IGNITE-4314
 URL: https://issues.apache.org/jira/browse/IGNITE-4314
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Semen Boikov
 Fix For: 1.9


Currently when offheap is enabled then cache.clear() operations fully destroys 
offheap map (GridCacheClearAllRunnable calls 
GridCacheSwapManager.clearOffHeap). This is not correct since there can be 
entry referenceing cleared memory, it seems offheap should be cleared in the 
same way as swap using offheap keys iterator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4308) Make QueryEntity.keyFields optional for caches having SQL types as keys

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4308:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type



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

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

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

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


commit 8a522ec9457363b107fe4a6df0742e5c629689ca
Author: Alexander Paschenko 
Date:   2016-11-25T13:33:46Z

IGNITE-4308 Ignore QueryEntity.keyFields when key is an SQL type




> Make QueryEntity.keyFields optional for caches having SQL types as keys
> ---
>
> Key: IGNITE-4308
> URL: https://issues.apache.org/jira/browse/IGNITE-4308
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>
> Initial implementation of DML requires the user to specify keyFields in 
> configuration explicitly, even if it's empty, in cases when DML is used and 
> binary marshaller is used. As [~vozerov] noted, it could affect usability, if 
> even a little, so this should be fixed - when a primitive/simple SQL type is 
> used as a key, it's obvious that there's no key fields and hence it's not 
> necessary to specify empty keyFields in this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4311:


Fixed in ignite-1.8

> .NET: MultiTieredCacheExample has some issues 
> --
>
> Key: IGNITE-4311
> URL: https://issues.apache.org/jira/browse/IGNITE-4311
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
> Fix For: 1.8
>
>
> Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
> 1) Typo
> {noformat}
> Console.WriteLine(">>> Lifecycle example started.");
> {noformat}
> 2) 
> {noformat}
> OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
> {noformat}
> This size is not enough to store 10 entries, overhead is not taked into 
> account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
> minimum required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4311.

   Resolution: Fixed
 Assignee: (was: Pavel Tupitsyn)
Fix Version/s: 1.8

> .NET: MultiTieredCacheExample has some issues 
> --
>
> Key: IGNITE-4311
> URL: https://issues.apache.org/jira/browse/IGNITE-4311
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
> Fix For: 1.8
>
>
> Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
> 1) Typo
> {noformat}
> Console.WriteLine(">>> Lifecycle example started.");
> {noformat}
> 2) 
> {noformat}
> OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
> {noformat}
> This size is not enough to store 10 entries, overhead is not taked into 
> account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
> minimum required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4243) Add examples of using Redis

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-4243:


Looks good for me, but please remove version from link to documentation: 
https://dash.readme.io/project/apacheignite/v1.8/docs/redis and merge PR to 
master.

> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
> similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4313:
--
Attachment: IGNITE-4313.zip

> DML: update causes IgniteCheckedException: Not enough data to read the value
> 
>
> Key: IGNITE-4313
> URL: https://issues.apache.org/jira/browse/IGNITE-4313
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
> Attachments: IGNITE-4313.zip
>
>
> 0. Extract teh attachment in {{examples}} directory.
> 1. Start node {{ExtSqlExampleNodeStartup}}
> 2. Run {{ExtSqlExample}}. It failed:
> {noformat}
> Processing the caches...
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:652)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:483)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   at 
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: 104496cc-dd94-4150-90de-8628c2ddf6ff, class 
> org.apache.ignite.IgniteCheckedException:Failed to execute SQL query.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:278)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:268)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:249)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:197)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1915)
>   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)
> [16:10:49] Ignite node stopped OK [uptime=00:00:00:372]
> Process finished with exit code 1
> {noformat}
> Exception on the node:
> {noformat}
> [16:10:49,679][ERROR][sys-#75%null%][GridMapQueryExecutor] Failed to execute 
> local 

[jira] [Created] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4313:
-

 Summary: DML: update causes IgniteCheckedException: Not enough 
data to read the value
 Key: IGNITE-4313
 URL: https://issues.apache.org/jira/browse/IGNITE-4313
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


0. Extract teh attachment in {{examples}} directory.
1. Start node {{ExtSqlExampleNodeStartup}}
2. Run {{ExtSqlExample}}. It failed:
{noformat}
Processing the caches...
Exception in thread "main" javax.cache.CacheException: Failed to run map query 
remotely.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:652)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:483)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
104496cc-dd94-4150-90de-8628c2ddf6ff, class 
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:278)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:268)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:249)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:197)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1915)
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)
[16:10:49] Ignite node stopped OK [uptime=00:00:00:372]

Process finished with exit code 1
{noformat}

Exception on the node:
{noformat}
[16:10:49,679][ERROR][sys-#75%null%][GridMapQueryExecutor] Failed to execute 
local query.
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:958)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1010)
at 

[jira] [Assigned] (IGNITE-4312) DML: update causes IgniteCheckedException: Invalid flag value: -2

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4312:
---

Assignee: Alexander Paschenko

> DML: update causes IgniteCheckedException: Invalid flag value: -2
> -
>
> Key: IGNITE-4312
> URL: https://issues.apache.org/jira/browse/IGNITE-4312
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
> Attachments: IGNITE-4312.zip
>
>
> {noformat}
> [15:58:04] Ignite node stopped OK [uptime=00:00:00:111]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:817)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid flag 
> value: -2
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1788)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
>   ... 7 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Invalid flag 
> value: -2
>   at 
> org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:285)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:186)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:524)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
>   ... 8 more
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4312) DML: update causes IgniteCheckedException: Invalid flag value: -2

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4312:
--
Attachment: IGNITE-4312.zip

> DML: update causes IgniteCheckedException: Invalid flag value: -2
> -
>
> Key: IGNITE-4312
> URL: https://issues.apache.org/jira/browse/IGNITE-4312
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
> Attachments: IGNITE-4312.zip
>
>
> {noformat}
> [15:58:04] Ignite node stopped OK [uptime=00:00:00:111]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:817)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid flag 
> value: -2
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1788)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
>   ... 7 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Invalid flag 
> value: -2
>   at 
> org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:285)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:186)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:524)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
>   ... 8 more
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova closed IGNITE-4299.
---

verified

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4312) DML: update causes IgniteCheckedException: Invalid flag value: -2

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4312:
-

 Summary: DML: update causes IgniteCheckedException: Invalid flag 
value: -2
 Key: IGNITE-4312
 URL: https://issues.apache.org/jira/browse/IGNITE-4312
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


{noformat}
[15:58:04] Ignite node stopped OK [uptime=00:00:00:111]
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Invalid flag value: -2
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteException: Invalid flag value: -2
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:817)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
... 6 more
Caused by: class org.apache.ignite.IgniteCheckedException: Invalid flag value: 
-2
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1788)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
... 7 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Invalid flag 
value: -2
at 
org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:285)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:186)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doUpdate(DmlStatementsProcessor.java:524)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:256)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1765)
... 8 more

Process finished with exit code 1
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4311:


2) I suggest to modify comment: "Limit off-heap to *(roughly)* 10 entries" 
since we can't know the overhead for sure

> .NET: MultiTieredCacheExample has some issues 
> --
>
> Key: IGNITE-4311
> URL: https://issues.apache.org/jira/browse/IGNITE-4311
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
>
> Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
> 1) Typo
> {noformat}
> Console.WriteLine(">>> Lifecycle example started.");
> {noformat}
> 2) 
> {noformat}
> OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
> {noformat}
> This size is not enough to store 10 entries, overhead is not taked into 
> account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
> minimum required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4311:
--

Assignee: Pavel Tupitsyn

> .NET: MultiTieredCacheExample has some issues 
> --
>
> Key: IGNITE-4311
> URL: https://issues.apache.org/jira/browse/IGNITE-4311
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
>
> Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
> 1) Typo
> {noformat}
> Console.WriteLine(">>> Lifecycle example started.");
> {noformat}
> 2) 
> {noformat}
> OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
> {noformat}
> This size is not enough to store 10 entries, overhead is not taked into 
> account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
> minimum required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4309) IgniteLockExample hangs in multi-node mode.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4309:

Fix Version/s: (was: 1.8)
   2.0

> IgniteLockExample hangs in multi-node mode.
> ---
>
> Key: IGNITE-4309
> URL: https://issues.apache.org/jira/browse/IGNITE-4309
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>
> Steps to reproduce:
> 1) Start CacheExamplesMultiNodeSelfTest.testCacheLockExample.
> 2) Observe that example hangs and the following metrics printout appears form 
> time to time:
> {code}
> ^-- Public thread pool [active=2, idle=0, qSize=0]
> {code}
> or
> {code}
> ^-- Public thread pool [active=3, idle=0, qSize=0]
> {code}
> Logs with thread dumps on TC: 
> http://195.239.208.174/viewLog.html?buildId=368311=IgniteTests_IgniteExamples=buildLog#_focus=24510



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4017) DML: Add Java Example

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4017:

Assignee: Alexander Paschenko  (was: Vladimir Ozerov)

> DML: Add Java Example
> -
>
> Key: IGNITE-4017
> URL: https://issues.apache.org/jira/browse/IGNITE-4017
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> In Apache Ignite 1.8 the community is planning to release DML support.
> To adopt DML usage we need to improve existed or add additional examples.
> We need to add {{CacheDmlExample}} doing the following with DML's *GridGain 
> Java API*:
> - fill up a cache using INSERT commands.
> - execute SELECT statements. There are should be queries with joins.
> - perform cache update using UPDATE and MERGE statements.
> - execute SELECT statements. There are should be queries with joins.
> - remove a part of the data from cache using DELETE command.
> execute SELECTs again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-4311:

Description: 
Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:

1) Typo
{noformat}
Console.WriteLine(">>> Lifecycle example started.");
{noformat}

2) 
{noformat}
OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
{noformat}
This size is not enough to store 10 entries, overhead is not taked into 
account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
minimum required.


  was:
Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:

1) Typo
{noformat}
Console.WriteLine(">>> Lifecycle example started.");
{noformat}

2) 
{noformat}
OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
{noformat}
This size is not enough to store 10 entries, overhead is not taked into 
account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
minimum.



> .NET: MultiTieredCacheExample has some issues 
> --
>
> Key: IGNITE-4311
> URL: https://issues.apache.org/jira/browse/IGNITE-4311
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>
> Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:
> 1) Typo
> {noformat}
> Console.WriteLine(">>> Lifecycle example started.");
> {noformat}
> 2) 
> {noformat}
> OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
> {noformat}
> This size is not enough to store 10 entries, overhead is not taked into 
> account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
> minimum required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4311) .NET: MultiTieredCacheExample has some issues

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4311:
---

 Summary: .NET: MultiTieredCacheExample has some issues 
 Key: IGNITE-4311
 URL: https://issues.apache.org/jira/browse/IGNITE-4311
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova


Apache.Ignite.Examples.Datagrid.MultiTieredCacheExample has some issues:

1) Typo
{noformat}
Console.WriteLine(">>> Lifecycle example started.");
{noformat}

2) 
{noformat}
OffHeapMaxMemory = EntrySize * 10, // Limit off-heap to 10 entries.
{noformat}
This size is not enough to store 10 entries, overhead is not taked into 
account. In my case some experiments showed that  (EntrySize * 10) + 810 is 
minimum.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4309) IgniteLockExample hangs in multi-node mode.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4309:
---

Assignee: Vladimir Ozerov  (was: Semen Boikov)

> IgniteLockExample hangs in multi-node mode.
> ---
>
> Key: IGNITE-4309
> URL: https://issues.apache.org/jira/browse/IGNITE-4309
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1) Start CacheExamplesMultiNodeSelfTest.testCacheLockExample.
> 2) Observe that example hangs and the following metrics printout appears form 
> time to time:
> {code}
> ^-- Public thread pool [active=2, idle=0, qSize=0]
> {code}
> or
> {code}
> ^-- Public thread pool [active=3, idle=0, qSize=0]
> {code}
> Logs with thread dumps on TC: 
> http://195.239.208.174/viewLog.html?buildId=368311=IgniteTests_IgniteExamples=buildLog#_focus=24510



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4310) Add release notes for Ignite 1.8.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4310:
---

 Summary: Add release notes for Ignite 1.8.
 Key: IGNITE-4310
 URL: https://issues.apache.org/jira/browse/IGNITE-4310
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 1.8






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4200) ODBC: Integrate generation of the ODBC installer to build process.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4200:


GitHub user isapego opened a pull request:

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

IGNITE-4200: Added copying of the C++ binaries.



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

$ git pull https://github.com/isapego/ignite ignite-4200

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

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


commit 5858f746a5aec9dd697199c2b7a0961d839119f8
Author: Igor Sapego 
Date:   2016-11-25T11:32:22Z

IGNITE-4200: Added copying of the C++ binaries.




> ODBC: Integrate generation of the ODBC installer to build process.
> --
>
> Key: IGNITE-4200
> URL: https://issues.apache.org/jira/browse/IGNITE-4200
> Project: Ignite
>  Issue Type: Task
>  Components: build, odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> We are going to have ability to generate ODBC driver soon. We should add 
> generation of such an installer as a build step.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4309) IgniteLockExample hangs in multi-node mode.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4309:
---

 Summary: IgniteLockExample hangs in multi-node mode.
 Key: IGNITE-4309
 URL: https://issues.apache.org/jira/browse/IGNITE-4309
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 1.8


Steps to reproduce:
1) Start CacheExamplesMultiNodeSelfTest.testCacheLockExample.
2) Observe that example hangs and the following metrics printout appears form 
time to time:
{code}
^-- Public thread pool [active=2, idle=0, qSize=0]
{code}
or
{code}
^-- Public thread pool [active=3, idle=0, qSize=0]
{code}

Logs with thread dumps on TC: 
http://195.239.208.174/viewLog.html?buildId=368311=IgniteTests_IgniteExamples=buildLog#_focus=24510



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4279.
-
Resolution: Fixed

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4308) Make QueryEntity.keyFields optional for caches having SQL types as keys

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4308:
---

 Summary: Make QueryEntity.keyFields optional for caches having SQL 
types as keys
 Key: IGNITE-4308
 URL: https://issues.apache.org/jira/browse/IGNITE-4308
 Project: Ignite
  Issue Type: Improvement
  Components: SQL
Affects Versions: 1.8
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko


Initial implementation of DML requires the user to specify keyFields in 
configuration explicitly, even if it's empty, in cases when DML is used and 
binary marshaller is used. As [~vozerov] noted, it could affect usability, if 
even a little, so this should be fixed - when a primitive/simple SQL type is 
used as a key, it's obvious that there's no key fields and hence it's not 
necessary to specify empty keyFields in this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4304.
-
Resolution: Fixed

Fixed.

> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> The server node prints out the following exception after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, order=1480016808989, nodeOrder=1]], 
> super=GridCacheMessage [msgId=-1, depInfo=null, err=null, skipPrepare=false, 
> cacheId=0, cacheId=0]]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4279:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4279 Fix for testFetchSize in JdbcResultSetSelfTest



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

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

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

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


commit c8936fbe4708f6901c49f0aa69f0932843b67c76
Author: Alexander Paschenko 
Date:   2016-11-25T11:04:37Z

IGNITE-4279 Fix for testFetchSize in JdbcResultSetSelfTest




> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-4244:


Hi [~roman_s],

In incr/decr command we can receive Long overflow, which behavior is expected 
from Redis?

{code}
jedis.set("outOfRange", "" + Long.MAX_VALUE);

Long res = jedis.incr("outOfRange");

assertFalse(res == Long.MIN_VALUE);
{code}

> Redis INCR/DECR to operate on AtomicLong.
> -
>
> Key: IGNITE-4244
> URL: https://issues.apache.org/jira/browse/IGNITE-4244
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> "The INCR command parses the string value as an integer, increments it by 
> one, and finally sets the obtained value as the new value. " 
> http://redis.io/topics/data-types-intro



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4279:
-

Fixed everything except of JdbcResultSetSelfTest.testFetchSize. Pushed to 
{{ignite-1.8}} branch,

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4305) GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal invoke arguments properly.

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov reassigned IGNITE-4305:
-

Assignee: Konstantin Dudkov  (was: Semen Boikov)

> GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal invoke arguments 
> properly.
> ---
>
> Key: IGNITE-4305
> URL: https://issues.apache.org/jira/browse/IGNITE-4305
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1) Set binary marshaller as deafult for 
> {{GridCacheBinaryAtomicEntryProcessorDeploymentSelfTest}}:
> {code}
> static {
> GridTestProperties.setProperty(GridTestProperties.MARSH_CLASS_NAME, 
> BinaryMarshaller.class.getName());
> GridTestProperties.setProperty(GridTestProperties.ENTRY_PROCESSOR_CLASS_NAME,
> 
> "org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor");
> }
> {code}
> 2) Run the test, observe failures in {{testInvokeDeployment*}} tests.
> 3) Go to {{GridNearAtomicSingleUpdateFuture.mapSingleUpdate}} and force 
> single transform to use old {{GridNearAtomicFullUpdateRequest}}
> 4) Re-run test. No all pass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1443) CPP: Implement cache continuous queries.

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-1443 at 11/25/16 10:46 AM:


Vladimir,

Here is my approach:

I've added special class {{ignite::Reference}} which can hold any kind of user 
reference. It can be used like that:
{code}
// Function that takes ignite::Reference as an argument.
void foo(ignite::Reference ref);

...
// User passes reference of their object like that:
SomeType obj1;

// Passing simple reference.
foo(ignite::PassReference(obj1);

// Passing object copy.
foo(ignite::PassCopy(obj1);

SomeType* obj2 = new SomeType;

// Passing ownership to the function. That means, object will be deleted,
// once Ignite does not need it anymore. User should not use pointer after
// they have passed it to Ignite.
foo(ignite::PassOwnership(obj2);

std::shared_ptr obj3 = std::make_shared();

// Passing smart pointer. In this case, Reference class behaves like 
// smart pointer of the type, user passes to it.
foo(ignite::PassSmartPointer(obj3);
{code}

You can take a closer look at the code on linked Upsource page. There are also 
tests with all kind of scenarios in file {{reference_test.cpp}}.
Please, review and let me know what you think. Thanks.


was (Author: isapego):
Vladimir,

Here is my approach:

I've added special class {{ignite::Reference}} which can hold any kind of user 
reference. It can be used like that:
{code}
// Function that takes ignite::Reference as an argument.
void foo(ignite::Reference ref);

...
// User passes reference of their object like that:
SomeType obj1;

// Passing simple reference.
foo(ignite::PassReference(obj1);

// Passing object copy.
foo(ignite::PassCopy(obj1);

SomeType* obj2 = new SomeType;

// Passing ownership to the function. That means, object will be deleted,
// once Ignite does not need it anymore. User should not use pointer after
// they have passed it to Ignite.
foo(ignite::PassOwnership(obj2);

std::shared_ptr obj3 = std::make_shared();

// Passing smart pointer. In this case, Reference class behaves like 
// smart pointer of the type, user passes to it.
foo(ignite::PassSmartPointer(obj3);
{code}

You can take a closer look at the code on linked Upsource page. There are also 
tests with all kind of scenarios in file {{reference_test.cpp}}.
Please, review and tell me what do you think. Thanks.

> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4303.
-
Resolution: Fixed

Not reproducible after recent DML fixes.

> CacheClientBinaryQueryExample returns wrong result
> --
>
> Key: IGNITE-4303
> URL: https://issues.apache.org/jira/browse/IGNITE-4303
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
> employees must be not empty.
> {noformat}
> >>> Employees working for GridGain:
> >>> Employee names and their salaries:
> >>> [Name=Allison Mathis, salary=25300]
> >>> [Name=Breana Robbin, salary=6500]
> >>> [Name=Philip Horsley, salary=19800]
> >>> [Name=Brian Peters, salary=10600]
> >>> [Name=James Wilson, salary=12500]
> >>> [Name=Daniel Adams, salary=11000]
> >>> [Name=Cristian Moss, salary=12500]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3169) .NET: Provide error messages for incorrect Apache.Ignite.exe command line arguments

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3169:
---
Description: Make sure invalid argument names and values are not 
ignored/swallowed  (was: Make sure we do not ignore failed assembly load in 
Apache.Ignite.exe)

> .NET: Provide error messages for incorrect Apache.Ignite.exe command line 
> arguments
> ---
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.9
>
>
> Make sure invalid argument names and values are not ignored/swallowed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3169) .NET: Provide error messages for incorrect Apache.Ignite.exe command line arguments

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3169:
---
Summary: .NET: Provide error messages for incorrect Apache.Ignite.exe 
command line arguments  (was: .NET: Provide better error messages when user 
assembly loading has failed)

> .NET: Provide error messages for incorrect Apache.Ignite.exe command line 
> arguments
> ---
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.9
>
>
> Make sure we do not ignore failed assembly load in Apache.Ignite.exe



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4306) .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4306:
---
Fix Version/s: (was: 1.8)
   1.9

> .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently
> ---
>
> Key: IGNITE-4306
> URL: https://issues.apache.org/jira/browse/IGNITE-4306
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.9
>
>
> Looks like standalone node fails to join



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4306) .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails sporadically

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4306:
---
Summary: .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails 
sporadically  (was: .NET: TestRemoteNodesClientMode(AtomicSequenceExample) 
fails intermittently)

> .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails sporadically
> -
>
> Key: IGNITE-4306
> URL: https://issues.apache.org/jira/browse/IGNITE-4306
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.9
>
>
> Looks like standalone node fails to join



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4307) .NET: AtomicSequenceExample uses AtomicConfiguration incorrectly

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4307:
--

 Summary: .NET: AtomicSequenceExample uses AtomicConfiguration 
incorrectly
 Key: IGNITE-4307
 URL: https://issues.apache.org/jira/browse/IGNITE-4307
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.9


AtomicConfiguration is specified only on local node. Standalone nodes use 
default configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4303:

Assignee: Sergey Kozlov

> CacheClientBinaryQueryExample returns wrong result
> --
>
> Key: IGNITE-4303
> URL: https://issues.apache.org/jira/browse/IGNITE-4303
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
> employees must be not empty.
> {noformat}
> >>> Employees working for GridGain:
> >>> Employee names and their salaries:
> >>> [Name=Allison Mathis, salary=25300]
> >>> [Name=Breana Robbin, salary=6500]
> >>> [Name=Philip Horsley, salary=19800]
> >>> [Name=Brian Peters, salary=10600]
> >>> [Name=James Wilson, salary=12500]
> >>> [Name=Daniel Adams, salary=11000]
> >>> [Name=Cristian Moss, salary=12500]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4304:

Assignee: Vladimir Ozerov

> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> The server node prints out the following exception after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, order=1480016808989, nodeOrder=1]], 
> super=GridCacheMessage [msgId=-1, depInfo=null, err=null, skipPrepare=false, 
> cacheId=0, cacheId=0]]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4306) .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4306:


Added more info to the assert, waiting for new runs

> .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently
> ---
>
> Key: IGNITE-4306
> URL: https://issues.apache.org/jira/browse/IGNITE-4306
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Looks like standalone node fails to join



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4306) .NET: TestRemoteNodesClientMode(AtomicSequenceExample) fails intermittently

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4306:
--

 Summary: .NET: TestRemoteNodesClientMode(AtomicSequenceExample) 
fails intermittently
 Key: IGNITE-4306
 URL: https://issues.apache.org/jira/browse/IGNITE-4306
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


Looks like standalone node fails to join



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4287:

Comment: was deleted

(was: Will that fix work with OptimizedMarshaller?)

> DML: DELETE statement failed: Invalid number of query parameters. Cannot find 
> 2 parameter.
> --
>
> Key: IGNITE-4287
> URL: https://issues.apache.org/jira/browse/IGNITE-4287
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergi Vladykin
> Fix For: 1.8
>
>
> {code:title=test.java|borderStyle=solid}
>   IgniteCache orgCache = 
> Ignition.ignite().cache(ORG_CACHE);
> orgCache.clear();
> for (int z=100; z < 10; z++) {
> orgCache.query(new SqlFieldsQuery("insert into Organization 
> (_key, name) values (?, ?)").setArgs(z, "Org " + Integer.toString(z)));
> }
> for (int z=100; z < 10; z++) {
> if (z > 0 && z % 10 == 0)
> System.out.println("Delete " + z);
> orgCache.query(new SqlFieldsQuery("delete from Organization where 
> _key >= ?").setArgs(z));
> }
> {code}
> The code above failed with IgniteException
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid number of query parameters. Cannot 
> find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:336)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:110)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:818)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid number of 
> query parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1789)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   ... 8 more
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:634)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:604)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:403)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:184)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1277)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:813)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:811)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> 

[jira] [Updated] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4279:

Component/s: SQL
 jdbc-driver

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4279:

Assignee: Alexander Paschenko  (was: Vladimir Ozerov)

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4279:
---

Assignee: Vladimir Ozerov  (was: Alexander Paschenko)

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4279:

Affects Version/s: 1.8

> Make DML related JDBC driver tests pass within suite
> 
>
> Key: IGNITE-4279
> URL: https://issues.apache.org/jira/browse/IGNITE-4279
> Project: Ignite
>  Issue Type: Test
>  Components: jdbc-driver, SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4017) DML: Add Java Example

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4017:

Assignee: Vladimir Ozerov  (was: Alexander Paschenko)

> DML: Add Java Example
> -
>
> Key: IGNITE-4017
> URL: https://issues.apache.org/jira/browse/IGNITE-4017
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> In Apache Ignite 1.8 the community is planning to release DML support.
> To adopt DML usage we need to improve existed or add additional examples.
> We need to add {{CacheDmlExample}} doing the following with DML's *GridGain 
> Java API*:
> - fill up a cache using INSERT commands.
> - execute SELECT statements. There are should be queries with joins.
> - perform cache update using UPDATE and MERGE statements.
> - execute SELECT statements. There are should be queries with joins.
> - remove a part of the data from cache using DELETE command.
> execute SELECTs again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4305) GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal invoke arguments properly.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4305:
---

 Summary: GridNearAtomicSingleUpdateInvokeRequest cannot unmarshal 
invoke arguments properly.
 Key: IGNITE-4305
 URL: https://issues.apache.org/jira/browse/IGNITE-4305
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 1.8


Steps to reproduce:
1) Set binary marshaller as deafult for 
{{GridCacheBinaryAtomicEntryProcessorDeploymentSelfTest}}:
{code}
static {
GridTestProperties.setProperty(GridTestProperties.MARSH_CLASS_NAME, 
BinaryMarshaller.class.getName());
GridTestProperties.setProperty(GridTestProperties.ENTRY_PROCESSOR_CLASS_NAME,
"org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor");
}
{code}

2) Run the test, observe failures in {{testInvokeDeployment*}} tests.

3) Go to {{GridNearAtomicSingleUpdateFuture.mapSingleUpdate}} and force single 
transform to use old {{GridNearAtomicFullUpdateRequest}}

4) Re-run test. No all pass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4295) GridUnsafe: implement specialized methods for every kind of copy operation.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4295:


GitHub user devozerov opened a pull request:

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

IGNITE-4295



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 7a47a0185d308cd3a58c7bfcb4d1cd548bff5b87
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit b73fa8c4e9f52e96bd806e1cdbec1bed3623a54f
Author: devozerov 
Date:   2016-11-24T08:53:29Z

IGNITE-4295: Replaced "unsafe" byte[]->byte[] copying with System.arrayCopy.

commit 29a3a4fa12ed7642ec750f339ed36279323931b7
Author: devozerov 
Date:   2016-11-24T09:35:00Z

offheap->heap routine.

commit 3af04bd1326aa08796b9876795c227be25089d9b
Author: devozerov 
Date:   2016-11-24T09:38:52Z

heap->offheap routine.

commit 3539b448aa81dbdd541a5c168826b1806bdfded6
Author: devozerov 
Date:   2016-11-24T10:05:19Z

Added threshold.

commit bdbf64d55d76c91ed214bb34625dad4a10a3453d
Author: devozerov 
Date:   2016-11-24T10:26:22Z

Fix to default value.




> GridUnsafe: implement specialized methods for every kind of copy operation.
> ---
>
> Key: IGNITE-4295
> URL: https://issues.apache.org/jira/browse/IGNITE-4295
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
>  Labels: performance
> Fix For: 2.0
>
>
> 1) copy(OFFHEAP, HEAP)
> 2) copy(HEAP, OFFHEAP)
> 3) copy(OFFHEAP, OFFHEAP)
> 4) copy(HEAP, HEAP) 
> 5) copy(T[], T[]) must be avoided and replaced with System.arrayCopy().
> 6) Add optional threshold. If we copy too small memory chunk which size is 
> below the threshold, then resort to byte-by-byte copying, as it will be 
> faster.
> E.g. on PowerPC with OpenJDK 8, copying of <100 bytes of data is faster on 
> byte-by-byte basis.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)