[jira] [Comment Edited] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.
[
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/27/16 5:01 AM:
[~anovikov]
The behavior for starting with Long.MAX_VALUE will have to produce "ERR
increment or decrement would overflow". But if you set larger than that, "ERR
value is not an integer or out of range."(https://redis.io/commands/incr) In
terms of jedis, it's both {{JedisDataException}}.
I fixed that, thank you!
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]
The behavior for starting with Long.MAX_VALUE will have to produce "ERR
increment or decrement would overflow". But if you set larger than that, "ERR
value is not an integer or out of range."(https://redis.io/commands/incr) I
fixed that, thank you!
Do you think this fix can be merged to the master branch? I would like to see
it in 1.8.0 release.
> 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
>Affects Versions: 1.8
>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] [Comment Edited] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.
[
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/27/16 4:49 AM:
[~anovikov]
The behavior for starting with Long.MAX_VALUE will have to produce "ERR
increment or decrement would overflow". But if you set larger than that, "ERR
value is not an integer or out of range."(https://redis.io/commands/incr) I
fixed that, thank you!
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 (which is {{JedisDataException}} for
jedis
https://github.com/xetorthio/jedis/blob/master/src/test/java/redis/clients/jedis/tests/commands/StringValuesCommandsTest.java#L195).
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.
> 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
>Affects Versions: 1.8
>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] [Comment Edited] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.
[
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/27/16 4:00 AM:
[~anovikov]
Andrey, an error message starting with ERR (which is {{JedisDataException}} for
jedis
https://github.com/xetorthio/jedis/blob/master/src/test/java/redis/clients/jedis/tests/commands/StringValuesCommandsTest.java#L195).
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 (which is {{JedisDataException}} for
jedis).
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.
> 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
>Affects Versions: 1.8
>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-4017) DML: Add Java Example
[
https://issues.apache.org/jira/browse/IGNITE-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698995#comment-15698995
]
Denis Magda commented on IGNITE-4017:
-
[~al.psc], have we already added the example into 1.8 release?
> 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] [Commented] (IGNITE-4288) ODBC: Fix ODBC and DML interoperability.
[ https://issues.apache.org/jira/browse/IGNITE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698991#comment-15698991 ] Denis Magda commented on IGNITE-4288: - [~isapego], please make sure to commit all DML+ODBC related changed into 1.8 branch before the voting starts. > ODBC: Fix ODBC and DML interoperability. > > > Key: IGNITE-4288 > URL: https://issues.apache.org/jira/browse/IGNITE-4288 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.8 > > > Need to fix ODBC-DML interoperability issues on ignite-1.8 branch. > Failing tests list: > * odbc-tests/QueriesTestSuite/TestInsertDeleteSelect > * odbc-tests/QueriesTestSuite/TestInsertMergeSelect > * odbc-tests/QueriesTestSuite/TestInsertSelect > * odbc-tests/QueriesTestSuite/TestInsertUpdateSelect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4288) ODBC: Fix ODBC and DML interoperability.
[ https://issues.apache.org/jira/browse/IGNITE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698989#comment-15698989 ] Denis Magda commented on IGNITE-4288: - Sounds reasonable. > ODBC: Fix ODBC and DML interoperability. > > > Key: IGNITE-4288 > URL: https://issues.apache.org/jira/browse/IGNITE-4288 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.8 > > > Need to fix ODBC-DML interoperability issues on ignite-1.8 branch. > Failing tests list: > * odbc-tests/QueriesTestSuite/TestInsertDeleteSelect > * odbc-tests/QueriesTestSuite/TestInsertMergeSelect > * odbc-tests/QueriesTestSuite/TestInsertSelect > * odbc-tests/QueriesTestSuite/TestInsertUpdateSelect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.
[ https://issues.apache.org/jira/browse/IGNITE-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh updated IGNITE-4244: - Affects Version/s: 1.8 > 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 >Affects Versions: 1.8 >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] [Comment Edited] (IGNITE-4244) Redis INCR/DECR to operate on AtomicLong.
[
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/27/16 3:52 AM:
[~anovikov]
Andrey, an error message starting with ERR (which is {{JedisDataException}} for
jedis).
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.
Do you think this fix can be merged to the master branch? I would like to see
it in 1.8.0 release.
> 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] [Closed] (IGNITE-4233) Add documentation for REDIS support
[ https://issues.apache.org/jira/browse/IGNITE-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-4233. --- > Add documentation for REDIS support > --- > > Key: IGNITE-4233 > URL: https://issues.apache.org/jira/browse/IGNITE-4233 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Roman Shtykh > Labels: redis > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4312) DML: update causes IgniteCheckedException: Invalid flag value: -2
[
https://issues.apache.org/jira/browse/IGNITE-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698209#comment-15698209
]
Alexander Paschenko commented on IGNITE-4312:
-
Investigated, still little to no luck for now. Thought that setting
{{BinaryIdentityResolver}} for type in config explicitly would help, but it did
not.
> 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] [Resolved] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value
[
https://issues.apache.org/jira/browse/IGNITE-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Paschenko resolved IGNITE-4313.
-
Resolution: Won't Fix
> 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
>Assignee: Alexander Paschenko
> 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}
>
[jira] [Commented] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value
[
https://issues.apache.org/jira/browse/IGNITE-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15698206#comment-15698206
]
Alexander Paschenko commented on IGNITE-4313:
-
Example fails because of this query
{code:sql}
update AllTypes set intCol = 1 where _val = ?
{code}
{{_val}} is of type {{AllTypes}}, and argument is a {{Long}}, so query should
rather be
{code:sql}
update AllTypes set intCol = 1 where longCol = ?
{code}
When corrected, the error disappears. Will think about additional type checks
for more informative exceptions.
> 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
>
[jira] [Assigned] (IGNITE-4313) DML: update causes IgniteCheckedException: Not enough data to read the value
[
https://issues.apache.org/jira/browse/IGNITE-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Paschenko reassigned IGNITE-4313:
---
Assignee: Alexander Paschenko
> 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
>Assignee: Alexander Paschenko
> 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}
>
