[jira] [Commented] (IGNITE-2662) .NET Standard support

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2662:


.NET Standard 2.0 and Core 2.0 are on the way 
(https://github.com/dotnet/standard/blob/master/docs/versions/netstandard2.0.md),
 and they offer awesome new concept of "Reference Everything".

This means that our package can be referenced from .NET Standard 2.0 and .NET 
Core 2.0 applications and libraries.
However, some APIs, such as Windows Registry access (Which we use to locate 
Java home dir) are not supported and cause {{FileNotFoundException}}.
We should detect current execution environment and avoid these APIs when they 
are not available.

In short, what should be done (once .NET Standard 2.0 is released):
* Create a new test project in a separate solution targeting .NET Core 2.0
* Write unit test to cover all major functionality
* Make sure Windows-specific APIs are not called when they are not available

> .NET Standard support
> -
>
> Key: IGNITE-2662
> URL: https://issues.apache.org/jira/browse/IGNITE-2662
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Ignite.NET should target .NET Standard so it is available on maximum number 
> of platforms, see
> https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
> https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
> https://github.com/dotnet/core/blob/master/roadmap.md
> This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
> additional to good old regular .NET.
> Possible difficulties:
> * JNI interop. Core has dllImport and it works on linux, and our C++ client 
> works on linux, so it should be possible
> * Reflection. We use it a lot, and API has changed.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5238:


Github user asfgit closed the pull request at:

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


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/20/17 12:43 AM:


[~dmagda], yes it failed with the message you described before the fix.
What I did to fix and check it
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
So it's completely maven.

4. Ran TC, Spark and Examples are green.



was (Author: roman_s):
[~dmagda], yes it failed with the message you described before the fix.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
So it's completely maven.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/20/17 12:42 AM:


[~dmagda], yes it failed with the message you described before the fix.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
So it's completely maven.
4. Ran TC, Spark and Examples are green.



was (Author: roman_s):
[~dmagda], yes it failed with the message you described.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
So it's completely maven.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/20/17 12:34 AM:


[~dmagda], yes it failed with the message you described.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
So it's completely maven.
4. Ran TC, Spark and Examples are green.



was (Author: roman_s):
[~dmagda], yes it failed with the message you described.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/20/17 12:33 AM:


[~dmagda], yes it failed with the message you described.
What I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.



was (Author: roman_s):
[~dmagda], what I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5238:
--

[~dmagda], what I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install_ all Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/20/17 12:32 AM:


[~dmagda], what I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install -DskipTests_ the whole Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.



was (Author: roman_s):
[~dmagda], what I did to check
1. Made changes to 2.1.0-SNAPSHOT as in the pull request
2. _mvn clean install_ all Ignite project
3. Uncommented http-rest in pom of the IoT project and changed dependencies 
from 2.0.0 to 2.1.0-SNAPSHOT.
4. Ran TC, Spark and Examples are green.


> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Assigned] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5238:
---

Assignee: Roman Shtykh  (was: Denis Magda)

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5238:
-

[~roman_s], the example still fails with the same error if I move it sources 
under "ignite/examples/" folder and run from here applying your patch. 
Probably, this is because your patch is not synced up with master and it caused 
chaos in my local repo. :)

How did you check that example works on your side? Did you make sure it fails 
before applying the patch? Currently, the project that is in the repository 
includes a hack - I imported ignite-http-rest directly as a lib (not using 
maven). You need to go to the project settings and remove all the external libs 
(not imported by Maven) from there.

Finally, as for TC we need to make sure all Spark suites and Examples suite are 
green.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5247) TcpCommunicationSpi calls GridNioRecoveryDescriptor with looks unusually large rcvCnt and fail with null.

[Chandra Bose Renganathan (JIRA)]

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

Chandra Bose Renganathan commented on IGNITE-5247:
--

I think it is because of Big and Little endian.

> TcpCommunicationSpi calls GridNioRecoveryDescriptor with looks unusually 
> large rcvCnt and fail with null. 
> --
>
> Key: IGNITE-5247
> URL: https://issues.apache.org/jira/browse/IGNITE-5247
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Chandra Bose Renganathan
>Priority: Critical
>
> TcpCommunicationSpi calls GridNioRecoveryDescriptor with looks unusually 
> large rcvCnt and fail with null. 
> This happens when new node try to join existing grid of size 2 or 3, 
> Environment Machine 1: 
> SunOS betapm 5.10 Generic_150400-48 sun4v sparc sun4v
> Environment Machine 2: 
> Linux sbpmwsv1 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Nov 23 16:03:01 EST 2016 
> x86_64 x86_64 x86_64 GNU/Linux
> rcvCnt=216172782113783808 ???
> The configuration following. MyTcpDiscoveryIpFinderAdapter returns 3 
> InetSocketAddress including self.
> IgniteConfiguration cfg = new IgniteConfiguration();
> TcpDiscoverySpi spi = new TcpDiscoverySpi();
> JdkMarshaller marshaller = new JdkMarshaller();
> cfg.setMarshaller(marshaller);
> spi.setLocalPort(8087);
> spi.setSocketTimeout(8L);
> spi.setAckTimeout(8L);
>
> spi.setLocalPortRange(1);
> spi.setIpFinder(new MyTcpDiscoveryIpFinderAdapter());
> cfg.setDiscoverySpi(spi);
> cfg.setGridName("demo-cluster");
> cfg.setClientMode(false);
> Ignite ignite = Ignition.start(cfg);
> IgniteCache cache = ignite.getOrCreateCache("bose");
> System.out.println(cache.get("key1"));
> May 19, 2017 10:09:13 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2043)
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1868)
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1573)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.ignite.internal.util.nio.GridNioRecoveryDescriptor.ackReceived(GridNioRecoveryDescriptor.java:211)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2.onMessage(TcpCommunicationSpi.java:647)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2.onMessage(TcpCommunicationSpi.java:342)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:117)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:88)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3062)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1121)
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2031)
> ... 4 more
> May 19, 2017 10:09:14 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2043)
> at 
> 

[jira] [Commented] (IGNITE-5113) K-means clustering

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5113:


GitHub user artemmalykh opened a pull request:

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

IGNITE-5113: Implemented basic distributed/local kmeans clusterizatio…

…n algorithm.

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

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

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

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


commit 48d8d73ca0744008cae09b6967d337d72fd2fa0e
Author: Artem Malykh 
Date:   2017-05-19T16:40:12Z

IGNITE-5113: Implemented basic distributed/local kmeans clusterization 
algorithm.




> K-means clustering
> --
>
> Key: IGNITE-5113
> URL: https://issues.apache.org/jira/browse/IGNITE-5113
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
> Fix For: 2.1
>
>




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

[jira] [Commented] (IGNITE-4831) Add an option to disable MBeans

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-4831:
-

My comments on the PR:
* What is the purpose of {{mbeans-disallowed.policy}} file?
* Why the catch block for {{JMException}} is changed multiple times like below? 
This seems to be a redundant change.

{code}
catch (JMException e) {
if (! (e instanceof InstanceNotFoundException && 
IgniteUtils.IGNITE_DISABLE_MBEANS))
U.error(log, "Failed to unregister MBean for memory metrics: " +
memPlc.memoryMetrics().getName(), e);
}
{code}

> Add an option to disable MBeans
> ---
>
> Key: IGNITE-4831
> URL: https://issues.apache.org/jira/browse/IGNITE-4831
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>
> There are multiple MBeans registered by Ignite and there is no way to avoid 
> their registration (in case they're not allowed for security reasons for 
> example). We should have a system property that will disable MBeans.
> In addition, if MBean registration throws a {{RuntimeException}}, this 
> exception is not properly handled. For example, if it happens during cache 
> creation, {{createCache}} method hangs forever.



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

[jira] [Commented] (IGNITE-5203) JDBC driver should support BLOB fields

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5203:
-

Vladimir,

in current design BLOB is just a wrapper for byte array that can be stored as 
field of some object. Only simplest operations are supported. It is mostly 
designed for reading data from byte arrays. {{ResultSet.getBlob()}} method just 
delegates call to {{ResultSet.getBytes()}} method. {{ResultSet.updateBlob()}} 
and {{PreparedStatement.setBlob()}} methods are not supported yet.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Commented] (IGNITE-4892) Support DML for thin client based JDBC driver

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4892:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4892  Support DML for thin client based JDBC driver



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

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

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

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


commit 3ce02a3331cfa38cdb29859b69d4a5cd5cfd6e5b
Author: tledkov-gridgain 
Date:   2017-04-26T14:42:16Z

IGNITE-4892: save the progress

commit 64ed8bdfe94ac01bd15f1e26a9b437ec13a511eb
Author: tledkov-gridgain 
Date:   2017-04-26T14:51:45Z

Merge branch '_master' into ignite-4892

commit 5e9a03cc36270d8bd6d4cc0eba800a9d23284988
Author: tledkov-gridgain 
Date:   2017-04-27T09:26:31Z

IGNITE-4892: save the progress

commit 7c394d1f79992a8e74a8bd021740e72732314e37
Author: tledkov-gridgain 
Date:   2017-04-27T15:36:31Z

IGNITE-4892: save the progress

commit 31cafbf1d4873aecafca5e7d49c6c6a2f27a53ef
Author: tledkov-gridgain 
Date:   2017-04-28T08:11:39Z

IGNITE-4892: save the progress

commit a6a3d1e34f70165fac1c2a8958a0a2060e83d0ae
Author: tledkov-gridgain 
Date:   2017-04-28T08:12:50Z

Merge branch '_master' into ignite-4892

commit 7dd7b7082b8831e649e634cfa2991db6a0512734
Author: tledkov-gridgain 
Date:   2017-05-02T08:05:50Z

IGNITE-4892: save the progress

commit 3f88d45fc0cdd9a579cf4483d062a8f5db4d6499
Author: tledkov-gridgain 
Date:   2017-05-19T12:56:27Z

Merge branch '_master' into ignite-4892

commit ecdd60d3cdf71b353c9edcd2e738b6dd2588ab37
Author: tledkov-gridgain 
Date:   2017-05-19T12:58:12Z

IGNITE-4892: save the progress

commit 11277385815bbbac9b3e78568c5962f866b03781
Author: tledkov-gridgain 
Date:   2017-05-19T12:58:40Z

Merge branch '_master' into ignite-4892

commit 075cc01aa4b885d26f41819b8d26459b5769a179
Author: tledkov-gridgain 
Date:   2017-05-19T13:00:35Z

IGNITE-4892: save the progress




> Support DML for thin client based JDBC driver
> -
>
> Key: IGNITE-4892
> URL: https://issues.apache.org/jira/browse/IGNITE-4892
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Support all DML operations for the thin client based JDBC driver:
> https://apacheignite.readme.io/docs/jdbc-driver#hostname-based-jdbc-connection



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

[jira] [Commented] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5163:
--

Done. [~vozerov], please review the changes again. 

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Assigned] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-2671:


Assignee: (was: Alexey Kuznetsov)

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>  Labels: community
> Fix For: 2.1
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



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

[jira] [Assigned] (IGNITE-5110) Topology version should be included in synchronous continuous message

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5110:


Assignee: Alexey Kuznetsov

> Topology version should be included in synchronous continuous message
> -
>
> Key: IGNITE-5110
> URL: https://issues.apache.org/jira/browse/IGNITE-5110
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
>
> I've observed the following situation on TC:
> {code}
> "sys-stripe-11-#12316%continuous.GridCacheContinuousQueryConcurrentTest1%" 
> prio=10 tid=0x7f8e1888f800 nid=0x44ad waiting on condition 
> [0x7f91050fa000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:930)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:817)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$800(CacheContinuousQueryHandler.java:92)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:420)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:346)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:1029)
>   - locked <0x000766998a50> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCacheEntry)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:663)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:772)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:580)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:466)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:514)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:841)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:720)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:676)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:95)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:153)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:151)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> {code}
> 

[jira] [Assigned] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-2671:


Assignee: Alexey Kuznetsov

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
>  Labels: community
> Fix For: 2.1
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



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

[jira] [Assigned] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-2671:


Assignee: (was: Alexey Kuznetsov)

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>  Labels: community
> Fix For: 2.1
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



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

[jira] [Commented] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5163:
-

[~tledkov-gridgain], done.

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol

[Roman Shtykh (JIRA)]

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

Roman Shtykh updated IGNITE-5229:
-
Description: 
Currently there's no way to switch caches -- all requests go to 'default'.
_Note that this is the switch needed only for a subset of Redis data structures 
(currently only STRINGs) -- for SETs and HASHTABLEs caches will be specified as 
keys (see IGNITE-5241)_

The solution to be implemented:
1. A user specifies the cache configuration (template) with predefined name 
‘redis-ignite-internal-cache’
2. Then issues ‘SELECT n’, and uses ‘redis-ignite-internal-cache-n’.

Caches are configurable by providing a template.

http://apache-ignite-developers.2346864.n4.nabble.com/Changing-cache-name-when-using-Redis-protocol-td17727.html


  was:
Currently there's no way to switch caches -- all requests go to 'default'.
_Note that this is the switch needed only for a subset of Redis data structures 
(currently only STRINGs) -- for SETs and HASHTABLEs caches will be specified as 
keys (see IGNITE-5241)_

As an idea, we can use {{CONFIG SET parameter value}} to set the current cache, 
save it in {{GridRestProcessor}} and use it until the user switches to another 
one.


> Specify caches when using Redis protocol
> 
>
> Key: IGNITE-5229
> URL: https://issues.apache.org/jira/browse/IGNITE-5229
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Currently there's no way to switch caches -- all requests go to 'default'.
> _Note that this is the switch needed only for a subset of Redis data 
> structures (currently only STRINGs) -- for SETs and HASHTABLEs caches will be 
> specified as keys (see IGNITE-5241)_
> The solution to be implemented:
> 1. A user specifies the cache configuration (template) with predefined name 
> ‘redis-ignite-internal-cache’
> 2. Then issues ‘SELECT n’, and uses ‘redis-ignite-internal-cache-n’.
> Caches are configurable by providing a template.
> http://apache-ignite-developers.2346864.n4.nabble.com/Changing-cache-name-when-using-Redis-protocol-td17727.html



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5238:
--

[~dmagda] TC looks good (there are some errors, but I think they are unrelated 
to this change).
Your IoT example doesn't fail with the error anymore.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2671:
-

More technical details: 
http://apache-ignite-developers.2346864.n4.nabble.com/waiting-for-partition-release-question-td17782.html

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
>  Labels: community
> Fix For: 2.1
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



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

[jira] [Assigned] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh reassigned IGNITE-5238:


Assignee: Denis Magda  (was: Roman Shtykh)

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5238:
-

[~roman_s], once you get positive results from TC please assign the ticket to 
me. I'll check the changes against the example used at conferences.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Updated] (IGNITE-5260) JDBC Driver: implement SQLWarning support

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5260:

Summary: JDBC Driver: implement SQLWarning support  (was: JDBC Driver: 
implement SQLWarning supportion)

> JDBC Driver: implement SQLWarning support
> -
>
> Key: IGNITE-5260
> URL: https://issues.apache.org/jira/browse/IGNITE-5260
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>




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

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/19/17 10:52 AM:


1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) Fixed.
8) Fixed.
9) Fixed.
10) Fixed.
11) Fixed.
12) IGNITE-5260 is filed.
13) [~isapego], please change the ODBC native part.


was (Author: tledkov-gridgain):
1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9) Fixed.
10) Fixed.
11) Fixed.
12) IGNITE-5260 is filed.
13) [~isapego], please change the ODBC native part.

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/19/17 10:22 AM:


1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9) Fixed.
10) Fixed.
11) Fixed.
12) IGNITE-5260 is filed.
13) [~isapego], please change the ODBC native part.


was (Author: tledkov-gridgain):
1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10) Fixed.
11) Fixed.
12) IGNITE-5260 is filed.
13)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Commented] (IGNITE-4534) Implement offheap eviction policies based on page memory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4534:


Github user asfgit closed the pull request at:

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


> Implement offheap eviction policies based on page memory
> 
>
> Key: IGNITE-4534
> URL: https://issues.apache.org/jira/browse/IGNITE-4534
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Since the internal structure of offheap storage has changed, we need to 
> re-implement Fifo, Lru and Sorted eviction policies



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

[jira] [Commented] (IGNITE-4712) Memory leaks in PageMemory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4712:


Github user asfgit closed the pull request at:

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


> Memory leaks in PageMemory
> --
>
> Key: IGNITE-4712
> URL: https://issues.apache.org/jira/browse/IGNITE-4712
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Igor Seliverstov
> Fix For: 2.0
>
>
> During performing put/get/remove operations on large objects (objects, which 
> size is more than 1kb) allocated pages number constantly grows.



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

[jira] [Commented] (IGNITE-4930) Try to move free lists into a tread-local structure to avoid contention

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4930:


Github user asfgit closed the pull request at:

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


> Try to move free lists into a tread-local structure to avoid contention
> ---
>
> Key: IGNITE-4930
> URL: https://issues.apache.org/jira/browse/IGNITE-4930
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
>




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

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/19/17 10:16 AM:


1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10) Fixed.
11) Fixed.
12) IGNITE-5260 is filed.
13)


was (Author: tledkov-gridgain):
1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10)
11)
12)
13)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Commented] (IGNITE-4952) Delete swap-related functionality

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4952:


Github user asfgit closed the pull request at:

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


> Delete swap-related functionality
> -
>
> Key: IGNITE-4952
> URL: https://issues.apache.org/jira/browse/IGNITE-4952
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> As swap storage was removed in 
> [IGNITE-3477|https://issues.apache.org/jira/browse/IGNITE-3477] there is no 
> need to keep swap-related functionality in Ignite codebase.
> h2. Acceptance Criteria
> # Swap-related functionality is removed from codebase.
> # All tests verifying swap functionality are removed from tests set.



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

[jira] [Created] (IGNITE-5260) JDBC Driver: implement SQLWarning supportion

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5260:


 Summary: JDBC Driver: implement SQLWarning supportion
 Key: IGNITE-5260
 URL: https://issues.apache.org/jira/browse/IGNITE-5260
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1






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

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/19/17 10:13 AM:


1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) Fixed.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10)
11)
12)
13)


was (Author: tledkov-gridgain):
1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) please take a look at the IGNITE-4762. [~vkulichenko] suggested use this 
temporary stub as-is.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10)
11)
12)
13)

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Assigned] (IGNITE-5205) Optimize SQL messaging

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov reassigned IGNITE-5205:
--

Assignee: Sergey Kalashnikov

> Optimize SQL messaging
> --
>
> Key: IGNITE-5205
> URL: https://issues.apache.org/jira/browse/IGNITE-5205
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergi Vladykin
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>
> Currently we create Message object for each H2 Value being sent or received 
> over the wire. Lets write and read them directly without intermediate 
> conversions.



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

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/19/17 9:51 AM:
---

1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) please take a look at the IGNITE-4762. [~vkulichenko] suggested use this 
temporary stub as-is.
5) Fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -
8) Fixed.
9)
10)
11)
12)
13)


was (Author: tledkov-gridgain):
1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) please take a look at the IGNITE-4762. [~vkulichenko] suggested use this 
temporary stub as-is.
5) fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Commented] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5163:
--

1) Removed
2) Because we have to use default public cache when uses doesn't specify the 
cache name.
3) Fixed.
4) please take a look at the IGNITE-4762. [~vkulichenko] suggested use this 
temporary stub as-is.
5) fixed.
6) Fixed. It was a bug, The exception is thrown up. Test for invalid connection 
URL is added.
7) -

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Commented] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5163:
-

[~tledkov-gridgain], my comments:

1) {{BinaryUtils}}: unused method {{doReadSqlDateArray}}; Is it a bug or just 
dead code?
2) {{SqlListenerRequestHandlerImpl}}: call to {{getOrStartPublicCache}}? what 
for?
3) {{SqlListenerProcessor}}: check for {{BinaryMarshaller}} is removed, but did 
you add it to ODBC handshake?
4) {{IgniteJdbcThinDriver.PARAM_TX_ALLOWED}}: we will support transactions in 
SQL quite soon, so I think it is better to remove this property and print a 
warning instead
5) {{JdbcTcpIo.closed}}: no JavaDocs
6) {{JdbcTcpIo.start}}: silent close without prtinting anything to log? How 
users are going to understand what is wrong when they receive a connection 
which is closed without a reason?
7) {{JdbcTcpIo.handshake}}: inconclusive error message; what should user do 
when receiving this kind of error?
8) {{JdbcTcpIo.read}}: please follow standard error message format
9) {{JdbcConnection}}: duplciate code in {{createStatement}} and 
{{prepareStatement}}. This should be refactored into common validation routine
10) {{JdbcConnection.setAutoCommit}}: show a warning instead of exception
11) {{JdbcConnection}}: {{getAutoCommit}} and {{getHoldability}} - inconsistent 
with other tx-related methods (e.g. {{getTransactionIsolation}})
12) {{JdbcConnectiongetWarnings/clearWarnings}}: do we have a ticket for this? 
it could be important for warnings about unsupported transactions
13) Does ODBC works fine at the moment?

> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



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

[jira] [Updated] (IGNITE-5254) Add web-console folder structure description

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-5254:
---
Fix Version/s: 2.1

> Add web-console folder structure description
> 
>
> Key: IGNITE-5254
> URL: https://issues.apache.org/jira/browse/IGNITE-5254
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Fix For: 2.1
>
>
> structure example
> Web Console Frontend
> -- components 
> -- -- index.js [web-console.components]
> -- -- some-component
> -- -- -- index.js (imports)
> -- -- -- controller.js
> -- -- -- directive.js
> -- -- -- service.js
> -- -- -- style.scss
> -- -- -- template.tpl.pug (components template)
> -- filters
> -- -- index.js [web-console.filters]
> -- -- some filter.js
> -- models
> -- -- index.js [web-console.models]
> -- ignite_modules
> -- -- index.js (states, deps) [web-console.modules]
> -- -- components
> -- -- -- index.js [web-console.modules.components]
> -- -- pages
> -- -- -- index.js [web-console.modules.pages]
> -- -- -- page_1
> -- -- -- -- index.js (imports)
> -- -- -- -- components
> -- -- -- -- -- some-page-component
> -- -- -- -- -- -- index.js (imports)
> -- -- -- -- -- -- decorator.js
> -- -- -- -- style.scss
> 
> -- services
> -- -- index.js [web-console.services]
> -- -- some service.js
> -- -- some services group
> -- -- -- some service1.js
> -- -- -- some service2.js
> -- pages
> -- -- index.js (imports) [web-console.pages]
> -- -- page_1
> -- -- -- index.js (states, deps) [web-console.pages.page_1]
> -- -- -- template.tpl.pug (page template)
> -- -- -- components
> -- -- -- -- index.js (imports)
> -- -- -- -- some-page-component
> -- -- -- -- -- index.js (imports)
> -- -- -- -- -- controller.js
> -- -- -- -- -- directive.js
> -- -- -- -- -- service.js
> -- -- -- -- -- template.tpl.pug
> -- -- -- -- -- models
> -- -- -- -- -- -- index.js (imports)
> -- -- -- services
> -- -- -- -- some page service.js
> -- index.tpl.pug (index page)
> -- index.js (app enter point, bootstraps app component) [web-console]
> -- variables.scss
> -- vendors.js
> -- style.scss



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

[jira] [Updated] (IGNITE-5254) Add web-console folder structure description

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-5254:
---
Affects Version/s: 2.0

> Add web-console folder structure description
> 
>
> Key: IGNITE-5254
> URL: https://issues.apache.org/jira/browse/IGNITE-5254
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Fix For: 2.1
>
>
> structure example
> Web Console Frontend
> -- components 
> -- -- index.js [web-console.components]
> -- -- some-component
> -- -- -- index.js (imports)
> -- -- -- controller.js
> -- -- -- directive.js
> -- -- -- service.js
> -- -- -- style.scss
> -- -- -- template.tpl.pug (components template)
> -- filters
> -- -- index.js [web-console.filters]
> -- -- some filter.js
> -- models
> -- -- index.js [web-console.models]
> -- ignite_modules
> -- -- index.js (states, deps) [web-console.modules]
> -- -- components
> -- -- -- index.js [web-console.modules.components]
> -- -- pages
> -- -- -- index.js [web-console.modules.pages]
> -- -- -- page_1
> -- -- -- -- index.js (imports)
> -- -- -- -- components
> -- -- -- -- -- some-page-component
> -- -- -- -- -- -- index.js (imports)
> -- -- -- -- -- -- decorator.js
> -- -- -- -- style.scss
> 
> -- services
> -- -- index.js [web-console.services]
> -- -- some service.js
> -- -- some services group
> -- -- -- some service1.js
> -- -- -- some service2.js
> -- pages
> -- -- index.js (imports) [web-console.pages]
> -- -- page_1
> -- -- -- index.js (states, deps) [web-console.pages.page_1]
> -- -- -- template.tpl.pug (page template)
> -- -- -- components
> -- -- -- -- index.js (imports)
> -- -- -- -- some-page-component
> -- -- -- -- -- index.js (imports)
> -- -- -- -- -- controller.js
> -- -- -- -- -- directive.js
> -- -- -- -- -- service.js
> -- -- -- -- -- template.tpl.pug
> -- -- -- -- -- models
> -- -- -- -- -- -- index.js (imports)
> -- -- -- services
> -- -- -- -- some page service.js
> -- index.tpl.pug (index page)
> -- index.js (app enter point, bootstraps app component) [web-console]
> -- variables.scss
> -- vendors.js
> -- style.scss



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

[jira] [Updated] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-5244:
---
Fix Version/s: 2.1

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: download.png, download.png
>
>
> No direct way to download Ignite Web Agent. Let's add the btn.



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

[jira] [Updated] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-5244:
---
Affects Version/s: 2.0

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: download.png, download.png
>
>
> No direct way to download Ignite Web Agent. Let's add the btn.



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

[jira] [Closed] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-5244.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Attachments: download.png, download.png
>
>
> No direct way to download Ignite Web Agent. Let's add the btn.



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

[jira] [Commented] (IGNITE-5203) JDBC driver should support BLOB fields

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5203:
-

Also as far as I see, PR is created to some old Ignite version. Can we have a 
PR to master?

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Commented] (IGNITE-5203) JDBC driver should support BLOB fields

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5203:
-

[~agura], [~vkulichenko], could you please briefly describe the design? Is it 
about passing byte arrays back and forth in streaming fashion through JDBC 
driver?  I am trying to understand how it could affect development of the new 
JDBC driver.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Updated] (IGNITE-5203) JDBC driver should support BLOB fields

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5203:

Component/s: sql

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



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

[jira] [Commented] (IGNITE-3275) .NET: Enable REST HTTP in .NET nodes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3275:
-

[~ptupitsyn],
Let's postpone this. REST and the whole TCP client will be reviewed and 
possibly redesigned significantly around AI 2.2 - 2.3 releases. No need to 
expose outdated API to .NET users.

> .NET: Enable REST HTTP in .NET nodes
> 
>
> Key: IGNITE-3275
> URL: https://issues.apache.org/jira/browse/IGNITE-3275
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
> Fix For: 2.1
>
>
> * Include REST HTTP jars in NuGet (either in core, or in a separate package). 
> Keep in mind NuGet size limitation
> * Add required options to IgniteConfiguration to enable/disable REST 
> ({{ConnectorConfiguration}})



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

[jira] [Updated] (IGNITE-5259) Minor serialization fix

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-5259:

Summary: Minor serialization fix  (was: Support backward compatibility with 
versions without service permissions)

> Minor serialization fix
> ---
>
> Key: IGNITE-5259
> URL: https://issues.apache.org/jira/browse/IGNITE-5259
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> [IGNITE-5077|https://issues.apache.org/jira/browse/IGNITE-5077] adds service 
> security permissions, but breaks compatibility with older versions. This must 
> be fixed somehow.



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

[jira] [Updated] (IGNITE-5259) Minor serialization fix

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-5259:

Description: (was: 
[IGNITE-5077|https://issues.apache.org/jira/browse/IGNITE-5077] adds service 
security permissions, but breaks compatibility with older versions. This must 
be fixed somehow.)

> Minor serialization fix
> ---
>
> Key: IGNITE-5259
> URL: https://issues.apache.org/jira/browse/IGNITE-5259
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-5254) Add web-console folder structure description

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-5254:
---
Description: 
structure example

Web Console Frontend

-- components 
-- -- index.js [web-console.components]
-- -- some-component
-- -- -- index.js (imports)
-- -- -- controller.js
-- -- -- directive.js
-- -- -- service.js
-- -- -- style.scss
-- -- -- template.tpl.pug (components template)
-- filters
-- -- index.js [web-console.filters]
-- -- some filter.js
-- models
-- -- index.js [web-console.models]
-- ignite_modules
-- -- index.js (states, deps) [web-console.modules]
-- -- components
-- -- -- index.js [web-console.modules.components]
-- -- pages
-- -- -- index.js [web-console.modules.pages]
-- -- -- page_1
-- -- -- -- index.js (imports)
-- -- -- -- components
-- -- -- -- -- some-page-component
-- -- -- -- -- -- index.js (imports)
-- -- -- -- -- -- decorator.js
-- -- -- -- style.scss


-- services
-- -- index.js [web-console.services]
-- -- some service.js
-- -- some services group
-- -- -- some service1.js
-- -- -- some service2.js
-- pages
-- -- index.js (imports) [web-console.pages]
-- -- page_1
-- -- -- index.js (states, deps) [web-console.pages.page_1]
-- -- -- template.tpl.pug (page template)
-- -- -- components
-- -- -- -- index.js (imports)
-- -- -- -- some-page-component
-- -- -- -- -- index.js (imports)
-- -- -- -- -- controller.js
-- -- -- -- -- directive.js
-- -- -- -- -- service.js
-- -- -- -- -- template.tpl.pug
-- -- -- -- -- models
-- -- -- -- -- -- index.js (imports)
-- -- -- services
-- -- -- -- some page service.js
-- index.tpl.pug (index page)
-- index.js (app enter point, bootstraps app component) [web-console]
-- variables.scss
-- vendors.js
-- style.scss

  was:
structure example

Web Console Frontend

-- components 
-- -- index.js [web-console.components]
-- -- some-component
-- -- -- index.js (imports)
-- -- -- controller.js
-- -- -- directive.js
-- -- -- service.js
-- -- -- template.tpl.pug (components template)
-- filters
-- -- index.js [web-console.filters]
-- -- some filter.js
-- models
-- -- index.js [web-console.models]
-- ignite_modules
-- -- index.js (states, deps) [web-console.modules]
-- -- components
-- -- -- index.js [web-console.modules.components]
-- -- pages
-- -- -- index.js [web-console.modules.pages]
-- -- -- page_1
-- -- -- -- index.js (imports)
-- -- -- -- components
-- -- -- -- -- some-page-component
-- -- -- -- -- -- index.js (imports)
  -- -- -- -- decorator.js


-- services
-- -- index.js [web-console.services]
-- -- some service.js
-- -- some services group
-- -- -- some service1.js
-- -- -- some service2.js
-- pages
-- -- index.js (states, deps) [web-console.pages]
-- -- page_1
-- -- -- index.js (imports)
-- -- -- template.tpl.pug (page template)
-- -- -- components
-- -- -- -- index.js (imports)
-- -- -- -- some-page-component
-- -- -- -- -- index.js (imports)
-- -- -- -- -- controller.js
-- -- -- -- -- directive.js
-- -- -- -- -- service.js
-- -- -- -- -- template.tpl.pug
-- -- -- -- -- models
-- -- -- -- -- -- index.js (imports)
-- -- -- services
-- -- -- -- some page service.js
-- index.tpl.pug (index page)
-- index.js (app enter point, bootstraps app component) [web-console]
-- vendors.js


> Add web-console folder structure description
> 
>
> Key: IGNITE-5254
> URL: https://issues.apache.org/jira/browse/IGNITE-5254
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
>
> structure example
> Web Console Frontend
> -- components 
> -- -- index.js [web-console.components]
> -- -- some-component
> -- -- -- index.js (imports)
> -- -- -- controller.js
> -- -- -- directive.js
> -- -- -- service.js
> -- -- -- style.scss
> -- -- -- template.tpl.pug (components template)
> -- filters
> -- -- index.js [web-console.filters]
> -- -- some filter.js
> -- models
> -- -- index.js [web-console.models]
> -- ignite_modules
> -- -- index.js (states, deps) [web-console.modules]
> -- -- components
> -- -- -- index.js [web-console.modules.components]
> -- -- pages
> -- -- -- index.js [web-console.modules.pages]
> -- -- -- page_1
> -- -- -- -- index.js (imports)
> -- -- -- -- components
> -- -- -- -- -- some-page-component
> -- -- -- -- -- -- index.js (imports)
> -- -- -- -- -- -- decorator.js
> -- -- -- -- style.scss
> 
> -- services
> -- -- index.js [web-console.services]
> -- -- some service.js
> -- -- some services group
> -- -- -- some service1.js
> -- -- -- some service2.js
> -- pages
> -- -- index.js (imports) [web-console.pages]
> -- -- page_1
> -- -- -- index.js (states, deps) [web-console.pages.page_1]
> -- -- -- template.tpl.pug (page template)
> -- -- -- components
> -- -- -- -- index.js (imports)
> -- -- -- -- some-page-component
> -- -- -- -- -- 

[jira] [Closed] (IGNITE-5180) Inconsistent return type in javadoc of GridSecurityProcessor

[Wuwei Lin (JIRA)]

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

Wuwei Lin closed IGNITE-5180.
-

> Inconsistent return type in javadoc of GridSecurityProcessor
> 
>
> Key: IGNITE-5180
> URL: https://issues.apache.org/jira/browse/IGNITE-5180
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.0
>Reporter: Wuwei Lin
>Priority: Trivial
>
> In {{GridSecurityProcessor}}, the return types of methods {{authenticate}} 
> and {{authenticateNode}} are {{SecurityContext}}, but documented as returning 
> {{boolean}}.



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

[jira] [Updated] (IGNITE-5205) Optimize SQL messaging

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5205:

Component/s: sql

> Optimize SQL messaging
> --
>
> Key: IGNITE-5205
> URL: https://issues.apache.org/jira/browse/IGNITE-5205
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergi Vladykin
> Fix For: 2.1
>
>
> Currently we create Message object for each H2 Value being sent or received 
> over the wire. Lets write and read them directly without intermediate 
> conversions.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-5238:
--

[~roman_s] Yes, go ahead. But just in case, please, run all tests on TC.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5238:


GitHub user shroman opened a pull request:

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

IGNITE-5238: Resolved dependency problems of Ignite Spark and Ignite …

…Rest modules.

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

$ git pull https://github.com/shroman/ignite IGNITE-5238

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

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






> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Comment Edited] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-5238 at 5/19/17 6:03 AM:
---

Spark has the dependency on the following version
{{2.6.5}}, which 
conflicts with what we have in the parent pom.

{code}
[INFO] |  +- org.apache.spark:spark-core_2.11:jar:2.1.0:compile
…
[INFO] |  |  +- (com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile 
- omitted for conflict with 2.8.8)
{code}

I propose to change jackson to 2.6.5 in IGNITE project.

[~kuaw26] I think you upgraded Jackson before and know this part best. Do you 
think this solution is ok?


was (Author: roman_s):
Spark has the dependency on the following version
{{2.6.5}}, which 
conflicts with what we have in the parent pom.

{code}
[INFO] |  +- org.apache.spark:spark-core_2.11:jar:2.1.0:compile
…
[INFO] |  |  +- (com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile 
- omitted for conflict with 2.8.8)
{code}

I propose to change jackson to 2.6.5 in IGNITE project.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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

[jira] [Commented] (IGNITE-5238) Ignite Spark can't be used with Ignite REST

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5238:
--

Spark has the dependency on the following version
{{2.6.5}}, which 
conflicts with what we have in the parent pom.

{code}
[INFO] |  +- org.apache.spark:spark-core_2.11:jar:2.1.0:compile
…
[INFO] |  |  +- (com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile 
- omitted for conflict with 2.8.8)
{code}

I propose to change jackson to 2.6.5 in IGNITE project.

> Ignite Spark can't be used with Ignite REST
> ---
>
> Key: IGNITE-5238
> URL: https://issues.apache.org/jira/browse/IGNITE-5238
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Roman Shtykh
>Priority: Blocker
> Fix For: 2.1
>
>
> {{ignite-rest-http}} can't be used together with {{ignite-spark}} because the 
> former imports some legacy version of Jackson library and the following 
> exception is thrown from an IDEA in attempt to use Ignite+Spark application:
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
>   at org.apache.spark.SparkContext.withScope(SparkContext.scala:701)
>   at org.apache.spark.SparkContext.parallelize(SparkContext.scala:715)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:153)
>   at 
> org.apache.spark.api.java.JavaSparkContext.parallelizePairs(JavaSparkContext.scala:158)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.preloadSensorsData(SparkStreamerStartup.java:123)
>   at 
> org.apache.ignite.iot.SparkStreamerStartup.main(SparkStreamerStartup.java:96)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible 
> Jackson version: 2.8.8
>   at 
> com.fasterxml.jackson.module.scala.JacksonModule$class.setupModule(JacksonModule.scala:64)
>   at 
> com.fasterxml.jackson.module.scala.DefaultScalaModule.setupModule(DefaultScalaModule.scala:19)
>   at 
> com.fasterxml.jackson.databind.ObjectMapper.registerModule(ObjectMapper.java:745)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala:82)
>   at 
> org.apache.spark.rdd.RDDOperationScope$.(RDDOperationScope.scala)
>   ... 11 more
> {code}
> To reproduce:
> - Download this project and open in IntellijIdea: 
> https://github.com/dmagda/IgniteSparkIoT
> - Go to pom.xml and uncomment {{ignite-rest-http}} module. It has to be 
> imported.
> - Start a cluster node with IgniteNodeStartup
> - Start SparkStreamerStartup and you will get the error above.
> Looks like the Ignite REST module has to be upgraded to the recent Jackson 
> version.



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