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

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-6083:
--

[~Alexey Kuznetsov], I like the second version of the test better. Note 
however, that we must make sure that the EntryProcessor will never change the 
entry value to a value based on some outdated cached entry. 
Consider the following scenario:
T1:
Start tx, run cache.invoke(), the value is stored in TxEntry
T2:
run cache.put(), which overwrites the original value
T1:
run cache.invoke(), it received an old cached value
commit()

Can you please add a multi-threaded test verifying that in such a scenario the 
second thread will get a proper optimistic conflict exception?

Also, please attach a link to a TC run.

Thanks!

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



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

[jira] [Updated] (IGNITE-7774) Missing Google Cloud libraries at binary release

[Roman Guseinov (JIRA)]

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

Roman Guseinov updated IGNITE-7774:
---
Description: 
It looks like following libraries aren't included in the build:
 * google-http-client-1.22.0.jar
 * google-http-client-jackson2-1.22.0.jar
 * google-oauth-client-1.22.0.jar

Steps to reproduce:
1. Download apache-ignite-fabric-2.3.0-bin.zip 
([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
2. Unzip archive.
3. Move ignite-rest-http from /libs/optional to /libs
4. Move ignite-gce from /libs/optional to /libs
5. Update IgniteConfiguration in default-config.xml:

{code:xml}

  

  




  

  

{code}
4. Copy  into $IGNITE_HOME
5. Run bin/ignite.sh
6. Log:
{code:java}
class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
application context (make sure all classes used in Spring configuration are 
present at CLASSPATH) 
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
 at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
 at org.apache.ignite.Ignition.start(Ignition.java:350)
 at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
instantiate Spring XML application context (make sure all classes used in 
Spring configuration are present at CLASSPATH) 
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
 at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
 at org.apache.ignite.Ignition.start(Ignition.java:347)
 ... 1 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' 
defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Cannot create inner bean 
'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type 
[org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean 
property 'discoverySpi'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' 
defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Cannot create inner bean 
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
 of type 
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
 while setting bean property 'ipFinder'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
 defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Instantiation of bean failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]:
 No default constructor found; nested exception is 
java.lang.NoClassDefFoundError: 
com/google/api/client/http/AbstractInputStreamContent
 at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
 at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1531)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1276)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
 at 

[jira] [Updated] (IGNITE-7774) Missing Google Cloud libraries at binary release

[Roman Guseinov (JIRA)]

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

Roman Guseinov updated IGNITE-7774:
---
Description: 
It looks like following libraries aren't included in the build:
 * google-http-client-1.22.0.jar
 * google-http-client-jackson2-1.22.0.jar
 * google-oauth-client-1.22.0.jar

Steps to reproduce:
1. Download apache-ignite-fabric-2.3.0-bin.zip 
([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
2. Unzip archive.
3. Move ignite-rest-http from /libs/optional to /libs
4. Move ignite-gce from /libs/optional to /libs
5. Update IgniteConfiguration in default-config.xml:

{code:xml}

  

  




  

  

{code}
6. Copy  into $IGNITE_HOME
7. Run bin/ignite.sh
8. Log:
{code:java}
class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
application context (make sure all classes used in Spring configuration are 
present at CLASSPATH) 
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
 at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
 at org.apache.ignite.Ignition.start(Ignition.java:350)
 at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
instantiate Spring XML application context (make sure all classes used in 
Spring configuration are present at CLASSPATH) 
[springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
 at 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
 at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
 at org.apache.ignite.Ignition.start(Ignition.java:347)
 ... 1 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' 
defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Cannot create inner bean 
'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type 
[org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean 
property 'discoverySpi'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' 
defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Cannot create inner bean 
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
 of type 
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]
 while setting bean property 'ipFinder'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 
'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
 defined in URL 
[file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
 Instantiation of bean failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder]:
 No default constructor found; nested exception is 
java.lang.NoClassDefFoundError: 
com/google/api/client/http/AbstractInputStreamContent
 at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
 at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1531)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1276)
 at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
 at 

[jira] [Commented] (IGNITE-7774) Missing Google Cloud libraries at binary release

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7774:


GitHub user gromtech opened a pull request:

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

IGNITE-7774 Missing Google Cloud libraries at binary release

Added missing dependencies

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

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

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

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


commit 545c5c30934729a00e889c7e35a5a16e33a21155
Author: Roman Guseinov 
Date:   2018-02-21T10:34:39Z

IGNITE-7774 Missing Google Cloud libraries at binary release

Added missing dependencies




> Missing Google Cloud libraries at binary release
> 
>
> Key: IGNITE-7774
> URL: https://issues.apache.org/jira/browse/IGNITE-7774
> Project: Ignite
>  Issue Type: Bug
>  Components: build
> Environment: * Ubuntu 16.04.3 LTS
> * Apache Ignite 2.3.0
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>  Labels: build
>
> It looks like following libraries aren't included in the build:
>  * google-http-client-1.22.0.jar
>  * google-http-client-jackson2-1.22.0.jar
>  * google-oauth-client-1.22.0.jar
> Steps to reproduce:
>  # Download apache-ignite-fabric-2.3.0-bin.zip 
> ([http://apache-mirror.rbc.ru/pub/apache//ignite/2.3.0/apache-ignite-fabric-2.3.0-bin.zip]).
> 2. Unzip archive.
> 2. Move ignite-gce from /libs/optional to /libs
> 3. Update IgniteConfiguration in default-config.xml:
> {code:xml}
> 
>   
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder">
> 
> 
> 
>  value="discovery-sp...@apache-ignite.iam.gserviceaccount.com"/>
>   
> 
>   
> 
> {code}
> 4. Copy  into $IGNITE_HOME
> 5. Run bin/ignite.sh
> 6. Log:
> {code:java}
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
> application context (make sure all classes used in Spring configuration are 
> present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
>  at org.apache.ignite.Ignition.start(Ignition.java:350)
>  at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> instantiate Spring XML application context (make sure all classes used in 
> Spring configuration are present at CLASSPATH) 
> [springUrl=file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
>  at 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
>  at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:673)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
>  at org.apache.ignite.Ignition.start(Ignition.java:347)
>  ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' of type 
> [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean 
> property 'discoverySpi'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#65e2dbf3' 
> defined in URL 
> [file:/home/roman/Desktop/releases/gridgain-professional-fabric-2.3.3/config/default-config.xml]:
>  Cannot create inner bean 
> 'org.apache.ignite.spi.discovery.tcp.ipfinder.gce.TcpDiscoveryGoogleStorageIpFinder#1d16f93d'
>  of type 
> 

[jira] [Commented] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-7805:
--

[This|https://github.com/DevExpress/testcafe/issues/2085] issue might be 
related.

> Web console: fix admin-panel E2E test under macOS
> -
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During 
> the issue initial research I managed to find that AngularStrap modal 
> animations take way more time to complete compared to a regular, non-TestCafe 
> environment. The broken animation makes elements appear in an unexpected 
> order, which in turn causes TestCafe selectors to select wrong elements or 
> correct elements, but at wrong time. The cause might lie in both TestCafe and 
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
> GitHub issue or report one (don't forget about a minimal reproduction 
> scenario the TestCafe guys can use). If there's something wrong with either 
> our own E2E or web console code, try to fix it.



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

[jira] [Assigned] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7805:


Assignee: Alexander Kalinin  (was: Ilya Borisov)

> Web console: fix admin-panel E2E test under macOS
> -
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexander Kalinin
>Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During 
> the issue initial research I managed to find that AngularStrap modal 
> animations take way more time to complete compared to a regular, non-TestCafe 
> environment. The broken animation makes elements appear in an unexpected 
> order, which in turn causes TestCafe selectors to select wrong elements or 
> correct elements, but at wrong time. The cause might lie in both TestCafe and 
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
> GitHub issue or report one (don't forget about a minimal reproduction 
> scenario the TestCafe guys can use). If there's something wrong with either 
> our own E2E or web console code, try to fix it.



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

[jira] [Commented] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-7805:
--

IGNITE-7805 was found during IGNITE-7729

> Web console: fix admin-panel E2E test under macOS
> -
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During 
> the issue initial research I managed to find that AngularStrap modal 
> animations take way more time to complete compared to a regular, non-TestCafe 
> environment. The broken animation makes elements appear in an unexpected 
> order, which in turn causes TestCafe selectors to select wrong elements or 
> correct elements, but at wrong time. The cause might lie in both TestCafe and 
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
> GitHub issue or report one (don't forget about a minimal reproduction 
> scenario the TestCafe guys can use). If there's something wrong with either 
> our own E2E or web console code, try to fix it.



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

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

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-7655 at 2/26/18 6:01 AM:
--

[~dmagda]

> What does appending mean here? As far as I understand, you're just going to 
> insert new data ignoring the data which keys are already in the table.

Appends mean we will not execute {{DROP TABLE}}/{{CREATE TABLE}}.
Since all inserts are executed through IgniteDataStreamer behaviour will be 
like this:

* {{OPTION_STREAMER_ALLOW_OVERWRITE=false}} - existing keys will be ignored.
* {{OPTION_STREAMER_ALLOW_OVERWRITE=true}} - existing key/value will 
overwritten with DataFrame data.

> which mode is a default? 

ErrorIfExsists

> Is there a mode that updates existing rows, inserts new from the data frame 
> and does NOT delete the rows that were in the table initially?

{{SaveMode.Append}} + {{OPTION_STREAMER_ALLOW_OVERWRITE=true}}

> How do I set a mode? You start talking about the data frames right away but 
> do not explain how to use them.

One can use {{dataFrame.write.mode(SaveMode.Append)}}.  It's a part of Spark 
API. 
OK, I will add an example to the page.

> I would start "Saving Data Frame" section with the explanation of how all 
> this works

OK. Will do.


was (Author: nizhikov):
[~dmagda]

> What does appending mean here? As far as I understand, you're just going to 
> insert new data ignoring the data which keys are already in the table.

Appends mean we will not execute `DROP TABLE`/`CREATE TABLE`.
Since all inserts are executed through IgniteDataStreamer behaviour will be 
like this:

* `OPTION_STREAMER_ALLOW_OVERWRITE=false` - existing keys will be ignored.
* `OPTION_STREAMER_ALLOW_OVERWRITE=true` - existing key/value will overwritten 
with DataFrame data.

> which mode is a default? 

ErrorIfExsists

> Is there a mode that updates existing rows, inserts new from the data frame 
> and does NOT delete the rows that were in the table initially?

`SaveMode.Append` + `OPTION_STREAMER_ALLOW_OVERWRITE=true`

> How do I set a mode? You start talking about the data frames right away but 
> do not explain how to use them.

One can use `dataFrame.write.mode(SaveMode.Append)`. It's a part of Spark API. 
OK, I will add an example to the page.

> I would start "Saving Data Frame" section with the explanation of how all 
> this works

OK. Will do.

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



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

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

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7655:
-

[~dmagda]

> What does appending mean here? As far as I understand, you're just going to 
> insert new data ignoring the data which keys are already in the table.

Appends mean we will not execute `DROP TABLE`/`CREATE TABLE`.
Since all inserts are executed through IgniteDataStreamer behaviour will be 
like this:

* `OPTION_STREAMER_ALLOW_OVERWRITE=false` - existing keys will be ignored.
* `OPTION_STREAMER_ALLOW_OVERWRITE=true` - existing key/value will overwritten 
with DataFrame data.

> which mode is a default? 

ErrorIfExsists

> Is there a mode that updates existing rows, inserts new from the data frame 
> and does NOT delete the rows that were in the table initially?

`SaveMode.Append` + `OPTION_STREAMER_ALLOW_OVERWRITE=true`

> How do I set a mode? You start talking about the data frames right away but 
> do not explain how to use them.

One can use `dataFrame.write.mode(SaveMode.Append)`. It's a part of Spark API. 
OK, I will add an example to the page.

> I would start "Saving Data Frame" section with the explanation of how all 
> this works

OK. Will do.

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



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

[jira] [Updated] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7805:
-
Component/s: wizards

> Web console: fix admin-panel E2E test under macOS
> -
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During 
> the issue initial research I managed to find that AngularStrap modal 
> animations take way more time to complete compared to a regular, non-TestCafe 
> environment. The broken animation makes elements appear in an unexpected 
> order, which in turn causes TestCafe selectors to select wrong elements or 
> correct elements, but at wrong time. The cause might lie in both TestCafe and 
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
> GitHub issue or report one (don't forget about a minimal reproduction 
> scenario the TestCafe guys can use). If there's something wrong with either 
> our own E2E or web console code, try to fix it.



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

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

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7803:
-
Description: 
Scenario 1:
 # cache.put(1, new Person(1, Alex, 300))
 # get via REST: 
{{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}

Scenario 2:
 # create table person(id integer primary key, name varchar(100), salary 
integer);
 # insert into person(id, name, salary) values (1, Alex, 300)
 # get via REST: 
{{[http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1|http://hostport/]}}

  was:
Scenario:
 # create table person(id integer primary key, name varchar(100), salary 
integer);
 # insert into person(id, name, salary) values (1, Alex, 300)
 # get via REST: 
{{http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1}}


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



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

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

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7803:
-
Summary: REST: Add support to get values inserted via API or SQL  (was: 
REST: Add support to get values inserted via SQL)

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



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

[jira] [Closed] (IGNITE-7598) SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table

[Roman Shtykh (JIRA)]

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

Roman Shtykh closed IGNITE-7598.


> SQL: INSERT requires you to specify the column names even if you are adding 
> values for all the columns of the table
> ---
>
> Key: IGNITE-7598
> URL: https://issues.apache.org/jira/browse/IGNITE-7598
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Roman Shtykh
>Priority: Major
>
> Checked via JDBC thin.
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Column count does not match; SQL 
> statement:
> INSERT INTO MYTABLE VALUES (?,?,?,?,?,?,?,?,?,?,?) [21002-195]
>     at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
>     at org.h2.message.DbException.get(DbException.java:179)
>     at org.h2.message.DbException.get(DbException.java:155)
>     at org.h2.message.DbException.get(DbException.java:144)
>     at org.h2.command.dml.Insert.prepare(Insert.java:265){noformat}



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

[jira] [Assigned] (IGNITE-7641) Add CacheEntry#ttl method

[Roman Shtykh (JIRA)]

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

Roman Shtykh reassigned IGNITE-7641:


Assignee: Roman Shtykh

> Add CacheEntry#ttl method
> -
>
> Key: IGNITE-7641
> URL: https://issues.apache.org/jira/browse/IGNITE-7641
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.5
>
>
> Ignite provides a way to specify an expiry policy on per entry level, but 
> there is no way to know the current TTL for a particular key.
> We can add {{CacheEntry#ttl()}} and/or {{IgniteCache#ttl(K key)}} method that 
> will provide this information. Looks like it's already available via 
> {{GridCacheMapEntry#ttl()}}, so we just need to properly expose it to public 
> API.
> Here is the user forum discussion about this: 
> http://apache-ignite-users.70518.x6.nabble.com/Get-TTL-of-the-specific-K-V-entry-td19817.html



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

[jira] [Commented] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin commented on IGNITE-7729:
---

[~anovikov] Fixed tests with setting notifications. Please review. Mac OS 
related bugs will be solved in diffirent ticket - 
https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7801

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
>




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

[jira] [Updated] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7805:
-
Description: 
*What happens:*

The "Testing setting notifications" test fails when run under macOS. During the 
issue initial research I managed to find that AngularStrap modal animations 
take way more time to complete compared to a regular, non-TestCafe environment. 
The broken animation makes elements appear in an unexpected order, which in 
turn causes TestCafe selectors to select wrong elements or correct elements, 
but at wrong time. The cause might lie in both TestCafe and our app code.

*What to do:*
Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
GitHub issue or report one (don't forget about a minimal reproduction scenario 
the TestCafe guys can use). If there's something wrong with either our own E2E 
or web console code, try to fix it.

  was:The "Testing setting notifications" test fails when run under macOS. 
During the issue initial research I managed to find that AngularStrap modal 
animations take way more time to complete compared to a regular, non-TestCafe 
environment. The broken animation makes elements appear in an unexpected order, 
which in turn causes TestCafe selectors to select wrong elements or correct 
elements, but at wrong time. The cause might lie in both TestCafe and our app 
code.


> Web console: fix admin-panel E2E test under macOS
> -
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During 
> the issue initial research I managed to find that AngularStrap modal 
> animations take way more time to complete compared to a regular, non-TestCafe 
> environment. The broken animation makes elements appear in an unexpected 
> order, which in turn causes TestCafe selectors to select wrong elements or 
> correct elements, but at wrong time. The cause might lie in both TestCafe and 
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding 
> GitHub issue or report one (don't forget about a minimal reproduction 
> scenario the TestCafe guys can use). If there's something wrong with either 
> our own E2E or web console code, try to fix it.



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

[jira] [Created] (IGNITE-7805) Web console: fix admin-panel E2E test under macOS

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7805:


 Summary: Web console: fix admin-panel E2E test under macOS
 Key: IGNITE-7805
 URL: https://issues.apache.org/jira/browse/IGNITE-7805
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Borisov
Assignee: Ilya Borisov


The "Testing setting notifications" test fails when run under macOS. During the 
issue initial research I managed to find that AngularStrap modal animations 
take way more time to complete compared to a regular, non-TestCafe environment. 
The broken animation makes elements appear in an unexpected order, which in 
turn causes TestCafe selectors to select wrong elements or correct elements, 
but at wrong time. The cause might lie in both TestCafe and our app code.



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

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

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7712:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

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



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

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

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-7712:
---

To implement lazy query on node level issue will be assigned on [~vozerov] 
after test of Web console.

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



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

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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7712:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

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



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

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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7712 at 2/26/18 3:52 AM:
-

The first point is tested successfully.
What about the second point from the description - "Add a system property that 
will allow to do the same on node level."?


was (Author: pkonstantinov):
What about the second point from the description - "Add a system property that 
will allow to do the same on node level."?

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



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

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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7712:


What about the second point from the description - "Add a system property that 
will allow to do the same on node level."?

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



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

[jira] [Assigned] (IGNITE-7421) Thin client Java API - data grid API

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin reassigned IGNITE-7421:


Assignee: Alexey Kukushkin

> Thin client Java API - data grid API
> 
>
> Key: IGNITE-7421
> URL: https://issues.apache.org/jira/browse/IGNITE-7421
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement below Java bindings for the thin client protocol. The client 
> configuration must support failover and encryption.
> Cache
>      JCache (limited)
>          getName(): String
>          put(key, val)
>          get(key): V
>          getAll(keys: Set): Map
>          containsKey(key): boolean
>          getAndPut(key, val): V
>          getAndReplace(key, val): V
>          getAndRemove(key): V
>          putIfAbsent
>          replace(key, val)
>          replace(key, oldVal, newVal)
>          putAll
>          clear
>          remove(key)
>          remove(key, val)
>          removeAll()
>          removeAll(keys: Set)
>          getConfiguration(clazz): Configuration
>          close()
>      size(modes: CachePeekMode...)
>      query(qry: Query): QueryCursor
>      query(qry: SqlFieldsQuery): FieldsQueryCursor
>      withKeepBinary(): IgniteCache
>  Ignite
>      cache(name: String)
>      cacheNames(): Collection
>      binary(): IgniteBinary
>      createCache(name): Cache
>      getOrCreateCache(name): Cache
>      destroyCache(name)
>  Ignition
>      startClient(:ClientConfiguration): Ignite
>  ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
>  etc...)



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

[jira] [Resolved] (IGNITE-7427) Thin client Java API - failover

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin resolved IGNITE-7427.
--
Resolution: Fixed

> Thin client Java API - failover
> ---
>
> Key: IGNITE-7427
> URL: https://issues.apache.org/jira/browse/IGNITE-7427
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement failover in thin client Java API including unit and system tests 
> and samples.
> ClientConfiguration(failover configuration)



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

[jira] [Resolved] (IGNITE-6585) SVM for Apache Ignite ML module

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-6585.

   Resolution: Fixed
Fix Version/s: 2.5

All sub-tasks was resolved.

> SVM for Apache Ignite ML module
> ---
>
> Key: IGNITE-6585
> URL: https://issues.apache.org/jira/browse/IGNITE-6585
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.5
>
>
> SVM - support vector machine, is pretty common algorithm and I think that we 
> need it in our module.



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