[jira] [Commented] (IGNITE-6846) Add metrics for entry processor invocations

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-6846:
-

[~Alexey Kuznetsov], I'm sorry for delays from my side, but looks like there 
are conflicts with master again. Can you please take a look?

> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
>  Labels: iep-6
> Fix For: 2.5
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations 
> like {{get}}, {{put}} and {{remove}}, but nothing for 
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for 
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7874) Update of an enum through jdbc yields a flag mismatch when object is retrieved through get

[Danny Mui (JIRA)]

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

Danny Mui updated IGNITE-7874:
--
Environment: (was: Sample maven project:
https://github.com/dannymui/igniteReport

mvn test

)
Description: 
Sample maven project:
https://github.com/dannymui/igniteReport

JDBC query update is issued and then the object fails to be deserialized with 
the stack trace below.

one is the binaryEnum and the other is the standard enum.

javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Unexpected field type [pos=24, expected=Enum, actual=Enum]
 at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1287)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1648)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:831)
 at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:662)
 at com.mycompany.app.AppTest.enum_update(AppTest.java:55)
 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:497)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
 at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)
Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected field 
type [pos=24, expected=Enum, actual=Enum]
 at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7252)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4512)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4493)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1326)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:828)
 ... 25 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Unexpected 
field type [pos=24, expected=Enum, actual=Enum]
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1676)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readEnum0(BinaryReaderExImpl.java:1403)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readEnum(BinaryReaderExImpl.java:1387)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:862)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:679)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
 at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
 at 

[jira] [Created] (IGNITE-7874) Update of an enum through jdbc yields a flag mismatch when object is retrieved through get

[Danny Mui (JIRA)]

Danny Mui created IGNITE-7874:
-

 Summary: Update of an enum through jdbc yields a flag mismatch 
when object is retrieved through get
 Key: IGNITE-7874
 URL: https://issues.apache.org/jira/browse/IGNITE-7874
 Project: Ignite
  Issue Type: Bug
  Components: binary, jdbc
Affects Versions: 2.3
 Environment: Sample maven project:
https://github.com/dannymui/igniteReport

mvn test


Reporter: Danny Mui


JDBC query update is issued and then the object fails to be deserialized with 
the stack trace below.

one is the binaryEnum and the other is the standard enum.

javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Unexpected field type [pos=24, expected=Enum, actual=Enum]
 at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1287)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1648)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:831)
 at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:662)
 at com.mycompany.app.AppTest.enum_update(AppTest.java:55)
 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:497)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
 at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)
Caused by: class org.apache.ignite.IgniteCheckedException: Unexpected field 
type [pos=24, expected=Enum, actual=Enum]
 at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7252)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4512)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4493)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1326)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:828)
 ... 25 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Unexpected 
field type [pos=24, expected=Enum, actual=Enum]
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlagNoHandles(BinaryReaderExImpl.java:1676)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readEnum0(BinaryReaderExImpl.java:1403)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readEnum(BinaryReaderExImpl.java:1387)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:862)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:679)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
 at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
 at 

[jira] [Comment Edited] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri edited comment on IGNITE-7655 at 3/2/18 10:49 PM:
-

Attached is an example using Java.

[^JavaIgniteDataFrameExample.java]

Probably needs improvement, but it works.


was (Author: abchaudhri):
Attached is an example using Java.

[^JavaIgniteDataFrameExample.java]

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteDataFrameExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri edited comment on IGNITE-7655 at 3/2/18 10:41 PM:
-

Attached is an example using Java.

[^JavaIgniteDataFrameExample.java]


was (Author: abchaudhri):
Attached is an example using Java.


[^JavaIgniteDataFrameExample.java]

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteDataFrameExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri commented on IGNITE-7655:


Attached is an example using Java.


[^JavaIgniteDataFrameExample.java]

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteDataFrameExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri updated IGNITE-7655:
---
Attachment: JavaIgniteDataFrameExample.java

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteDataFrameExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7253) JDBC thin driver: introduce streaming mode

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-7253:
-

[~vozerov], all fixed.

> JDBC thin driver: introduce streaming mode
> --
>
> Key: IGNITE-7253
> URL: https://issues.apache.org/jira/browse/IGNITE-7253
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: IGNITE_7253.patch
>
>
> Should be done after IGNITE-6022. We should allow optional streaming mode for 
> JDBC driver. In this mode only INSERTs without SELECT should be possible. All 
> other DML operations should throw an exception. 
> Design considerations:
> 1) Add command {{SET STREAMING=1|ON|0|OFF}} which will enable or disable 
> streaming for connection.
> 2) Add command {{STREAMER FLUSH}} which will force data flush.
> 3) Only INSERT without SELECT works, all other DML statements should throw an 
> exception
> 4) It should be possible to stream into several tables simultaneously (i.e. 
> several streamers could be opened)
> 5) Any DDL statement should force flush of all currently opened streamers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri commented on IGNITE-7655:


[~vkulichenko], [~NIzhikov], thank you.

[~dmagda] assisted me today and we were able to get some simple Java code 
working with Ignite DataFrames. I need to look further at the Spark 
documentation and I think I will have the equivalent Java code ready quite soon.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-7655:
-

[~abchaudhri], this is actually Spark API not Ignite API, so I think you should 
look for Java examples in Spark and them adapt them to Ignite.

[~NIzhikov], probably makes sense to create a Java example for data frames 
integration and include it into the product. Can you please create a ticket?

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7873) Partition update counters and sizes may be different if cache is using readThrough

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7873:
---

 Summary: Partition update counters and sizes may be different if 
cache is using readThrough
 Key: IGNITE-7873
 URL: https://issues.apache.org/jira/browse/IGNITE-7873
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko


Tracking partition update counters and cache sizes may not properly work if 
cache is using readThrough behavior.

Read requests to such cache can increment update counters or cache sizes not on 
all nodes serving such cache in case if data in underlying storage is changed.
It means that update counter or cache size will be incremented only on 
partition where we followed such request (primary or any random node).

BackupPostProcessingClosure should use preload=false for entry. In other case 
it can increment update counter for read request while data is not changed.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-6083:
--

[~agoncharuk] Hi!

 

I've fixed test, checked failed tests in TC run and now its ok, plz review it : 
[new TC 
run|https://ci.ignite.apache.org/viewQueued.html?itemId=1118525=queuedBuildOverviewTab]

> Null value have appear in the entry processor, but the entry is existing
> 
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute 
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}} 
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at 
> second.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7872) Actualize code style rules in Ignite

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov edited comment on IGNITE-7872 at 3/2/18 4:03 PM:


[~agoncharuk], could you please  pick up this issue?


was (Author: dpavlov):
[~agoncharuk], could please you pick up this issue?

> Actualize code style rules in Ignite
> 
>
> Key: IGNITE-7872
> URL: https://issues.apache.org/jira/browse/IGNITE-7872
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Minor
>
> Code style used by Ignite contributors ( ignite\idea\ignite_codeStyle.xml ) 
> is outdated now.
> Need to update code style with new suggestions
> Operators (newline)
> Lamdas (Java 8)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7872) Actualize code style rules in Ignite

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7872:


[~agoncharuk], could please you pick up this issue?

> Actualize code style rules in Ignite
> 
>
> Key: IGNITE-7872
> URL: https://issues.apache.org/jira/browse/IGNITE-7872
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Minor
>
> Code style used by Ignite contributors ( ignite\idea\ignite_codeStyle.xml ) 
> is outdated now.
> Need to update code style with new suggestions
> Operators (newline)
> Lamdas (Java 8)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7872) Actualize code style rules in Ignite

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7872:
--

 Summary: Actualize code style rules in Ignite
 Key: IGNITE-7872
 URL: https://issues.apache.org/jira/browse/IGNITE-7872
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov


Code style used by Ignite contributors ( ignite\idea\ignite_codeStyle.xml ) is 
outdated now.

Need to update code style with new suggestions
Operators (newline)
Lamdas (Java 8)




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7871) Partition update counters may be different during exchange

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7871:
---

 Summary: Partition update counters may be different during exchange
 Key: IGNITE-7871
 URL: https://issues.apache.org/jira/browse/IGNITE-7871
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko


Using validation implemented in IGNITE-7467 we can observe the following 
situation:

Let's we have some partition and nodes which owning it N1 (primary) and N2 
(backup)

1) Exchange is started
2) N2 finished waiting for partitions release and started to create Single 
message (with update counters).
3) N1 waits for partitions release.
4) We have pending cache update N1 -> N2. This update is done after step 2.
5) This update increments update counters both on N1 and N2.
6) N1 finished waiting for partitions release, while N2 already sent Single 
message to coordinator with outdated update counter.
7) Coordinator sees different partition update counters for N1 and N2. 
Validation is failed, while data is equal.  

Possible solutions:
1) Cancel transactions and atomic updates on backups if topology version on 
them is already changed (or waiting for partitions release is finished).
2) Each node participating in exchange should wait for partitions release of 
other nodes not only self (like distributed countdown latch right after waiting 
for partitions release).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7831) Throw Exceptions instead of AssertionErrors when reading from corrupted persistence

[Aleksey Plekhanov (JIRA)]

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

Aleksey Plekhanov commented on IGNITE-7831:
---

[~ilantukh], I search for assertions in the persistance implementation, there 
are about 7 hundreds occurrencies, but almost all of this assertions are used 
to ensure internal logic and not depend on external reasons.

Also, most of explicitly thrown AssertionErrors in the persistance 
implementation are rethrown assertions with additional information. 

I found only couple of cases which can potentialy match your description:

{{PageMemoryImpl#tryToRestorePage:}}
{code:java}
throw new AssertionError(String.format(
"Page is broken. Can't restore it from WAL. (grpId = %d, pageId = %X).",
fullId.groupId(), fullId.pageId()
));
{code}
{{GridTreePrinter#getChildren}}: 
{code:java}
catch (IgniteCheckedException ignored) {
throw new AssertionError("Can not acquire page.");
}
{code}
But this method used only for dumping debug information in the test framework.
  
 {{FilePageStoreManager#beforeCacheGroupStart}}:
{code:java}
assert dir.exists();
{code}
{{FilePageStoreManager#storeCacheData}}:
{code:java}
assert cacheWorkDir.exists() : "Work directory does not exist: " + cacheWorkDir;
{code}
But this method creates dir (and checks result code) before assertion.

Did you mean these cases or something else? If something else, do you have 
stacktraces or any description of real cases?

> Throw Exceptions instead of AssertionErrors when reading from corrupted 
> persistence
> ---
>
> Key: IGNITE-7831
> URL: https://issues.apache.org/jira/browse/IGNITE-7831
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ilya Lantukh
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: iep-14
> Fix For: 2.5
>
>
> There are a few places in our code where we explicitly throw AssertionErrors 
> due to inability to correctly read data from persistence and many more places 
> where we make assertions based on read values.
> Assertions are used to indicate problems in internal logic, while persistence 
> might also get corrupted by various external reasons. It also makes uniform 
> handling of such issues considerably harder, because exception handling logic 
> in Ignite ignores Errors. If we want to improve stability and minimize 
> consequenses of pesistence corruption, we should replace all those 
> AssertionErrors and asserts with Exceptions, so that current exception 
> handling mechanisms could be reduce. In a number of situations it means that 
> instead of causing cluster-wide hang-up problematic node will be 
> automatically killed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7870) Update Discovery and Communication Technical Docs

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7870:

Attachment: IgniteNetworkingOverview.md

> Update Discovery and Communication Technical Docs
> -
>
> Key: IGNITE-7870
> URL: https://issues.apache.org/jira/browse/IGNITE-7870
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteNetworkingOverview.md
>
>
> Existing discovery and communication pages are not in the best shape and 
> require an overhaul. Use the revisited version (attached) contributed by a 
> community member and see how to improve or mix discovery, communication, 
> servers & clients docs from readme.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7870) Update Discovery and Communication Technical Docs

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7870:
---

 Summary: Update Discovery and Communication Technical Docs
 Key: IGNITE-7870
 URL: https://issues.apache.org/jira/browse/IGNITE-7870
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
Assignee: Prachi Garg
 Fix For: 2.5
 Attachments: IgniteNetworkingOverview.md

Existing discovery and communication pages are not in the best shape and 
require an overhaul. Use the revisited version (attached) contributed by a 
community member and see how to improve or mix discovery, communication, 
servers & clients docs from readme.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7869) Dynamic start cache by stored cache data

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7869:


GitHub user akalash opened a pull request:

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

IGNITE-7869 Dynamic start cache by stored cache data



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13535-master

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

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


commit f8f701ea110a0dbd655b4a0ff23a85f1549ebd59
Author: Anton Kalashnikov 
Date:   2018-03-02T14:45:49Z

GG-13535 add storedCacheData to snapshot




> Dynamic start cache by stored cache data
> 
>
> Key: IGNITE-7869
> URL: https://issues.apache.org/jira/browse/IGNITE-7869
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> Dynamic start cache by stored cache data



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7869) Dynamic start cache by stored cache data

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-7869:
-

 Summary: Dynamic start cache by stored cache data
 Key: IGNITE-7869
 URL: https://issues.apache.org/jira/browse/IGNITE-7869
 Project: Ignite
  Issue Type: Improvement
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov


Dynamic start cache by stored cache data



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7253) JDBC thin driver: introduce streaming mode

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-7253 at 3/2/18 12:56 PM:
--

[~al.psc], my comments:
1) ConnectionPropertiesImpl.LongProperty - appears to be a dead code
2) org.apache.ignite.internal.jdbc.thin.JdbcThinConnection#setStream - dead code
3) JdbcThinStatement.isEligibleForNativeParsing - executed twice every time. 
Why?
4) GridQueryProcessor.cliCtxs - why do we need to track these objects? AFAIK 
data streamers are already closed by DataStreamerProcessor during node stop
5) JdbcThinConnection - why do we need {{synchronized}} on some methods? 
Connection is single-threaded object already.
6) JdbcThinConnection.drainBatchToStreamIfNeeded - looks like it would return 
incorrect update count when executed on half-formed batch; IMO it is better to 
throw an exception if there is something prebatched.
7) Looks like it is allowed to execute DDL statements in streaming mode at the 
moment ({{streamBatchedUpdateQuery}} -> 
{{tryQueryDistributedSqlFieldsNative}}), which is wrong. Instead of adding a 
command to batch, I would set a special flag in it to close the streaming. This 
way you would not have to parse {{STREAMING OFF}} on the server.


was (Author: vozerov):
[~al.psc], my comments:
1) ConnectionPropertiesImpl.LongProperty - appears to be a dead code
2) org.apache.ignite.internal.jdbc.thin.JdbcThinConnection#setStream - dead code
3) JdbcThinStatement.isEligibleForNativeParsing - executed twice every time. 
Why?
4) GridQueryProcessor.cliCtxs - why do we need to track these objects? AFAIK 
data streamers are already closed by DataStreamerProcessor during node stop
5) JdbcThinConnection - why do we need {{synchronized}} on some methods? 
Connection is single-threaded object already.
6) JdbcThinConnection.drainBatchToStreamIfNeeded - looks like it would return 
incorrect update count when executed on half-formed batch; IMO it is better to 
throw an exception if there is something prebatched.

> JDBC thin driver: introduce streaming mode
> --
>
> Key: IGNITE-7253
> URL: https://issues.apache.org/jira/browse/IGNITE-7253
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: IGNITE_7253.patch
>
>
> Should be done after IGNITE-6022. We should allow optional streaming mode for 
> JDBC driver. In this mode only INSERTs without SELECT should be possible. All 
> other DML operations should throw an exception. 
> Design considerations:
> 1) Add command {{SET STREAMING=1|ON|0|OFF}} which will enable or disable 
> streaming for connection.
> 2) Add command {{STREAMER FLUSH}} which will force data flush.
> 3) Only INSERT without SELECT works, all other DML statements should throw an 
> exception
> 4) It should be possible to stream into several tables simultaneously (i.e. 
> several streamers could be opened)
> 5) Any DDL statement should force flush of all currently opened streamers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7777) Thin Client lib: Node.js

[Alexey Kosenchuk (JIRA)]

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

Alexey Kosenchuk updated IGNITE-:
-
Description: 
Implement Thin (lightweight) Client lib in Node.js programming language for 
Ignite Binary Client Protocol.

Examples of other Thin Clients:
.net 
https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client
java https://github.com/gridgain/apache-ignite/tree/ignite-7421
https://apacheignite.readme.io/v2.3/docs/java-thin-client

Scope of work
-

Functionality:

Support all operations of the Ignite Binary Client Protocol 2.4:
https://apacheignite.readme.io/docs/binary-client-protocol
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol

Support name/password authentication - TBD (not in the protocol yet).
Support optional SSL/TLS communication.

Support failover/reconnect algorithm:
https://issues.apache.org/jira/browse/IGNITE-7282
http://apache-ignite-developers.2346864.n4.nabble.com/Thin-client-failover-mechanism-ODBC-JDBC-td26553.html

Minimal Node.js version - TBD.
Synch ops emulation - callbacks, or Promises, or asynch/await - TBD.

Examples:
Cover all basic features - Key-value API, SQL, Scan queries, Cluster 
configuration/management, Authentication, SSL/TLS.

Tests:
Jasmine tests for all API methods and all basic features.
Simple Jasmine tests to start examples.
How to emulate node failure to test failover/reconnect? - TBD.

Docs:
Auto-generated API spec from jsdoc comments:
http://usejsdoc.org/
https://www.npmjs.com/package/jsdoc

Readme for the lib.
Simple instruction to setup/run examples.
Simple instruction to setup/run Jasmine tests.

Docs should be on readme.io

 

  was:
Implement Thin (lightweight) Client lib in Node.js programming language for 
Ignite Binary Client Protocol 
https://apacheignite.readme.io/docs/binary-client-protocol

Examples of other Thin Clients:
.net 
https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client
java 
https://github.com/gridgain/apache-ignite/tree/ignite-7421/modules/thinclient

Scope of work
-

Functionality:
Support all operations of the Ignite Binary Client Protocol 2.4.
Support name/password authentication - TBD (not in the protocol yet).
Support optional SSL/TLS communication - TBD (not in the protocol yet).
Support optional failover/reconnect - TBD.

Minimal Node.js version - TBD.
Synch ops emulation - callbacks, or Promises, or asynch/await - TBD.

Examples:
Cover all basic features - Key-value API, SQL, Scan queries, Cluster 
configuration/management, Authentication, SSL/TLS.

Tests:
Jasmine tests for all API methods and all basic features.
Simple Jasmine tests to start examples.
How to emulate node failure to test failover/reconnect? - TBD.

Docs:
Auto-generated API spec from comments. JSdoc, or javadoc, or what? - TBD.
Readme for the lib.
Simple instruction to setup/run examples.
Simple instruction to setup/run Jasmine tests.

Docs format - .md in the repo, or dash.readme.io ? - TBD.

 


> Thin Client lib: Node.js
> 
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Alexey Kosenchuk
>Assignee: Alexey Kosenchuk
>Priority: Major
>
> Implement Thin (lightweight) Client lib in Node.js programming language for 
> Ignite Binary Client Protocol.
> Examples of other Thin Clients:
> .net 
> https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client
> java https://github.com/gridgain/apache-ignite/tree/ignite-7421
> https://apacheignite.readme.io/v2.3/docs/java-thin-client
> Scope of work
> -
> Functionality:
> Support all operations of the Ignite Binary Client Protocol 2.4:
> https://apacheignite.readme.io/docs/binary-client-protocol
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol
> Support name/password authentication - TBD (not in the protocol yet).
> Support optional SSL/TLS communication.
> Support failover/reconnect algorithm:
> https://issues.apache.org/jira/browse/IGNITE-7282
> http://apache-ignite-developers.2346864.n4.nabble.com/Thin-client-failover-mechanism-ODBC-JDBC-td26553.html
> Minimal Node.js version - TBD.
> Synch ops emulation - callbacks, or Promises, or asynch/await - TBD.
> Examples:
> Cover all basic features - Key-value API, SQL, Scan queries, Cluster 
> configuration/management, Authentication, SSL/TLS.
> Tests:
> Jasmine tests for all API methods and all basic features.
> Simple Jasmine tests to start examples.
> How to emulate node failure to test failover/reconnect? - TBD.
> Docs:
> Auto-generated API spec from jsdoc comments:
> http://usejsdoc.org/
> 

[jira] [Commented] (IGNITE-7253) JDBC thin driver: introduce streaming mode

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-7253:
-

[~al.psc], my comments:
1) ConnectionPropertiesImpl.LongProperty - appears to be a dead code
2) org.apache.ignite.internal.jdbc.thin.JdbcThinConnection#setStream - dead code
3) JdbcThinStatement.isEligibleForNativeParsing - executed twice every time. 
Why?
4) GridQueryProcessor.cliCtxs - why do we need to track these objects? AFAIK 
data streamers are already closed by DataStreamerProcessor during node stop
5) JdbcThinConnection - why do we need {{synchronized}} on some methods? 
Connection is single-threaded object already.
6) JdbcThinConnection.drainBatchToStreamIfNeeded - looks like it would return 
incorrect update count when executed on half-formed batch; IMO it is better to 
throw an exception if there is something prebatched.

> JDBC thin driver: introduce streaming mode
> --
>
> Key: IGNITE-7253
> URL: https://issues.apache.org/jira/browse/IGNITE-7253
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: IGNITE_7253.patch
>
>
> Should be done after IGNITE-6022. We should allow optional streaming mode for 
> JDBC driver. In this mode only INSERTs without SELECT should be possible. All 
> other DML operations should throw an exception. 
> Design considerations:
> 1) Add command {{SET STREAMING=1|ON|0|OFF}} which will enable or disable 
> streaming for connection.
> 2) Add command {{STREAMER FLUSH}} which will force data flush.
> 3) Only INSERT without SELECT works, all other DML statements should throw an 
> exception
> 4) It should be possible to stream into several tables simultaneously (i.e. 
> several streamers could be opened)
> 5) Any DDL statement should force flush of all currently opened streamers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7865:


Github user asfgit closed the pull request at:

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


> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7809:


[~ilantukh], [~agoncharuk], can we merge 
 1. partial fix for existing tests 
 2. and later new cases tests

> Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
> IgniteWalFlushDefaultSelfTest
> 
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
>Ignite PDS 2 (Direct IO) [ tests 2 ]  
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%) 
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%) 
>Ignite PDS 2 [ tests 2 ]  
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart 
> (fail rate 8,4%) 
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart 
> (fail rate 8,4%) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7782) Thin Client lib: Python

[Alexey Kosenchuk (JIRA)]

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

Alexey Kosenchuk updated IGNITE-7782:
-
Description: 
Implement Thin (lightweight) Client lib in Python programming language for 
Ignite Binary Client Protocol 
https://apacheignite.readme.io/docs/binary-client-protocol

Prototype:
https://github.com/skozlov-gridgain/apache-ignite-python-thin-client


  was:Implement Thin (lightweight) Client lib in Python programming language 
for Ignite Binary Client Protocol 
https://apacheignite.readme.io/docs/binary-client-protocol


> Thin Client lib: Python
> ---
>
> Key: IGNITE-7782
> URL: https://issues.apache.org/jira/browse/IGNITE-7782
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Alexey Kosenchuk
>Assignee: Alexey Kosenchuk
>Priority: Major
>
> Implement Thin (lightweight) Client lib in Python programming language for 
> Ignite Binary Client Protocol 
> https://apacheignite.readme.io/docs/binary-client-protocol
> Prototype:
> https://github.com/skozlov-gridgain/apache-ignite-python-thin-client



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7712) Add an ability to globally enable 'lazy' flag for SQL queries

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7712:


Assignee: Vladimir Ozerov  (was: Alexey Kuznetsov)

[~vozerov] I merged UI changed. Please proceed with server-side.

> Add an ability to globally enable 'lazy' flag for SQL queries
> -
>
> Key: IGNITE-7712
> URL: https://issues.apache.org/jira/browse/IGNITE-7712
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.5
>
>
> We have the {{lazy}} flag that can be set when a particular query is 
> executed, it's disabled by default.
> In some cases it can be useful to enable this flag globally, especially it 
> makes sense for the tools like Visor and Web Console.
> Let's do the following:
>  * Set it to {{true}} by default in Web Console.
>  * Add a system property that will allow to do the same on node level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7866) TcpCommunicationSpi metrics causes cache operations slowdown

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7866:


Github user devozerov closed the pull request at:

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


> TcpCommunicationSpi metrics causes cache operations slowdown
> 
>
> Key: IGNITE-7866
> URL: https://issues.apache.org/jira/browse/IGNITE-7866
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.4
>
>
> Extended TCP metrics were added as a part of IGNITE-6868 ticket. 
> Unfortunately, they causes ~5-10% performance drop for cache operations when 
> working in in-memory mode. Causes:
> 1) Contention on shared data structures (LongAdder, CMH)
> 2) A lot of string comparisons because we use class names to track particulat 
> message types
> Suggested fix:
> 1) Move all processing to NIO threads
> 2) Introcduce thread-local state and update it from NIO threads
> 3) Metrics readers should merge state from all NIO threads
> 4) User {{Message}} type ID instead of class names
> 5) When returning final result we should use {{Class.getName()}} instead of 
> {{Class.getSimpleName()}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7851:
--

TC run:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F3595%2Fhead

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
> errMsgChars, Int32 errMsgCharsLen, SByte* 

[jira] [Resolved] (IGNITE-7866) TcpCommunicationSpi metrics causes cache operations slowdown

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-7866.
-
Resolution: Fixed

> TcpCommunicationSpi metrics causes cache operations slowdown
> 
>
> Key: IGNITE-7866
> URL: https://issues.apache.org/jira/browse/IGNITE-7866
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.4
>
>
> Extended TCP metrics were added as a part of IGNITE-6868 ticket. 
> Unfortunately, they causes ~5-10% performance drop for cache operations when 
> working in in-memory mode. Causes:
> 1) Contention on shared data structures (LongAdder, CMH)
> 2) A lot of string comparisons because we use class names to track particulat 
> message types
> Suggested fix:
> 1) Move all processing to NIO threads
> 2) Introcduce thread-local state and update it from NIO threads
> 3) Metrics readers should merge state from all NIO threads
> 4) User {{Message}} type ID instead of class names
> 5) When returning final result we should use {{Class.getName()}} instead of 
> {{Class.getSimpleName()}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-5357) Replicated cache reads load balancing.

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-5357:
-

> https://github.com/apache/ignite/pull/3578

Looks good to me.

> Replicated cache reads load balancing.
> --
>
> Key: IGNITE-5357
> URL: https://issues.apache.org/jira/browse/IGNITE-5357
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Vyacheslav Daradur
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> Currently all read requests from client node to replicated cache will go 
> through primary node for key.
> Need to select random affinity node in topology and send request here (only 
> if readFromBackups=true)
> If where are server nodes collocated on same host with client, must select 
> target node from them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7868) Continuous Query LocalListener on backup node works unstable

[Dmitry Uskov (JIRA)]

Dmitry Uskov created IGNITE-7868:


 Summary: Continuous Query LocalListener on backup node works 
unstable
 Key: IGNITE-7868
 URL: https://issues.apache.org/jira/browse/IGNITE-7868
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Dmitry Uskov


 I have two nodes (*node1* and *node2*) with configuration:
{code:java}
Ignition.start();

ProgramContext.ignite = Ignition.ignite(); //ProgramContext.ignite is public 
static field

String cacheName = "A-Cache";

CacheConfiguration cacheConfiguration = new 
CacheConfiguration<>();
cacheConfiguration.setName(cacheName);
cacheConfiguration.setAtomicityMode(CacheAtomicityMode.ATOMIC);
cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
cacheConfiguration.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
cacheConfiguration.setBackups(1);

IgniteCache cache = 
ProgramContext.ignite.getOrCreateCache(cacheConfiguration);

ContinuousQuery query = new ContinuousQuery<>();

ClusterNode node = ProgramContext.ignite.cluster().localNode();

query.setRemoteFilterFactory((Factory>) () -> (CacheEntryEventFilter) event -> {
 boolean currentNodeIsPrimary = 
node.equals(ProgramContext.ignite.cluster().localNode());
 boolean eventTypeIsCreated = 
event.getEventType().equals(javax.cache.event.EventType.CREATED);
 return currentNodeIsPrimary && eventTypeIsCreated;
});
query.setLocalListener(cacheEntryEvents -> {
 for (CacheEntryEvent cacheEntryEvent 
: cacheEntryEvents) {
 System.out.println("CacheEntryUpdatedListener: " + cacheEntryEvent.getKey() + 
"/" + cacheEntryEvent.getValue());
 }
});
cache.query(query);
{code}
CacheKey:
{code:java}
public class CacheKey {

 public static final String DEFAULT_AFFINITY_KEY = "cons";

 private static String affinityKeyValue = DEFAULT_AFFINITY_KEY;

 private String key;

 @AffinityKeyMapped
 private String affinityKey;

 public CacheKey(String key) {
 this.key = key;
 this.affinityKey = affinityKeyValue; //always DEFAULT_AFFINITY_KEY 
 }

 //... getters/setters and toString()

}{code}
CacheValue:
{code:java}
public class CacheValue {

 private String value;

 public CacheValue(String value) {
 this.value = value;
 }
 //... getters/setters and toString()
 
}{code}
I put two values in cache. As affinityKey always equals DAFAULT_AFFINITY_KEY 
one node (suppose *node1*)  is primary for both values. LocalListener has 
worked twice on *node1*.

Console output:
{noformat}
CacheEntryUpdatedListener: CacheKey{key='node1-0', 
affinityKey='cons'}/CacheValue{value='node1-0'}
CacheEntryUpdatedListener: CacheKey{key='node1-1', 
affinityKey='cons'}/CacheValue{value='node1-1'}
{noformat}
 

Then I stoped it and I saw LocalListener on *node2* has worked once, but I 
expected LocalListener on *node2* had to work twice.

Console out node1:
{noformat}
[12:36:36] Ignite node stopped OK [uptime=00:00:14.243]{noformat}
Console out node2:
{noformat}
[12:36:36] Topology snapshot [ver=3, servers=1, clients=0, CPUs=4, heap=1.6GB]
CacheEntryUpdatedListener: CacheKey{key='node1-1', 
affinityKey='cons'}/CacheValue{value='node1-1'}{noformat}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7851:
--

[~isapego], [~skalashnikov]
Please review the changes.

I force the key type assignment for QueryEntity in .NET code if it is not 
passed. Java code does not have similar CacheConfiguration constructor, so it 
is better to fix at .NET side.

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> 

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7851:


GitHub user apopovgg opened a pull request:

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

IGNITE-7851: .NET: linq query throws Hexadecimal string with odd numb…

…er of characters exception

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

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

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

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


commit f0575df148e7c6e9a952a9da601adb09536914db
Author: apopov 
Date:   2018-03-02T09:54:39Z

IGNITE-7851: .NET: linq query throws Hexadecimal string with odd number of 
characters exception




> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)

[jira] [Created] (IGNITE-7867) Document new feature in REST: possibility to get objects inserted via API or SQL

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7867:


 Summary: Document new feature in REST: possibility to get objects 
inserted via API or SQL
 Key: IGNITE-7867
 URL: https://issues.apache.org/jira/browse/IGNITE-7867
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Alexey Kuznetsov
Assignee: Prachi Garg
 Fix For: 2.5


[~pgarg] Please document changes from IGNITE-7803.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (IGNITE-5357) Replicated cache reads load balancing.

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5357:
---
Comment: was deleted

(was: Hi, [~ascherbakov], I've updated [the 
PR|https://github.com/apache/ignite/pull/3578/files] to avoid memory's 
overhead. Please have a look, if you have time.

Now it covers {{get}} and {{getAll}} operations. I moved logic to 
{{GridCacheUtils}} since classes have no suitable common superclasses in the 
hierarchy.

New 
[ci.tests|https://ci.ignite.apache.org/viewLog.html?buildId=1115559=buildResultsDiv=IgniteTests24Java8_RunAll]
 look good.

About such optimization for {{READ_COMMITED}} mode, I'd like to implement it in 
a separate ticket, since it may need significant changes.)

> Replicated cache reads load balancing.
> --
>
> Key: IGNITE-5357
> URL: https://issues.apache.org/jira/browse/IGNITE-5357
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Vyacheslav Daradur
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> Currently all read requests from client node to replicated cache will go 
> through primary node for key.
> Need to select random affinity node in topology and send request here (only 
> if readFromBackups=true)
> If where are server nodes collocated on same host with client, must select 
> target node from them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7803) REST: Add support to get values inserted via API or SQL

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-7803.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master.

> REST: Add support to get values inserted via API or SQL
> ---
>
> Key: IGNITE-7803
> URL: https://issues.apache.org/jira/browse/IGNITE-7803
> Project: Ignite
>  Issue Type: Task
>  Components: rest
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Scenario 1:
>  # cache.put(1, new Person(1, Alex, 300))
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}
> Scenario 2:
>  # create table person(id integer primary key, name varchar(100), salary 
> integer);
>  # insert into person(id, name, salary) values (1, Alex, 300)
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin reassigned IGNITE-7865:
--

Assignee: Dmitriy Govorukhin

> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-7865:


[~agoncharuk] Please review my changes.

> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7866) TcpCommunicationSpi metrics causes cache operations slowdown

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7866:

Priority: Blocker  (was: Major)

> TcpCommunicationSpi metrics causes cache operations slowdown
> 
>
> Key: IGNITE-7866
> URL: https://issues.apache.org/jira/browse/IGNITE-7866
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.4
>
>
> Extended TCP metrics were added as a part of IGNITE-6868 ticket. 
> Unfortunately, they causes ~5-10% performance drop for cache operations when 
> working in in-memory mode. Causes:
> 1) Contention on shared data structures (LongAdder, CMH)
> 2) A lot of string comparisons because we use class names to track particulat 
> message types
> Suggested fix:
> 1) Move all processing to NIO threads
> 2) Introcduce thread-local state and update it from NIO threads
> 3) Metrics readers should merge state from all NIO threads
> 4) User {{Message}} type ID instead of class names
> 5) When returning final result we should use {{Class.getName()}} instead of 
> {{Class.getSimpleName()}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7865:


GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-7865 Supported serializerVersion method for WAL manager



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

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

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

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


commit 569836532000c0224132dc01c6b07366e4796f75
Author: Dmitriy Govorukhin 
Date:   2018-03-02T09:16:27Z

IGNITE-7865 Supported serializerVersion method for WAL manager




> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri commented on IGNITE-7655:


[~vkulichenko], I am trying to take the existing Scala code example:

[https://github.com/apache/ignite/blob/master/examples/src/main/spark/org/apache/ignite/examples/spark/IgniteDataFrameExample.scala]

and rewrite it for Java. I am blocked here for the moment:
{code:java}
val igniteDF = spark.read
.format(FORMAT_IGNITE) //Data source type.
.option(OPTION_TABLE, "person") //Table to read.
.option(OPTION_CONFIG_FILE, CONFIG) //Ignite config.
.load()
.filter(col("id") >= 2) //Filter clause.
.filter(col("name") like "%M%") //Another filter clause.
{code}
The Java code to create the tables works ok. However, I don't know Scala, so 
trying to do a conversion from one language to another is difficult.

> Spark Data Frames: saving data frames into Ignite needs to be documented
> 
>
> Key: IGNITE-7655
> URL: https://issues.apache.org/jira/browse/IGNITE-7655
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Nikolay Izhikov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.4
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7866) TcpCommunicationSpi metrics causes cache operations slowdown

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7866:


GitHub user devozerov opened a pull request:

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

IGNITE-7866



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

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

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

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


commit 4925ffc10ce8e8287980eaec38b587512568a302
Author: Alexey Goncharuk 
Date:   2018-01-17T12:26:03Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in PageSnapshot

commit bcd68a058683b2f17b7ac60471b6e7aab3e4f6de
Author: Pavel Tupitsyn 
Date:   2018-01-17T12:38:20Z

IGNITE-7301 .NET: Baseline topology

This closes #3352

commit 66b96316a7775ce8a6e2ff4475185d5929e4998b
Author: devozerov 
Date:   2018-01-17T12:54:17Z

Merge branch 'master' into ignite-2.4

commit 268481c1cf7fe57df24be130eb67c3e3a13afe01
Author: Alexey Goncharuk 
Date:   2018-01-17T13:50:34Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in WalStat

commit db0cd105719c8ae713b13b34d9dca0a8cd45d377
Author: Pavel Tupitsyn 
Date:   2018-01-17T14:05:25Z

IGNITE-6776 .NET: Thin client: Add SQL & LINQ example

This closes #3390

commit c214db879101aa5660e2a50b11cd20964c0bc114
Author: Andrey Gura 
Date:   2018-01-17T12:42:41Z

ignite-7450 FileWriteAheadLogManager always uses RandomAccessFileIOFactory 
now

commit 75c27d5e49d7458e46eb46e6f87a445c3f1320ea
Author: Alexey Kuznetsov 
Date:   2018-01-18T02:25:19Z

IGNITE-7274 Web Console: Support multiple statements on Queries screen.
(cherry picked from commit 1926783)

commit 36cc822935387b2150e690c29bc6992dca0563f7
Author: Dmitriy Shabalin 
Date:   2018-01-18T04:49:08Z

IGNITE-7306 Web Console: Fixed export data from tables.
(cherry picked from commit 1bb60ec)

commit d753298b4012894b56f5c9218325211cd84a21d5
Author: Peter Ivanov 
Date:   2018-01-18T06:18:53Z

IGNITE-7107 Apache Ignite RPM packages

* added changelog to package specification

This closes #3396

commit 63445893f1bc75dc9777184499f7eabc1d4e51b1
Author: Denis Mekhanikov 
Date:   2018-01-18T08:36:18Z

IGNITE-3935 Use PeerDeployAware for streamer transformer - Fixes #3378.

Signed-off-by: Alexey Goncharuk 

commit f3f9f2a24b23027cf0c835140322e41a788932ae
Author: Pavel Tupitsyn 
Date:   2018-01-18T09:05:12Z

IGNITE-7413 Fix SqlDmlExample

This closes #3389

commit 1daa7c41bf1460a4d9a2b0c26a7a317f2fca3fb7
Author: Alexey Kuznetsov 
Date:   2018-01-18T10:14:53Z

IGNITE-7461 UI tools: Actualized data storage configuration.
(cherry picked from commit 577e632)

commit cf0080210d24d9dd8b057f959446fac5f8a4ca01
Author: dpavlov 
Date:   2018-01-18T10:53:29Z

IGNITE-7380 Implemented pluggable Direct IO - Fixes #3226.

Signed-off-by: Alexey Goncharuk 

commit dd06d0bd7ef266bfbe156e858b312d1ac86e8982
Author: Pavel Tupitsyn 
Date:   2018-01-18T12:55:49Z

IGNITE-7465 .NET: Fix SqlDdlExample failure with standalone node

commit 57479ec564e1761716da3d5f9feb7a64c396a9f9
Author: Pavel Tupitsyn 
Date:   2018-01-18T13:45:54Z

.NET: Fix CacheLocalTest.TestTxDeadlockDetection

commit bd6be8a4653322905a3b63850c7e033ce3801ce5
Author: Pavel Tupitsyn 
Date:   2018-01-18T18:25:05Z

.NET: Thin client: Fix OP_BINARY_TYPE_GET schema passing format

commit 97564d160586d6d57d300937e6b8877994e35fc7
Author: rkondakov 
Date:   2018-01-19T08:24:51Z

IGNITE-6456: Ability to separately enable or disable JDBC, ODBC and thin 
client endpoints. This closes #3309.

commit d50274ca8875c9680c12e8786ac355a787ba95e0
Author: Yakov Zhdanov 
Date:   2018-01-18T17:57:17Z

Javadoc enhancements - added @see

commit cb2d3cf22388ab19fb2d34ae5bdfc8f1b608db75
Author: Dmitriy Govorukhin 
Date:   2018-01-18T14:14:26Z

IGNITE-7471 Use soft reference for checkpoint entry contents to avoid 
excessive memory usage

commit 3965923369870bb4e8e57e3332c1a1eb1e5f5ed3
Author: rkondakov 
Date:   2018-01-19T09:00:55Z

IGNITE-6772: SQL exception messages became more informative. This closes 
#3342.

commit ba68cb0fa87f776fcd0499d030c333f182611f41
Author: devozerov 
Date:   2018-01-19T09:03:52Z

Merge remote-tracking branch 

[jira] [Created] (IGNITE-7866) TcpCommunicationSpi metrics causes cache operations slowdown

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7866:
---

 Summary: TcpCommunicationSpi metrics causes cache operations 
slowdown
 Key: IGNITE-7866
 URL: https://issues.apache.org/jira/browse/IGNITE-7866
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 2.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.4


Extended TCP metrics were added as a part of IGNITE-6868 ticket. Unfortunately, 
they causes ~5-10% performance drop for cache operations when working in 
in-memory mode. Causes:
1) Contention on shared data structures (LongAdder, CMH)
2) A lot of string comparisons because we use class names to track particulat 
message types

Suggested fix:
1) Move all processing to NIO threads
2) Introcduce thread-local state and update it from NIO threads
3) Metrics readers should merge state from all NIO threads
4) User {{Message}} type ID instead of class names
5) When returning final result we should use {{Class.getName()}} instead of 
{{Class.getSimpleName()}}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-7865:
---
Component/s: persistence

> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7462) Web console: remove invoking of depricated methods from code generation

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7462:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master.

> Web console: remove invoking of depricated methods from code generation
> ---
>
> Key: IGNITE-7462
> URL: https://issues.apache.org/jira/browse/IGNITE-7462
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.5
>
>
> e.g. Warning:(2867, 13) java: setLongQueryWarningTimeout(long) in 
> org.apache.ignite.configuration.CacheConfiguration has been deprecated



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-7865:
--

 Summary: Need to provide method WAL manager for return serialize 
version
 Key: IGNITE-7865
 URL: https://issues.apache.org/jira/browse/IGNITE-7865
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Govorukhin


{code}
public interface IgniteWriteAheadLogManager {
.
/**
 * @return Current serializer version.
 */
public int serializerVersion();
.
}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7865) Need to provide method WAL manager for return serialize version

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-7865:
---
Fix Version/s: 2.5

> Need to provide method WAL manager for return serialize version
> ---
>
> Key: IGNITE-7865
> URL: https://issues.apache.org/jira/browse/IGNITE-7865
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> {code}
> public interface IgniteWriteAheadLogManager {
> .
> /**
>  * @return Current serializer version.
>  */
> public int serializerVersion();
> .
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7861) Web console: invalid column on Activity details modal

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7861:
--

Assignee: Alexey Kuznetsov  (was: Alexey Kuznetsov)

> Web console: invalid column on Activity details modal
> -
>
> Key: IGNITE-7861
> URL: https://issues.apache.org/jira/browse/IGNITE-7861
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: Selection_094.png
>
>
> Many items do not have right description



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7861) Web console: invalid column on Activity details modal

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7861:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: invalid column on Activity details modal
> -
>
> Key: IGNITE-7861
> URL: https://issues.apache.org/jira/browse/IGNITE-7861
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: Selection_094.png
>
>
> Many items do not have right description



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7861) Web console: invalid column on Activity details modal

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7861:


Tested

> Web console: invalid column on Activity details modal
> -
>
> Key: IGNITE-7861
> URL: https://issues.apache.org/jira/browse/IGNITE-7861
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Attachments: Selection_094.png
>
>
> Many items do not have right description



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7864) Control utility: Add confirm on dangerous operations

[Sergey Kosarev (JIRA)]

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

Sergey Kosarev reassigned IGNITE-7864:
--

Assignee: Sergey Kosarev

> Control utility: Add confirm on dangerous operations
> 
>
> Key: IGNITE-7864
> URL: https://issues.apache.org/jira/browse/IGNITE-7864
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kosarev
>Priority: Major
> Fix For: 2.5
>
>
> control.sh can deactivate cluster.
> It could be very dangerous in some cases.
> Lets add manual confirmation for dangerous operations: deactivate, change 
> base line, ...
> Also, lets add "-force" option to not ask for confirmation (will be useful in 
> scripts).
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7864) Control utility: Add confirm on dangerous operations

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7864:


 Summary: Control utility: Add confirm on dangerous operations
 Key: IGNITE-7864
 URL: https://issues.apache.org/jira/browse/IGNITE-7864
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
 Fix For: 2.5


control.sh can deactivate cluster.

It could be very dangerous in some cases.

Lets add manual confirmation for dangerous operations: deactivate, change base 
line, ...

Also, lets add "-force" option to not ask for confirmation (will be useful in 
scripts).

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7862) Update flatten-plugin to 1.0.1 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7862:


GitHub user nizhikov opened a pull request:

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

IGNITE-7862: flatten plugin updated to version 1.0.1



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

$ git pull https://github.com/nizhikov/ignite IGNITE-7862

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

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


commit 4b9536ac6621761d538a6133c9ac6c7f0dae4696
Author: Nikolay Izhikov 
Date:   2018-03-02T08:22:14Z

IGNITE-7862: flatten plugin updated to version 1.0.1




> Update flatten-plugin to 1.0.1 version
> --
>
> Key: IGNITE-7862
> URL: https://issues.apache.org/jira/browse/IGNITE-7862
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> With flatten-plugin version {{1.0.0-beta-3}} we has to enlist all transitive 
> dependencies.
> dev-list discussion - 
> http://apache-ignite-developers.2346864.n4.nabble.com/Maven-Issues-with-flatten-plugin-td27537.html
> Solution is to update plugin to {{1.0.1}} version



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7863) Cleanup spark and spark_2.10 dependencies

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7863:
---

 Summary: Cleanup spark and spark_2.10 dependencies
 Key: IGNITE-7863
 URL: https://issues.apache.org/jira/browse/IGNITE-7863
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov


After solving issue with flatten plugin it possible to cleanup dependency list 
in spark and spark_2.10 modules. Transitive dependencies should be resolved 
using standart maven mechanism.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7862) Update flatten-plugin to 1.0.1 version

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7862:
---

 Summary: Update flatten-plugin to 1.0.1 version
 Key: IGNITE-7862
 URL: https://issues.apache.org/jira/browse/IGNITE-7862
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.4
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
 Fix For: 2.5


With flatten-plugin version {{1.0.0-beta-3}} we has to enlist all transitive 
dependencies.

dev-list discussion - 
http://apache-ignite-developers.2346864.n4.nabble.com/Maven-Issues-with-flatten-plugin-td27537.html

Solution is to update plugin to {{1.0.1}} version



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov reassigned IGNITE-7851:


Assignee: Alexey Popov

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32 
> stackTraceCharsLen, Void* errData, Int32 errDataLen)
>at 
> 

[jira] [Commented] (IGNITE-7803) REST: Add support to get values inserted via API or SQL

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7803:


Successfully tested with simple types like int, float, Integer, String as well 
as with POJO classes.

> REST: Add support to get values inserted via API or SQL
> ---
>
> Key: IGNITE-7803
> URL: https://issues.apache.org/jira/browse/IGNITE-7803
> Project: Ignite
>  Issue Type: Task
>  Components: rest
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Scenario 1:
>  # cache.put(1, new Person(1, Alex, 300))
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}
> Scenario 2:
>  # create table person(id integer primary key, name varchar(100), salary 
> integer);
>  # insert into person(id, name, salary) values (1, Alex, 300)
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7803) REST: Add support to get values inserted via API or SQL

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7803:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> REST: Add support to get values inserted via API or SQL
> ---
>
> Key: IGNITE-7803
> URL: https://issues.apache.org/jira/browse/IGNITE-7803
> Project: Ignite
>  Issue Type: Task
>  Components: rest
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Scenario 1:
>  # cache.put(1, new Person(1, Alex, 300))
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}
> Scenario 2:
>  # create table person(id integer primary key, name varchar(100), salary 
> integer);
>  # insert into person(id, name, salary) values (1, Alex, 300)
>  # get via REST: 
> {{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)