[jira] [Created] (IGNITE-3946) Web console: Implement configuration of EventStorageSpi

2016-09-20 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-3946:
-

 Summary: Web console: Implement configuration of EventStorageSpi
 Key: IGNITE-3946
 URL: https://issues.apache.org/jira/browse/IGNITE-3946
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko






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

[jira] [Created] (IGNITE-3947) Web console: Implement configuration of LoadBalancingSpis

2016-09-20 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-3947:
-

 Summary: Web console: Implement configuration of LoadBalancingSpis
 Key: IGNITE-3947
 URL: https://issues.apache.org/jira/browse/IGNITE-3947
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko






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

[jira] [Created] (IGNITE-3945) Web console: Implement configuration of DeploymentSpi

2016-09-20 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-3945:
-

 Summary: Web console: Implement configuration of DeploymentSpi
 Key: IGNITE-3945
 URL: https://issues.apache.org/jira/browse/IGNITE-3945
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko






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

[jira] [Created] (IGNITE-3944) Web console: Implement configuration of CheckpointSpi

2016-09-20 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-3944:
-

 Summary: Web console: Implement configuration of CheckpointSpi
 Key: IGNITE-3944
 URL: https://issues.apache.org/jira/browse/IGNITE-3944
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko






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

Re: Support for Spark 2.0

2016-09-20 Thread Roman Shtykh 
There is a bunch of requests from users for this upgrade.
https://issues.apache.org/jira/browse/IGNITE-3822 and related.

-Roman
 

On Wednesday, September 21, 2016 5:14 AM, Denis Magda  
wrote:
 

 Is this the only issue we have with Spark 2.0?
https://issues.apache.org/jira/browse/IGNITE-3596 


—
Denis

> On Sep 20, 2016, at 11:54 AM, Vladimir Ozerov  wrote:
> 
> I think we can expect Spark 2.0 support to be added in one of the nearest
> releases (not sure if it will be 1.8 or 2.0).
> 
> On Mon, Sep 19, 2016 at 10:20 PM, Richard Siebeling 
> wrote:
> 
>> I'd wish someone could fix this, unfortunately I can't do anything about it
>> in the near future...
>> 
>> On Mon, Sep 19, 2016 at 3:20 PM, Phadnis, Varun 
>> wrote:
>> 
>>> Hello,
>>> 
>>> Just to be clear, I am not explicitly building the Hadoop edition. I get
>>> the described error when I simply specify the Spark version:
>>> 
>>>  mvn clean package -Dspark.version=2.0.0 -DskipTests
>>> 
>>> Thanks for the quick response!
>>> 
>>> 
>>> -Original Message-
>>> From: Sergey Kozlov [mailto:skoz...@gridgain.com]
>>> Sent: 19 September 2016 05:56
>>> To: dev@ignite.apache.org
>>> Subject: Re: Support for Spark 2.0
>>> 
>>> Hi
>>> 
>>> It's a known issue IGNITE-3596 Hadoop edition can't be compiled against
>>> spark 2.0.0 
>>> 
>>> Unfortunately there's no progress yet
>>> 
>>> On Mon, Sep 19, 2016 at 1:36 PM, Phadnis, Varun <
>> phad...@sky.optymyze.com>
>>> wrote:
>>> 
 Hello,
 
 Can someone please tell me when is the support for Spark 2.0 planned?
 
 Currently Ignite cannot be built for Spark 2.0. Attempting this yields
 the following error :
 
 
 --
 --
 
 [INFO] Building ignite-spark 1.8.0-SNAPSHOT [INFO]
 
 --
 --
 
 [INFO]
 
 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-spark
 --- [INFO] Deleting /home/spark/code/ignite/modules/spark/target
 
 [INFO]
 
 [INFO] --- flatten-maven-plugin:1.0.0-beta-3:clean
 (flatten.clean.before) @ ignite-spark --- [INFO] Deleting
 /home/spark/code/ignite/ modules/spark/pom-installed.xml
 
 [INFO]
 
 [INFO] --- maven-enforcer-plugin:1.4:enforce (default) @ ignite-spark
 --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process
 (default) @ ignite-spark --- [INFO] [INFO] ---
 maven-remote-resources-plugin:1.5:process
 (ignite-dependencies) @ ignite-spark --- [INFO] [INFO] ---
 maven-resources-plugin:2.6:resources (default-resources) @
 ignite-spark
 --- [INFO] Using 'UTF-8' encoding to copy filtered resources.
 
 [INFO] skip non existing resourceDirectory /home/spark/code/ignite/
 modules/spark/src/main/resources
 
 [INFO] Copying 4 resources
 
 [INFO] Copying 4 resources
 
 [INFO]
 
 [INFO] --- flatten-maven-plugin:1.0.0-beta-3:flatten (flatten) @
 ignite-spark --- [INFO] Generating flattened POM of project
 org.apache.ignite:ignite-spark:jar:1.8.0-SNAPSHOT...
 
 [WARNING] Ignoring multiple XML header comment!
 
 [INFO]
 
 [INFO] --- scala-maven-plugin:3.2.0:add-source (scala-compile-first) @
 ignite-spark --- [INFO] Add Source directory:
 
 /home/spark/code/ignite/modules/spark/src/main/scala
 
 [INFO] Add Test Source directory:
 
 /home/spark/code/ignite/modules/spark/src/test/scala
 
 [INFO]
 
 [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
 ignite-spark --- [WARNING]  Expected all dependencies to require Scala
 version: 2.11.7 [WARNING]
 org.apache.ignite:ignite-spark:1.8.0-SNAPSHOT
 requires scala
 
 version: 2.11.7
 
 [WARNING]  com.twitter:chill_2.11:0.8.0 requires scala version: 2.11.7
 [WARNING]  org.apache.spark:spark-core_2.11:2.0.0 requires scala
>>> version:
 
 2.11.8
 
 [WARNING] Multiple versions of scala libraries detected!
 
 [INFO] /home/spark/code/ignite/modules/spark/src/main/scala:-1: info:
 
 compiling
 
 [INFO] Compiling 8 source files to
 
 /home/spark/code/ignite/modules/spark/target/classes at 1474028222935
 [ERROR]
 
 /home/spark/code/ignite/modules/spark/src/main/scala/
 org/apache/ignite/spark/IgniteContext.scala:25:
 
 error: object Logging is not a member of package org.apache.spark
 [ERROR] import org.apache.spark.{Logging, SparkContext}
 
 [ERROR]        ^
 
 [ERROR]
 
 /home/spark/code/ignite/modules/spark/src/main/scala/
 org/apache/ignite/spark/IgniteContext.scala:37:
 
 error: not found: type

Re: Support for Spark 2.0

2016-09-20 Thread Denis Magda 
Is this the only issue we have with Spark 2.0?
https://issues.apache.org/jira/browse/IGNITE-3596 


—
Denis

> On Sep 20, 2016, at 11:54 AM, Vladimir Ozerov  wrote:
> 
> I think we can expect Spark 2.0 support to be added in one of the nearest
> releases (not sure if it will be 1.8 or 2.0).
> 
> On Mon, Sep 19, 2016 at 10:20 PM, Richard Siebeling 
> wrote:
> 
>> I'd wish someone could fix this, unfortunately I can't do anything about it
>> in the near future...
>> 
>> On Mon, Sep 19, 2016 at 3:20 PM, Phadnis, Varun 
>> wrote:
>> 
>>> Hello,
>>> 
>>> Just to be clear, I am not explicitly building the Hadoop edition. I get
>>> the described error when I simply specify the Spark version:
>>> 
>>>  mvn clean package -Dspark.version=2.0.0 -DskipTests
>>> 
>>> Thanks for the quick response!
>>> 
>>> 
>>> -Original Message-
>>> From: Sergey Kozlov [mailto:skoz...@gridgain.com]
>>> Sent: 19 September 2016 05:56
>>> To: dev@ignite.apache.org
>>> Subject: Re: Support for Spark 2.0
>>> 
>>> Hi
>>> 
>>> It's a known issue IGNITE-3596 Hadoop edition can't be compiled against
>>> spark 2.0.0 
>>> 
>>> Unfortunately there's no progress yet
>>> 
>>> On Mon, Sep 19, 2016 at 1:36 PM, Phadnis, Varun <
>> phad...@sky.optymyze.com>
>>> wrote:
>>> 
 Hello,
 
 Can someone please tell me when is the support for Spark 2.0 planned?
 
 Currently Ignite cannot be built for Spark 2.0. Attempting this yields
 the following error :
 
 
 --
 --
 
 [INFO] Building ignite-spark 1.8.0-SNAPSHOT [INFO]
 
 --
 --
 
 [INFO]
 
 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-spark
 --- [INFO] Deleting /home/spark/code/ignite/modules/spark/target
 
 [INFO]
 
 [INFO] --- flatten-maven-plugin:1.0.0-beta-3:clean
 (flatten.clean.before) @ ignite-spark --- [INFO] Deleting
 /home/spark/code/ignite/ modules/spark/pom-installed.xml
 
 [INFO]
 
 [INFO] --- maven-enforcer-plugin:1.4:enforce (default) @ ignite-spark
 --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process
 (default) @ ignite-spark --- [INFO] [INFO] ---
 maven-remote-resources-plugin:1.5:process
 (ignite-dependencies) @ ignite-spark --- [INFO] [INFO] ---
 maven-resources-plugin:2.6:resources (default-resources) @
 ignite-spark
 --- [INFO] Using 'UTF-8' encoding to copy filtered resources.
 
 [INFO] skip non existing resourceDirectory /home/spark/code/ignite/
 modules/spark/src/main/resources
 
 [INFO] Copying 4 resources
 
 [INFO] Copying 4 resources
 
 [INFO]
 
 [INFO] --- flatten-maven-plugin:1.0.0-beta-3:flatten (flatten) @
 ignite-spark --- [INFO] Generating flattened POM of project
 org.apache.ignite:ignite-spark:jar:1.8.0-SNAPSHOT...
 
 [WARNING] Ignoring multiple XML header comment!
 
 [INFO]
 
 [INFO] --- scala-maven-plugin:3.2.0:add-source (scala-compile-first) @
 ignite-spark --- [INFO] Add Source directory:
 
 /home/spark/code/ignite/modules/spark/src/main/scala
 
 [INFO] Add Test Source directory:
 
 /home/spark/code/ignite/modules/spark/src/test/scala
 
 [INFO]
 
 [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
 ignite-spark --- [WARNING]  Expected all dependencies to require Scala
 version: 2.11.7 [WARNING]
 org.apache.ignite:ignite-spark:1.8.0-SNAPSHOT
 requires scala
 
 version: 2.11.7
 
 [WARNING]  com.twitter:chill_2.11:0.8.0 requires scala version: 2.11.7
 [WARNING]  org.apache.spark:spark-core_2.11:2.0.0 requires scala
>>> version:
 
 2.11.8
 
 [WARNING] Multiple versions of scala libraries detected!
 
 [INFO] /home/spark/code/ignite/modules/spark/src/main/scala:-1: info:
 
 compiling
 
 [INFO] Compiling 8 source files to
 
 /home/spark/code/ignite/modules/spark/target/classes at 1474028222935
 [ERROR]
 
 /home/spark/code/ignite/modules/spark/src/main/scala/
 org/apache/ignite/spark/IgniteContext.scala:25:
 
 error: object Logging is not a member of package org.apache.spark
 [ERROR] import org.apache.spark.{Logging, SparkContext}
 
 [ERROR]^
 
 [ERROR]
 
 /home/spark/code/ignite/modules/spark/src/main/scala/
 org/apache/ignite/spark/IgniteContext.scala:37:
 
 error: not found: type Logging
 
 [ERROR] ) extends Serializable with Logging {
 
 [ERROR] ^
 
 [ERROR]
 
 /home/spark/code/ignite/modules/spark/src/main/scala/

Re: Support for Spark 2.0

2016-09-20 Thread Vladimir Ozerov 
I think we can expect Spark 2.0 support to be added in one of the nearest
releases (not sure if it will be 1.8 or 2.0).

On Mon, Sep 19, 2016 at 10:20 PM, Richard Siebeling 
wrote:

> I'd wish someone could fix this, unfortunately I can't do anything about it
> in the near future...
>
> On Mon, Sep 19, 2016 at 3:20 PM, Phadnis, Varun 
> wrote:
>
> > Hello,
> >
> > Just to be clear, I am not explicitly building the Hadoop edition. I get
> > the described error when I simply specify the Spark version:
> >
> >   mvn clean package -Dspark.version=2.0.0 -DskipTests
> >
> > Thanks for the quick response!
> >
> >
> > -Original Message-
> > From: Sergey Kozlov [mailto:skoz...@gridgain.com]
> > Sent: 19 September 2016 05:56
> > To: dev@ignite.apache.org
> > Subject: Re: Support for Spark 2.0
> >
> > Hi
> >
> > It's a known issue IGNITE-3596 Hadoop edition can't be compiled against
> > spark 2.0.0 
> >
> > Unfortunately there's no progress yet
> >
> > On Mon, Sep 19, 2016 at 1:36 PM, Phadnis, Varun <
> phad...@sky.optymyze.com>
> > wrote:
> >
> > > Hello,
> > >
> > > Can someone please tell me when is the support for Spark 2.0 planned?
> > >
> > > Currently Ignite cannot be built for Spark 2.0. Attempting this yields
> > > the following error :
> > >
> > >
> > > --
> > > --
> > >
> > > [INFO] Building ignite-spark 1.8.0-SNAPSHOT [INFO]
> > >
> > > --
> > > --
> > >
> > > [INFO]
> > >
> > > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-spark
> > > --- [INFO] Deleting /home/spark/code/ignite/modules/spark/target
> > >
> > > [INFO]
> > >
> > > [INFO] --- flatten-maven-plugin:1.0.0-beta-3:clean
> > > (flatten.clean.before) @ ignite-spark --- [INFO] Deleting
> > > /home/spark/code/ignite/ modules/spark/pom-installed.xml
> > >
> > > [INFO]
> > >
> > > [INFO] --- maven-enforcer-plugin:1.4:enforce (default) @ ignite-spark
> > > --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process
> > > (default) @ ignite-spark --- [INFO] [INFO] ---
> > > maven-remote-resources-plugin:1.5:process
> > > (ignite-dependencies) @ ignite-spark --- [INFO] [INFO] ---
> > > maven-resources-plugin:2.6:resources (default-resources) @
> > > ignite-spark
> > > --- [INFO] Using 'UTF-8' encoding to copy filtered resources.
> > >
> > > [INFO] skip non existing resourceDirectory /home/spark/code/ignite/
> > > modules/spark/src/main/resources
> > >
> > > [INFO] Copying 4 resources
> > >
> > > [INFO] Copying 4 resources
> > >
> > > [INFO]
> > >
> > > [INFO] --- flatten-maven-plugin:1.0.0-beta-3:flatten (flatten) @
> > > ignite-spark --- [INFO] Generating flattened POM of project
> > > org.apache.ignite:ignite-spark:jar:1.8.0-SNAPSHOT...
> > >
> > > [WARNING] Ignoring multiple XML header comment!
> > >
> > > [INFO]
> > >
> > > [INFO] --- scala-maven-plugin:3.2.0:add-source (scala-compile-first) @
> > > ignite-spark --- [INFO] Add Source directory:
> > >
> > > /home/spark/code/ignite/modules/spark/src/main/scala
> > >
> > > [INFO] Add Test Source directory:
> > >
> > > /home/spark/code/ignite/modules/spark/src/test/scala
> > >
> > > [INFO]
> > >
> > > [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> > > ignite-spark --- [WARNING]  Expected all dependencies to require Scala
> > > version: 2.11.7 [WARNING]
> > > org.apache.ignite:ignite-spark:1.8.0-SNAPSHOT
> > > requires scala
> > >
> > > version: 2.11.7
> > >
> > > [WARNING]  com.twitter:chill_2.11:0.8.0 requires scala version: 2.11.7
> > > [WARNING]  org.apache.spark:spark-core_2.11:2.0.0 requires scala
> > version:
> > >
> > > 2.11.8
> > >
> > > [WARNING] Multiple versions of scala libraries detected!
> > >
> > > [INFO] /home/spark/code/ignite/modules/spark/src/main/scala:-1: info:
> > >
> > > compiling
> > >
> > > [INFO] Compiling 8 source files to
> > >
> > > /home/spark/code/ignite/modules/spark/target/classes at 1474028222935
> > > [ERROR]
> > >
> > > /home/spark/code/ignite/modules/spark/src/main/scala/
> > > org/apache/ignite/spark/IgniteContext.scala:25:
> > >
> > > error: object Logging is not a member of package org.apache.spark
> > > [ERROR] import org.apache.spark.{Logging, SparkContext}
> > >
> > > [ERROR]^
> > >
> > > [ERROR]
> > >
> > > /home/spark/code/ignite/modules/spark/src/main/scala/
> > > org/apache/ignite/spark/IgniteContext.scala:37:
> > >
> > > error: not found: type Logging
> > >
> > > [ERROR] ) extends Serializable with Logging {
> > >
> > > [ERROR] ^
> > >
> > > [ERROR]
> > >
> > > /home/spark/code/ignite/modules/spark/src/main/scala/
> > > org/apache/ignite/spark/IgniteContext.scala:50:
> > >
> > > error: not found: value logInfo
> > >
> > > [ERROR] logInfo("Will start Ignite nodes on " + workers + "
> > >
> > > workers")
> > >
> > > [ERROR]

[jira] [Created] (IGNITE-3943) Hadoop: change scripts.

2016-09-20 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3943:
---

 Summary: Hadoop: change scripts.
 Key: IGNITE-3943
 URL: https://issues.apache.org/jira/browse/IGNITE-3943
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Assignee: Ivan Veselovsky
 Fix For: 1.8


1) Remove and do not use {{HadoopClasspathMain}}.
2) Do not include {{hadoop-impl}} module into node class path.
3) {{HadoopClasspathUtils.classpathForClassLoader}} must include 
{{hadoop-impl}} in class path.



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

[GitHub] ignite pull request #1091: Ignite 3941

2016-09-20 Thread devozerov 
Github user devozerov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1086: IGNITE-3313 Make table name optional in Cassandra...

2016-09-20 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3942) Hadoop: HadoopProcesor must be created using HadoopClassLoader.

2016-09-20 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3942:
---

 Summary: Hadoop: HadoopProcesor must be created using 
HadoopClassLoader.
 Key: IGNITE-3942
 URL: https://issues.apache.org/jira/browse/IGNITE-3942
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.7
Reporter: Vladimir Ozerov
 Fix For: 1.8






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

[GitHub] ignite pull request #1089: Ignite 3929 1

2016-09-20 Thread devozerov 
Github user devozerov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1091: Ignite 3941

2016-09-20 Thread devozerov 
GitHub user devozerov opened a pull request:

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

Ignite 3941



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

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

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

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


commit 2fe0272ba5f2c9003ab57844ba730a384bb67ca1
Author: vozerov-gridgain 
Date:   2016-09-16T09:55:00Z

IGNITE-3912: Preliminary changes.

commit 64b0094533f7ea85d1fa37794165a94b4ef27d2d
Author: iveselovskiy 
Date:   2016-09-16T13:52:17Z

IGNITE-3914: refactored HadoopClassLoader : extracted hadoop-specific logic 
into separate processor.

commit a6c837d78cf7a21e7ffea40b1a55ae502caa63f5
Author: iveselovskiy 
Date:   2016-09-16T13:54:16Z

IGNITE-3914: moved Hadop class loader

commit d68d0add5e353f6f0cd1ed004f441a995e87a6f1
Author: iveselovskiy 
Date:   2016-09-16T13:58:37Z

Revert "IGNITE-3914: moved Hadop class loader"

This reverts commit a6c837d78cf7a21e7ffea40b1a55ae502caa63f5.

commit cb5f9ec61b97dc939c06569a217d4c0c9ab9a441
Author: iveselovskiy 
Date:   2016-09-16T13:58:59Z

Revert "IGNITE-3914: refactored HadoopClassLoader : extracted 
hadoop-specific logic into separate processor."

This reverts commit 64b0094533f7ea85d1fa37794165a94b4ef27d2d.

commit 857cdcde65f1885ee032a1a85462818c585dfa82
Author: vozerov-gridgain 
Date:   2016-09-19T10:26:23Z

IGNITE-3916: Created separate module.

commit cb304b14508011c9a3f3ba73d4a8ae3d51bd9045
Author: vozerov-gridgain 
Date:   2016-09-20T07:55:22Z

IGNITE-3914: Introduced HadoopHelper.

commit 41de3ab575a8bfbea07fa661beac1d6e7735ea3b
Author: vozerov-gridgain 
Date:   2016-09-20T12:54:48Z

IGNITE-3918: Moved public classes from "ignite-hadoop-impl" to 
"ignite-hadoop" module.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1090: IGNITE-3939: Compact long zero values binary repr...

2016-09-20 Thread AMashenkov 
GitHub user AMashenkov opened a pull request:

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

IGNITE-3939: Compact long zero values binary representation



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

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

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

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


commit 780bf23d5c89452dd062be4fab9e2e56d50bb9e2
Author: sboikov 
Date:   2016-09-19T15:19:33Z

ignite-3810 Fixed hang in FileSwapSpaceSpi when too large value is stored

commit c1372ce2f0633968036fcfb079718214605c3350
Author: sboikov 
Date:   2016-09-20T08:39:37Z

Client discovery: wait during join if receive RES_CONTINUE_JOIN, RES_WAIT.

commit f6f417ff84f7823ebf3ab166980893d22995f143
Author: Andrey V. Mashenkov 
Date:   2016-09-20T12:02:56Z

Implemented.

commit c92803ec3f31e7ef5384876fa4fa0a959b08247d
Author: Andrey V. Mashenkov 
Date:   2016-09-20T14:03:37Z

Minor fixes.
Tests added.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3941) Hadoop: Introduce common HadoopClassLoader.

2016-09-20 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-3941:
---

 Summary: Hadoop: Introduce common HadoopClassLoader.
 Key: IGNITE-3941
 URL: https://issues.apache.org/jira/browse/IGNITE-3941
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.8






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

[GitHub] ignite pull request #1089: Ignite 3929 1

2016-09-20 Thread devozerov 
GitHub user devozerov opened a pull request:

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

Ignite 3929 1



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

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

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

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


commit c2f8df96907e096fdeaa8d040463ff5ec1662395
Author: vozerov-gridgain 
Date:   2016-06-14T08:09:01Z

IGNITE-3294: IGFS: Improved "create" performance in DUAL mode.

commit 95513d3214dd1ea7a1a68d6f1709af004c2efccd
Author: vozerov-gridgain 
Date:   2016-06-14T08:36:33Z

IGNITE-3294: IGFS: Created separate processor optimized for entry rename.

commit e733e912cccf2c83d7e31d6f856b30fc4c663975
Author: vozerov-gridgain 
Date:   2016-06-14T14:39:44Z

IGNITE-2938: IGFS: Puts during secondary file reads are now performed 
synchronously and with proper semantics.

commit b46422ad64f531900263fb36f6ff28373e4346f1
Author: vozerov-gridgain 
Date:   2016-06-15T13:02:53Z

IGNITE-3312: IGFS: Fixed a bug introduced during create() routine reworking.

commit b8411955e5169b38430e077c5b4ed85d8e95b83c
Author: Vladislav Pyatkov 
Date:   2016-06-15T14:18:27Z

IGNITE-2767: Cont. query remote filter requires to be in client nodes class 
path.
Reviewed and merged by Denis Magda.

commit a672e576cf88e21859944474355a91d9f4699550
Author: agura 
Date:   2016-06-14T14:32:25Z

ignite-3209 Waiting for affinity topology in case of failover for affinity 
call

commit 19aeec39fe84f141a97ba1b0f4e6b48d2bb21f27
Author: Vladislav Pyatkov 
Date:   2016-06-15T15:43:22Z

IGNITE-3151: Using IgniteCountDownLatch sometimes drives to dead lock.
Reviewed and merged by Denis Magda.

commit b5f4aac2a5daad96cdac4df9abf91713824ff2c0
Author: Anton Vinogradov 
Date:   2016-06-16T11:14:33Z

GG-11237 KeepBinary flag will not be send to another node.

commit 40d41c10e3179436bc1ae1e12bdc2d6e3a7208f0
Author: Anton Vinogradov 
Date:   2016-06-16T07:25:38Z

IGNITE-3216 Need to deduplicate addresses registered in the IP finder

commit e05c012f293dcad2cd3a184e6d257a0cb2af509a
Author: Anton Vinogradov 
Date:   2016-06-16T07:49:48Z

IGNITE-3153 TcpDiscoveryZookeeperIpFinder doesn't properly handle client 
reconnections

commit 1689164bf0c7cf2d506478f8eaff27c5405e1d04
Author: Kristian Rosenvold 
Date:   2016-06-16T11:46:17Z

When multiple addresses resolve to same name, TcpDiscoverySharedFsIpFinder 
fails on unregister.
Reviewed and merged by Denis Magda.

commit 6fb108f1c24aa4ffc2e5dcf0442637bbdf856b50
Author: Anton Vinogradov 
Date:   2016-06-16T15:58:08Z

Compatibility fix (removal reverted)

commit a527bf88133820885be1f6bd4d8e286bf97ac6d0
Author: sboikov 
Date:   2016-06-17T08:19:27Z

IgniteCacheRandomOperationBenchmark: distinguish small/large value classes 
to better estimate cache size.

commit 0fd1ab6d21447ae63e09535057cec6326539520f
Author: sboikov 
Date:   2016-06-17T09:04:13Z

IgniteCacheRandomOperationBenchmark: minor code style changes.

commit 0773332335f965af3ec18a474138e3ea6157fc6e
Author: agura 
Date:   2016-06-16T10:03:03Z

ignite-3239 Fix of java.io.IOException: Resource deadlock avoided

commit 106b8691a313d2c4480bb18bd8e3cfc902b5e214
Author: Valentin Kulichenko 
Date:   2016-06-17T11:57:45Z

IGNITE-3334 - TcpDiscoveryZookeeperIpFinder used INFO logging without 
isInfoEnabled() check

commit f177d4312c47cd31e4931c8c1e0f89c2325dedb1
Author: Alexey Kuznetsov 
Date:   2016-06-21T04:45:29Z

IGNITE-3277 Replaced outdated json-lib 2.4 to modern Jackson 2.7.5.

commit 0c5db20be936997b7fa07dd26840424d1633bdae
Author: Alexey Kuznetsov 
Date:   2016-06-21T08:08:47Z

IGNITE-3277 Cleanup pom.xml.

commit 482015e9924425c70901fdae36222110af6e6c16
Author: Alexey Kuznetsov 
Date:   2016-06-21T10:49:47Z

IGNITE-3277 Fixed null key serialization.

commit 68b25df3b3e1979c0972d75675f2c9aa2b48d9a7
Author: vozerov-gridgain 
Date:   2016-06-21T13:57:28Z

IGNITE-3341: Hadoop: Added ability to link user-define native libraries to 
HadoopClassLoader.

commit 3ca0bc877bf356eca93c9c9a5e225362c2b58769
Author: vozerov-gridgain 
Date:   2016-06-21T14:11:37Z

Merge remote-tracking branch 'upstream/gridgain-7.6.1' into gridgain-7.6.1

commit 5177c33ec66d98ae379f2908dc056f58ee3cbb40
Author: Anton Vinogradov

about isolated ignite clusters on the same set of machines

2016-09-20 Thread 李玉珏 

Guys:

in our network, we want to isolate some of the machine to build cluster 
for testing, I looked at the following document,also do the test, but 
found that this document may not be correct:


https://apacheignite.readme.io/v1.7/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin

If the addresses property of TcpDiscoveryVmIpFinder is set to 127.0.0.1, 
multiple ignite nodes started in the same machine,is the isolation of 
cluster, has nothing to do with the localPort attribute, if do not set 
the addresses property, even if the localPort property of 
TcpDiscoverySpi and TcpCommunicationSpi are diff, also belong to the 
same cluster.



The way I think is to set the IP address list for the addresses 
property, but it doesn't look elegant, does anyone in the community know 
the right, or elegant way?

[GitHub] ignite pull request #1088: Ignite 3918

2016-09-20 Thread devozerov 
Github user devozerov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3939) Compact long zero values binary representation

2016-09-20 Thread Andrew Mashenkov (JIRA) 
Andrew Mashenkov created IGNITE-3939:


 Summary: Compact long zero values binary representation
 Key: IGNITE-3939
 URL: https://issues.apache.org/jira/browse/IGNITE-3939
 Project: Ignite
  Issue Type: Improvement
  Components: binary
Affects Versions: 1.7
Reporter: Andrew Mashenkov
 Fix For: 1.8


We can use separate type for Long zero values and exclude 8-byte value from 
binary representation. This will reduce memory footprint and network load.



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

[GitHub] ignite pull request #1088: Ignite 3918

2016-09-20 Thread devozerov 
GitHub user devozerov opened a pull request:

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

Ignite 3918



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

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

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

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


commit 2fe0272ba5f2c9003ab57844ba730a384bb67ca1
Author: vozerov-gridgain 
Date:   2016-09-16T09:55:00Z

IGNITE-3912: Preliminary changes.

commit 64b0094533f7ea85d1fa37794165a94b4ef27d2d
Author: iveselovskiy 
Date:   2016-09-16T13:52:17Z

IGNITE-3914: refactored HadoopClassLoader : extracted hadoop-specific logic 
into separate processor.

commit a6c837d78cf7a21e7ffea40b1a55ae502caa63f5
Author: iveselovskiy 
Date:   2016-09-16T13:54:16Z

IGNITE-3914: moved Hadop class loader

commit d68d0add5e353f6f0cd1ed004f441a995e87a6f1
Author: iveselovskiy 
Date:   2016-09-16T13:58:37Z

Revert "IGNITE-3914: moved Hadop class loader"

This reverts commit a6c837d78cf7a21e7ffea40b1a55ae502caa63f5.

commit cb5f9ec61b97dc939c06569a217d4c0c9ab9a441
Author: iveselovskiy 
Date:   2016-09-16T13:58:59Z

Revert "IGNITE-3914: refactored HadoopClassLoader : extracted 
hadoop-specific logic into separate processor."

This reverts commit 64b0094533f7ea85d1fa37794165a94b4ef27d2d.

commit 857cdcde65f1885ee032a1a85462818c585dfa82
Author: vozerov-gridgain 
Date:   2016-09-19T10:26:23Z

IGNITE-3916: Created separate module.

commit 25d50a272f57e1d1fac31435d69400b16f51fc2f
Author: vozerov-gridgain 
Date:   2016-09-19T14:14:04Z

IGNITE-3918: Split secondary file system interface.

commit c1eab80317b8aaf625b0bc8c4ee77100d17a6285
Author: vozerov-gridgain 
Date:   2016-09-19T14:15:44Z

IGNITE-3918: WIP. No Hadoop dependencies in secondary FS.

commit 9e50a4799f39ccb1559e43854cd1e45787acb39f
Author: vozerov-gridgain 
Date:   2016-09-19T14:18:51Z

IGNITE-3918: Preparing factories.

commit b9fb23521df3821435912b135fbda1bc7b2402f3
Author: vozerov-gridgain 
Date:   2016-09-19T14:21:49Z

IGNITE-3918: Better naming.

commit a7e26dc4a85db92ca846533b2ba2ad91d820393f
Author: vozerov-gridgain 
Date:   2016-09-19T14:37:35Z

IGNITE-3918: WIP.

commit 3aa360c3849bf7869b39bdd1f0eece5de64da046
Author: vozerov-gridgain 
Date:   2016-09-19T14:57:02Z

IGNITE-3918: WIP.

commit cb304b14508011c9a3f3ba73d4a8ae3d51bd9045
Author: vozerov-gridgain 
Date:   2016-09-20T07:55:22Z

IGNITE-3914: Introduced HadoopHelper.

commit cc11ef20b5425d41ca665fd8e43d4fae304b0e96
Author: vozerov-gridgain 
Date:   2016-09-20T08:14:54Z

Merge branch 'ignite-1.6.8-hadoop' into ignite-3918

commit 53cedbbde4bff5573e0ed73bddb627cfaafac0a0
Author: vozerov-gridgain 
Date:   2016-09-20T08:16:22Z

Reverting serialization changes in factories.

commit 95f6fc54c52bcb0c48d9ef7bf4e867eda2682ae6
Author: vozerov-gridgain 
Date:   2016-09-20T08:23:03Z

Inverting control.

commit 2195fa59afd5754f4e42f9b5c7eb10dc088661c2
Author: vozerov-gridgain 
Date:   2016-09-20T08:36:08Z

Finalized factories.

commit 841716c919f3069cf0a026d79226af46a2827f8c
Author: vozerov-gridgain 
Date:   2016-09-20T08:59:35Z

WIP on delegates.

commit c048858b604f4cfea69c24aaed8114a535b35b2d
Author: vozerov-gridgain 
Date:   2016-09-20T09:16:38Z

WIP.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1065: IGNITE-3859 IGFS: Support direct PROXY mode invoc...

2016-09-20 Thread tledkov-gridgain 
Github user tledkov-gridgain closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1083: IGNITE-3859 IGFS: Support direct PROXY mode invoc...

2016-09-20 Thread tledkov-gridgain 
Github user tledkov-gridgain closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1087: IGNITE-3926: Exception thrown from static job ini...

2016-09-20 Thread AMashenkov 
GitHub user AMashenkov opened a pull request:

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

IGNITE-3926: Exception thrown from static job initializer hangs remote 
future.



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

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

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

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


commit 8fc5092610865e80d81b86b50b4ecfc0921b67ff
Author: Andrey V. Mashenkov 
Date:   2016-09-19T16:01:09Z

Fixed

commit 7e5b51486ccff375b943f6ce2e1bc5505d39400e
Author: Andrey V. Mashenkov 
Date:   2016-09-19T16:27:11Z

 Fixed similar bug inTasksProcessor

commit d930866b5bc49f057dddeeb4a2548ae83a0810b2
Author: Andrey V. Mashenkov 
Date:   2016-09-20T09:07:51Z

Minor fixes




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1075: Ignite 3914

2016-09-20 Thread devozerov 
Github user devozerov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3938) JDBC POJO should support escaping for database schema, table and field names

2016-09-20 Thread Alexey Kuznetsov (JIRA) 
Alexey Kuznetsov created IGNITE-3938:


 Summary: JDBC POJO should support escaping for database schema, 
table and field names
 Key: IGNITE-3938
 URL: https://issues.apache.org/jira/browse/IGNITE-3938
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.8


Sometimes database names could be very *strange* and this could be handled only 
via escaping. We need to support this.
Adding {code}String JdbcDialect.escape(name){code} method looks like a good 
solution.



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

[jira] [Created] (IGNITE-3937) DatabaseMetadataDialect should properly handle unsigned types

2016-09-20 Thread Alexey Kuznetsov (JIRA) 
Alexey Kuznetsov created IGNITE-3937:


 Summary: DatabaseMetadataDialect should properly handle unsigned 
types
 Key: IGNITE-3937
 URL: https://issues.apache.org/jira/browse/IGNITE-3937
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.8


Some databases (for example MySQL) could declare columns like this {code}id 
int(11) unsigned{code} in this case *DatabaseMetadataDialect* will map to 
*int*, but should map to *long*.



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

[jira] [Created] (IGNITE-3935) ClassLoaders are not switched during object deserialization

2016-09-20 Thread Denis Magda (JIRA) 
Denis Magda created IGNITE-3935:
---

 Summary: ClassLoaders are not switched during object 
deserialization
 Key: IGNITE-3935
 URL: https://issues.apache.org/jira/browse/IGNITE-3935
 Project: Ignite
  Issue Type: Bug
  Components: binary
Affects Versions: 1.6
Reporter: Denis Magda


If an object is being deserialized with ClassLoader A then this ClassLoader A 
will be used for the deserialization of the whole object's state, i.e., 
including all its fields that can be custom objects loaded by ClassLoader B. 

In a basic scenario we can have an object of some Ignite class that is 
presented in the classpath. That Ignite class may enclose an object that is 
loaded by peer-class-loading class loader. The deserialization will fail 
because Ignite won't switch to the peer-class-loading loader when it's needed.

To reproduce the issue do the following:
1. Start a remote ignite node using {{./ignite.sh 
../examples/config/example-ignite.xml}}
2. Run the code below
{code}
public class StreamingExample {`
public static class StreamingExampleCacheEntryProcessor implements 
CacheEntryProcessor {
@Override
public Object process(MutableEntry e, Object... arg) throws 
EntryProcessorException {
Long val = e.getValue();
e.setValue(val == null ? 1L : val + 1);
return null;
}
}

public static void main(String[] args) throws IgniteException, IOException {
Ignition.setClientMode(true);
try (Ignite ignite = Ignition.start("examples/config/example-ignite.xml")) {
IgniteCache stmCache = ignite.getOrCreateCache("mycache");
try (IgniteDataStreamer stmr = 
ignite.dataStreamer(stmCache.getName())) {
stmr.allowOverwrite(true);
stmr.receiver(StreamTransformer.from(new 
StreamingExampleCacheEntryProcessor()));
stmr.addData("word", 1L);
System.out.println("Finished");
}
}
}
{code}

However if to modify this code to the following everything will work fine 

{code}
public class StreamingExample {

public static class StreamingExampleCacheEntryProcessor extends 
StreamTransformer {
@Override
public Object process(MutableEntry e, Object... arg) 
throws EntryProcessorException {
System.out.println("Executed!");
Long val = e.getValue();
e.setValue(val == null ? 1L : val + 1);
return null;
}
}

public static void main(String[] args) throws IgniteException, IOException {
Ignition.setClientMode(true);
try (Ignite ignite = 
Ignition.start("examples/config/example-ignite.xml")) {
IgniteCache stmCache = 
ignite.getOrCreateCache("mycache");
try (IgniteDataStreamer stmr = 
ignite.dataStreamer(stmCache.getName())) {
stmr.allowOverwrite(true);
stmr.receiver(new StreamingExampleCacheEntryProcessor());
stmr.addData("word", 1L);
System.out.println("Finished");
}
}
}
}
{code}



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

[GitHub] ignite pull request #1086: IGNITE-3313 Make table name optional in Cassandra...

2016-09-20 Thread irudyak 
GitHub user irudyak opened a pull request:

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

IGNITE-3313 Make table name optional in Cassandra persistence descriptor



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

$ git pull https://github.com/irudyak/ignite ignite-3313

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

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


commit e328234cd86f2c1ca16885cdc0e20cc6d492ce85
Author: Igor 
Date:   2016-09-20T04:57:02Z

table name is optional now in Cassandra persistence descriptor




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---