[jira] [Commented] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-3084:
-

{quote}I so, is there any way to avoid this and to make sure that only 
IgniteSparkSession is actually public?{quote}

[~vkulichenko]

Thank you, good catch.

I made {{IgniteExternalCatalog}} and {{IgniteSharedState}} classes private.

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: bigdata, important
> Fix For: 2.4
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7257) Web console: fix reconnection after change profile

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7257:


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

Looks good. Merged to master.

> Web console: fix reconnection after change profile
> --
>
> Key: IGNITE-7257
> URL: https://issues.apache.org/jira/browse/IGNITE-7257
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7257) Web console: fix reconnection after change profile

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7257:
-
Fix Version/s: 2.4

> Web console: fix reconnection after change profile
> --
>
> Key: IGNITE-7257
> URL: https://issues.apache.org/jira/browse/IGNITE-7257
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6998) Activation on bigger topology with enabled persistence doesn't work as expected.

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh edited comment on IGNITE-6998 at 12/29/17 3:59 AM:


This issue still exists in the 'master' branch.

It happens because local mappings in GridDhtPartitionTopologyImpl.node2part are 
calculated without considering which partitions actually exist in ignite 
persistence (see GridDhtPartitionTopologyImpl.initPartitions0(...) method), and 
so all partitions that in new topology are assigned to different nodes will get 
state == EVICTED.

In means, you will lose data in the following example scenario:
- start 2 nodes
- activate
- create cache with persistence and 0 backup
- load data
- shutdown
- start 3 nodes
- activate
- all data in partitions that are now assigned by affinity to node 3 (new one) 
is lost


was (Author: ilantukh):
This issue still exists in the 'master' branch.

It happens because local mappings in GridDhtPartitionTopologyImpl.node2part are 
calculated without considering which partitions actually exist in ignite 
persistence (see GridDhtPartitionTopologyImpl.initPartitions0(...) method), and 
so all partitions that in new topology are assigned to different nodes will get 
state == EVICTED.

In means, you will lose data in the following example scenario:
- start 2 nodes
- activate
- create cache with persistence and 0 backup
- load data
- shutdown
- start 3 nodes
- activate
- all data in partitions that are now assigned to node 3 (new one) is lost

> Activation on bigger topology with enabled persistence doesn't work as 
> expected.
> 
>
> Key: IGNITE-6998
> URL: https://issues.apache.org/jira/browse/IGNITE-6998
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, persistence
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.persistence;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cache.query.ScanQuery;
> import org.apache.ignite.cluster.ClusterNode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.configuration.MemoryPolicyConfiguration;
> import org.apache.ignite.configuration.PersistentStoreConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteKernal;
> import org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion;
> import org.apache.ignite.internal.processors.cache.IgniteInternalCache;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> /**
>  * Check correctness of activation on bigger topology.
>  */
> public class IgnitePdsActivationOnBiggerTopologyTest extends 
> GridCommonAbstractTest {
> /** */
> private static TcpDiscoveryIpFinder ipFinder = new 
> TcpDiscoveryVmIpFinder(true);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setMemoryConfiguration(new 
> 

[jira] [Commented] (IGNITE-6998) Activation on bigger topology with enabled persistence doesn't work as expected.

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-6998:
--

This issue still exists in the 'master' branch.

It happens because local mappings in GridDhtPartitionTopologyImpl.node2part are 
calculated without considering which partitions actually exist in ignite 
persistence (see GridDhtPartitionTopologyImpl.initPartitions0(...) method), and 
so all partitions that in new topology are assigned to different nodes will get 
state == EVICTED.

In means, you will lose data in the following example scenario:
- start 2 nodes
- activate
- create cache with persistence and 0 backup
- load data
- shutdown
- start 3 nodes
- activate
- all data in partitions that are now assigned to node 3 (new one) is lost

> Activation on bigger topology with enabled persistence doesn't work as 
> expected.
> 
>
> Key: IGNITE-6998
> URL: https://issues.apache.org/jira/browse/IGNITE-6998
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, persistence
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.persistence;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.cache.CacheWriteSynchronizationMode;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cache.query.ScanQuery;
> import org.apache.ignite.cluster.ClusterNode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.configuration.MemoryPolicyConfiguration;
> import org.apache.ignite.configuration.PersistentStoreConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteKernal;
> import org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion;
> import org.apache.ignite.internal.processors.cache.IgniteInternalCache;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> /**
>  * Check correctness of activation on bigger topology.
>  */
> public class IgnitePdsActivationOnBiggerTopologyTest extends 
> GridCommonAbstractTest {
> /** */
> private static TcpDiscoveryIpFinder ipFinder = new 
> TcpDiscoveryVmIpFinder(true);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setMemoryConfiguration(new 
> MemoryConfiguration().setDefaultMemoryPolicyName("d").
> setPageSize(1024).setMemoryPolicies(new 
> MemoryPolicyConfiguration().setName("d").
> setInitialSize(50 * 1024 * 1024L).setMaxSize(50 * 1024 * 1024)));
> cfg.setPersistentStoreConfiguration(new 
> PersistentStoreConfiguration().setWalMode(WALMode.LOG_ONLY));
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(ipFinder);
> CacheConfiguration ccfg = new 
> CacheConfiguration<>(DEFAULT_CACHE_NAME);
> 
> ccfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> ccfg.setAffinity(new RendezvousAffinityFunction(false, 64));
> cfg.setCacheConfiguration(ccfg);
> 

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

[dean (JIRA)]

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

dean updated IGNITE-7338:
-
Description: 
bossapp@Linux-Power-NB-AltiDB2-XT:/home/bossapp6$java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxp6470_27sr4fp15-20171116_01(SR4 FP15))
IBM J9 VM (build 2.7, JRE 1.7.0 Linux ppc64-64 Compressed References 
20171011_366929 (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR4_20171011_1720_B366929
JIT  - tr.r13.java_20171011_366929
GC   - R27_Java727_SR4_20171011_1720_B366929_CMPRSS
J9CL - 20171011_366929)
JCL - 20171109_01 based on Oracle jdk7u161-b13
bossapp@Linux-Power-NB-AltiDB2-XT:/home/bossapp6$lsb_release -a
LSB Version:
:core-4.0-noarch:core-4.0-ppc64:graphics-4.0-noarch:graphics-4.0-ppc64:printing-4.0-noarch:printing-4.0-ppc64
Distributor ID: n/a
Description:redhat-4 
Release:n/a
Codename:   n/a
{color:#d04437}test code:{color}
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" 
+ cacheDate );
ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1  
+"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  
 List cacheModelList = (List) 
cacheDate3.get(e.getKey());

{color:#d04437}logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() 
+" cacheModelList:" + cacheModelList );
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() 
);{color}
   }
}
results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}

  was:
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" 
+ cacheDate );
ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1  
+"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  
 List cacheModelList = (List) 
cacheDate3.get(e.getKey());

{color:#d04437}logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() 
+" cacheModelList:" + cacheModelList );
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() 
);{color}
   }
}
results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}


> can get value by entry.getValue but cann't get value by 
> cache.get(entry.getKey)
> ---
>
> Key: IGNITE-7338
> URL: 

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

[dean (JIRA)]

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

dean updated IGNITE-7338:
-
Description: 
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" 
+ cacheDate );
ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1  
+"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  
 List cacheModelList = (List) 
cacheDate3.get(e.getKey());

{color:#d04437}logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() 
+" cacheModelList:" + cacheModelList );
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() 
);{color}
   }
}
results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}

  was:
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" + 
cacheDate );
ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1 
+"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  
List cacheModelList = (List) 
cacheDate3.get(e.getKey());
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}
results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 e.getKey():573,5 cacheModelList:null
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5, 
bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]


> can get value by entry.getValue but cann't get value by 
> cache.get(entry.getKey)
> ---
>
> Key: IGNITE-7338
> URL: https://issues.apache.org/jira/browse/IGNITE-7338
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: dean
>Priority: Critical
>
> if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
> CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
> ccbCdrChargeRuleKey.setFileType("573");
> ccbCdrChargeRuleKey.setSourceType("5");
> Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
> logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object 
> eKey:" + cacheDate );
> ccbCdrChargeRuleKey.setFileType("1233");
> ccbCdrChargeRuleKey.setSourceType("14");
> Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
> logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1  
> +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
> 

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

[dean (JIRA)]

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

dean updated IGNITE-7338:
-
Description: 
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" + 
cacheDate );
ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1 
+"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  
List cacheModelList = (List) 
cacheDate3.get(e.getKey());
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );
logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}
results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 e.getKey():573,5 cacheModelList:null
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5, 
bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]

> can get value by entry.getValue but cann't get value by 
> cache.get(entry.getKey)
> ---
>
> Key: IGNITE-7338
> URL: https://issues.apache.org/jira/browse/IGNITE-7338
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: dean
>Priority: Critical
>
> if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
> CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new CcbCdrChargeRuleKey();
> ccbCdrChargeRuleKey.setFileType("573");
> ccbCdrChargeRuleKey.setSourceType("5");
> Object cacheDate = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
> logger.debug(LogProperty.LOGTYPE_DETAIL, ccbCdrChargeRuleKey+"Object eKey:" + 
> cacheDate );
> ccbCdrChargeRuleKey.setFileType("1233");
> ccbCdrChargeRuleKey.setSourceType("14");
> Object cacheDate1 = ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
> logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + cacheDate1 
> +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
> IgniteCache cacheDate3 = ignite.cache(cacheName);
> for (Cache.Entry e : cacheDate3) {
> List cacheModelList = (List) 
> cacheDate3.get(e.getKey());
> logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
> cacheModelList:" + cacheModelList );
> logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
> }
> }
> results:
> 2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
> com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
>  e.getKey():573,5 cacheModelList:null
> 2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
> com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
>  e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5, 
> bizDomainCode='3', conditionGroupId=, fileType='573', 
> preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
> ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
> userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

[dean (JIRA)]

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

dean updated IGNITE-7338:
-
Summary: can get value by entry.getValue but cann't get value by 
cache.get(entry.getKey)  (was: can get value by entry.getValue but cann't get 
value by entry.getKey)

> can get value by entry.getValue but cann't get value by 
> cache.get(entry.getKey)
> ---
>
> Key: IGNITE-7338
> URL: https://issues.apache.org/jira/browse/IGNITE-7338
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: dean
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

[dean (JIRA)]

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

dean edited comment on IGNITE-7338 at 12/29/17 1:06 AM:


if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
  CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

{color:#d04437}logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() 
+" cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );{color}
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}


was (Author: dreamingdean):
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
  CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}

> can get value by entry.getValue but cann't get value by entry.getKey
> 

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

[dean (JIRA)]

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

dean edited comment on IGNITE-7338 at 12/29/17 1:05 AM:


if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
  CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}


was (Author: dreamingdean):
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}

> can get value by entry.getValue but cann't get value by entry.getKey
> 
>

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

[dean (JIRA)]

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

dean edited comment on IGNITE-7338 at 12/29/17 1:04 AM:


if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 {color:#d04437}e.getKey():573,5 cacheModelList:null{color}
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 
{color:#d04437}e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5,
 bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]{color}


was (Author: dreamingdean):
if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 e.getKey():573,5 cacheModelList:null
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5, 
bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]

> can get value by entry.getValue but cann't get value by entry.getKey
> 
>
> Key: IGNITE-7338
>

[jira] [Commented] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

[dean (JIRA)]

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

dean commented on IGNITE-7338:
--

if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){
CcbCdrChargeRuleKey ccbCdrChargeRuleKey = new 
CcbCdrChargeRuleKey();
ccbCdrChargeRuleKey.setFileType("573");
ccbCdrChargeRuleKey.setSourceType("5");
Object cacheDate = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, 
ccbCdrChargeRuleKey+"Object eKey:" + cacheDate );

ccbCdrChargeRuleKey.setFileType("1233");
ccbCdrChargeRuleKey.setSourceType("14");
Object cacheDate1 = 
ignite.cache(cacheName).get(ccbCdrChargeRuleKey);
logger.debug(LogProperty.LOGTYPE_DETAIL, "Object1:" + 
cacheDate1 +"ccbCdrChargeRuleKey"+ccbCdrChargeRuleKey.hashCode());
IgniteCache cacheDate3 = 
ignite.cache(cacheName);
for (Cache.Entry e : cacheDate3) {  

List cacheModelList = 
(List) cacheDate3.get(e.getKey());

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getKey():"+e.getKey() +" 
cacheModelList:" + cacheModelList );

logger.debug(LogProperty.LOGTYPE_DETAIL,"e.getValue():"+e.getValue() );
}
}


results:
2017-12-2819:17:36,322||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:337)|
 e.getKey():573,5 cacheModelList:null
2017-12-2819:17:36,323||DEBUG||frame_thread_nodestart| 
com.newland.boss.cloud.commons.igniteclient.PlatformInitIgniteClient.test(PlatformInitIgniteClient.java:338)|
 e.getValue():[CcbCdrChargeRule{ccbCdrChargeRuleKey=573,5, 
bizDomainCode='3', conditionGroupId=, fileType='573', 
preProcessUnitClass='PreProcessGprs', priority=1, rateItemTypes='6', 
ratingClass='RatingGprs', ruleDesc='国际出访GPRS 专网', sourceType='5', 
userTariffClass='GetUserTariffInfoGprs', version='0.0.1'}]

> can get value by entry.getValue but cann't get value by entry.getKey
> 
>
> Key: IGNITE-7338
> URL: https://issues.apache.org/jira/browse/IGNITE-7338
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: dean
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

[dean (JIRA)]

dean created IGNITE-7338:


 Summary: can get value by entry.getValue but cann't get value by 
entry.getKey
 Key: IGNITE-7338
 URL: https://issues.apache.org/jira/browse/IGNITE-7338
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.9
Reporter: dean
Priority: Critical






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7291) Apache Ignite "in use at" section

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7291:
-

ING: 
https://www.imcsummit.org/2017/eu/sessions/journey-use-imdg-strengthen-electronic-banking-offering-ing-be

> Apache Ignite "in use at" section
> -
>
> Key: IGNITE-7291
> URL: https://issues.apache.org/jira/browse/IGNITE-7291
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Put together a list of publicly disclosed Apache Ignite use cases and present 
> them on the main page right below the benefits. The "Ignite is in use at" 
> section might be like Cassandra's "PROVEN" section:
> http://cassandra.apache.org
> A list of the known use cases:
> * 
> https://www.imcsummit.org/us/sessions/implementation-investment-book-record-ibor-using-apache-ignitegridgain
> * 
> https://www.imcsummit.org/us/sessions/high-availability-and-disaster-recovery-imdg
> * https://www.imcsummit.org/us/sessions/ignite-compute-grid-in-cloud
> * https://youtu.be/1D8hyLWMtfM
> * 
> https://www.imcsummit.org/us/sessions/how-in-memory-solutions-can-assist-saas-integrations
> * https://www.youtube.com/watch?v=RxWLt3x_yBk
> In addition, create a dedicated page that will host all the videos in the 
> following format:
> * Youtube vide rectangle
> * Talk title goes below
> * Presenter (name and company) goes below
> * At the very bottom of the page add the text saying "If you want to add your 
> presentation or video to the page send a message at d...@ignite.apache.org"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-3084:
-

As for writing data, I created a separate ticket for task: 
https://issues.apache.org/jira/browse/IGNITE-7337. However, I would really like 
to have it in 2.4 as well. Do you think that would be possible?

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: bigdata, important
> Fix For: 2.4
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7337) Spark Data Frames: support saving a data frame in Ignite

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7337:
---

 Summary: Spark Data Frames: support saving a data frame in Ignite
 Key: IGNITE-7337
 URL: https://issues.apache.org/jira/browse/IGNITE-7337
 Project: Ignite
  Issue Type: New Feature
  Components: spark
Affects Versions: 2.3
Reporter: Valentin Kulichenko
Assignee: Nikolay Izhikov
Priority: Critical
 Fix For: 2.4


Once Ignite data source for Spark is implemented, we need to add an ability to 
store a data frame in Ignite. Most likely if should be enough to provide 
implementation for the following traits:
* {{InsertableRelation}}
* {{CreatableRelationProvider}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-3084:

Issue Type: New Feature  (was: Task)

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: bigdata, important
> Fix For: 2.4
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-3084:
-

[~NIzhikov], I'm OK with moving {{OPTION_GRID}} to private, looks good now.

My last concern is the {{org.apache.ignite.examples.spark}} package. Do I 
understand correctly that currently user has access to 
{{IgniteExternalCatalog}} and {{IgniteSharedState}} classes? I so, is there any 
way to avoid this and to make sure that only {{IgniteSparkSession}} is actually 
public?

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: Task
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: bigdata, important
> Fix For: 2.4
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7336) Improve peer class loading documentation

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7336:
---

 Summary: Improve peer class loading documentation
 Key: IGNITE-7336
 URL: https://issues.apache.org/jira/browse/IGNITE-7336
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.3
Reporter: Valentin Kulichenko
Assignee: Prachi Garg


[Zero Deployment|https://apacheignite.readme.io/docs/zero-deployment] page 
should be updated with the following:
* Applicability of the feature (where it can and can't be used).
* Warning about anonymous classes and lambdas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-6548) Improve service grid documentation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-6548.
---

> Improve service grid documentation
> --
>
> Key: IGNITE-6548
> URL: https://issues.apache.org/jira/browse/IGNITE-6548
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Valentin Kulichenko
>Priority: Minor
>
> Documentation should include information about the way how services 
> configuration is stored.
> Currently it's unclear whether it is stored on all nodes, or only on nodes 
> that are matched by the node filter, and in what cases services should be 
> redeployed.
> It would be good to specify what actions are required to update service's 
> implementation or configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6548) Improve service grid documentation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-6548:
-

Added a section in documentation: 
https://apacheignite.readme.io/docs/service-grid#service-undeployment

> Improve service grid documentation
> --
>
> Key: IGNITE-6548
> URL: https://issues.apache.org/jira/browse/IGNITE-6548
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Valentin Kulichenko
>Priority: Minor
>
> Documentation should include information about the way how services 
> configuration is stored.
> Currently it's unclear whether it is stored on all nodes, or only on nodes 
> that are matched by the node filter, and in what cases services should be 
> redeployed.
> It would be good to specify what actions are required to update service's 
> implementation or configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6548) Improve service grid documentation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko resolved IGNITE-6548.
-
Resolution: Fixed

> Improve service grid documentation
> --
>
> Key: IGNITE-6548
> URL: https://issues.apache.org/jira/browse/IGNITE-6548
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Valentin Kulichenko
>Priority: Minor
>
> Documentation should include information about the way how services 
> configuration is stored.
> Currently it's unclear whether it is stored on all nodes, or only on nodes 
> that are matched by the node filter, and in what cases services should be 
> redeployed.
> It would be good to specify what actions are required to update service's 
> implementation or configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6548) Improve service grid documentation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-6548:

Fix Version/s: 2.4

> Improve service grid documentation
> --
>
> Key: IGNITE-6548
> URL: https://issues.apache.org/jira/browse/IGNITE-6548
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Valentin Kulichenko
>Priority: Minor
>
> Documentation should include information about the way how services 
> configuration is stored.
> Currently it's unclear whether it is stored on all nodes, or only on nodes 
> that are matched by the node filter, and in what cases services should be 
> redeployed.
> It would be good to specify what actions are required to update service's 
> implementation or configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6548) Improve service grid documentation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko reassigned IGNITE-6548:
---

Assignee: Valentin Kulichenko  (was: Prachi Garg)

> Improve service grid documentation
> --
>
> Key: IGNITE-6548
> URL: https://issues.apache.org/jira/browse/IGNITE-6548
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Valentin Kulichenko
>Priority: Minor
>
> Documentation should include information about the way how services 
> configuration is stored.
> Currently it's unclear whether it is stored on all nodes, or only on nodes 
> that are matched by the node filter, and in what cases services should be 
> redeployed.
> It would be good to specify what actions are required to update service's 
> implementation or configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7335) DatabaseMetaData getTables error

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7335:

Fix Version/s: 2.4

> DatabaseMetaData getTables error
> 
>
> Key: IGNITE-7335
> URL: https://issues.apache.org/jira/browse/IGNITE-7335
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
> Environment: Default ignite cluster with a table created via SQL from 
> the JDBC driver
>Reporter: Maxwell Pettit
> Fix For: 2.4
>
>
> Exception when calling the java.sql.DatabaseMetaData.getTables(String 
> catalog, String schemaPattern, String tableNamePattern, String[] types) 
> method.  Exception is listed below:
> Caused by: java.sql.SQLException: Failed to communicate with Ignite cluster.
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:681)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata.getTables(JdbcThinDatabaseMetadata.java:740)
>   at 
> org.apache.commons.dbcp.DelegatingDatabaseMetaData.getTables(DelegatingDatabaseMetaData.java:604)
>   ... 20 more
> Caused by: java.io.IOException: Failed to read incoming message (not enough 
> data).
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:406)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:384)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.sendRequest(JdbcThinTcpIo.java:327)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:668)
>   ... 26 more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7335) DatabaseMetaData getTables error

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7335:

Component/s: sql

> DatabaseMetaData getTables error
> 
>
> Key: IGNITE-7335
> URL: https://issues.apache.org/jira/browse/IGNITE-7335
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
> Environment: Default ignite cluster with a table created via SQL from 
> the JDBC driver
>Reporter: Maxwell Pettit
> Fix For: 2.4
>
>
> Exception when calling the java.sql.DatabaseMetaData.getTables(String 
> catalog, String schemaPattern, String tableNamePattern, String[] types) 
> method.  Exception is listed below:
> Caused by: java.sql.SQLException: Failed to communicate with Ignite cluster.
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:681)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata.getTables(JdbcThinDatabaseMetadata.java:740)
>   at 
> org.apache.commons.dbcp.DelegatingDatabaseMetaData.getTables(DelegatingDatabaseMetaData.java:604)
>   ... 20 more
> Caused by: java.io.IOException: Failed to read incoming message (not enough 
> data).
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:406)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:384)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.sendRequest(JdbcThinTcpIo.java:327)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:668)
>   ... 26 more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7335) DatabaseMetaData getTables error

[Maxwell Pettit (JIRA)]

Maxwell Pettit created IGNITE-7335:
--

 Summary: DatabaseMetaData getTables error
 Key: IGNITE-7335
 URL: https://issues.apache.org/jira/browse/IGNITE-7335
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.3
 Environment: Default ignite cluster with a table created via SQL from 
the JDBC driver
Reporter: Maxwell Pettit


Exception when calling the java.sql.DatabaseMetaData.getTables(String catalog, 
String schemaPattern, String tableNamePattern, String[] types) method.  
Exception is listed below:

Caused by: java.sql.SQLException: Failed to communicate with Ignite cluster.
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:681)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata.getTables(JdbcThinDatabaseMetadata.java:740)
at 
org.apache.commons.dbcp.DelegatingDatabaseMetaData.getTables(DelegatingDatabaseMetaData.java:604)
... 20 more
Caused by: java.io.IOException: Failed to read incoming message (not enough 
data).
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:406)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:384)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.sendRequest(JdbcThinTcpIo.java:327)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:668)
... 26 more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7331) create MLP examples

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7331:


additionally, create a "self test" suite similar to [those done for many other 
examples|https://github.com/apache/ignite/blob/master/examples/src/test/java/org/apache/ignite/testsuites/IgniteExamplesSelfTestSuite.java|see
 IgniteExamplesSelfTestSuite]. And after IGNITE-7203 is over, add it into 
{{IgniteExamplesSelfTestSuite}}.

For ML examples self tests, avoid those impacted by features referred in 
IGNITE-5725, so that it would be possible to automatically run on Teamcity.



> create MLP examples
> ---
>
> Key: IGNITE-7331
> URL: https://issues.apache.org/jira/browse/IGNITE-7331
> Project: Ignite
>  Issue Type: Sub-task
>  Components: examples, ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> create examples for local and distributed MLP in order to help project users 
> see how to use these features



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7334) MBeans fail to be created for caches with special symbols in names

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7334:


GitHub user slukyano opened a pull request:

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

IGNITE-7334: added escaping of special characters to MBean registrati…

…on code

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

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

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

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


commit 8650dddb717a32a05071fda0053ac89029bf4a13
Author: Stanislav Lukyanov 
Date:   2017-12-28T17:13:08Z

IGNITE-7334: added escaping of special characters to MBean registration code




> MBeans fail to be created for caches with special symbols in names
> --
>
> Key: IGNITE-7334
> URL: https://issues.apache.org/jira/browse/IGNITE-7334
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>
> If a cache contains a certain symbols, e.g. an asterisk, its creation will 
> fail due to an exception during MBean creation. This is because of 
> insufficient escaping in the shared MBean registration code in IgniteUtils.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7264) Caches with forward slash "/" in names cause problems for PDS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7264:


GitHub user slukyano opened a pull request:

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

IGNITE-7264: Caches with forward slash "/" in names cause problems for PDS



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

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

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

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


commit fcacf73d2db54865fa3ff1387e04dfc2fe6ca4b8
Author: Stanislav Lukyanov 
Date:   2017-12-28T09:26:10Z

IGNITE-7264: removed unused method

commit f796b61b8f25c32022c6a3041e46deea2002ad0a
Author: Stanislav Lukyanov 
Date:   2017-12-28T14:35:06Z

IGNITE-7264: added escaping of unsafe characters in persistent storage names

commit 62d7c38f4cc3c561420ae9f0289acf646011a04a
Author: Stanislav Lukyanov 
Date:   2017-12-28T16:13:36Z

IGNITE-7264: restored afterTest action in IgnitePdsExoticCacheNamesTest

commit f7bbcc63d91953d8188566442a36661ad4819ced
Author: Stanislav Lukyanov 
Date:   2017-12-28T17:42:17Z

IGNITE-7264: added handling of long cache names




> Caches with forward slash "/" in names cause problems for PDS
> -
>
> Key: IGNITE-7264
> URL: https://issues.apache.org/jira/browse/IGNITE-7264
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, persistence
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Stanislav Lukyanov
>
> If I am to create cache with name "caches/1", there's no immediate error, but 
> nodes fail when trying to rejoin topology with storage already initialized.
> I think there should be an immediate exception in case persistence is enabled 
> for such case.
> Moreover, I suggest first trying to create directory, then making sure it was 
> created and that dir.parent == expected parent directory. Because on Windows 
> there are more restrictions on FS file names, etc...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7334) MBeans fail to be created for caches with special symbols in names

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-7334:
--

 Summary: MBeans fail to be created for caches with special symbols 
in names
 Key: IGNITE-7334
 URL: https://issues.apache.org/jira/browse/IGNITE-7334
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Stanislav Lukyanov
Assignee: Stanislav Lukyanov


If a cache contains a certain symbols, e.g. an asterisk, its creation will fail 
due to an exception during MBean creation. This is because of insufficient 
escaping in the shared MBean registration code in IgniteUtils.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7332) Create selftest suite for ml examples

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7332:


GitHub user dmitrievanthony opened a pull request:

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

IGNITE-7332: Add test suite for ML examples



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

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

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

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


commit f4c852ffb131221757e9f5e6774d6c807e2d9c39
Author: dmitrievanthony 
Date:   2017-12-28T16:17:38Z

IGNITE-7332 Add test suite for ML tests.




> Create selftest suite for ml examples
> -
>
> Key: IGNITE-7332
> URL: https://issues.apache.org/jira/browse/IGNITE-7332
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>  Labels: examples
> Fix For: 2.5
>
>
> We want to add self test suite for our examples like we have for java8 
> examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5217) Gradient descent for OLS lin reg

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-5217.

   Resolution: Fixed
Fix Version/s: 2.4

Reviewed and merged

> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
> Fix For: 2.4
>
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7251) Remove term "fabric" from Ignite deliverables

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7251:


GitHub user vveider opened a pull request:

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

IGNITE-7251 Remove term "fabric" from Ignite deliverables



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

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

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

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


commit 02d44464e30877dcb61831ffb1ac93c2284f756a
Author: Ivanov Petr 
Date:   2017-12-28T16:07:09Z

IGNITE-7251 Remove term "fabric" from Ignite deliverables




> Remove term "fabric" from Ignite deliverables
> -
>
> Key: IGNITE-7251
> URL: https://issues.apache.org/jira/browse/IGNITE-7251
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
>  Labels: important
> Fix For: 2.4
>
>
> Apache Ignite binary releases still include “fabric” word in their names:
> https://ignite.apache.org/download.cgi#binaries
> For instance, this is a full name of the previous release - 
> apache-ignite-fabric-2.3.0-bin.
> It’s a little oversight on our side because the project has not been 
> positioned as a fabric for a while.
> Remove “fabric” from the name and have the binary releases named as - 
> {{apache-ignite-\{version}-bin}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5217) Gradient descent for OLS lin reg

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5217:


Github user asfgit closed the pull request at:

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


> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7333) SQL: Documentation for ALTER TABLE DROP COLUMN statement

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-7333:
--

 Summary: SQL: Documentation for ALTER TABLE DROP COLUMN statement
 Key: IGNITE-7333
 URL: https://issues.apache.org/jira/browse/IGNITE-7333
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 2.4
Reporter: Sergey Kalashnikov
Assignee: Sergey Kalashnikov
 Fix For: 2.4


Add a documentation for ALTER TABLE DROP COLUMN statement.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7214) performance measurement for FCM and KNN algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7214 at 12/28/17 3:52 PM:
--

Lic & javadoc check at TC 
([buildId=1023362|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;]) 
currently fails with cryptic warnings that don't look like even remotely 
relevant: {noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}
Pinged [~oleg-ostanin] to take a look at what could happen at TC.

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.


was (Author: oignatenko):
Lic & javadoc check at TC 
([buildId=1023362|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;]) 
currently fails with cryptic warnings that don't look like even remotely 
relevant: {noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.

> performance measurement for FCM and KNN algorithms
> --
>
> Key: IGNITE-7214
> URL: https://issues.apache.org/jira/browse/IGNITE-7214
> Project: Ignite
>  Issue Type: Task
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance of Fuzzy c-means (FCM) and k 
> nearest neighbours (KNN) to avoid performance degradation. Also we need some 
> performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5949:


Github user asfgit closed the pull request at:

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


> DDL: Support ALTER TABLE DROP COLUMN
> 
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Andrew Mashenkov
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.4
>
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.
> Design considerations:
> 1) Drop should only be possible on binary types without schema (see 
> IGNITE-6611). Probably we will need a new option for {{CREATE TABLE}} command
> 2) Drop should not block other operations for a long time. We should 
> synchronously block the table, change meta, then release the lock and let 
> operations continue.
> 3) Actual data remove should be performed asynchronously in the same way we 
> create index. During this time we should not allow any other modifications to 
> the table
> 4) Be careful with node stop - we do not want to wait for years for this 
> command to complete.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7214) performance measurement for FCM and KNN algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7214 at 12/28/17 3:14 PM:
--

Lic & javadoc check at TC 
([buildId=1023362|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;]) 
currently fails with cryptic warnings that don't look like even remotely 
relevant: {noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.


was (Author: oignatenko):
Lic & javadoc check at TC 
([buildId=1023362|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;]) 
fails with cryptic warnings that don't look like even remotely relevant: 
{noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.

> performance measurement for FCM and KNN algorithms
> --
>
> Key: IGNITE-7214
> URL: https://issues.apache.org/jira/browse/IGNITE-7214
> Project: Ignite
>  Issue Type: Task
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance of Fuzzy c-means (FCM) and k 
> nearest neighbours (KNN) to avoid performance degradation. Also we need some 
> performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7214) performance measurement for FCM and KNN algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7214 at 12/28/17 3:13 PM:
--

Lic & javadoc check at TC 
([buildId=1023362|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;]) 
fails with cryptic warnings that don't look like even remotely relevant: 
{noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.


was (Author: oignatenko):
[Lic & javadoc|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;] 
check at TC fails with cryptic warnings that don't look like even remotely 
relevant: {noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.

> performance measurement for FCM and KNN algorithms
> --
>
> Key: IGNITE-7214
> URL: https://issues.apache.org/jira/browse/IGNITE-7214
> Project: Ignite
>  Issue Type: Task
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance of Fuzzy c-means (FCM) and k 
> nearest neighbours (KNN) to avoid performance degradation. Also we need some 
> performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7214) performance measurement for FCM and KNN algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7214:


[Lic & javadoc|https://ci.ignite.apache.org/viewLog.html?buildId=1023362;] 
check at TC fails with cryptic warnings that don't look like even remotely 
relevant: {noformat}
[18:05:56][org.apache.ignite:ignite-visor-console] Compiler warnings:
[18:05:56][org.apache.ignite:ignite-visor-console]   WARNING:  
'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
{noformat}

As a result I had to manually verify that all 15 files involved in [PR 
3314|https://github.com/apache/ignite/pull/3314/files] have proper Apache 
license in headers and legit javadocs.

> performance measurement for FCM and KNN algorithms
> --
>
> Key: IGNITE-7214
> URL: https://issues.apache.org/jira/browse/IGNITE-7214
> Project: Ignite
>  Issue Type: Task
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance of Fuzzy c-means (FCM) and k 
> nearest neighbours (KNN) to avoid performance degradation. Also we need some 
> performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6217) Add benchmark to compare JDBC drivers and native SQL execution

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6217:
---

Assignee: Pavel Kuznetsov  (was: Taras Ledkov)

> Add benchmark to compare JDBC drivers and native SQL execution
> --
>
> Key: IGNITE-6217
> URL: https://issues.apache.org/jira/browse/IGNITE-6217
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql, yardstick
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Pavel Kuznetsov
>
> We have to compare performance of the native SQL execution (via Ignite SQL 
> API), JDBC v2 driver, that uses Ignite client to connect to grid and JDBC 
> thin client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4726) SQL: benchmark DML operations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4726:
---

Assignee: Pavel Kuznetsov

> SQL: benchmark DML operations
> -
>
> Key: IGNITE-4726
> URL: https://issues.apache.org/jira/browse/IGNITE-4726
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>
> We need to create benchmarks for DML operations similar to our cache 
> benchmarks and compare common cases. Results of cache API benchmarks can be 
> used as baseline for us.
> Preliminray list of benchmarks:
> 1) INSERT + DELETE (vs {{IgniteCache.put}} + {{IgniteCache.remove}})
> 2) Simple MERGE (vs {{IgniteCache.put}})
> 3) Simple UPDATE (vs {{IgniteCache.invoke}})



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7214) performance measurement for FCM and KNN algorithms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7214:


GitHub user oignatenko opened a pull request:

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

IGNITE-7214 performance measurement for FCM and KNN algorithms



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

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

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

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


commit b328d6b2856c7998e6a3de2f8344ddefaad81196
Author: Oleg Ignatenko 
Date:   2017-12-25T18:14:44Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- kNN benchmarks
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

commit 7c4b06dc2eff5c68c8bd0e05d82e98af8d9f02ab
Author: Oleg Ignatenko 
Date:   2017-12-26T07:10:00Z

Merge branch 'master-ml' into ignite-7214-preliminary

commit 9fa1c42c76e26037d5e4eab16bcbb195c5ece51d
Author: Oleg Ignatenko 
Date:   2017-12-26T09:49:42Z

Merge branch 'master-ml' into ignite-7214-preliminary

commit 7acc2db76434868bed5436aaed5243684d0f394c
Author: Oleg Ignatenko 
Date:   2017-12-26T10:23:35Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- kNN examples cleanup
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

commit ce5c4be654bb2e1f7ac7193ecaaf2538d1570ad0
Author: Oleg Ignatenko 
Date:   2017-12-26T10:51:30Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- corrected data for IgniteKNNRegressionBenchmark
-- verified with diffs overview

commit 5ffdf8d951a9af0fa4391e17a62cd2ca764bd8e9
Author: Oleg Ignatenko 
Date:   2017-12-26T15:21:35Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- preliminary cleanup for FCM benchmark
-- verified with diffs overview

commit 3901a2df34908c7f9df37932940920510989fb34
Author: Oleg Ignatenko 
Date:   2017-12-26T16:03:10Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- drafted distributed FCM benchmark
-- verified with diffs overview

commit 9148e50fbe61f5c963e2c433d3a45c9af936e9fb
Author: Oleg Ignatenko 
Date:   2017-12-26T16:05:21Z

Merge branch 'master-ml' into ignite-7214-preliminary

commit b0d9c6cb58716f28913f53d3e5780824758fe558
Author: Oleg Ignatenko 
Date:   2017-12-26T16:24:00Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- preliminary cleanup for FCM benchmark
-- verified with diffs overview

commit e626d194400bbadae31e2f6da0410a8bddabb5bf
Author: Oleg Ignatenko 
Date:   2017-12-26T16:34:00Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- preliminary cleanup for FCM benchmark
-- verified with diffs overview

commit 7cfaed9d4d5ea407c91a256100767b05bc942059
Author: Oleg Ignatenko 
Date:   2017-12-27T07:22:23Z

Merge branch 'master-ml' into ignite-7214-preliminary

commit 353e8ab70294c599f262278c54b04c55fd2c349c
Author: Oleg Ignatenko 
Date:   2017-12-27T11:55:31Z

Merge branch 'master-ml' into ignite-7214-preliminary

commit f16a37e5a088df23a6b9b716731b14018791c534
Author: Oleg Ignatenko 
Date:   2017-12-27T12:32:32Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- preliminary cleanup for FCM benchmark // added missing example for local 
FCM
-- verified with diffs overview

commit 50bb3d24c6001dee8351fdb8c8d68ebdd19d57bf
Author: Oleg Ignatenko 
Date:   2017-12-27T12:44:05Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- drafted local FCM benchmark
-- verified with diffs overview

commit 14cea0e89de17e625f526bf08338fea65d9d6a5c
Author: Oleg Ignatenko 
Date:   2017-12-27T13:05:32Z

IGNITE-7214 performance measurement for FCM and KNN algorithms
- FCM benchmarks
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

commit 4f71ff9d88d4f016fcbe52e49104d17687191f3f
Author: Oleg Ignatenko 
Date:   2017-12-28T14:34:34Z

Merge branch 'master-ml' into ignite-7214

# Conflicts:
#   
modules/ml/src/main/java/org/apache/ignite/ml/structures/LabeledDataset.java

commit efbfda49a040ec290239e00a29fbc6818361e4be
Author: Oleg Ignatenko 
Date:   2017-12-28T14:43:21Z

IGNITE-7214 performance measurement for 

[jira] [Commented] (IGNITE-7332) Create selftest suite for ml examples

[Yury Babak (JIRA)]

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

Yury Babak commented on IGNITE-7332:


[~dmitrievanthony] please also take a look on IGNITE-7203.

> Create selftest suite for ml examples
> -
>
> Key: IGNITE-7332
> URL: https://issues.apache.org/jira/browse/IGNITE-7332
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>  Labels: examples
> Fix For: 2.5
>
>
> We want to add self test suite for our examples like we have for java8 
> examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7332) Create selftest suite for ml examples

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7332:
--

 Summary: Create selftest suite for ml examples
 Key: IGNITE-7332
 URL: https://issues.apache.org/jira/browse/IGNITE-7332
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Yury Babak
 Fix For: 2.5


We want to add self test suite for our examples like we have for java8 examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7332) Create selftest suite for ml examples

[Yury Babak (JIRA)]

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

Yury Babak reassigned IGNITE-7332:
--

Assignee: Anton Dmitriev

> Create selftest suite for ml examples
> -
>
> Key: IGNITE-7332
> URL: https://issues.apache.org/jira/browse/IGNITE-7332
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>  Labels: examples
> Fix For: 2.5
>
>
> We want to add self test suite for our examples like we have for java8 
> examples.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7217) Add abilities to monitor custom thread pools

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7217:
-

LGTM. Merged to master. Thanks for contribution!

> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Stanislav Lukyanov
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-7217) Add abilities to monitor custom thread pools

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-7217.
-
Resolution: Fixed

> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Stanislav Lukyanov
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7331) create MLP examples

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7331:
---
Fix Version/s: 2.4

> create MLP examples
> ---
>
> Key: IGNITE-7331
> URL: https://issues.apache.org/jira/browse/IGNITE-7331
> Project: Ignite
>  Issue Type: Sub-task
>  Components: examples, ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> create examples for local and distributed MLP in order to help project users 
> see how to use these features



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7331) create MLP examples

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko reassigned IGNITE-7331:
--

Assignee: Oleg Ignatenko

> create MLP examples
> ---
>
> Key: IGNITE-7331
> URL: https://issues.apache.org/jira/browse/IGNITE-7331
> Project: Ignite
>  Issue Type: Sub-task
>  Components: examples, ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> create examples for local and distributed MLP in order to help project users 
> see how to use these features



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7331) create MLP examples

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-7331:
--

 Summary: create MLP examples
 Key: IGNITE-7331
 URL: https://issues.apache.org/jira/browse/IGNITE-7331
 Project: Ignite
  Issue Type: Sub-task
  Components: examples, ml
Reporter: Oleg Ignatenko


create examples for local and distributed MLP in order to help project users 
see how to use these features



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5623) DDL needs to support DEFAULT operator

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5623:


{{QueryField.DefaultValue}} and {{QuerySqlFieldAttribute.DefaultValue}} added 
to .NET, DML tests updated.

> DDL needs to support DEFAULT operator 
> --
>
> Key: IGNITE-5623
> URL: https://issues.apache.org/jira/browse/IGNITE-5623
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.4
>
>
> There should be a way to set a default value for a column/field if the one is 
> not specified during an insert operation. In general, we need to support 
> {{ DEFAULT }} in a way it's show below:
> {code}
> CREATE TABLE Persons (
>   ID int,
>   FirstName varchar(255),
>   Age int,
>   City varchar(255) DEFAULT 'Sandnes'
> );
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7205) DataSet API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7205:


Github user asfgit closed the pull request at:

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


> DataSet API
> ---
>
> Key: IGNITE-7205
> URL: https://issues.apache.org/jira/browse/IGNITE-7205
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
>  Labels: ml
>
> We want to create and implement API for Dataset.
> This should include Dataset, Labeled Dataset, dataset 
> preprocessors(normalizer, filter, mapper, etc...) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7203) Java 8 by default

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7203:


GitHub user vveider reopened a pull request:

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

IGNITE-7203 Java 8 by default



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

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

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

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


commit 7b66609de9da4705926fb0a7845d69240eb0dee2
Author: Ivanov Petr 
Date:   2017-12-15T14:35:35Z

IGNITE-7203 Java 8 by default
 * got rid of java-1.8 related profiles
 * remove ml profile and included ml build into main reactor
 * added master properties to maven-compiler-plugin for whole project to be 
compiled only by java-1.8
 * refactored met properties + gathered them in parent module

commit b20f6ab8cb22528d7717229c1a7acc586cda44bc
Author: Ivanov Petr 
Date:   2017-12-18T07:25:19Z

IGNITE-7203 Java 8 by default
IGNITE-7216 Refactor examples project
 * refactored examples module and ml part of other modules: merged java8 
and java packages

commit 3177f28d5651f4ad910e6d54d5e8a225b9664c6b
Author: Ivanov Petr 
Date:   2017-12-18T15:19:02Z

IGNITE-7203 Java 8 by default
IGNITE-7216 Refactor examples project
 * fixed notes from review

commit ab8d197d8ed3c430e7720750db6c00aaf845b249
Author: Pavel Tupitsyn 
Date:   2017-12-26T09:11:41Z

.NET: Fix ExecutableTest

commit f4b0bdc72ba3f62f9125843680ff3ae78098deed
Author: Pavel Tupitsyn 
Date:   2017-12-26T09:26:23Z

.NET: Fix TestStopFromJava

commit b361ac4f6edfaa7d0645a9352145b84bd02745b1
Author: devozerov 
Date:   2017-12-26T11:31:07Z

Attempty to fix AOP failure.

commit 1390677806c9a28aba6720566260b31cdb58b086
Author: Ivanov Petr 
Date:   2017-12-26T12:40:15Z

IGNITE-7203 Java 8 by default
 * replaced aspectj dependency with newest one for attempt to fix AOP tests

commit aa2546aa55a9c22253206add2839917faef47027
Author: Pavel Tupitsyn 
Date:   2017-12-26T14:20:44Z

.NET: Another attempt to fix WindowsServiceTest

commit 017f63b4cb36a62234b8c406b2ebe085549d5628
Author: Pavel Tupitsyn 
Date:   2017-12-27T07:22:22Z

.NET: Another attempt to fix WindowsServiceTest

commit 83b9d21edc71c8f263a093c19be60042dfca36c1
Author: Pavel Tupitsyn 
Date:   2017-12-27T08:24:29Z

.NET: Another attempt to fix WindowsServiceTest

commit a93f2625c08b4c116c5a5df21c0e277f3821ad5f
Author: Pavel Tupitsyn 
Date:   2017-12-27T09:28:30Z

.NET: Another attempt to fix WindowsServiceTest, adding logger, no idea 
what the problem is

commit 2cf50943fb7451f7d5916fc824716b07c911093b
Author: Pavel Tupitsyn 
Date:   2017-12-27T11:35:10Z

.NET: Fix WindowsServiceTest - pass JVM path to the service

commit da9e76a5f093f745c51a0c55b6f8fa13dfc63ae9
Author: Ivanov Petr 
Date:   2017-12-27T15:20:40Z

IGNITE-7203 Java 8 by default
 * further improved AOP test behaviour by moving javaagent call into pom.xml

commit 602830163960b64e370f55b7a1269bb2fab513ba
Author: Ivanov Petr 
Date:   2017-12-28T13:03:40Z

Merge remote-tracking branch 'ignite/master' into ignite-7203




> Java 8 by default
> -
>
> Key: IGNITE-7203
> URL: https://issues.apache.org/jira/browse/IGNITE-7203
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Peter Ivanov
>  Labels: important
> Fix For: 2.4
>
>
> We should drop Java 7 support.
> 1) We should 
> - get rid of java8 profiles
> - relocate tests and sources with *.java8.* package to regular sources
> - set 
> {noformat}
>  1.8
>  1.8
> {noformat} 
> by default
> 2) Release process
> https://ci.ignite.apache.org/project.html?projectId=AssemblyAndRelease
> should be updated if necessary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7107:


Github user vveider closed the pull request at:

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


> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7203) Java 8 by default

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7203:


Github user vveider closed the pull request at:

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


> Java 8 by default
> -
>
> Key: IGNITE-7203
> URL: https://issues.apache.org/jira/browse/IGNITE-7203
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Peter Ivanov
>  Labels: important
> Fix For: 2.4
>
>
> We should drop Java 7 support.
> 1) We should 
> - get rid of java8 profiles
> - relocate tests and sources with *.java8.* package to regular sources
> - set 
> {noformat}
>  1.8
>  1.8
> {noformat} 
> by default
> 2) Release process
> https://ci.ignite.apache.org/project.html?projectId=AssemblyAndRelease
> should be updated if necessary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6745) Java 9: rework usages of URLClassLoader.getURLs()

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-6745.
-
Resolution: Fixed

> Java 9: rework usages of URLClassLoader.getURLs()
> -
>
> Key: IGNITE-6745
> URL: https://issues.apache.org/jira/browse/IGNITE-6745
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Cergey Chaulin
> Fix For: 2.4
>
> Attachments: IGNITE-6745.patch
>
>
> We use this method in multiple places:
> 1) {{MessageCodeGenerator}}
> 2) {{BinaryContext}}
> 3) {{ClassesGenerator}}
> 4) {{GridUriDeploymentFileProcessor}}
> The problem is that in Java 9 application class loader is not 
> {{URLClassLoader}}, so we cannot get URLs easily. Instead typically it is 
> {{BuiltinClassLoader}}, which refers to {{URLClassLoader}} in it's internal 
> field {{ucp}}.
> Let's refactor all usages of {{URLClassLoader.getURLs}} to some utility 
> method, which will be able to handle both Java 7/8 and Java 9 (through 
> reflection).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6745) Java 9: rework usages of URLClassLoader.getURLs()

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6745:
-

This issue is critical for release 2.4. So I've implemented and tested fix.
Merged to master branch.

> Java 9: rework usages of URLClassLoader.getURLs()
> -
>
> Key: IGNITE-6745
> URL: https://issues.apache.org/jira/browse/IGNITE-6745
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Cergey Chaulin
> Fix For: 2.4
>
> Attachments: IGNITE-6745.patch
>
>
> We use this method in multiple places:
> 1) {{MessageCodeGenerator}}
> 2) {{BinaryContext}}
> 3) {{ClassesGenerator}}
> 4) {{GridUriDeploymentFileProcessor}}
> The problem is that in Java 9 application class loader is not 
> {{URLClassLoader}}, so we cannot get URLs easily. Instead typically it is 
> {{BuiltinClassLoader}}, which refers to {{URLClassLoader}} in it's internal 
> field {{ucp}}.
> Let's refactor all usages of {{URLClassLoader.getURLs}} to some utility 
> method, which will be able to handle both Java 7/8 and Java 9 (through 
> reflection).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7107:
-

LGTM! Merged to master. Thanks for contribution!
[~ilyak] Thanks a lot for testing and comments!

> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7107:
-

Ignite will not started after package installation at this moment. User should 
use {{sudo systemctl start apache-ign...@default-config.xml}}.

> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7330) When client connects during cluster activation process it hangs on obtaining cache proxy

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7330:
---

 Summary: When client connects during cluster activation process it 
hangs on obtaining cache proxy
 Key: IGNITE-7330
 URL: https://issues.apache.org/jira/browse/IGNITE-7330
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
Priority: Critical
 Fix For: 2.4


The test below reproduces the issue:

{noformat}
public void testClientJoinWhenActivationInProgress() throws Exception {
Ignite srv = startGrids(5);

srv.active(true);

srv.createCaches(Arrays.asList(cacheConfigurations1()));

Map cacheData = new LinkedHashMap<>();

for (int i = 1; i <= 100; i++) {
for (CacheConfiguration ccfg : cacheConfigurations1()) {
srv.cache(ccfg.getName()).put(-i, i);

cacheData.put(-i, i);
}
}

stopAllGrids();

srv = startGrids(5);

final CountDownLatch clientStartLatch = new CountDownLatch(1);

IgniteInternalFuture clStartFut = GridTestUtils.runAsync(new Runnable() 
{
@Override public void run() {
try {
clientStartLatch.await();

Thread.sleep(10);

client = true;

Ignite cl = startGrid("client0");

IgniteCache atomicCache = 
cl.cache(CACHE_NAME_PREFIX + '0');
IgniteCache txCache = 
cl.cache(CACHE_NAME_PREFIX + '1');

assertEquals(100, atomicCache.size());
assertEquals(100, txCache.size());
}
catch (Exception e) {
log.error("Error occurred", e);
}
}
}, "client-starter-thread");

clientStartLatch.countDown();
srv.active(true);

clStartFut.get();
}
{noformat}

Expected behavior: test finishes successfully.

Actual behavior: test hangs on waiting for client start future to complete 
while "client-started-thread" will be hanging on obtaining a reference to the 
first cache.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7329) .NET: Thin client: SSL

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7329:
--

 Summary: .NET: Thin client: SSL
 Key: IGNITE-7329
 URL: https://issues.apache.org/jira/browse/IGNITE-7329
 Project: Ignite
  Issue Type: Improvement
  Components: platforms, thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn


Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7328) Improve Labeled Dataset loading from txt file

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-7328:


 Summary: Improve Labeled Dataset loading from txt file
 Key: IGNITE-7328
 URL: https://issues.apache.org/jira/browse/IGNITE-7328
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev


1. Wouldn't it be better to parse rows in-place (not to save them as strings at 
first)? In current implementation we will be needed to keep a dataset in memory 
twice and it might be a problem for big datasets.

2. What about the case when a dataset contains not only a numerical data? Do we 
consider this case or for such purposes some other "DatasetLoader" will be used?

3. Just an idea, in case we don't want to fall on bad data (99% of cases) would 
be great to understand the quality of loaded dataset such as number of missed 
rows/values.

4. Does a situation when a row doesn't contain required number of columns 
should be considered as "bad data" and don't break parsing with 
IndexOutOfBoundException?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7327) Add CSV loading to Labeled Dataset with Loader

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-7327:


 Summary: Add CSV loading to Labeled Dataset with Loader 
 Key: IGNITE-7327
 URL: https://issues.apache.org/jira/browse/IGNITE-7327
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev


Comment from [~dmitrievanthony]
Lots of datasets (from Kaggle for example) are supplied in CSV format with 
header line. In connection with it does it make sense to:

Use some CSV parsing (it's a bit more complicated than just splitting by comma)?
Add ability to use first header line as a source for so called feature names?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7326) Fix ignitevisorcmd | sqlline scripts to be able to run from /usr/bin installed as symbolic links

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-7326:
-

For the first point we should probably use readlink(3) to infer real location 
of script.

> Fix ignitevisorcmd | sqlline scripts to be able to run from /usr/bin 
> installed as symbolic links
> 
>
> Key: IGNITE-7326
> URL: https://issues.apache.org/jira/browse/IGNITE-7326
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
> Fix For: 2.5
>
>
> Currenlty, {{ignitevisorcmd.sh}} and {{sqlline.sh}} being installed into 
> {{/usr/bin}} will fail to run because of:
> * their unawarelessness of theirs real location;
> * necessity to write to {{$\{IGNITE_HOME}/work}} which can have different 
> permissions and owner (in packages, for example).
> It is required to rewrite these scripts to be able to run from anywhere by 
> theirs symbolic linka and with some temporary dir ({{/tmp}} for example) as 
> workdir.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-6625 at 12/28/17 12:35 PM:
-

SSL properties:
|| Ignite || MySQL ||
| useSSL | useSSL |
|  | requireSSL | 
| javax.net.ssl.* properties | javax.net.ssl.* properties | 
| sslProtocol | enabledTLSProtocols | 
| sslClientCertificateKeyStoreUrl | clientCertificateKeyStoreUrl | 
| sslClientCertificateKeyStorePassword | clientCertificateKeyStorePassword | 
| sslClientCertificateKeyStoreType | clientCertificateKeyStoreType | 
| sslTrustCertificateKeyStoreUrl | trustCertificateKeyStoreUrl | 
| sslTrustCertificateKeyStorePassword | trustCertificateKeyStorePassword  | 
| sslTrustCertificateKeyStoreType | trustCertificateKeyStoreType | 
| sslTrustAll | verifyServerCertificate | 
| sslFactory | socketFactory | 

PosgreSQL JDBC also supports Java SSL API and {{javax.net.ssl.*}} properties.
Also PostgreSQL has its own library (LibPQ) that allow to work with SSL 
properties by postres-specific way.

The interesting things at the PostgreSQL JDBC that may be applicable for Ignite:
- {{sslpaswordcallback}} Class name of the SSL password provider
- 'argument' property for each factory property e.g.: {{sslfactory}} class 
name, {{sslfactoryarg}} - arguments for factory.




was (Author: tledkov-gridgain):
SSL properties:
|| Ignite || MySQL ||
| useSSL | useSSL |
|  | requireSSL | 
| javax.net.ssl.* properties | javax.net.ssl.* properties | 
| sslProtocol | enabledTLSProtocols | 
| sslClientCertificateKeyStoreUrl | clientCertificateKeyStoreUrl | 
| sslClientCertificateKeyStorePassword | clientCertificateKeyStorePassword | 
| sslClientCertificateKeyStoreType | clientCertificateKeyStoreType | 
| sslTrustCertificateKeyStoreUrl | trustCertificateKeyStoreUrl | 
| sslTrustCertificateKeyStorePassword | trustCertificateKeyStorePassword  | 
| sslTrustCertificateKeyStoreType | trustCertificateKeyStoreType | 
| sslTrustAll | verifyServerCertificate | 
| sslFactory | socketFactory | 

PosgreSQL JDBC also supports Java SSL API and {{javax.net.ssl.*}} properties.
Also PostgreSQL has its own library (LibPQ) that allow to work with SSL 
properties by postres-specific way.

> JDBC thin: support SSL connection to Ignite node
> 
>
> Key: IGNITE-6625
> URL: https://issues.apache.org/jira/browse/IGNITE-6625
> Project: Ignite
>  Issue Type: Improvement
>  Components: jdbc
>Affects Versions: 2.2
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> SSL connection must be supported for JDBC thin driver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7326) Fix ignitevisorcmd | sqlline scripts to be able to run from /usr/bin installed as symbolic links

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7326:


 Summary: Fix ignitevisorcmd | sqlline scripts to be able to run 
from /usr/bin installed as symbolic links
 Key: IGNITE-7326
 URL: https://issues.apache.org/jira/browse/IGNITE-7326
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.5


Currenlty, {{ignitevisorcmd.sh}} and {{sqlline.sh}} being installed into 
{{/usr/bin}} will fail to run because of:
* their unawarelessness of theirs real location;
* necessity to write to {{$\{IGNITE_HOME}/work}} which can have different 
permissions and owner (in packages, for example).

It is required to rewrite these scripts to be able to run from anywhere by 
theirs symbolic linka and with some temporary dir ({{/tmp}} for example) as 
workdir.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7325) Remove ExternalizeTest from all test and change on ExternalizableTest

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-7325:


 Summary: Remove ExternalizeTest from all test and change on 
ExternalizableTest
 Key: IGNITE-7325
 URL: https://issues.apache.org/jira/browse/IGNITE-7325
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Aleksey Zinoviev






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov edited comment on IGNITE-5949 at 12/28/17 12:27 PM:
---

Fixed.
1) I have added the checks to the {{prepareChangeOnNotStartedCache()}} and 
{{prepareChangeOnStartedCache()}} where other similar checks are made.
2) There are tests that check for proper error messages.
JDBC column metadata is also checked in the new tests with the help of 
{{checkTableState()}} and {{getColumnMeta()}} routines.
TC test results seem to be OK.

[~vozerov], Please take a look.


was (Author: skalashnikov):
Fixed.
1) I have added the checks to the {{prepareChangeOnNotStartedCache()}} and 
{{prepareChangeOnStartedCache()}} where other similar checks are made.
2) There are tests that check for proper error messages.
JDBC column metadata is also checked in the new tests with the help of 
{{checkTableState()}} and {{getColumnMeta()}} routines.
TC test results seem to be OK.

> DDL: Support ALTER TABLE DROP COLUMN
> 
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Andrew Mashenkov
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.4
>
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.
> Design considerations:
> 1) Drop should only be possible on binary types without schema (see 
> IGNITE-6611). Probably we will need a new option for {{CREATE TABLE}} command
> 2) Drop should not block other operations for a long time. We should 
> synchronously block the table, change meta, then release the lock and let 
> operations continue.
> 3) Actual data remove should be performed asynchronously in the same way we 
> create index. During this time we should not allow any other modifications to 
> the table
> 4) Be careful with node stop - we do not want to wait for years for this 
> command to complete.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-6625:
--

SSL properties:
|| Ignite || MySQL ||
| useSSL | useSSL |
|  | requireSSL | 
| javax.net.ssl.* properties | javax.net.ssl.* properties | 
| sslProtocol | enabledTLSProtocols | 
| sslClientCertificateKeyStoreUrl | clientCertificateKeyStoreUrl | 
| sslClientCertificateKeyStorePassword | clientCertificateKeyStorePassword | 
| sslClientCertificateKeyStoreType | clientCertificateKeyStoreType | 
| sslTrustCertificateKeyStoreUrl | trustCertificateKeyStoreUrl | 
| sslTrustCertificateKeyStorePassword | trustCertificateKeyStorePassword  | 
| sslTrustCertificateKeyStoreType | trustCertificateKeyStoreType | 
| sslTrustAll | verifyServerCertificate | 
| sslFactory | socketFactory | 

PosgreSQL JDBC also supports Java SSL API and {{javax.net.ssl.*}} properties.
Also PostgreSQL has its own library (LibPQ) that allow to work with SSL 
properties by postres-specific way.

> JDBC thin: support SSL connection to Ignite node
> 
>
> Key: IGNITE-6625
> URL: https://issues.apache.org/jira/browse/IGNITE-6625
> Project: Ignite
>  Issue Type: Improvement
>  Components: jdbc
>Affects Versions: 2.2
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> SSL connection must be supported for JDBC thin driver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7293) "BinaryObjectException: Cannot find schema for object with compact footer" when "not null" field is defined

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7293:


Schema ID calculation fixed in .NET (return {{0}} when there are no fields). 
Tests added.

> "BinaryObjectException: Cannot find schema for object with compact footer" 
> when "not null" field is defined
> ---
>
> Key: IGNITE-7293
> URL: https://issues.apache.org/jira/browse/IGNITE-7293
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, sql
>Affects Versions: 2.3
>Reporter: Kirill Shirokov
>Assignee: Vladimir Ozerov
> Fix For: 2.4
>
>
> If the following test:
> org.apache.ignite.internal.processors.cache.index.H2DynamicTableSelfTest#testAffinityKey
> is modified by adding "not null" constraint to "age" column definition in 
> Person2 table:
> {noformat}
> execute("CREATE TABLE \"Person2\" (\"id\" int, \"city\" 
> varchar," +
> " \"name\" varchar, \"surname\" varchar, \"age\" int not 
> null, PRIMARY KEY (\"id\", \"city\")) WITH " +
> 
> "wrap_key,wrap_value,\"template=cache,affinity_key='city'\"");}}
> {noformat}
> The test fails with the following stack trace during INSERT operation:
> {noformat}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=-1199546406, schemaId=0]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2020)
>   at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.createSchema(BinaryObjectImpl.java:668)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:284)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:106)
>   at 
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:243)
>   at 
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:139)
>   at 
> org.apache.ignite.internal.processors.query.QueryTypeDescriptorImpl.validateKeyAndValue(QueryTypeDescriptorImpl.java:512)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:1031)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:877)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:438)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:420)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:194)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:229)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1568)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1983)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1979)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2465)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1988)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1944)
>   at 
> org.apache.ignite.internal.processors.cache.index.H2DynamicTableSelfTest.checkAffinityKey(H2DynamicTableSelfTest.java:1375)
>   at 
> org.apache.ignite.internal.processors.cache.index.H2DynamicTableSelfTest.testAffinityKey(H2DynamicTableSelfTest.java:1318)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7053) S3 IP finder: support server side encryption

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7053:
--

SHA-1: fe36e629e26a95163543d71aeb7d45dad96b961b

> S3 IP finder: support server side encryption
> 
>
> Key: IGNITE-7053
> URL: https://issues.apache.org/jira/browse/IGNITE-7053
> Project: Ignite
>  Issue Type: Improvement
>  Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Popov
> Fix For: 2.4
>
>
> In case server side encryption [1] is used, it may be required to specify the 
> algorithm in request headers when saving information in a bucket (can be done 
> via {{ObjectMetadata#setSSEAlgorithm}} method). To support this we need to 
> add corresponding configuration property to the S3 IP finder.
> [1] http://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7324) AssertionError Entry cannot become obsolete when DHT local candidate is added in deadlock detection suite

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7324:


 Summary: AssertionError Entry cannot become obsolete when DHT 
local candidate is added in deadlock detection suite
 Key: IGNITE-7324
 URL: https://issues.apache.org/jira/browse/IGNITE-7324
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.4


I observed this assertion in deadlock detection suite on TC:
{code}
[12:11:30]W: [org.apache.ignite:ignite-core] 
java.lang.AssertionError: Entry cannot become obsolete when DHT local candidate 
is added [e=GridDhtCacheEntry [rdrs=[], part=39, 
super=GridDistributedCacheEntry [super=GridCacheMapEntry 
[key=KeyCacheObjectImpl [part=39, val=39, hasValBytes=true], val=null, 
startVer=1514452286919, ver=GridCacheVersion [topVer=125932251, 
order=1514452286919, nodeOrder=2], hash=39, extras=GridCacheObsoleteEntryExtras 
[obsoleteVer=GridCacheVersion [topVer=2147483647, order=0, nodeOrder=0]], 
flags=2]]], 
ex=org.apache.ignite.internal.processors.cache.GridCacheEntryRemovedException]
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.map(GridDhtLockFuture.java:902)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onOwnerChanged(GridDhtLockFuture.java:655)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.notifyOwnerChanged(GridCacheMvccManager.java:226)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.access$200(GridCacheMvccManager.java:80)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onOwnerChanged(GridCacheMvccManager.java:163)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.checkOwnerChanged(GridCacheMapEntry.java:3709)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheEntry.removeLock(GridDistributedCacheEntry.java:400)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.removeLock(GridDhtCacheEntry.java:329)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheEntry.txUnlock(GridDistributedCacheEntry.java:665)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.unlockMultiple(IgniteTxManager.java:1672)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.rollbackTx(IgniteTxManager.java:1287)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userRollback(IgniteTxLocalAdapter.java:980)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3080)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:418)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3316)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.access$4900(GridNearTxLocal.java:122)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$26.run(GridNearTxLocal.java:4129)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6673)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[12:11:30]W: [org.apache.ignite:ignite-core]at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[12:11:30]W: 

[jira] [Commented] (IGNITE-4939) Receive event before cache initialized

[Andrey Davydov (JIRA)]

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

Andrey Davydov commented on IGNITE-4939:


If there is any workaroud? As I see in my logs, if this case happens service 
not started (i.e. no log messages from init(final ServiceContext ctx)).

> Receive event before cache initialized
> --
>
> Key: IGNITE-4939
> URL: https://issues.apache.org/jira/browse/IGNITE-4939
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: Nikolay Tikhonov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.1
>
>
> Receive event before cache initialized that leads to the following:
> {noformat}
> Exception in thread "sys-#755%Default%" java.lang.IllegalArgumentException: 
> Cache is not configured: ignite-sys-cache
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3343)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:719)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:691)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:650)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:1086)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$2000(GridContinuousProcessor.java:97)
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:741)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2332)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1042)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1011)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7288) Thin client: partial cache configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7288:


Doc updated: 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol

> Thin client: partial cache configuration
> 
>
> Key: IGNITE-7288
> URL: https://issues.apache.org/jira/browse/IGNITE-7288
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.4
>
>
> {{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
> {{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
> {{CacheConfiguration}}. User should be able to specify any combination of 
> properties in any order, leaving others at default state.
> Prefix each property with unique ID, then do a switch in a loop.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7306) Incorrect force key request processing when MVCC is enabled

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov reassigned IGNITE-7306:


Assignee: Igor Seliverstov

> Incorrect force key request processing when MVCC is enabled
> ---
>
> Key: IGNITE-7306
> URL: https://issues.apache.org/jira/browse/IGNITE-7306
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
> Fix For: 2.5
>
>
> Reproducer: {{IgniteCacheMultiTxLockSelfTest#testExplicitLockManyKeys}}
> Root cause: when {{GridDhtForceKeysRequest}} is processed locally, we obtain 
> {{GridCacheEntryInfo}} through {{GridCacheMapEntry.info}}. Returned instance 
> is unaware of MVCC version. Need to return {{GridCacheMvccEntryInfo}} instead.
> {code}
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccInitialValue(IgniteCacheOffheapManagerImpl.java:1433)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccInitialValue(IgniteCacheOffheapManagerImpl.java:396)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2624)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:537)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:199)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:176)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:193)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:191)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1406)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1388)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1567)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1195)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:128)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
>   at java.lang.Thread.run(Thread.java:748)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7288) Thin client: partial cache configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7288:


Github user asfgit closed the pull request at:

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


> Thin client: partial cache configuration
> 
>
> Key: IGNITE-7288
> URL: https://issues.apache.org/jira/browse/IGNITE-7288
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.4
>
>
> {{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
> {{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
> {{CacheConfiguration}}. User should be able to specify any combination of 
> properties in any order, leaving others at default state.
> Prefix each property with unique ID, then do a switch in a loop.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6814) Detailed memory consumption on start and OOM reporting

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin reassigned IGNITE-6814:
---

Assignee: Vyacheslav Koptilin  (was: Alexandr Fedotov)

> Detailed memory consumption on start and OOM reporting
> --
>
> Key: IGNITE-6814
> URL: https://issues.apache.org/jira/browse/IGNITE-6814
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Vyacheslav Koptilin
>Priority: Blocker
>  Labels: iep-6, important, usability
> Fix For: 2.4
>
>
> Presently Ignite allocates 20% of RAM on a node startup, however, the user 
> doesn't see automatically chosen memory settings. Also, if there a node runs 
> out of RAM and throws an OOM error there are no hints on why this happened 
> and how to fix it.
> Suggestions: 
> * Add {{off-heap}} field to {{Topology Snapshot}} message. The field will 
> accumulate maximum size of all the data regions defined cluster-wide:
> {code}
> Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, off-heap={N}, 
> heap=1.8GB, ]
> {code}
> * Print detailed memory configuration below {{Topology Snapshot}} message 
> following this format:
> {code}
> Data Regions Configured:
> ^-- Data_Region_Name [initSize=N, maxSize=N, persistenceEnabled={true|false}]
> {code}
> Example:
> {code}
> Data Regions Configured:
>^-- Default [initSize=100MB, maxSize=5.0 GB, persistenceEnabled=true]
>^-- RegionalMetrics [initSize=500MB, maxSize=15.0 GB, 
> persistenceEnabled=false]
> {code}
> * Provide guidelines on how to overcome OOM when it happens. Specify a data 
> region name with all its current parameters and suggest three possible things 
> - tweak maximum memory, setup eviction policies or enable Ignite persistence.
> {code}
> Out of memory in data region Region_Name [initSize=N, maxSize=N, 
> persistenceEnabled={true|false}]. Do one of the following:
>^-- Increase maximum size (DataRegionConfiguration.maxSize)
>^-- Enable Ignite persistence (DataRegionConfiguration.persistenceEnabled) 
> or
>^-- Enable eviction or expiration policies.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7288) Thin client: partial cache configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7288:


Merged to master: {{3c5d376605c7c12fad0dc67b9b58fc61c42ddfbd}}.

> Thin client: partial cache configuration
> 
>
> Key: IGNITE-7288
> URL: https://issues.apache.org/jira/browse/IGNITE-7288
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.4
>
>
> {{OP_CACHE_CREATE_WITH_CONFIGURATION}} and 
> {{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete 
> {{CacheConfiguration}}. User should be able to specify any combination of 
> properties in any order, leaving others at default state.
> Prefix each property with unique ID, then do a switch in a loop.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7239) In case of not serializable cache update response, future on node requester will never complete

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7239:


GitHub user dkarachentsev opened a pull request:

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

IGNITE-7239 - In case of not serializable cache update response, futu…

…re on node requester will never complete

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

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

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

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


commit e0a1ec657b6e638d4ed28fc3d4db4ff552929cff
Author: dkarachentsev 
Date:   2017-12-28T09:32:06Z

IGNITE-7239 - In case of not serializable cache update response, future on 
node requester will never complete




> In case of not serializable cache update response, future on node requester 
> will never complete
> ---
>
> Key: IGNITE-7239
> URL: https://issues.apache.org/jira/browse/IGNITE-7239
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Minor
>
> To avoid such hang, if response could not be serialized, create other 
> response with text of the error.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6456:


GitHub user dolphin1414 opened a pull request:

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

IGNITE-6456: Added opportunity to enable/disable different clients.

Added flags to ClientConnectorConfiguration which enable/disable different 
clients. Tests implemented.

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

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

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

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


commit d41ae61b8605df7c4f69af38c4b6f53f0f115cf2
Author: rkondakov 
Date:   2017-12-28T09:42:32Z

IGNITE-6456: Added flags to ClientConnectorConfiguration which 
enable/disable different clients.




> Add flags to ClientConnectorConfiguration which enable/disable different 
> clients
> 
>
> Key: IGNITE-6456
> URL: https://issues.apache.org/jira/browse/IGNITE-6456
> Project: Ignite
>  Issue Type: Improvement
>  Components: jdbc, odbc, thin client
>Affects Versions: 2.1
>Reporter: Igor Sapego
>Assignee: Roman Kondakov
>  Labels: usability
> Fix For: 2.4
>
>
> There is currently no way to disable only one client. For example, currently 
> you can't disallow thin JDBC driver connectivity alone, you can only disable 
> the whole {{ClientListenerProcessor}}, which is going to disable ODBC and 
> thin .NET clients as well.
> We should add options to disable/enable every single client, supported by the 
> {{ClientListenerProcessor}} separately. For example, we can add flags to the 
> {{ClientConnectorConfiguration}}:
> {{allowJdbc}}
> {{allowOdbc}}
> {{allowClient}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5217) Gradient descent for OLS lin reg

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5217:


GitHub user dmitrievanthony opened a pull request:

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

IGNITE-5217: Add Gradient Descent and QR-based trainers for Linear 
Regression



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

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

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

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


commit e95d8b6154f7ae1dc9b2e97a69b1abda145b0679
Author: dmitrievanthony 
Date:   2017-12-22T15:08:00Z

IGNITE-5217 Added initial version of Gradient Descent trainer of OLS 
regression

commit 1d67f26b1e85159e8734ec21d16bee0693ef0272
Author: Антон Дмитриев 
Date:   2017-12-24T15:09:43Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-5217

commit bd76022b11f7a3b0f9df5e1a85daebacfe094f8e
Author: dmitrievanthony 
Date:   2017-12-25T05:39:13Z

IGNITE-5217 Move gradient descent to optimization package, add test
datasets, add BarzilaiBorwein gradient descent updater.

commit 254dc7881f7bd7aaecc44f03c1ab3b7754045560
Author: dmitrievanthony 
Date:   2017-12-25T09:40:42Z

IGNITE-5217 Add artificial regression datasets and refactor SGD.

commit 0b588c1241cc4d8fbb825d5cda745f5c6dbdeb9a
Author: dmitrievanthony 
Date:   2017-12-25T09:58:06Z

IGNITE-5217 Improve code style in accordance with guidelines.

commit 22fb769f8f578e180d178397ecae853d4c3baf70
Author: dmitrievanthony 
Date:   2017-12-25T10:29:52Z

IGNITE-5217 Make LinearRegressionModel exportable.

commit 7c0f8a4e59ec6fa83363ffbfe59d773163ef19dd
Author: dmitrievanthony 
Date:   2017-12-25T10:57:49Z

IGNITE-5217 Add simple linear regression trainer based on QR decomposition.

commit f2a9d34afb09b95d66c70a3bdd72617671910517
Author: dmitrievanthony 
Date:   2017-12-25T13:08:04Z

IGNITE-5217 Linear regression tests refactoring.

commit 92e64e9364c2c42073e6ac782feb00b86fcd5366
Author: dmitrievanthony 
Date:   2017-12-26T07:05:34Z

Merge remote-tracking branch 'origin/master' into ignite-5217

commit f29d385184735fd2a71f6753c2bbd4af133154f6
Author: dmitrievanthony 
Date:   2017-12-26T15:18:24Z

IGNITE-5217 Add distributed matrices support to linear regression.

commit ed6cd77b3926899c17ce71982b27af0cd129b6aa
Author: dmitrievanthony 
Date:   2017-12-27T17:38:11Z

IGNITE-5217 Add distributed gradient calculator.

commit 053d7511e6070a66063c5a324c6e9b81c0d3a649
Author: dmitrievanthony 
Date:   2017-12-28T08:48:34Z

IGNITE-5217 Add SparseDistributedMatrixMapReducer.

commit 0792bee4d5e2fa0b7eba20ee436c55c92114e25f
Author: dmitrievanthony 
Date:   2017-12-28T09:13:29Z

IGNITE-5217 Revert accidental changes.

commit 06fb44ce155db3a39be2b530253a2e319bbd87fd
Author: dmitrievanthony 
Date:   2017-12-28T09:19:11Z

IGNITE-5217 Revert accidental changes.




> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)