[jira] [Commented] (IGNITE-7838) Fix redirection on logo click

2018-03-04 Thread Alexander Kalinin (JIRA) 

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

Alexander Kalinin commented on IGNITE-7838:
---

[~anovikov] Fixed restoring on initial loading. Placing this logic in run block 
doesn't work, implemented this in landing component, Please review.

> Fix redirection on logo click
> -
>
> Key: IGNITE-7838
> URL: https://issues.apache.org/jira/browse/IGNITE-7838
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Alexander Kalinin
>Priority: Major
>
> Redirection to last state was broken after login\landing pages split 
> (IGNITE-7650 )
>  
> Steps:
> 1) Login the app
> 2) Go to configuration page
> 3) Go to profile page
> 4) Click logo
> Actual: Redirection didn't occur
> Expected: User is redirectd to default state (confiuration)



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

[jira] [Assigned] (IGNITE-7838) Fix redirection on logo click

2018-03-04 Thread Alexander Kalinin (JIRA) 

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

Alexander Kalinin reassigned IGNITE-7838:
-

Assignee: Andrey Novikov  (was: Alexander Kalinin)

> Fix redirection on logo click
> -
>
> Key: IGNITE-7838
> URL: https://issues.apache.org/jira/browse/IGNITE-7838
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
>
> Redirection to last state was broken after login\landing pages split 
> (IGNITE-7650 )
>  
> Steps:
> 1) Login the app
> 2) Go to configuration page
> 3) Go to profile page
> 4) Click logo
> Actual: Redirection didn't occur
> Expected: User is redirectd to default state (confiuration)



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

2018-03-04 Thread Nikolay Izhikov (JIRA) 

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

Nikolay Izhikov commented on IGNITE-7655:
-

Hello, [~abchaudhri]

Do you still need help?
If yes, please, write your questions and I will try to help with examples.

> 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: Denis Magda
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteCatalogExample.java, 
> JavaIgniteCatalogExample.java, JavaIgniteCatalogExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameWriteExample.java, 
> JavaIgniteDataFrameWriteExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



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

[jira] [Commented] (IGNITE-7785) SQL query with COUNT and UNION in sub-query produces JdbcSQLException

2018-03-04 Thread Pavel Vinokurov (JIRA) 

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

Pavel Vinokurov commented on IGNITE-7785:
-

Workaround:

SELECT count(1) FROM (select * from person) p
LEFT JOIN (select id from company union select id from company) as c on 
c.id=p.company_id

> SQL query with COUNT and UNION in sub-query produces JdbcSQLException
> -
>
> Key: IGNITE-7785
> URL: https://issues.apache.org/jira/browse/IGNITE-7785
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1, 2.3
>Reporter: Pavel Vinokurov
>Priority: Major
>
> SQL initial script:
> CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER);
>  CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR);
>  INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3);
>  INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3');
> SQL Query:
> SELECT count(1) FROM person p
>  LEFT JOIN (select id from company union select id from company) as c on 
> c.id=p.company_id
> JDBC Exception:
> Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.COMPANY_ID" must be in 
> the GROUP BY list; SQL statement:
> SELECT
> P__Z0.COMPANY_ID __C0_0,
> COUNT(1) __C0_1
> FROM PUBLIC.PERSON P__Z0 [90016-195]
>  



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

[jira] [Assigned] (IGNITE-1023) Need to add more information for startNodes at cmd visor.

2018-03-04 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov reassigned IGNITE-1023:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Need to add more information for startNodes at cmd visor.
> -
>
> Key: IGNITE-1023
> URL: https://issues.apache.org/jira/browse/IGNITE-1023
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Vasiliy Sisko
>Priority: Major
> Attachments: 
> #_IGNITE-1023_Additional_information_about_start_node_command.patch, 
> #_IGNITE-1023_Fixed_reading_of_an_empty_environment_variable.patch
>
>
> See 
> http://apache-ignite-users.70518.x6.nabble.com/Topology-Specification-INI-td467.html
> TODO:
> - add note about where to find ignite-startNodes logs
> - Successful start attempts - means nothing
> - describe ini-file format file
> - '-s' option - is it mandatory.



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

[jira] [Commented] (IGNITE-1023) Need to add more information for startNodes at cmd visor.

2018-03-04 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov commented on IGNITE-1023:


Please fix path to example ini-file  in the HELP to 
https://apacheignite-tools.readme.io/docs/start-command.
After that, the issue can be merged to master.


> Need to add more information for startNodes at cmd visor.
> -
>
> Key: IGNITE-1023
> URL: https://issues.apache.org/jira/browse/IGNITE-1023
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Pavel Konstantinov
>Priority: Major
> Attachments: 
> #_IGNITE-1023_Additional_information_about_start_node_command.patch, 
> #_IGNITE-1023_Fixed_reading_of_an_empty_environment_variable.patch
>
>
> See 
> http://apache-ignite-users.70518.x6.nabble.com/Topology-Specification-INI-td467.html
> TODO:
> - add note about where to find ignite-startNodes logs
> - Successful start attempts - means nothing
> - describe ini-file format file
> - '-s' option - is it mandatory.



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

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

2018-03-04 Thread Alexey Kuznetsov (JIRA) 

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

Alexey Kuznetsov reassigned IGNITE-7861:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Lets return to this issue after IGNITE-5466 will be merged.

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



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

[jira] [Updated] (IGNITE-7822) SQL Query with union and left join produces "Column not found" error

2018-03-04 Thread Pavel Vinokurov (JIRA) 

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

Pavel Vinokurov updated IGNITE-7822:

Summary: SQL Query with union and left join produces "Column not found" 
error  (was: SQL Query with with union and left join produces "Column not 
found" error)

> SQL Query with union and left join produces "Column not found" error
> 
>
> Key: IGNITE-7822
> URL: https://issues.apache.org/jira/browse/IGNITE-7822
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1, 2.3
>Reporter: Pavel Vinokurov
>Priority: Major
>
>  
>  
> Initial script:
>  
> CREATE TABLE Person (id INTEGER PRIMARY KEY, company_id INTEGER, salary 
> DECIMAL);
> CREATE TABLE Company (id INTEGER PRIMARY KEY, name VARCHAR);
> CREATE TABLE Company_Value (id INTEGER PRIMARY KEY, company_id INTEGER, 
> market_value DECIMAL);
> INSERT INTO Person (id, company_id, salary) VALUES (1, 1, 100), (2, 2, 200), 
> (3, 3, 300);
> INSERT INTO Company (id, name) VALUES (1, 'n1'), (2, 'n2'), (3, 'n3');
> INSERT INTO Company_Value (id, company_id, market_value) VALUES (1, 1, 
> 1), (2, 2, 2), (3, 3, 3); CREATE TABLE Address (id INTEGER 
> PRIMARY KEY, person_id INTEGER, city VARCHAR);INSERT INTO Person (id, 
> company_id, salary) VALUES (1, 1, 100), (2, 2, 200), (3, 3, 300);INSERT INTO 
> Address (id, person_id, city) VALUES (1, 1, 'san francisco'), (2, 2, 
> 'paris'), (3, 3, 'new york');INSERT INTO Company (id, name) VALUES (1, 'n1'), 
> (2, 'n2'), (3, 'n3');INSERT INTO Company_Value (id, company_id, market_value) 
> VALUES (1, 1, 1), (2, 2, 2), (3, 3, 3);
>  
> Query:
> SELECT a.idFROM  (SELECT     p1.id as pid,     p1.salary,     p1.company_id   
> FROM Person p1   WHERE p1.id = 1   UNION   SELECT     p2.id as pid,     
> p2.salary,     p2.company_id   FROM Person p2   WHERE p2.id = 2)  p  LEFT 
> JOIN Company c ON p.company_id = c.id  LEFT JOIN Company_Value cv ON c.id = 
> cv.company_id  LEFT JOIN Address a ON a.person_id = p.pid;
>  
> Result:
> Exception:Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z2.ID" not 
> found; SQL statement:SELECTC__Z3.ID __C2_0FROM PUBLIC.COMPANY C__Z3  LEFT 
> OUTER JOIN PUBLIC.COMPANY_VALUE CV__Z4  ON C__Z3.ID = CV__Z4.COMPANY_ID  LEFT 
> OUTER JOIN PUBLIC.ADDRESS A__Z5  ON A__Z5.PERSON_ID = P__Z2.IDORDER BY 1 
> [42122-195]
>  



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

[jira] [Created] (IGNITE-7879) SQL query with group by and distinct in subquery produces JdbcSQLException

2018-03-04 Thread Pavel Vinokurov (JIRA) 
Pavel Vinokurov created IGNITE-7879:
---

 Summary: SQL query with group by and distinct in subquery produces 
JdbcSQLException
 Key: IGNITE-7879
 URL: https://issues.apache.org/jira/browse/IGNITE-7879
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.3, 2.1
Reporter: Pavel Vinokurov


SQL initial script:

CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER);
CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR);
INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3);
INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3');

SQL query:

SELECT p.id,sum(p.id) FROM person p
LEFT JOIN (select DISTINCT id from company) as c on c.id=p.company_id
group by p.id

Result:

Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.ID" must be in the GROUP 
BY list; SQL statement:
SELECT
P__Z0.ID __C0_0,
P__Z0.COMPANY_ID __C0_1,
SUM(P__Z0.ID) __C0_2
FROM PUBLIC.PERSON P__Z0 [90016-195]

 

 



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

[jira] [Commented] (IGNITE-5298) .NET: DML update via LINQ

2018-03-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-5298:


GitHub user gurustron opened a pull request:

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

IGNITE-5298 .NET: DML update via LINQ



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

$ git pull https://github.com/gurustron/ignite feature/IGNITE-5298

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

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


commit 35471479c5de161ab9aaf22ba55d4be807bdba0c
Author: gurustron 
Date:   2017-07-31T12:14:15Z

define API and interface

commit 303c89ff203b41b1beb85945363cf3aa49fa59f0
Author: gurustron 
Date:   2017-08-15T15:33:55Z

implementation started

commit 0747bfec5d81a17fb71e03c5f57b5b31d5d00b4a
Author: gurustron 
Date:   2017-08-15T15:43:04Z

Merge branch 'master'

commit 270e5cff52d7142964190ee84799beb93546bc8a
Author: gurustron 
Date:   2018-02-23T21:50:37Z

Merge branch 'master' into feature/IGNITE-5298

commit 46a7f00648e19a5480c850a8d69fbb6b8c51d316
Author: gurustron 
Date:   2018-02-26T20:58:19Z

remove impl for now

commit c551c80db3a5074cbfc00209f3c6b3dfae98e121
Author: gurustron 
Date:   2018-02-27T00:39:54Z

implementation experiments

commit fee3870c1e40edcd41deb06f780d26f98c204ac1
Author: gurustron 
Date:   2018-02-27T22:13:38Z

UpdateDescription set up

commit 45eceb26d6c594e952169f2307702a89891f5b2e
Author: gurustron 
Date:   2018-02-28T21:39:48Z

continue implementation(fix rewrite, generate sql). small refactoring

commit 8270c3ace564d20a097d951e821c2ed6df9dd8e6
Author: gurustron 
Date:   2018-03-01T06:38:14Z

change to be implementable

commit 42dc08e1fa6b39947b7f15b1afda3fc96899344c
Author: gurustron 
Date:   2018-03-01T20:08:55Z

play a little bit more, queryreference works

commit 2bceb7602078b6facfef78f013aebd3c88911b3e
Author: gurustron 
Date:   2018-03-01T22:16:11Z

base implementation

commit 28a6c111b534131a00a55b5e9ff8153d1601ac9e
Author: gurustron 
Date:   2018-03-01T22:20:41Z

typo fix

commit a01870ecbfc2f91f281b5c89bf5ad5ee65eda703
Author: gurustron 
Date:   2018-03-01T22:55:20Z

some clean up

commit b15c10932a1ae7fbfce7835f42faab130aab0956
Author: gurustron 
Date:   2018-03-01T23:00:54Z

some unit test

commit bee592d87c82e938f9693cd2d121850099375a44
Author: gurustron 
Date:   2018-03-02T00:53:51Z

Some more unit tests

commit 737b56ddb648a5fd0aab5f8cab685a6db6cf3604
Author: gurustron 
Date:   2018-03-02T01:15:27Z

simple condition

commit a1ae8d71639527aa4c81f6c924f0bde6a0ee8781
Author: gurustron 
Date:   2018-03-02T01:20:48Z

Test: conditional with limit

commit 5ffed8dc5b1543fda535ffb4d2c72328dc2d8197
Author: gurustron 
Date:   2018-03-02T01:21:41Z

Comment

commit 617f5f24fe1802fd45976c8c0d541bc3386689fe
Author: gurustron 
Date:   2018-03-02T02:10:42Z

small cleanup

commit 7172ba8c2ce5e3791520a4ae159b617530f87859
Author: gurustron 
Date:   2018-03-04T18:53:03Z

implement "Contains" in value

commit ea9ee417daa6697a83c1b7fbaacca7b3ccec9681
Author: gurustron 
Date:   2018-03-04T20:10:28Z

small clean up

commit eaffab9b7237187cd22924fda59f9fdae2f4cac7
Author: gurustron 
Date:   2018-03-04T20:30:17Z

small refactoring




> .NET: DML update via LINQ
> -
>
> Key: IGNITE-5298
> URL: https://issues.apache.org/jira/browse/IGNITE-5298
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
>  Labels: .NET, LINQ, important
>
> Bulk update with LINQ:
> {code}
> var persons = ignite.GetCache("persons").AsCacheQueryable();
> int affectedRows = persons.Where(x => x.Key > 10).UpdateAll(x => 
> x.Value.OrgId = 7);
> {code}
> See bulk delete with {{RemoveAll}}, IGNITE-4904.



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

[jira] [Updated] (IGNITE-7878) Ignite Platform .NET Long Running: Stable failed with execution timeout

2018-03-04 Thread Dmitriy Pavlov (JIRA) 

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

Dmitriy Pavlov updated IGNITE-7878:
---
Priority: Critical  (was: Major)

>  Ignite Platform .NET Long Running: Stable failed with execution timeout 
> -
>
> Key: IGNITE-7878
> URL: https://issues.apache.org/jira/browse/IGNITE-7878
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNetLongRunning=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E
> First failure changes
> https://ci.ignite.apache.org/viewLog.html?buildId=1120409=buildChangesDiv=IgniteTests24Java8_IgnitePlatformNetLongRunning
> {noformat}
> 15:10:35] :[Apache.Ignite.Core.Tests.exe] 
> Apache.Ignite.Core.Tests.IgniteStartStopTest.TestStartDefault (1h:19m:50s)
> [15:10:35] :   
> [Apache.Ignite.Core.Tests.IgniteStartStopTest.TestStartDefault] [Test Error 
> Output]
> [04-03-2018 12:10:35][INFO ][main][IgniteKernal] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 2.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2018 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [04-03-2018 12:10:35][INFO ][main][IgniteKernal] Config URL: 
> file:/C:/BuildAgent/work/bd85361428dcdb1/modules/platforms/dotnet/Apache.Ignite.Core.Tests/bin/Debug/Config/Compute/compute-grid2.xml
> [04-03-2018 12:10:35][INFO ][main][IgniteKernal] IgniteConfiguration 
> [igniteInstanceName=null, pubPoolSize=8, svcPoolSize=8, callbackPoolSize=8, 
> stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4, igfsPoolSize=8, 
> dataStreamerPoolSize=8, utilityCachePoolSize=8, 
> utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8, 
> igniteHome=C:\BuildAgent\work\bd85361428dcdb1, 
> igniteWorkDir=C:\BuildAgent\work\bd85361428dcdb1\work, 
> mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@5965d37, 
> nodeId=7cb3b3f7-bd11-4f02-b579-7871ca2063ca, 
> marsh=org.apache.ignite.internal.binary.BinaryMarshaller@f7d76a5, 
> marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000, 
> sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1, 
> metricsUpdateFreq=2000, metricsExpTime=9223372036854775807, 
> discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0, 
> marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60, 
> forceSrvMode=false, clientReconnectDisabled=false], segPlc=STOP, 
> segResolveAttempts=2, waitForSegOnStart=true, allResolversPassReq=true, 
> segChkFreq=1, commSpi=TcpCommunicationSpi [connectGate=null, 
> connPlc=null, enableForcibleNodeKill=false, enableTroubleshootingLog=false, 
> srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@75d9f436,
>  locAddr=null, locHost=null, locPort=47100, locPortRange=100, shmemPort=-1, 
> directBuf=true, directSndBuf=false, idleConnTimeout=60, connTimeout=5000, 
> maxConnTimeout=60, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768, 
> msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null, 
> usePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true, 
> filterReachableAddresses=false, ackSndThreshold=32, unackedMsgsBufSize=0, 
> sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1, boundTcpShmemPort=-1, 
> selectorsCnt=4, selectorSpins=0, addrRslvr=null, 
> ctxInitLatch=java.util.concurrent.CountDownLatch@760bcec6[Count = 1], 
> stopping=false, 
> metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@51912f3a],
>  evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@35bda3f3, 
> colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null], 
> indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@fff9936, 
> addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=1, 
> txCfg=org.apache.ignite.configuration.TransactionConfiguration@272a1bf1, 
> cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED, 
> p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100, 
> timeSrvPortRange=100, failureDetectionTimeout=1, 
> clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null, 
> connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@7f9a18d1, 
> odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration 
> [seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null, 
> grpName=null], classLdr=null, sslCtxFactory=null, 
> platformCfg=PlatformDotNetConfiguration [binaryCfg=null], binaryCfg=null, 
> memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration 
>

[jira] [Assigned] (IGNITE-7877) Improve code style in GA part

2018-03-04 Thread Turik Campbell (JIRA) 

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

Turik Campbell reassigned IGNITE-7877:
--

Assignee: Turik Campbell

> Improve code style in GA part
> -
>
> Key: IGNITE-7877
> URL: https://issues.apache.org/jira/browse/IGNITE-7877
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Minor
>
> Not all code in which located in genetic package follows your code style. 
> That should be fixed.



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

[jira] [Created] (IGNITE-7878) Ignite Platform .NET Long Running: Stable failed with execution timeout

2018-03-04 Thread Dmitriy Pavlov (JIRA) 
Dmitriy Pavlov created IGNITE-7878:
--

 Summary:  Ignite Platform .NET Long Running: Stable failed with 
execution timeout 
 Key: IGNITE-7878
 URL: https://issues.apache.org/jira/browse/IGNITE-7878
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov


https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNetLongRunning=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E

First failure changes
https://ci.ignite.apache.org/viewLog.html?buildId=1120409=buildChangesDiv=IgniteTests24Java8_IgnitePlatformNetLongRunning


{noformat}
15:10:35] :  [Apache.Ignite.Core.Tests.exe] 
Apache.Ignite.Core.Tests.IgniteStartStopTest.TestStartDefault (1h:19m:50s)
[15:10:35] : 
[Apache.Ignite.Core.Tests.IgniteStartStopTest.TestStartDefault] [Test Error 
Output]
[04-03-2018 12:10:35][INFO ][main][IgniteKernal] 
>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.5.0-SNAPSHOT#19700101-sha1:DEV
>>> 2018 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org
[04-03-2018 12:10:35][INFO ][main][IgniteKernal] Config URL: 
file:/C:/BuildAgent/work/bd85361428dcdb1/modules/platforms/dotnet/Apache.Ignite.Core.Tests/bin/Debug/Config/Compute/compute-grid2.xml
[04-03-2018 12:10:35][INFO ][main][IgniteKernal] IgniteConfiguration 
[igniteInstanceName=null, pubPoolSize=8, svcPoolSize=8, callbackPoolSize=8, 
stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4, igfsPoolSize=8, 
dataStreamerPoolSize=8, utilityCachePoolSize=8, 
utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8, 
igniteHome=C:\BuildAgent\work\bd85361428dcdb1, 
igniteWorkDir=C:\BuildAgent\work\bd85361428dcdb1\work, 
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@5965d37, 
nodeId=7cb3b3f7-bd11-4f02-b579-7871ca2063ca, 
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@f7d76a5, 
marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000, 
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1, 
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807, 
discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0, 
marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60, 
forceSrvMode=false, clientReconnectDisabled=false], segPlc=STOP, 
segResolveAttempts=2, waitForSegOnStart=true, allResolversPassReq=true, 
segChkFreq=1, commSpi=TcpCommunicationSpi [connectGate=null, connPlc=null, 
enableForcibleNodeKill=false, enableTroubleshootingLog=false, 
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@75d9f436, 
locAddr=null, locHost=null, locPort=47100, locPortRange=100, shmemPort=-1, 
directBuf=true, directSndBuf=false, idleConnTimeout=60, connTimeout=5000, 
maxConnTimeout=60, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768, 
msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null, 
usePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true, 
filterReachableAddresses=false, ackSndThreshold=32, unackedMsgsBufSize=0, 
sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1, boundTcpShmemPort=-1, 
selectorsCnt=4, selectorSpins=0, addrRslvr=null, 
ctxInitLatch=java.util.concurrent.CountDownLatch@760bcec6[Count = 1], 
stopping=false, 
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@51912f3a],
 evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@35bda3f3, 
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null], 
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@fff9936, 
addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=1, 
txCfg=org.apache.ignite.configuration.TransactionConfiguration@272a1bf1, 
cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED, 
p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100, 
timeSrvPortRange=100, failureDetectionTimeout=1, 
clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null, 
connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@7f9a18d1, 
odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration 
[seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null, 
grpName=null], classLdr=null, sslCtxFactory=null, 
platformCfg=PlatformDotNetConfiguration [binaryCfg=null], binaryCfg=null, 
memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration 
[sysRegionInitSize=41943040, sysCacheMaxSize=104857600, pageSize=0, concLvl=0, 
dfltDataRegConf=DataRegionConfiguration [name=default, maxSize=5153866547, 
initSize=268435456, swapPath=null, pageEvictionMode=DISABLED, 
evictionThreshold=0.9, emptyPagesPoolSize=100, metricsEnabled=false, 
metricsSubIntervalCount=5, metricsRateTimeInterval=6, 
persistenceEnabled=false, checkpointPageBufSize=0], storagePath=null, 
checkpointFreq=18,

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

2018-03-04 Thread Alexey Kukushkin (JIRA) 

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

Alexey Kukushkin edited comment on IGNITE-7421 at 3/4/18 3:38 PM:
--

[~vozerov]: Vladimir, I implemented all your comments above except #12: 
"_{{IgniteClient.nonQuery}} - let's remove this for now_"
 The method was added for two purposes:
 # Allow executing SQL statements outside the cache context. In other words, 
having this method inside IgniteClient (as opposed to ClientCache#query) allows 
running DDL without binding to any cache first.
 # it is called "nonQuery" (instead of "query") since the "query" methods are 
all lazy: you have to either iterate the returned cursor or call 
Cursor#getAll() to have the SQL statement actually executed. nonQuery semantics 
is eager: it executes the passed statement right away. If we replace it with a 
"query" method the user would have to write DDL like this: 
"ignite.query("CREATE TABLE TBL").getAll()". That "getAll" is really confusing 
for DDL.

This is why I still think we need IgniteClient#nonQury(String)

I had to recreate code review in Upsource. The new core review is 
https://reviews.ignite.apache.org/apache-ignite/review/IG-CR-25


was (Author: kukushal):
[~vozerov]: Vladimir, I implemented all your comments above except #12: 
"_{{IgniteClient.nonQuery}} - let's remove this for now_"
The method was added for two purposes:
 # Allow executing SQL statements outside the cache context. In other words, 
having this method inside IgniteClient (as opposed to ClientCache#query) allows 
running DDL without binding to any cache first.
 # it is called "nonQuery" (instead of "query") since the "query" methods are 
all lazy: you have to either iterate the returned cursor or call 
Cursor#getAll() to have the SQL statement actually executed. nonQuery semantics 
is eager: it executes the passed statement right away. If we replace it with a 
"query" method the user would have to write DDL like this: 
"ignite.query("CREATE TABLE TBL").getAll()". That "getAll" is really confusing 
for DDL.

This is why I still think we need IgniteClient#nonQury(String)

> 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] [Commented] (IGNITE-7421) Thin client Java API - data grid API

2018-03-04 Thread Alexey Kukushkin (JIRA) 

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

Alexey Kukushkin commented on IGNITE-7421:
--

[~vozerov]: Vladimir, I implemented all your comments above except #12: 
"_{{IgniteClient.nonQuery}} - let's remove this for now_"
The method was added for two purposes:
 # Allow executing SQL statements outside the cache context. In other words, 
having this method inside IgniteClient (as opposed to ClientCache#query) allows 
running DDL without binding to any cache first.
 # it is called "nonQuery" (instead of "query") since the "query" methods are 
all lazy: you have to either iterate the returned cursor or call 
Cursor#getAll() to have the SQL statement actually executed. nonQuery semantics 
is eager: it executes the passed statement right away. If we replace it with a 
"query" method the user would have to write DDL like this: 
"ignite.query("CREATE TABLE TBL").getAll()". That "getAll" is really confusing 
for DDL.

This is why I still think we need IgniteClient#nonQury(String)

> 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] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

2018-03-04 Thread Akmal Chaudhri (JIRA) 

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

Akmal Chaudhri commented on IGNITE-7655:


[~dmagda], some Java code snippets added to the documentation and a small 
introductory section on SparkSession, which could be expanded.

> 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: Denis Magda
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteCatalogExample.java, 
> JavaIgniteCatalogExample.java, JavaIgniteCatalogExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameWriteExample.java, 
> JavaIgniteDataFrameWriteExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



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

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

2018-03-04 Thread Akmal Chaudhri (JIRA) 

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

Akmal Chaudhri reassigned IGNITE-7655:
--

Assignee: Denis Magda  (was: Akmal Chaudhri)

> 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: Denis Magda
>Priority: Major
> Fix For: 2.4
>
> Attachments: JavaIgniteCatalogExample.java, 
> JavaIgniteCatalogExample.java, JavaIgniteCatalogExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameExample.java, 
> JavaIgniteDataFrameExample.java, JavaIgniteDataFrameWriteExample.java, 
> JavaIgniteDataFrameWriteExample.java
>
>
> Once IGNITE-7337 is ready for merge.
> This new feature of Ignite needs to be documented.



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

[jira] [Created] (IGNITE-7877) Improve code style in GA part

2018-03-04 Thread Yury Babak (JIRA) 
Yury Babak created IGNITE-7877:
--

 Summary: Improve code style in GA part
 Key: IGNITE-7877
 URL: https://issues.apache.org/jira/browse/IGNITE-7877
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Yury Babak


Not all code in which located in genetic package follows your code style. That 
should be fixed.



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

[jira] [Commented] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.

2018-03-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-6899:


Github user asfgit closed the pull request at:

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


> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Major
> Fix For: 2.5
>
> Attachments: coverage.zip
>
>
> We want to add GA Grid to our ML Module.
> This is the first iteration of this integration. On this step we will simple 
> add GA Grid to the separate package in ML module.
> (i) This is a good package for GA Grid: org.apache.ignite.ml.genetic 
> (i) For GA Grid we need unit tests as well as examples



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

[jira] [Resolved] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.

2018-03-04 Thread Yury Babak (JIRA) 

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

Yury Babak resolved IGNITE-6899.

Resolution: Fixed

Review by me and [~oignatenko].

Merged.

> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Major
> Fix For: 2.5
>
> Attachments: coverage.zip
>
>
> We want to add GA Grid to our ML Module.
> This is the first iteration of this integration. On this step we will simple 
> add GA Grid to the separate package in ML module.
> (i) This is a good package for GA Grid: org.apache.ignite.ml.genetic 
> (i) For GA Grid we need unit tests as well as examples



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

[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

2018-03-04 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-7791:


GitHub user Mmuzaf opened a pull request:

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

IGNITE-7791: add additional logging

Logging for reproducing bug

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

$ git pull https://github.com/Mmuzaf/ignite ignite-7791

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

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


commit 9e06b5f6c253af65373164d462efba4ef509a925
Author: Maxim Muzafarov 
Date:   2018-03-04T14:57:55Z

IGNITE-7791: add additional logging




> Ignite Client Nodes: failed test 
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test is flaky, success rate: 32.4%, test history is 
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9174769196124217030=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22 
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6, 
> minorTopVer=1], discoEvt=DiscoveryCustomEvent 
> [customMsg=CacheAffinityChangeMessage 
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36, 
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null, 
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion 
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:, 
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null, 
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330, 
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
>   at 
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
>   at 
>

[jira] [Updated] (IGNITE-7875) [ML] Adopt SVM to the new Partitioned Dataset

2018-03-04 Thread Aleksey Zinoviev (JIRA) 

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

Aleksey Zinoviev updated IGNITE-7875:
-
Summary: [ML] Adopt SVM to the new Partitioned Dataset  (was: Adopt SVM to 
the new Partitioned Dataset)

> [ML] Adopt SVM to the new Partitioned Dataset
> -
>
> Key: IGNITE-7875
> URL: https://issues.apache.org/jira/browse/IGNITE-7875
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Major
>




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

[jira] [Created] (IGNITE-7876) [ML] Adopt SVM Linear Binary Classification Model and Trainer to the new Partitioned Dataset

2018-03-04 Thread Aleksey Zinoviev (JIRA) 
Aleksey Zinoviev created IGNITE-7876:


 Summary: [ML] Adopt SVM Linear Binary Classification Model and 
Trainer to the new Partitioned Dataset
 Key: IGNITE-7876
 URL: https://issues.apache.org/jira/browse/IGNITE-7876
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev






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

[jira] [Created] (IGNITE-7875) Adopt SVM to the new Partitioned Dataset

2018-03-04 Thread Aleksey Zinoviev (JIRA) 
Aleksey Zinoviev created IGNITE-7875:


 Summary: Adopt SVM to the new Partitioned Dataset
 Key: IGNITE-7875
 URL: https://issues.apache.org/jira/browse/IGNITE-7875
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev






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