[jira] [Updated] (IGNITE-744) removeAll() doesn't remove swapped entries for LOCAL cache.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-744:
---
Priority: Minor  (was: Major)

> removeAll() doesn't remove swapped entries for LOCAL cache.
> ---
>
> Key: IGNITE-744
> URL: https://issues.apache.org/jira/browse/IGNITE-744
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> For local cache we simply iterate over in-memory keyset. As a result, swapped 
> entries are not removed.



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

[jira] [Updated] (IGNITE-361) IGFS metrics are always zero in examples' counters

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-361:
---
Priority: Minor  (was: Major)

> IGFS metrics are always zero in examples' counters
> --
>
> Key: IGNITE-361
> URL: https://issues.apache.org/jira/browse/IGNITE-361
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> *Steps to reproduce*
> # Run any built in Hadoop example or benchmark with 1 or more Gridgain nodes 
> (f.e.teragen)
> # Check *INFO mapreduce.Job: Counters:* after example is finished
> *Observed*
> GGFS counters are always '0'
> {noformat}
>   File System Counters
>   FILE: Number of bytes read=270352
>   FILE: Number of bytes written=458787
>   FILE: Number of read operations=0
>   FILE: Number of large read operations=0
>   FILE: Number of write operations=0
>   GGFS: Number of bytes read=0
>   GGFS: Number of bytes written=0
>   GGFS: Number of read operations=0
>   GGFS: Number of large read operations=0
>   GGFS: Number of write operations=0
> {noformat}
> Migrated from GG JIRA (GG-8641).



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

[jira] [Updated] (IGNITE-559) TransactionProxyImpl.future() must throw an exception in case of no previous async op.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-559:
---
Priority: Minor  (was: Major)

> TransactionProxyImpl.future() must throw an exception in case of no previous 
> async op.
> --
>
> Key: IGNITE-559
> URL: https://issues.apache.org/jira/browse/IGNITE-559
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> For sync future and for async future when there is no preceeding async op, we 
> must throw an exception to follow regular "WithAsync" semantics.
> Also, current future must be cleaned before return.



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

[jira] [Updated] (IGNITE-3614) Failed test: CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3614:

Priority: Minor  (was: Major)

> Failed test: 
> CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter
> 
>
> Key: IGNITE-3614
> URL: https://issues.apache.org/jira/browse/IGNITE-3614
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Tikhonov
>Priority: Minor
> Fix For: 2.0
>
>
> Test periodically fail with the following stack trace:
> {code}
> java.lang.Exception: Failed to find a server node.
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.testUpdatePartitionCounter(CacheContinuousQueryFailoverAbstractSelfTest.java:390)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Apparently, this is a bug in the test - somehow it cannot return cache 
> reliably.



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

[jira] [Updated] (IGNITE-2109) PlatformUtils.errorData() contains invalid call to PlatformInputStream.remaining()

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2109:

Priority: Minor  (was: Major)

> PlatformUtils.errorData() contains invalid call to 
> PlatformInputStream.remaining()
> --
>
> Key: IGNITE-2109
> URL: https://issues.apache.org/jira/browse/IGNITE-2109
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> See the following line:
> {code}int len = in.remaining();{code}
> WTF is that? Probably "length()" method should be called instead.



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

[jira] [Updated] (IGNITE-3492) IGFS: Support file-based evictions

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3492:

Priority: Minor  (was: Major)

> IGFS: Support file-based evictions
> --
>
> Key: IGNITE-3492
> URL: https://issues.apache.org/jira/browse/IGNITE-3492
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> Currently we support only per-block evictions. It means that block of any 
> file can be removed. 
> It might worth considering to drop the whole files instead of file blocks.



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

[jira] [Updated] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3542:

Priority: Minor  (was: Major)

> IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.
> -
>
> Key: IGNITE-3542
> URL: https://issues.apache.org/jira/browse/IGNITE-3542
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> If integrity check failed, it means that some concurrent file system update 
> occurred. We should always perform re-try in this case.



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

[jira] [Updated] (IGNITE-307) Review all GridCacheDrManager.onReceiveCacheEntriesReceived() usages.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-307:
---
Priority: Minor  (was: Major)

> Review all  GridCacheDrManager.onReceiveCacheEntriesReceived() usages.
> --
>
> Key: IGNITE-307
> URL: https://issues.apache.org/jira/browse/IGNITE-307
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> This method is expected to be called for DR only. However, with current 
> implementation it will ba called for local store as well.



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

[jira] [Resolved] (IGNITE-331) CacheTypeMetadata is not read in case CacheQueryConfiguration is not set.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-331.

Resolution: Not A Problem

> CacheTypeMetadata is not read in case CacheQueryConfiguration is not set.
> -
>
> Key: IGNITE-331
> URL: https://issues.apache.org/jira/browse/IGNITE-331
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>
> I see the following code in GridQueryProcessor.start():
> {code}
> CacheQueryConfiguration qryCfg = ccfg.getQueryConfiguration();
> if (qryCfg != null) {
> if (!F.isEmpty(ccfg.getTypeMetadata())) {
> for (CacheTypeMetadata meta : ccfg.getTypeMetadata())
> declaredTypesByName.put(new TypeName(ccfg.getName(), 
> meta.getValueType()), meta);
> }
> if (qryCfg.getTypeResolver() != null)
> typeResolvers.put(ccfg.getName(), qryCfg.getTypeResolver());
> }
> {code}
> So, type metadata is not read in case CacheQueryConfiguration is not set. If 
> we set empty CacheQueryConfiguration, all is fine. Looks like a usability 
> issue - why does user have to specify empty CacheQueryConfiguration?



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

[jira] [Resolved] (IGNITE-279) GridNoStorageCacheMap does not use TTL in putEntryIfObsoleteOrAbsent() method.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-279.

Resolution: Not A Problem

> GridNoStorageCacheMap does not use TTL in putEntryIfObsoleteOrAbsent() method.
> --
>
> Key: IGNITE-279
> URL: https://issues.apache.org/jira/browse/IGNITE-279
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>
> Is it fine that TTL is not passed to a newly created GridDhtCacheEntry?



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

[jira] [Resolved] (IGNITE-276) GridLocalAtomicCache does not use TTL in put/putAsync/putx/putxAsync methods

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-276.

Resolution: Won't Fix

> GridLocalAtomicCache does not use TTL in put/putAsync/putx/putxAsync methods
> 
>
> Key: IGNITE-276
> URL: https://issues.apache.org/jira/browse/IGNITE-276
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>
> Need to review TTL logic in GridLocalAtomicCache put-methods.



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

[jira] [Updated] (IGNITE-1152) Distribution of backup partitions is not uniform

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1152:
-
Priority: Minor  (was: Major)

> Distribution of backup partitions is not uniform
> 
>
> Key: IGNITE-1152
> URL: https://issues.apache.org/jira/browse/IGNITE-1152
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Goncharuk
>Priority: Minor
> Attachments: CacheBackupPartitionsTest.java
>
>
> I started 4 nodes with partitioned cache with 1 backup.
> And found that primary parts more or less uniform, but backup parts - not:
> Node n1: : pri=244, bak=367
> Node n2: : pri=260, bak=590
> Node n3: : pri=244, bak=367
> Node n4: : pri=260, bak=590
> Code to test this issue attached.



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

[jira] [Updated] (IGNITE-220) Continuations do not work as expected for anonymous IgniteCallable

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-220:

Priority: Minor  (was: Major)

> Continuations do not work as expected for anonymous IgniteCallable
> --
>
> Key: IGNITE-220
> URL: https://issues.apache.org/jira/browse/IGNITE-220
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Attachments: ContinuationTest.java
>
>
> Please find test in attached file



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

[jira] [Updated] (IGNITE-3067) Refactor validators messages from feedbacks to ngModel + form

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3067:
-
Priority: Minor  (was: Major)

> Refactor validators messages from feedbacks to ngModel + form
> -
>
> Key: IGNITE-3067
> URL: https://issues.apache.org/jira/browse/IGNITE-3067
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> Current implementation feedback directive put error message into form, but 
> validators have more info about error and could put more detailed message 
> into form.
> This should be refactored.



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

[jira] [Updated] (IGNITE-3017) igniteFormFieldInputAutofocus is not working as expected

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-3017:
-
Priority: Minor  (was: Major)

> igniteFormFieldInputAutofocus is not working as expected
> 
>
> Key: IGNITE-3017
> URL: https://issues.apache.org/jira/browse/IGNITE-3017
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> Setting attribute data-ignite-form-field-input-autofocus to false does not 
> prevent from setting focus into control.
> Could be tested on Clusters\binary\Type configurations table.



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

[jira] [Updated] (IGNITE-2571) Responsive web design

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2571:
-
Priority: Minor  (was: Major)

> Responsive web design
> -
>
> Key: IGNITE-2571
> URL: https://issues.apache.org/jira/browse/IGNITE-2571
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5.0.final
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> This is a parent ticket for all issues about responsive web design



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

[jira] [Updated] (IGNITE-2133) Schema Import Utility should print warning about wrong IGNITE_HOME

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2133:
-
Priority: Minor  (was: Major)

> Schema Import Utility should print warning about wrong IGNITE_HOME
> --
>
> Key: IGNITE-2133
> URL: https://issues.apache.org/jira/browse/IGNITE-2133
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Priority: Minor
>




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

[jira] [Updated] (IGNITE-2131) NPE in GridJobProcessor (non-reproducible, sibling bytes are null)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2131:
-
Priority: Minor  (was: Major)

> NPE in GridJobProcessor (non-reproducible, sibling bytes are null)
> --
>
> Key: IGNITE-2131
> URL: https://issues.apache.org/jira/browse/IGNITE-2131
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.5.0.final
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> I got this NPE.
> Looking into GridJobProcessor.java:1024 code, I see that NPE could happen if 
> marshaler return null.
> Maybe we could throw exception with appropriate message?
> {code}
> Exception in thread "pub-#7%null%" Exception in thread "pub-#8%null%" 
> java.lang.NullPointerException
>  at java.util.ArrayList.(ArrayList.java:164)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1024)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> {code}



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

[jira] [Updated] (IGNITE-2049) Add to GridProductVersionSelfTest new tests for new naming strategy

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2049:
-
Priority: Trivial  (was: Major)

> Add to GridProductVersionSelfTest new tests for new naming strategy
> ---
>
> Key: IGNITE-2049
> URL: https://issues.apache.org/jira/browse/IGNITE-2049
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Affects Versions: 1.5.0.final
>Reporter: Alexey Kuznetsov
>Priority: Trivial
>  Labels: newbie
>
> See 
> http://apache-ignite-developers.2346864.n4.nabble.com/EA-versioning-td5381.html



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

[jira] [Updated] (IGNITE-768) Failed to start LOCAL cache on part of the grid

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-768:

Priority: Minor  (was: Major)

> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Attachments: 
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException: 
> Failed to start cache (a cache with the same name is already started): 
> local-nid
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
>   at 
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}



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

[jira] [Updated] (IGNITE-1178) NPE in GridCacheProcessor.onKernalStop()

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1178:
-
Priority: Minor  (was: Major)

> NPE in GridCacheProcessor.onKernalStop()
> 
>
> Key: IGNITE-1178
> URL: https://issues.apache.org/jira/browse/IGNITE-1178
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> If user start node with incorrectly configured cache type metadata for 
> JdbcPojoStore NPE is raised in onKernalStop. See attached stacktrace:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to initialize property
> 'exceptionOid' for key class 'class
> org.apache.ignite.examples.algofusion.ExceptionMasterKey' and value class
> 'class org.apache.ignite.examples.algofusion.ExceptionMaster'. Make sure
> that one of these classes contains respective getter method or field.
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.buildClassProperty(GridQueryProcessor.java:1342)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processClassMeta(GridQueryProcessor.java:1148)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:149)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:249)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:922)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:779)
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at org.apache.ignite.examples.algofusion.AlgoDB.main(AlgoDB.java:89)
> [15:45:29,007][ERROR][main][IgniteKernal] Failed to pre-stop processor:
> GridProcessorAdapter []
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.GridCacheEventManager.isRecordable(GridCacheEventManager.java:342)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1089)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:896)
> at 
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1706)
> at 
> org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1650)
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:852)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at org.apache.ignite.examples.algofusion.AlgoDB.main(AlgoDB.java:89)
> [15:45:29] Ignite node stopped wih ERRORS [uptime=00:00:02:515]
> {code}



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

[jira] [Updated] (IGNITE-303) Create test reproducing the SO issue

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-303:

Priority: Minor  (was: Major)

> Create test reproducing the SO issue
> 
>
> Key: IGNITE-303
> URL: https://issues.apache.org/jira/browse/IGNITE-303
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>Priority: Minor
>
> http://stackoverflow.com/questions/27290272/failed-to-send-update-request-to-backup-node



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

[jira] [Commented] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-4205:
-

[~irudyak], the change looks good to me, but it seems to be not tested. Can you 
create a test for the scenario I described in the ticket? We need to make sure 
that the solution is actually working.

We also need to make similar change in {{CacheAbstractJdbcStore}}. Can you do 
this as well? Or you prefer to create a separate ticket for this?

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Igor Rudyak
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



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

[jira] [Comment Edited] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store

[Amir Akhmedov (JIRA)]

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

Amir Akhmedov edited comment on IGNITE-3699 at 11/28/16 8:42 PM:
-

Hi Semen,

I updated PR with corresponding changes:

1. Switched JDK to version 7 and ran TeamCity tests. Some of them are failing 
but from test's history I see that they are also failing on master

2. Now {{getAllAsync0}} calculates the ttl and passes it to {{versionedValue}}

3. The change in GridDhtTxPrepareFuture was done to fix IGNITE-821. But I 
realized that it's not correct fix and reverted back the changes.

Please let me know if you have any comments

Thanks.


was (Author: aakhmedov):
Hi Semen,

I updated PR with corresponding changes:

1. Switched JDK to version 7 and ran TeamCity tests. Some of them are failing 
but from test's history I see that they also failing on master

2. Now {{getAllAsync0}} calculates the ttl and passes it to {{versionedValue}}

3. The change in GridDhtTxPrepareFuture was done to fix IGNITE-821. But I 
realized that it's not correct fix and I reverted back the changes.

Please let me know if you any comments

Thanks.

> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be 
> triggered on {{get()}} operation if the entry is loaded from the store. 
> Currently this is not happening.
> Test reproducing the issue is attached.



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

[jira] [Comment Edited] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store

[Amir Akhmedov (JIRA)]

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

Amir Akhmedov edited comment on IGNITE-3699 at 11/28/16 8:41 PM:
-

Hi Semen,

I updated PR with corresponding changes:

1. Switched JDK to version 7 and ran TeamCity tests. Some of them are failing 
but from test's history I see that they also failing on master

2. Now {{getAllAsync0}} calculates the ttl and passes it to {{versionedValue}}

3. The change in GridDhtTxPrepareFuture was done to fix IGNITE-821. But I 
realized that it's not correct fix and I reverted back the changes.

Please let me know if you any comments

Thanks.


was (Author: aakhmedov):
Hi Semen,

I update PR with corresponding changes:

1. Switched JDK to version 7 and ran TeamCity tests. Some of them are failing 
but from test's history I see that they also failing on master

2. Now {{getAllAsync0}} calculates the ttl and passes it to {{versionedValue}}

3. The change in GridDhtTxPrepareFuture was done to fix IGNITE-821. But I 
realized that it's not correct fix and I reverted back the changes.

Please let me know if you any comments

Thanks.

> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be 
> triggered on {{get()}} operation if the entry is loaded from the store. 
> Currently this is not happening.
> Test reproducing the issue is attached.



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

[jira] [Commented] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store

[Amir Akhmedov (JIRA)]

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

Amir Akhmedov commented on IGNITE-3699:
---

Hi Semen,

I update PR with corresponding changes:

1. Switched JDK to version 7 and ran TeamCity tests. Some of them are failing 
but from test's history I see that they also failing on master

2. Now {{getAllAsync0}} calculates the ttl and passes it to {{versionedValue}}

3. The change in GridDhtTxPrepareFuture was done to fix IGNITE-821. But I 
realized that it's not correct fix and I reverted back the changes.

Please let me know if you any comments

Thanks.

> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be 
> triggered on {{get()}} operation if the entry is loaded from the store. 
> Currently this is not happening.
> Test reproducing the issue is attached.



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

[jira] [Commented] (IGNITE-4321) Cassandra modules

[Igor Rudyak (JIRA)]

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

Igor Rudyak commented on IGNITE-4321:
-

It should be done on the maven package creation side. Cassandra module was 
separated to two different modules for the purpose. Please find more details 
here:

https://issues.apache.org/jira/browse/IGNITE-3172

> Cassandra modules
> -
>
> Key: IGNITE-4321
> URL: https://issues.apache.org/jira/browse/IGNITE-4321
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> Binary fabric edition now has following modules:
> {noformat}
>  Содержимое папки 
> C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra
> 25.11.2016  22:13  .
> 25.11.2016  22:13  ..
> 25.11.2016  22:13   964 README.txt
>1 файлов964 байт
>  Содержимое папки 
> C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers
> 25.11.2016  22:13  .
> 25.11.2016  22:13  ..
> 25.11.2016  22:1353 231 asm-5.0.3.jar
> 25.11.2016  22:1312 181 
> ignite-cassandra-serializers-1.8.0-QASK2502.jar
> 25.11.2016  22:13   285 211 kryo-3.0.3.jar
> 25.11.2016  22:13  licenses
> 25.11.2016  22:13 5 711 minlog-1.3.0.jar
> 25.11.2016  22:1341 755 objenesis-2.1.jar
> 25.11.2016  22:13 1 345 README.txt
> 25.11.2016  22:1320 738 reflectasm-1.10.1.jar
>7 файлов420 172 байт
>  Содержимое папки 
> C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers\licenses
> 25.11.2016  22:13  .
> 25.11.2016  22:13  ..
> 25.11.2016  22:1311 358 apache-2.0.txt
> 25.11.2016  22:13 1 857 ignite-cassandra-serializers-licenses.txt
>2 файлов 13 215 байт
>  Содержимое папки 
> C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store
> 25.11.2016  22:13  .
> 25.11.2016  22:13  ..
> 25.11.2016  22:13   990 392 cassandra-driver-core-3.0.0.jar
> 25.11.2016  22:13   232 019 commons-beanutils-1.8.3.jar
> 25.11.2016  22:13 2 308 517 guava-19.0.jar
> 25.11.2016  22:1391 897 ignite-cassandra-store-1.8.0-QASK2502.jar
> 25.11.2016  22:13  licenses
> 25.11.2016  22:1385 448 metrics-core-3.0.2.jar
> 25.11.2016  22:13   196 881 netty-buffer-4.0.33.Final.jar
> 25.11.2016  22:13   145 779 netty-codec-4.0.33.Final.jar
> 25.11.2016  22:13   441 447 netty-common-4.0.33.Final.jar
> 25.11.2016  22:13   272 139 netty-handler-4.0.33.Final.jar
> 25.11.2016  22:13   349 164 netty-transport-4.0.33.Final.jar
> 25.11.2016  22:13 1 228 README.txt
>   11 файлов  5 114 911 байт
>  Содержимое папки 
> C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store\licenses
> 25.11.2016  22:13  .
> 25.11.2016  22:13  ..
> 25.11.2016  22:1311 358 apache-2.0.txt
> 25.11.2016  22:13   294 ignite-cassandra-store-licenses.txt
>2 файлов 11 652 байт
> {noformat}
> I suppose that {{ignite-cassandra}} directory must be removed and rest of 
> Cassandra modules should be joined into one.



--
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:
--
Assignee: Alexander Paschenko  (was: Sergey Kozlov)

> 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] [Closed] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-4287.
-

> 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] [Assigned] (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 reassigned IGNITE-4312:
-

Assignee: Sergey Kozlov  (was: 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: 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] [Created] (IGNITE-4325) Proposing new marshaller mapping should be done in synchronous way

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-4325:
---

 Summary: Proposing new marshaller mapping should be done in 
synchronous way
 Key: IGNITE-4325
 URL: https://issues.apache.org/jira/browse/IGNITE-4325
 Project: Ignite
  Issue Type: Sub-task
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov


h3. Notes
Previous version of DiscoveryCustomEvent-based MarshallerContext implementation 
returned immediately with "not registered" flag after submitting request for 
new mapping.
This may be ineffective in terms of network traffic and not well suited with 
current implementation of BinaryCache.

h3. Acceptance Criteria
# Registration of new mapping should return when the mapping is accepted by 
grid.
# Registration of new mapping should throw an exception when the mapping is in 
conflict with grid.



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

[jira] [Commented] (IGNITE-3886) .NET: Build script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3886:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-3886 .NET: Build script



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

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

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

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


commit 6b8942d305a24bc97f64414d6e863fc757a829d5
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:39:31Z

IGNITE-3886 .NET: Build script

commit 37bfc70b5f0dd3dedd4c00599d8b08865e5c9002
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:53:43Z

Merge branch 'master' into ignite-3886

commit 504c61c7bdfdcd99669851c65b6030551dec9174
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:58:26Z

wip

commit 22f20325fad53b41f97f453ed5acf5784ef253a7
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:59:29Z

wip

commit 271ac6e0d9efd8bd109cf3f62cc2f276928fa2ab
Author: Pavel Tupitsyn 
Date:   2016-11-28T14:56:07Z

wip build Java

commit bb3da08955eb87748ba74aea0b9a689472b1dedf
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:16:00Z

wip

commit dd4cd97631fb1d28cfd82022a221db037669699e
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:17:17Z

wip

commit 231761d274db4a6366ad32c3397666d4c027
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:22:55Z

wip

commit e76dd6c412de7c195bff82ada6f09395d8aa02ac
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:30:44Z

Java and .NET build steps done

commit 8cfb5870e3181e8af800960ee3ec546bcf732f49
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:33:33Z

wip

commit 35a581b34f96f78fb87a02a8acde9d02fc432ddc
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:34:10Z

wip

commit e144548beabd96d9dc243bf0516efcebfaf23605
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:44:13Z

wip

commit a03eadd92b33f9977173ec7ac47db58af7441efd
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:51:13Z

Fix quotes

commit 94b926d2f3f3c2f7c72f7cdacaebac0040016b67
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:52:53Z

Add gitignore

commit 1262d13e2c6fdaea5171eb06ff34faa92a2811ec
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:57:57Z

wip code analysis

commit b3ae02859b1424373a8cdecb13ff38a93313bb0e
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:33:04Z

Add batch file for easy run

commit bf787254932fbfd905060e0756356d8d647e0f2b
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:50:52Z

NuGet packaging added

commit 0600f548928bf6f9ecbb0ac5b594a3e2fff5bb60
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:54:03Z

minors




> .NET: Build script
> --
>
> Key: IGNITE-3886
> URL: https://issues.apache.org/jira/browse/IGNITE-3886
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Create a build script with powershell or cake http://cakebuild.net/.
> Currently, we have our build completely automated on TeamCity. However, it 
> should be possible to build everything (jars, dlls, NuGet) locally with a 
> single command.
> As a result, we should have:
> * bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
> with jar files
> * nupkg folder with all NuGet packages
> Investigate how to integrate this with Maven: IGNITE-2292



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

[jira] [Commented] (IGNITE-4140) KafkaStreamer should use tuple extractor instead of decoders

[Anil (JIRA)]

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

Anil commented on IGNITE-4140:
--


Hi [~avinogradov] 

Could you please review the changes ? Thanks

KafkaDataStreamer can be used when

1. Key of kafka message is key of the cache entry and message of the kafka 
message as value of cache entry 
2. Kafka message is actually number of cache entries

Tuple extractor is mandatory for both #1 and #2

I see two possible issues with KafkaStreamer and KafkaDataStreamer

a. Order of messages is not guaranteed as data streamer not guarantee the order 
by design
b. possibility of streamer closed exception when node rejoin.

#a - entries must be added to cache directly instead of data streamer if the 
order of messages is must
#b - could you please share your inputs ?

Thanks



> KafkaStreamer should use tuple extractor instead of decoders
> 
>
> Key: IGNITE-4140
> URL: https://issues.apache.org/jira/browse/IGNITE-4140
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Anil
> Fix For: 2.0
>
>
> Current design of {{KafkaStreamer}} looks incorrect to me. In particular, it 
> extends {{StreamAdapter}}, but ignores tuple extractors provided there and 
> uses native Kafka decoders instead. This for example makes impossible to 
> produce several entries from one message, like it can be done via 
> {{StreamMultipleTupleExtractor}} in other streamers.
> To fix this, we should:
> # Declare the {{KafkaStreamer}} like this:
> {code}
> KafkaStreamer extends StreamAdapter, 
> K, V>
> {code}
> # Remove {{keyDecoder}} and {{valDecoder}} in favor of tuple extractors.
> # Instead of doing {{getStreamer().addData(...)}} directly, call 
> {{addMessage(...)}} method providing the raw message consumed from Kafka 
> ({{MessageAndMetadata}}). This method will make sure that 
> configured extractor is invoked and that all entries are added to 
> {{IgniteDataStreamer}}.



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

[jira] [Commented] (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:comment-tabpanel=15702408#comment-15702408
 ] 

Konstantin Dudkov commented on IGNITE-4305:
---

fixed request marshalling bug, now tests run good. Please review.

> 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] [Assigned] (IGNITE-4140) KafkaStreamer should use tuple extractor instead of decoders

[Anil (JIRA)]

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

Anil reassigned IGNITE-4140:


Assignee: Anil

> KafkaStreamer should use tuple extractor instead of decoders
> 
>
> Key: IGNITE-4140
> URL: https://issues.apache.org/jira/browse/IGNITE-4140
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Anil
> Fix For: 2.0
>
>
> Current design of {{KafkaStreamer}} looks incorrect to me. In particular, it 
> extends {{StreamAdapter}}, but ignores tuple extractors provided there and 
> uses native Kafka decoders instead. This for example makes impossible to 
> produce several entries from one message, like it can be done via 
> {{StreamMultipleTupleExtractor}} in other streamers.
> To fix this, we should:
> # Declare the {{KafkaStreamer}} like this:
> {code}
> KafkaStreamer extends StreamAdapter, 
> K, V>
> {code}
> # Remove {{keyDecoder}} and {{valDecoder}} in favor of tuple extractors.
> # Instead of doing {{getStreamer().addData(...)}} directly, call 
> {{addMessage(...)}} method providing the raw message consumed from Kafka 
> ({{MessageAndMetadata}}). This method will make sure that 
> configured extractor is invoked and that all entries are added to 
> {{IgniteDataStreamer}}.



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

[jira] [Updated] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-4324:
-
Attachment: Tests.patch

> ScanQuery throws incomprehensible exception when topology does not contain 
> data nodes
> -
>
> Key: IGNITE-4324
> URL: https://issues.apache.org/jira/browse/IGNITE-4324
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: Nikolay Tikhonov
> Fix For: 2.0
>
> Attachments: Tests.patch
>
>
> ScanQuery throws incomprehensible exception when topology does not contain 
> data nodes (for example with node filter).  See attached test.
> {code}
> java.lang.IllegalArgumentException: bound must be positive
>   at java.util.Random.nextInt(Random.java:388)
>   at org.apache.ignite.internal.util.lang.GridFunc.rand(GridFunc.java:677)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.nodes(GridCacheQueryAdapter.java:582)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:527)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4119)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4094)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.iterator(IgniteCacheProxy.java:1979)
>   at 
> org.apache.ignite.internal.CacheFilterQueryTest.testScanQuery(CacheFilterQueryTest.java:90)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1768)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1706)
>   at java.lang.Thread.run(Thread.java:745)
> [
> {code}



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

[jira] [Created] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes

[Nikolay Tikhonov (JIRA)]

Nikolay Tikhonov created IGNITE-4324:


 Summary: ScanQuery throws incomprehensible exception when topology 
does not contain data nodes
 Key: IGNITE-4324
 URL: https://issues.apache.org/jira/browse/IGNITE-4324
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7, 1.8
Reporter: Nikolay Tikhonov
 Fix For: 2.0


ScanQuery throws incomprehensible exception when topology does not contain data 
nodes (for example with node filter).  See attached test.

{code}
java.lang.IllegalArgumentException: bound must be positive
at java.util.Random.nextInt(Random.java:388)
at org.apache.ignite.internal.util.lang.GridFunc.rand(GridFunc.java:677)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.nodes(GridCacheQueryAdapter.java:582)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:527)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4119)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4094)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.iterator(IgniteCacheProxy.java:1979)
at 
org.apache.ignite.internal.CacheFilterQueryTest.testScanQuery(CacheFilterQueryTest.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1768)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1706)
at java.lang.Thread.run(Thread.java:745)
[
{code}



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

[jira] [Updated] (IGNITE-4323) DML: INSERT INTO SELECT .. FROM statement causes IgniteException: Wrong value has been set

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4323:
--
Attachment: IGNITE-4323_20161128_2.zip

> DML: INSERT INTO SELECT .. FROM statement causes IgniteException: Wrong value 
> has been set
> --
>
> Key: IGNITE-4323
> URL: https://issues.apache.org/jira/browse/IGNITE-4323
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
> Attachments: IGNITE-4323_20161128.zip, IGNITE-4323_20161128_2.zip
>
>
> The idea of scenario to copy data from cache to cache.
> 0. Extract the attachment into {{examples}} directory
> 1. Start {{org.apache.ignite.examples.datagrid.ExtSqlExampleNodeStartup}}
> 2. Start one ore more {{org.apache.ignite.examples.datagrid.ExtSqlExample}}
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Wrong value has been set 
> [typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
> fieldType=Enum, assignedValueType=Object]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:92)
>   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: Wrong value has been set 
> [typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
> fieldType=Enum, assignedValueType=Object]
>   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: Wrong value has 
> been set [typeName=org.apache.ignite.testtools.model.AllTypes, 
> fieldName=enumCol, fieldType=Enum, assignedValueType=Object]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1800)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
>   ... 7 more
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Wrong value 
> has been set [typeName=org.apache.ignite.testtools.model.AllTypes, 
> fieldName=enumCol, fieldType=Enum, assignedValueType=Object]
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:418)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:227)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:187)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:809)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:705)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:282)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:155)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:185)
>   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:1777)
>   ... 8 more
> {noformat}



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

[jira] [Commented] (IGNITE-4323) DML: INSERT INTO SELECT .. FROM statement causes IgniteException: Wrong value has been set

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-4323:
---

resources xml fixes:
{code:xml}


{code}

Now I've got the exception on {{get()}}:
{noformat}
xception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteCheckedException: Can not set [Ljava.lang.Byte; field 
org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1440)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2183)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1125)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:237)
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.IgniteCheckedException: Can not set 
[Ljava.lang.Byte; field org.apache.ignite.testtools.model.AllTypes.bytesCol to 
[Ljava.lang.Object;
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7185)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:169)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:118)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:482)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
... 6 more
Caused by: java.lang.IllegalArgumentException: Can not set [Ljava.lang.Byte; 
field org.apache.ignite.testtools.model.AllTypes.bytesCol to [Ljava.lang.Object;
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:741)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:829)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1498)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:637)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:142)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:272)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:160)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:147)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1760)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:630)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.onResult(GridPartitionedSingleGetFuture.java:492)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetResponse(GridDhtCacheAdapter.java:155)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$2200(GridDhtAtomicCache.java:125)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$12.apply(GridDhtAtomicCache.java:440)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$12.apply(GridDhtAtomicCache.java:435)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:827)
at 

[jira] [Commented] (IGNITE-4247) Table aliases not supported for SqlQuery

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-4247:
--

H2Indexing.generateQuery() method should provide correct column names in 
"SELECT" part of query. The correct way is analyze "FROM" part of query, choose 
suitable alias and rewrite "SELECT" part with correct alias. It look like we 
can't fix this for more complex queries without replacing H2 parser.

Fix in attached PR works for simple queries (with trivial FROM part). Whether 
it will be enough?

> Table aliases not supported for SqlQuery
> 
>
> Key: IGNITE-4247
> URL: https://issues.apache.org/jira/browse/IGNITE-4247
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 2.0
>
>
> Here is the example of the query:
> {code}
> from Person p where p.salary > ? and p.salary <= ?
> {code}
> Ignite is not aware of the alias and incorrectly appends the SELECT 
> statement, which causes this exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to parse query: 
> SELECT "CacheQueryExamplePersons".Person._key, 
> "CacheQueryExamplePersons".Person._val from Person p where salary > ? and 
> salary <= ?
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1217)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1123)
>   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 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1760)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:733)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.sqlQuery(CacheQueryExample.java:176)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:116)
>   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:144)
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "CacheQueryExamplePersons.PERSON._KEY" not found; SQL statement:
> SELECT "CacheQueryExamplePersons".Person._key, 
> "CacheQueryExamplePersons".Person._val from Person p where salary > ? and 
> salary <= ? [42122-191]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
>   at org.h2.message.DbException.get(DbException.java:179)
>   at org.h2.message.DbException.get(DbException.java:155)
>   at 
> org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
>   at org.h2.command.dml.Select.prepare(Select.java:852)
>   at org.h2.command.Parser.prepareCommand(Parser.java:257)
>   at org.h2.engine.Session.prepareLocal(Session.java:560)
>   at org.h2.engine.Session.prepareCommand(Session.java:501)
>   at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
>   at 
> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:410)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1201)
>   ... 14 more
> {noformat}



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

[jira] [Assigned] (IGNITE-4247) Table aliases not supported for SqlQuery

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-4247:


Assignee: Andrew Mashenkov

> Table aliases not supported for SqlQuery
> 
>
> Key: IGNITE-4247
> URL: https://issues.apache.org/jira/browse/IGNITE-4247
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>
> Here is the example of the query:
> {code}
> from Person p where p.salary > ? and p.salary <= ?
> {code}
> Ignite is not aware of the alias and incorrectly appends the SELECT 
> statement, which causes this exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to parse query: 
> SELECT "CacheQueryExamplePersons".Person._key, 
> "CacheQueryExamplePersons".Person._val from Person p where salary > ? and 
> salary <= ?
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1217)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1123)
>   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 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1760)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:733)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.sqlQuery(CacheQueryExample.java:176)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:116)
>   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:144)
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "CacheQueryExamplePersons.PERSON._KEY" not found; SQL statement:
> SELECT "CacheQueryExamplePersons".Person._key, 
> "CacheQueryExamplePersons".Person._val from Person p where salary > ? and 
> salary <= ? [42122-191]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
>   at org.h2.message.DbException.get(DbException.java:179)
>   at org.h2.message.DbException.get(DbException.java:155)
>   at 
> org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
>   at org.h2.command.dml.Select.prepare(Select.java:852)
>   at org.h2.command.Parser.prepareCommand(Parser.java:257)
>   at org.h2.engine.Session.prepareLocal(Session.java:560)
>   at org.h2.engine.Session.prepareCommand(Session.java:501)
>   at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
>   at 
> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:410)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1201)
>   ... 14 more
> {noformat}



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

[jira] [Commented] (IGNITE-3886) .NET: Build script

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3886:


To easily integrate this with Maven later on we should create a script that 
builds everything .NET-related and *optionally* also runs Maven build.

This way .NET devs can run this script and produce binaries without messing 
with Maven directly, and Java people can do the opposite - build everything 
from Maven.

> .NET: Build script
> --
>
> Key: IGNITE-3886
> URL: https://issues.apache.org/jira/browse/IGNITE-3886
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Create a build script with powershell or cake http://cakebuild.net/.
> Currently, we have our build completely automated on TeamCity. However, it 
> should be possible to build everything (jars, dlls, NuGet) locally with a 
> single command.
> As a result, we should have:
> * bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
> with jar files
> * nupkg folder with all NuGet packages
> Investigate how to integrate this with Maven: IGNITE-2292



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

[jira] [Assigned] (IGNITE-4111) Communication fails to send message if target node did not finish join process

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin reassigned IGNITE-4111:
--

Assignee: Semen Boikov  (was: Alexandr Kuramshin)

> Communication fails to send message if target node did not finish join process
> --
>
> Key: IGNITE-4111
> URL: https://issues.apache.org/jira/browse/IGNITE-4111
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.0
>
> Attachments: test onFirstMessage hang.log
>
>
> Currently this scenario is possible:
> - joining node sent join request and waits for 
> TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology
> - others nodes already see this node and can send messages to it (for example 
> try to run compute job on this node)
> - joining node can not receive message: TcpCommunicationSpi will hang inside 
> 'onFirstMessage' on 'getSpiContext' call, so sending node will get error 
> trying to establish connection
> Possible fix: if in onFirstMessage() spi context is not available, then 
> TcpCommunicationSpi  should send special response which indicates that this 
> node is not ready yet, and sender should retry after some time.
> Also need check internal code for places where message can be unnecessarily 
> sent to node: one such place is 
> GridCachePartitionExchangeManager.refreshPartitions - message is sent to all 
> known nodes, but here we can filter by node order / finished exchage version.



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

[jira] [Resolved] (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 resolved IGNITE-3169.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .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
>  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] [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=15701986#comment-15701986
 ] 

ASF GitHub Bot commented on IGNITE-3169:


Github user asfgit closed the pull request at:

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


> .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] [Resolved] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4322.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .NET: ClientReconnectExample is not clear enough 
> -
>
> Key: IGNITE-4322
> URL: https://issues.apache.org/jira/browse/IGNITE-4322
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
> Fix For: 1.9
>
>
> ClientReconnectExample has the following output
> {noformat}
> >>> Client reconnect example started.
> [13:19:53]__  
> [13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:19:53]  _/ // (7 7// /  / / / _/
> [13:19:53] /___/\___/_/|_/___/ /_/ /___/
> [13:19:53]
> [13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:19:53] 2016 Copyright(C) Apache Software Foundation
> [13:19:53]
> [13:19:53] Ignite documentation: http://ignite.apache.org
> [13:19:53]
> [13:19:53] Quiet mode.
> [13:19:53]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:19:53]
> [13:19:53] OS: Windows 10 10.0 amd64
> [13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:19:53] Configured plugins:
> [13:19:53]   ^-- None
> [13:19:53]
> [13:19:58] Security status [authentication=off, tls/ssl=off]
> [13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
> [13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [13:19:59]   ^-- Disable fully synchronous writes (set 
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [13:19:59]
> [13:19:59] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:19:59]
> [13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
> [13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
> >>> Server node started.
> [13:20:00]__  
> [13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:20:00]  _/ // (7 7// /  / / / _/
> [13:20:00] /___/\___/_/|_/___/ /_/ /___/
> [13:20:00]
> [13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:20:00] 2016 Copyright(C) Apache Software Foundation
> [13:20:00]
> [13:20:00] Ignite documentation: http://ignite.apache.org
> [13:20:00]
> [13:20:00] Quiet mode.
> [13:20:00]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:20:00]
> [13:20:00] OS: Windows 10 10.0 amd64
> [13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:20:00] Configured plugins:
> [13:20:00]   ^-- None
> [13:20:00]
> [13:20:00] Security status [authentication=off, tls/ssl=off]
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> [13:20:02] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:20:02]
> [13:20:02] Ignite node started OK (id=2f5922f5)
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> >>> Client node connected to the cluster.
> >>> Put value with key:0
> >>> Put value with key:1
> >>> Put value with key:2
> [13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi]
>  Failed to send message: TcpDiscoveryClientPingRequest 
> [nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
> super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
> id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
> topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
> java.net.SocketException: Socket is closed
> at java.net.Socket.getOutputStream(Socket.java:943)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
> >>> Put value with key:3
> [13:20:09] New version is available at ignite.apache.org: 1.7.0
> >>> Restarting server node...
> [13:20:09]

[jira] [Commented] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4322:


Console output and timeouts improved.

There is nothing to do with SocketException, it is thrown and caught internally.

> .NET: ClientReconnectExample is not clear enough 
> -
>
> Key: IGNITE-4322
> URL: https://issues.apache.org/jira/browse/IGNITE-4322
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
> Fix For: 1.9
>
>
> ClientReconnectExample has the following output
> {noformat}
> >>> Client reconnect example started.
> [13:19:53]__  
> [13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:19:53]  _/ // (7 7// /  / / / _/
> [13:19:53] /___/\___/_/|_/___/ /_/ /___/
> [13:19:53]
> [13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:19:53] 2016 Copyright(C) Apache Software Foundation
> [13:19:53]
> [13:19:53] Ignite documentation: http://ignite.apache.org
> [13:19:53]
> [13:19:53] Quiet mode.
> [13:19:53]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:19:53]
> [13:19:53] OS: Windows 10 10.0 amd64
> [13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:19:53] Configured plugins:
> [13:19:53]   ^-- None
> [13:19:53]
> [13:19:58] Security status [authentication=off, tls/ssl=off]
> [13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
> [13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [13:19:59]   ^-- Disable fully synchronous writes (set 
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [13:19:59]
> [13:19:59] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:19:59]
> [13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
> [13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
> >>> Server node started.
> [13:20:00]__  
> [13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:20:00]  _/ // (7 7// /  / / / _/
> [13:20:00] /___/\___/_/|_/___/ /_/ /___/
> [13:20:00]
> [13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:20:00] 2016 Copyright(C) Apache Software Foundation
> [13:20:00]
> [13:20:00] Ignite documentation: http://ignite.apache.org
> [13:20:00]
> [13:20:00] Quiet mode.
> [13:20:00]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:20:00]
> [13:20:00] OS: Windows 10 10.0 amd64
> [13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:20:00] Configured plugins:
> [13:20:00]   ^-- None
> [13:20:00]
> [13:20:00] Security status [authentication=off, tls/ssl=off]
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> [13:20:02] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:20:02]
> [13:20:02] Ignite node started OK (id=2f5922f5)
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> >>> Client node connected to the cluster.
> >>> Put value with key:0
> >>> Put value with key:1
> >>> Put value with key:2
> [13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi]
>  Failed to send message: TcpDiscoveryClientPingRequest 
> [nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
> super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
> id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
> topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
> java.net.SocketException: Socket is closed
> at java.net.Socket.getOutputStream(Socket.java:943)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
> >>> Put 

[jira] [Resolved] (IGNITE-1464) GridCacheDeploymentOffHeapSelfTest fails

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-1464.
--
   Resolution: Cannot Reproduce
Fix Version/s: 1.7

Close since all tests in GridCacheDeploymentOffHeapSelfTest pass now.

> GridCacheDeploymentOffHeapSelfTest fails
> 
>
> Key: IGNITE-1464
> URL: https://issues.apache.org/jira/browse/IGNITE-1464
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
> Fix For: 1.7
>
>
> 3 cases in GridCacheDeploymentOffHeapSelfTest fail. Most probably this issue 
> exists for a long time, but exception thrown in test was ignored utnil 
> IGNITE-264 was fixed.
> http://94.72.60.102/viewLog.html?buildId=536126=buildResultsDiv=Ignite_IgniteCache3.



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

[jira] [Created] (IGNITE-4323) DML: INSERT INTO SELECT .. FROM statement causes IgniteException: Wrong value has been set

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4323:
-

 Summary: DML: INSERT INTO SELECT .. FROM statement causes 
IgniteException: Wrong value has been set
 Key: IGNITE-4323
 URL: https://issues.apache.org/jira/browse/IGNITE-4323
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


The idea of scenario to copy data from cache to cache.

0. Extract the attachment into {{examples}} directory
1. Start {{org.apache.ignite.examples.datagrid.ExtSqlExampleNodeStartup}}
2. Start one ore more {{org.apache.ignite.examples.datagrid.ExtSqlExample}}
{noformat}
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Wrong value has been set 
[typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:92)
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: Wrong value has been set 
[typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
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: Wrong value has been 
set [typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1800)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
... 7 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Wrong value 
has been set [typeName=org.apache.ignite.testtools.model.AllTypes, 
fieldName=enumCol, fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:418)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:227)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:187)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:809)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:705)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:282)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:155)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:185)
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:1777)
... 8 more
{noformat}



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

[jira] [Resolved] (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 resolved IGNITE-4306.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .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
> Fix For: 1.9
>
>
> Looks like standalone node fails to join



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

[jira] [Commented] (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:comment-tabpanel=15701828#comment-15701828
 ] 

Pavel Tupitsyn commented on IGNITE-4306:


Does not fail for now. Closing.

> .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
> Fix For: 1.9
>
>
> Looks like standalone node fails to join



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4263:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4263  Hadoop: abstract out offheap/heap memory management.



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

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

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

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


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 517deeb718d91ad5727504c48228106e283b76c2
Author: tledkov-gridgain 
Date:   2016-11-25T16:27:27Z

IGNITE-4263: save the progress

commit ea2f6b0ffcfa723742ade762051ce39d13f24837
Author: tledkov-gridgain 
Date:   2016-11-28T10:49:06Z

IGNITE-4263: fix HeapMemeoryManager, add test

commit 9f5ea4391270d09d5e4bf2d64f6ae2ff58e9a91a
Author: tledkov-gridgain 
Date:   2016-11-28T10:50:39Z

IGNITE-4263: revert base test




> 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-898) Ignite does not starts from folder which name contains space

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-898:

Priority: Trivial  (was: Major)

> Ignite does not starts from folder which name contains space
> 
>
> Key: IGNITE-898
> URL: https://issues.apache.org/jira/browse/IGNITE-898
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Priority: Trivial
> Fix For: 2.0
>
>
> Observed:
> In case folder name contains space character Ignite node cannot be started.
> Expected:
> Ingine node should be startable even when folder name contains space 
> character.



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4017:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4017 DML example.



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

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

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

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


commit 62a9afe06ef2e6b2e65097c79c4ebc24a3c67166
Author: Alexander Paschenko 
Date:   2016-11-28T10:08:26Z

IGNITE-4017 DML example.




> 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-4322) .NET: ClientReconnectExample is not clear enough

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4322:
---
Fix Version/s: 1.8

> .NET: ClientReconnectExample is not clear enough 
> -
>
> Key: IGNITE-4322
> URL: https://issues.apache.org/jira/browse/IGNITE-4322
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> ClientReconnectExample has the following output
> {noformat}
> >>> Client reconnect example started.
> [13:19:53]__  
> [13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:19:53]  _/ // (7 7// /  / / / _/
> [13:19:53] /___/\___/_/|_/___/ /_/ /___/
> [13:19:53]
> [13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:19:53] 2016 Copyright(C) Apache Software Foundation
> [13:19:53]
> [13:19:53] Ignite documentation: http://ignite.apache.org
> [13:19:53]
> [13:19:53] Quiet mode.
> [13:19:53]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:19:53]
> [13:19:53] OS: Windows 10 10.0 amd64
> [13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:19:53] Configured plugins:
> [13:19:53]   ^-- None
> [13:19:53]
> [13:19:58] Security status [authentication=off, tls/ssl=off]
> [13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
> [13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [13:19:59]   ^-- Disable fully synchronous writes (set 
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [13:19:59]
> [13:19:59] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:19:59]
> [13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
> [13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
> >>> Server node started.
> [13:20:00]__  
> [13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:20:00]  _/ // (7 7// /  / / / _/
> [13:20:00] /___/\___/_/|_/___/ /_/ /___/
> [13:20:00]
> [13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:20:00] 2016 Copyright(C) Apache Software Foundation
> [13:20:00]
> [13:20:00] Ignite documentation: http://ignite.apache.org
> [13:20:00]
> [13:20:00] Quiet mode.
> [13:20:00]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:20:00]
> [13:20:00] OS: Windows 10 10.0 amd64
> [13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:20:00] Configured plugins:
> [13:20:00]   ^-- None
> [13:20:00]
> [13:20:00] Security status [authentication=off, tls/ssl=off]
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> [13:20:02] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:20:02]
> [13:20:02] Ignite node started OK (id=2f5922f5)
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> >>> Client node connected to the cluster.
> >>> Put value with key:0
> >>> Put value with key:1
> >>> Put value with key:2
> [13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi]
>  Failed to send message: TcpDiscoveryClientPingRequest 
> [nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
> super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
> id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
> topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
> java.net.SocketException: Socket is closed
> at java.net.Socket.getOutputStream(Socket.java:943)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
> >>> Put value with key:3
> [13:20:09] New version is available at ignite.apache.org: 1.7.0
> >>> Restarting server node...
> [13:20:09]

[jira] [Assigned] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4322:
--

Assignee: Pavel Tupitsyn

> .NET: ClientReconnectExample is not clear enough 
> -
>
> Key: IGNITE-4322
> URL: https://issues.apache.org/jira/browse/IGNITE-4322
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> ClientReconnectExample has the following output
> {noformat}
> >>> Client reconnect example started.
> [13:19:53]__  
> [13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:19:53]  _/ // (7 7// /  / / / _/
> [13:19:53] /___/\___/_/|_/___/ /_/ /___/
> [13:19:53]
> [13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:19:53] 2016 Copyright(C) Apache Software Foundation
> [13:19:53]
> [13:19:53] Ignite documentation: http://ignite.apache.org
> [13:19:53]
> [13:19:53] Quiet mode.
> [13:19:53]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:19:53]
> [13:19:53] OS: Windows 10 10.0 amd64
> [13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:19:53] Configured plugins:
> [13:19:53]   ^-- None
> [13:19:53]
> [13:19:58] Security status [authentication=off, tls/ssl=off]
> [13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
> [13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [13:19:59]   ^-- Disable fully synchronous writes (set 
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [13:19:59]
> [13:19:59] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:19:59]
> [13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
> [13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
> >>> Server node started.
> [13:20:00]__  
> [13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
> [13:20:00]  _/ // (7 7// /  / / / _/
> [13:20:00] /___/\___/_/|_/___/ /_/ /___/
> [13:20:00]
> [13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
> [13:20:00] 2016 Copyright(C) Apache Software Foundation
> [13:20:00]
> [13:20:00] Ignite documentation: http://ignite.apache.org
> [13:20:00]
> [13:20:00] Quiet mode.
> [13:20:00]   ^-- Logging to file 
> 'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
> [13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:20:00]
> [13:20:00] OS: Windows 10 10.0 amd64
> [13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
> [13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:20:00] Configured plugins:
> [13:20:00]   ^-- None
> [13:20:00]
> [13:20:00] Security status [authentication=off, tls/ssl=off]
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> [13:20:02] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [13:20:02]
> [13:20:02] Ignite node started OK (id=2f5922f5)
> [13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
> >>> Client node connected to the cluster.
> >>> Put value with key:0
> >>> Put value with key:1
> >>> Put value with key:2
> [13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi]
>  Failed to send message: TcpDiscoveryClientPingRequest 
> [nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
> super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
> id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
> topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
> java.net.SocketException: Socket is closed
> at java.net.Socket.getOutputStream(Socket.java:943)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
> >>> Put value with key:3
> [13:20:09] New version is available at ignite.apache.org: 1.7.0
> >>> Restarting server node...
> 

[jira] [Created] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4322:
---

 Summary: .NET: ClientReconnectExample is not clear enough 
 Key: IGNITE-4322
 URL: https://issues.apache.org/jira/browse/IGNITE-4322
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova


ClientReconnectExample has the following output

{noformat}
>>> Client reconnect example started.
[13:19:53]__  
[13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
[13:19:53]  _/ // (7 7// /  / / / _/
[13:19:53] /___/\___/_/|_/___/ /_/ /___/
[13:19:53]
[13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:19:53] 2016 Copyright(C) Apache Software Foundation
[13:19:53]
[13:19:53] Ignite documentation: http://ignite.apache.org
[13:19:53]
[13:19:53] Quiet mode.
[13:19:53]   ^-- Logging to file 
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[13:19:53]
[13:19:53] OS: Windows 10 10.0 amd64
[13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[13:19:53] Configured plugins:
[13:19:53]   ^-- None
[13:19:53]
[13:19:58] Security status [authentication=off, tls/ssl=off]
[13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
[13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[13:19:59]   ^-- Disable fully synchronous writes (set 
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[13:19:59]
[13:19:59] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:19:59]
[13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
[13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
>>> Server node started.
[13:20:00]__  
[13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
[13:20:00]  _/ // (7 7// /  / / / _/
[13:20:00] /___/\___/_/|_/___/ /_/ /___/
[13:20:00]
[13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:00] 2016 Copyright(C) Apache Software Foundation
[13:20:00]
[13:20:00] Ignite documentation: http://ignite.apache.org
[13:20:00]
[13:20:00] Quiet mode.
[13:20:00]   ^-- Logging to file 
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[13:20:00]
[13:20:00] OS: Windows 10 10.0 amd64
[13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[13:20:00] Configured plugins:
[13:20:00]   ^-- None
[13:20:00]
[13:20:00] Security status [authentication=off, tls/ssl=off]
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
[13:20:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:20:02]
[13:20:02] Ignite node started OK (id=2f5922f5)
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
>>> Client node connected to the cluster.
>>> Put value with key:0
>>> Put value with key:1
>>> Put value with key:2
[13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi] 
Failed to send message: TcpDiscoveryClientPingRequest 
[nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:943)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
>>> Put value with key:3
[13:20:09] New version is available at ignite.apache.org: 1.7.0
>>> Restarting server node...
[13:20:09]__  
[13:20:09]   /  _/ ___/ |/ /  _/_  __/ __/
[13:20:09]  _/ // (7 7// /  / / / _/
[13:20:09] /___/\___/_/|_/___/ /_/ /___/
[13:20:09]
[13:20:09] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:09] 2016 Copyright(C) Apache Software Foundation
[13:20:09]
[13:20:09] Ignite documentation: http://ignite.apache.org
[13:20:09]
[13:20:09] Quiet mode.
[13:20:09]   ^-- Logging to file 

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4312.
-
Resolution: Duplicate

> 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] [Created] (IGNITE-4321) Cassandra modules

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4321:
-

 Summary: Cassandra modules
 Key: IGNITE-4321
 URL: https://issues.apache.org/jira/browse/IGNITE-4321
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


Binary fabric edition now has following modules:
{noformat}
 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:13   964 README.txt
   1 файлов964 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1353 231 asm-5.0.3.jar
25.11.2016  22:1312 181 
ignite-cassandra-serializers-1.8.0-QASK2502.jar
25.11.2016  22:13   285 211 kryo-3.0.3.jar
25.11.2016  22:13  licenses
25.11.2016  22:13 5 711 minlog-1.3.0.jar
25.11.2016  22:1341 755 objenesis-2.1.jar
25.11.2016  22:13 1 345 README.txt
25.11.2016  22:1320 738 reflectasm-1.10.1.jar
   7 файлов420 172 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers\licenses

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1311 358 apache-2.0.txt
25.11.2016  22:13 1 857 ignite-cassandra-serializers-licenses.txt
   2 файлов 13 215 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:13   990 392 cassandra-driver-core-3.0.0.jar
25.11.2016  22:13   232 019 commons-beanutils-1.8.3.jar
25.11.2016  22:13 2 308 517 guava-19.0.jar
25.11.2016  22:1391 897 ignite-cassandra-store-1.8.0-QASK2502.jar
25.11.2016  22:13  licenses
25.11.2016  22:1385 448 metrics-core-3.0.2.jar
25.11.2016  22:13   196 881 netty-buffer-4.0.33.Final.jar
25.11.2016  22:13   145 779 netty-codec-4.0.33.Final.jar
25.11.2016  22:13   441 447 netty-common-4.0.33.Final.jar
25.11.2016  22:13   272 139 netty-handler-4.0.33.Final.jar
25.11.2016  22:13   349 164 netty-transport-4.0.33.Final.jar
25.11.2016  22:13 1 228 README.txt
  11 файлов  5 114 911 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store\licenses

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1311 358 apache-2.0.txt
25.11.2016  22:13   294 ignite-cassandra-store-licenses.txt
   2 файлов 11 652 байт

{noformat}

I suppose that {{ignite-cassandra}} directory must be removed and rest of 
Cassandra modules should be joined into one.



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

[jira] [Reopened] (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 reopened IGNITE-4305:
---

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

Roman Shtykh commented on IGNITE-4243:
--

Yes, the related issue IGNITE-4233.

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

Ilya Suntsov edited comment on IGNITE-4243 at 11/28/16 9:21 AM:


[~roman_s]
Did you add docs on https://apacheignite.readme.io/docs ?


was (Author: ustas):
[~roman_s]
Did you add docs about examples on https://apacheignite.readme.io/docs ?

> 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-4320) Minor fixes in DmlStatementsProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4320:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4320 Minor fixes inside DML engine



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

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

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

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


commit 78313af8699130b0f6dee16bd5c969224e640a8b
Author: Alexander Paschenko 
Date:   2016-11-27T17:52:50Z

IGNITE-4320 Minor fixes inside DML engine




> Minor fixes in DmlStatementsProcessor
> -
>
> Key: IGNITE-4320
> URL: https://issues.apache.org/jira/browse/IGNITE-4320
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> 1. Important local variable renamed to more sane name
> 2. Removed duplicate operation manipulations in doUpdate
> 3. Small optimization in doUpdate (don't read key fields as we won't use them 
> anyway)



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

Ilya Suntsov commented on IGNITE-4243:
--

[~roman_s]
Did you add docs about examples on https://apacheignite.readme.io/docs ?

> 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-4320) Minor fixes in DmlStatementsProcessor

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-4320:

Fix Version/s: 1.8

> Minor fixes in DmlStatementsProcessor
> -
>
> Key: IGNITE-4320
> URL: https://issues.apache.org/jira/browse/IGNITE-4320
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> 1. Important local variable renamed to more sane name
> 2. Removed duplicate operation manipulations in doUpdate
> 3. Small optimization in doUpdate (don't read key fields as we won't use them 
> anyway)



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

[jira] [Updated] (IGNITE-4320) Minor fixes in DmlStatementsProcessor

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-4320:

Component/s: SQL

> Minor fixes in DmlStatementsProcessor
> -
>
> Key: IGNITE-4320
> URL: https://issues.apache.org/jira/browse/IGNITE-4320
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> 1. Important local variable renamed to more sane name
> 2. Removed duplicate operation manipulations in doUpdate
> 3. Small optimization in doUpdate (don't read key fields as we won't use them 
> anyway)



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

[jira] [Created] (IGNITE-4320) Minor fixes in DmlStatementsProcessor

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4320:
---

 Summary: Minor fixes in DmlStatementsProcessor
 Key: IGNITE-4320
 URL: https://issues.apache.org/jira/browse/IGNITE-4320
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.8
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko


1. Important local variable renamed to more sane name
2. Removed duplicate operation manipulations in doUpdate
3. Small optimization in doUpdate (don't read key fields as we won't use them 
anyway)



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

[jira] [Updated] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-4319:

Component/s: SQL

> Fix IgniteCacheAbstractSqlDmlQuerySelfTest
> --
>
> Key: IGNITE-4319
> URL: https://issues.apache.org/jira/browse/IGNITE-4319
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> Somehow it's green on TC in non binary mode but fails locally. Purely test 
> problem.



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

[jira] [Updated] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-4319:

Fix Version/s: 1.8

> Fix IgniteCacheAbstractSqlDmlQuerySelfTest
> --
>
> Key: IGNITE-4319
> URL: https://issues.apache.org/jira/browse/IGNITE-4319
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> Somehow it's green on TC in non binary mode but fails locally. Purely test 
> problem.



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

[jira] [Commented] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4319:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4319 Test fix



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

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

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

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






> Fix IgniteCacheAbstractSqlDmlQuerySelfTest
> --
>
> Key: IGNITE-4319
> URL: https://issues.apache.org/jira/browse/IGNITE-4319
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>
> Somehow it's green on TC in non binary mode but fails locally. Purely test 
> problem.



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

[jira] [Updated] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-4319:

Affects Version/s: 1.8

> Fix IgniteCacheAbstractSqlDmlQuerySelfTest
> --
>
> Key: IGNITE-4319
> URL: https://issues.apache.org/jira/browse/IGNITE-4319
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>
> Somehow it's green on TC in non binary mode but fails locally. Purely test 
> problem.



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

[jira] [Assigned] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4319:
---

Assignee: Alexander Paschenko

> Fix IgniteCacheAbstractSqlDmlQuerySelfTest
> --
>
> Key: IGNITE-4319
> URL: https://issues.apache.org/jira/browse/IGNITE-4319
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>
> Somehow it's green on TC in non binary mode but fails locally. Purely test 
> problem.



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

[jira] [Created] (IGNITE-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4319:
---

 Summary: Fix IgniteCacheAbstractSqlDmlQuerySelfTest
 Key: IGNITE-4319
 URL: https://issues.apache.org/jira/browse/IGNITE-4319
 Project: Ignite
  Issue Type: Test
Reporter: Alexander Paschenko


Somehow it's green on TC in non binary mode but fails locally. Purely test 
problem.



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

[jira] [Closed] (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 closed IGNITE-4313.
-

> 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: 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] [Commented] (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:comment-tabpanel=15701346#comment-15701346
 ] 

Sergey Kozlov commented on IGNITE-4313:
---

I agree. Let's close to for now.

> 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: 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}
> 

[jira] [Assigned] (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 reassigned IGNITE-4313:
-

Assignee: Sergey Kozlov  (was: 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: 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}
> 

[jira] [Created] (IGNITE-4318) GridNioEmbeddedFuture and GridEmbeddedFuture have different interface and behaviour.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4318:


 Summary: GridNioEmbeddedFuture and GridEmbeddedFuture have 
different interface and behaviour.
 Key: IGNITE-4318
 URL: https://issues.apache.org/jira/browse/IGNITE-4318
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Denis Kholodov


{{GridNioEmbeddedFuture}} should be put in line with {{GridEmbeddedFuture}}. 
Tests should look similar.



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

[jira] [Updated] (IGNITE-4317) Redesign Queries Screen

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4317:
-
Description: Simplify queries screen to implement divide execute action to 
SCAN and QUERY actions.  (was: Simplify queries screen to implement divide 
execute action and sql action)

> Redesign Queries Screen
> ---
>
> Key: IGNITE-4317
> URL: https://issues.apache.org/jira/browse/IGNITE-4317
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
>
> Simplify queries screen to implement divide execute action to SCAN and QUERY 
> actions.



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

[jira] [Created] (IGNITE-4317) Redesign Queries Screen

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-4317:


 Summary: Redesign Queries Screen
 Key: IGNITE-4317
 URL: https://issues.apache.org/jira/browse/IGNITE-4317
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin


Simplify queries screen to implement divide execute action and sql action



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

[jira] [Updated] (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:all-tabpanel
 ]

Roman Shtykh updated IGNITE-4244:
-
Description: Making INCR/DECR behave as expected by Redis.  (was: "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)

> 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
>
>
> Making INCR/DECR behave as expected by Redis.



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

[jira] [Created] (IGNITE-4316) visorcmd: batch mode works incorrect in some case

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-4316:
--

 Summary: visorcmd: batch mode works incorrect in some case
 Key: IGNITE-4316
 URL: https://issues.apache.org/jira/browse/IGNITE-4316
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 1.8
Reporter: Pavel Konstantinov
 Fix For: 1.9


I've faced with incorrect working in case of such run:
"ignitevisorcmd -np -e=open;1;top;node;0"

I'm expected the following execution of this command:
1) open connection with config file by number 1 in the list
2) execute 'top'
3) execute 'node' command selected node number 0

But really visor executed 'open'   with default config (config with number 0) 
and do not use node number in command 'node;0'

Another issue if I set commands inside quotes "open;1;top;node;0"
In this case visor prints "Input string is too long".



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