[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7851:
--

[~ptupitsyn], ok got it. Why do we have CacheConfiguration constructor in C# 
that makes users fill they do everything correct and get this error?

{{new CacheConfiguration("Person", typeof(Person))}}

BTW, Java part does not have such constructor. 

Shall we deprecate it?

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at 

[jira] [Assigned] (IGNITE-7810) Web console: replace Roboto slab font with Roboto regular

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7810:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

> Web console: replace Roboto slab font with Roboto regular
> -
>
> Key: IGNITE-7810
> URL: https://issues.apache.org/jira/browse/IGNITE-7810
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Minor
>
> Since the Roboto slab font is considered deprecated, it should be replaced 
> with Roboto regular.
> What to do:
> 1. Replace global font on  with Roboto.
> 2. Look for Roboto slab in other place and remove it too.
> 3. Remove Roboto slab from dependencies, if applicable.



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

[jira] [Closed] (IGNITE-3345) Implement support for optional key type in REST HTTP get command

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-3345.
--

> Implement support for optional key type in REST HTTP get command
> 
>
> Key: IGNITE-3345
> URL: https://issues.apache.org/jira/browse/IGNITE-3345
> Project: Ignite
>  Issue Type: Task
>  Components: cache, rest
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> It seems that in current implementation 
> (https://apacheignite.readme.io/docs/rest-api#get)
> GET command could work only with String keys.
> We can add optional parameter "keyType" and implement support for common 
> built-in types such as Integer, Long, UUID,... and user classes that a valid 
> JavaBeans.
> Sample: http://host:port/ignite?cmd=get=1=myCache=Long



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

[jira] [Commented] (IGNITE-3345) Implement support for optional key type in REST HTTP get command

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-3345:


re-tested on master

> Implement support for optional key type in REST HTTP get command
> 
>
> Key: IGNITE-3345
> URL: https://issues.apache.org/jira/browse/IGNITE-3345
> Project: Ignite
>  Issue Type: Task
>  Components: cache, rest
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> It seems that in current implementation 
> (https://apacheignite.readme.io/docs/rest-api#get)
> GET command could work only with String keys.
> We can add optional parameter "keyType" and implement support for common 
> built-in types such as Integer, Long, UUID,... and user classes that a valid 
> JavaBeans.
> Sample: http://host:port/ignite?cmd=get=1=myCache=Long



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

[jira] [Comment Edited] (IGNITE-7810) Web console: replace Roboto slab font with Roboto regular

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7810 at 3/6/18 7:19 AM:
--

[~Dmitriyff] please review.

I've replaced Robot Slab font with Roboto as a sans-serif font in Bootstrap 
variables file. All pages look good afterwards, including main app loader and 
queries. There were no other references to Roboto Slab. It couldn't be removed 
from dependencies because all Roboto fonts come from a single package.


was (Author: klaster_1):
I've replaced Robot Slab font with Roboto as a sans-serif font in Bootstrap 
variables file. All pages look good afterwards, including main app loader and 
queries. There were no other references to Roboto Slab. It couldn't be removed 
from dependencies because all Roboto fonts come from a single package.

> Web console: replace Roboto slab font with Roboto regular
> -
>
> Key: IGNITE-7810
> URL: https://issues.apache.org/jira/browse/IGNITE-7810
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>Priority: Minor
>
> Since the Roboto slab font is considered deprecated, it should be replaced 
> with Roboto regular.
> What to do:
> 1. Replace global font on  with Roboto.
> 2. Look for Roboto slab in other place and remove it too.
> 3. Remove Roboto slab from dependencies, if applicable.



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

[jira] [Assigned] (IGNITE-7810) Web console: replace Roboto slab font with Roboto regular

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7810:


Assignee: Dmitriy Shabalin  (was: Ilya Borisov)

I've replaced Robot Slab font with Roboto as a sans-serif font in Bootstrap 
variables file. All pages look good afterwards, including main app loader and 
queries. There were no other references to Roboto Slab. It couldn't be removed 
from dependencies because all Roboto fonts come from a single package.

> Web console: replace Roboto slab font with Roboto regular
> -
>
> Key: IGNITE-7810
> URL: https://issues.apache.org/jira/browse/IGNITE-7810
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>Priority: Minor
>
> Since the Roboto slab font is considered deprecated, it should be replaced 
> with Roboto regular.
> What to do:
> 1. Replace global font on  with Roboto.
> 2. Look for Roboto slab in other place and remove it too.
> 3. Remove Roboto slab from dependencies, if applicable.



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

[jira] [Closed] (IGNITE-7033) Web console: Increase width of columns on admin page

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7033.
--

> Web console: Increase width of columns on admin page
> 
>
> Key: IGNITE-7033
> URL: https://issues.apache.org/jira/browse/IGNITE-7033
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> *"Last activity" and "email" columns are too narrow*



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

[jira] [Commented] (IGNITE-7033) Web console: Increase width of columns on admin page

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7033:


re-tested on master

> Web console: Increase width of columns on admin page
> 
>
> Key: IGNITE-7033
> URL: https://issues.apache.org/jira/browse/IGNITE-7033
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> *"Last activity" and "email" columns are too narrow*



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

[jira] [Commented] (IGNITE-7862) Update flatten-plugin to 1.0.1 version

[Peter Ivanov (JIRA)]

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

Peter Ivanov commented on IGNITE-7862:
--

I'll pass this build to QA in order to understand whether fix has impact on 
release procedure. Please stand by.

> Update flatten-plugin to 1.0.1 version
> --
>
> Key: IGNITE-7862
> URL: https://issues.apache.org/jira/browse/IGNITE-7862
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> With flatten-plugin version {{1.0.0-beta-3}} we has to enlist all transitive 
> dependencies.
> dev-list discussion - 
> http://apache-ignite-developers.2346864.n4.nabble.com/Maven-Issues-with-flatten-plugin-td27537.html
> Solution is to update plugin to {{1.0.1}} version



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

[jira] [Closed] (IGNITE-7725) REST: expand parameters list of GetOrCreateCache command

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7725.
--

> REST: expand parameters list of GetOrCreateCache command
> 
>
> Key: IGNITE-7725
> URL: https://issues.apache.org/jira/browse/IGNITE-7725
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.3
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Current implementation is very primitive and do not allow to create caches 
> with custom options via REST.
> http://host:port/ignite?cmd=getorcreate=cache_name[=template_name][=1][=FULL_SYNC][;
>  other options]
> Ignite will support two pre-configured templates out of the box: PARTITIONED 
> and REPLICATED (same as SQL engine).
> If template name is not specified, by default it will be PARTITIONED.
>  
>  



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

[jira] [Commented] (IGNITE-7725) REST: expand parameters list of GetOrCreateCache command

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7725:


re-tested on master

> REST: expand parameters list of GetOrCreateCache command
> 
>
> Key: IGNITE-7725
> URL: https://issues.apache.org/jira/browse/IGNITE-7725
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.3
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
>
> Current implementation is very primitive and do not allow to create caches 
> with custom options via REST.
> http://host:port/ignite?cmd=getorcreate=cache_name[=template_name][=1][=FULL_SYNC][;
>  other options]
> Ignite will support two pre-configured templates out of the box: PARTITIONED 
> and REPLICATED (same as SQL engine).
> If template name is not specified, by default it will be PARTITIONED.
>  
>  



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

[jira] [Commented] (IGNITE-5737) Web Console: make cluster a root configuration entity

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-5737:
--

[~anovikov] please review.

> Web Console: make cluster a root configuration entity
> -
>
> Key: IGNITE-5737
> URL: https://issues.apache.org/jira/browse/IGNITE-5737
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>Priority: Major
>
> It has been agreed upon to make cluster a root entity for configuration 
> screens. That means that all caches/igfs/models will not be shared among 
> clusters and be owned by a single cluster instead of current many to many 
> relation.
> Backend requirements:
> 1. Implement REST endpoints to manage clusters.
> Frontend requirements:
> 1. Remove cluster selection from cluster edit screens.
> 2. Remove cluster selection from basic/caches/igfss/models screens.



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

[jira] [Assigned] (IGNITE-5466) Web Console: New Configuration Screen

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5466:


Assignee: Dmitriy Shabalin  (was: Ilya Borisov)

Please review.

> Web Console: New Configuration Screen
> -
>
> Key: IGNITE-5466
> URL: https://issues.apache.org/jira/browse/IGNITE-5466
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
>Priority: Major
>




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

[jira] [Assigned] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7459:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Commented] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7459:


Looks acceptable. Works correctly. 

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Commented] (IGNITE-7459) Web console: do not show result title until query end

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin commented on IGNITE-7459:
---

[~pkonstantinov] Added hiding table with results when new scan is performed. 
Also removed node ID8  in table when cancel is clicked in modal.

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Closed] (IGNITE-7886) Provide a list of node Ids on the Baseline page on Web Console

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-7886.
---

> Provide a list of node Ids on the Baseline page on Web Console
> --
>
> Key: IGNITE-7886
> URL: https://issues.apache.org/jira/browse/IGNITE-7886
> Project: Ignite
>  Issue Type: Bug
>Reporter: Prachi Garg
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.4
>
>
> It seems that the only way to get node IDs (needed for baseline topology) is 
> from Web Console ->Monitoring ->Dashboard ->Node -> select node -> click Info 
> -> General. However, Monitoring is not part of Ignite. Additionally, on the 
> baseline page, on the web console, there is no list of nodes (or node Ids) to 
> select from; it's blank. There should be a list of nodes that can be selected 
> for baseline topology. Could this issue be related to - 
> https://issues.apache.org/jira/browse/IGNITE-7885 ?



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

[jira] [Resolved] (IGNITE-7886) Provide a list of node Ids on the Baseline page on Web Console

[Prachi Garg (JIRA)]

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

Prachi Garg resolved IGNITE-7886.
-
Resolution: Fixed

> Provide a list of node Ids on the Baseline page on Web Console
> --
>
> Key: IGNITE-7886
> URL: https://issues.apache.org/jira/browse/IGNITE-7886
> Project: Ignite
>  Issue Type: Bug
>Reporter: Prachi Garg
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.4
>
>
> It seems that the only way to get node IDs (needed for baseline topology) is 
> from Web Console ->Monitoring ->Dashboard ->Node -> select node -> click Info 
> -> General. However, Monitoring is not part of Ignite. Additionally, on the 
> baseline page, on the web console, there is no list of nodes (or node Ids) to 
> select from; it's blank. There should be a list of nodes that can be selected 
> for baseline topology. Could this issue be related to - 
> https://issues.apache.org/jira/browse/IGNITE-7885 ?



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

[jira] [Resolved] (IGNITE-7885) Error on Baseline page on Web Console

[Prachi Garg (JIRA)]

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

Prachi Garg resolved IGNITE-7885.
-
Resolution: Fixed

> Error on Baseline page on Web Console
> -
>
> Key: IGNITE-7885
> URL: https://issues.apache.org/jira/browse/IGNITE-7885
> Project: Ignite
>  Issue Type: Bug
>Reporter: Prachi Garg
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.4
>
>
> Every time I go to the baseline page on the web console, I get the following 
> error -
> {code:java}
> Failed to handle request: [req=EXE, 
> taskName=org.apache.ignite.internal.visor.compute.VisorGatewayTask, 
> params=[null, org.apache.ignite.internal.visor.baseline.VisorBaselineTask, 
> org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg, COLLECT, -1, 
> java.util.List, java.lang.String, null], 
> err=org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg]{code}



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

[jira] [Closed] (IGNITE-7885) Error on Baseline page on Web Console

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-7885.
---

> Error on Baseline page on Web Console
> -
>
> Key: IGNITE-7885
> URL: https://issues.apache.org/jira/browse/IGNITE-7885
> Project: Ignite
>  Issue Type: Bug
>Reporter: Prachi Garg
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.4
>
>
> Every time I go to the baseline page on the web console, I get the following 
> error -
> {code:java}
> Failed to handle request: [req=EXE, 
> taskName=org.apache.ignite.internal.visor.compute.VisorGatewayTask, 
> params=[null, org.apache.ignite.internal.visor.baseline.VisorBaselineTask, 
> org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg, COLLECT, -1, 
> java.util.List, java.lang.String, null], 
> err=org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg]{code}



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

[jira] [Assigned] (IGNITE-7536) Document baseline topology feature and its WebConsole screen

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-7536:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Document baseline topology feature and its WebConsole screen 
> -
>
> Key: IGNITE-7536
> URL: https://issues.apache.org/jira/browse/IGNITE-7536
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> Document Baseline topology:
> [https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches]
> and how to manage it with Web Console and control.sh script (Ignite 
> activation doc has to be updated).



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

[jira] [Created] (IGNITE-7886) Provide a list of node Ids on the Baseline page on Web Console

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7886:
---

 Summary: Provide a list of node Ids on the Baseline page on Web 
Console
 Key: IGNITE-7886
 URL: https://issues.apache.org/jira/browse/IGNITE-7886
 Project: Ignite
  Issue Type: Bug
Reporter: Prachi Garg
Assignee: Alexey Kuznetsov
 Fix For: 2.4


It seems that the only way to get node IDs (needed for baseline topology) is 
from Web Console ->Monitoring ->Dashboard ->Node -> select node -> click Info 
-> General. However, Monitoring is not part of Ignite. Additionally, on the 
baseline page, on the web console, there is no list of nodes (or node Ids) to 
select from; it's blank. There should be a list of nodes that can be selected 
for baseline topology. Could this issue be related to - 
https://issues.apache.org/jira/browse/IGNITE-7885 ?



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

[jira] [Created] (IGNITE-7885) Error on Baseline page on Web Console

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7885:
---

 Summary: Error on Baseline page on Web Console
 Key: IGNITE-7885
 URL: https://issues.apache.org/jira/browse/IGNITE-7885
 Project: Ignite
  Issue Type: Bug
Reporter: Prachi Garg
Assignee: Alexey Kuznetsov
 Fix For: 2.4


Every time I go to the baseline page on the web console, I get the following 
error -
{code:java}
Failed to handle request: [req=EXE, 
taskName=org.apache.ignite.internal.visor.compute.VisorGatewayTask, 
params=[null, org.apache.ignite.internal.visor.baseline.VisorBaselineTask, 
org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg, COLLECT, -1, 
java.util.List, java.lang.String, null], 
err=org.apache.ignite.internal.visor.baseline.VisorBaselineTaskArg]{code}



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

[jira] [Created] (IGNITE-7884) Ship SQL scripts with same database in Ignite

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7884:
---

 Summary: Ship SQL scripts with same database in Ignite
 Key: IGNITE-7884
 URL: https://issues.apache.org/jira/browse/IGNITE-7884
 Project: Ignite
  Issue Type: New Feature
  Components: examples, sql
Affects Versions: 2.5
Reporter: Denis Magda
 Fix For: 2.5


As per discussion on @dev list, let's ship two kind of SQL scripts that can be 
used to create and populate a database quickly:

[http://apache-ignite-developers.2346864.n4.nabble.com/Shipping-SQL-script-CSV-files-in-Ignite-examples-td27440.html]

 

The database below is suggested to be used because it represents real data, 
allows setting up affinity collocation and demonstrate meaningful SQL queries 
with joins:

[https://github.com/dmagda/ignite_world_demo/blob/master/ignite_world.sql]

 

First, this script can be used as is and executed in any SQL tool such as 
SQLline.

Second, to demonstrate the use of {{COPY}} command we should take the same 
script, create a file that will store DDL statements and turn INSERTS into a 
CSV file.

 



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

[jira] [Assigned] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-7419:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> Explain how swap is supported and works in Ignite. Provide a rationale on 
> Ignite persistence vs swap.
> In addition, looks people don't catch what happens when memory region goes 
> beyond the maximum size. Revisit the persistence configuration:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]



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

[jira] [Commented] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-7419:
-

[~dmagda], Please review -
 * 
[https://apacheignite.readme.io/v2.3/docs/durable-memory-24#section-persistence-features]
 * [https://en.wikipedia.org/wiki/Apache_Ignite#Memory_architecture] ( See Swap 
Space section)

> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>
> Explain how swap is supported and works in Ignite. Provide a rationale on 
> Ignite persistence vs swap.
> In addition, looks people don't catch what happens when memory region goes 
> beyond the maximum size. Revisit the persistence configuration:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]



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

[jira] [Commented] (IGNITE-7862) Update flatten-plugin to 1.0.1 version

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7862:
-

Hello, [~vveider].

We got TC run without maven crash.

https://ci.ignite.apache.org/viewQueued.html?itemId=1126280=queuedBuildOverviewTab

Please, tell me, can we merge this fix?

> Update flatten-plugin to 1.0.1 version
> --
>
> Key: IGNITE-7862
> URL: https://issues.apache.org/jira/browse/IGNITE-7862
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> With flatten-plugin version {{1.0.0-beta-3}} we has to enlist all transitive 
> dependencies.
> dev-list discussion - 
> http://apache-ignite-developers.2346864.n4.nabble.com/Maven-Issues-with-flatten-plugin-td27537.html
> Solution is to update plugin to {{1.0.1}} version



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

[jira] [Commented] (IGNITE-7685) Incorrect AllocationRate counting

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7685:


Github user andrey-kuznetsov closed the pull request at:

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


> Incorrect AllocationRate counting
> -
>
> Key: IGNITE-7685
> URL: https://issues.apache.org/jira/browse/IGNITE-7685
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.4
>Reporter: Anton Vinogradov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Each call of 
> {{org.apache.ignite.internal.processors.cache.persistence.DataRegionMetricsImpl#updateTotalAllocatedPages}}
>  performs {{allocRate.onHit()}} call which is not correct since delta can be 
> negative or bigger that 1.
> Need to fix allocationRate counting. The fix should affect only "proper" 
> allocations, as opposed to allocations made during recovery, storage 
> initialization, etc. 



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

[jira] [Commented] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7419:
-

[~pgarg] , excellent coverage, I've done minor changes and improvements. Please 
go ahead and update the rest of the pages.

 

> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>
> Explain how swap is supported and works in Ignite. Provide a rationale on 
> Ignite persistence vs swap.
> In addition, looks people don't catch what happens when memory region goes 
> beyond the maximum size. Revisit the persistence configuration:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]



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

[jira] [Closed] (IGNITE-7825) ODBC: Update specification documentation

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-7825.
---

> ODBC: Update specification documentation
> 
>
> Key: IGNITE-7825
> URL: https://issues.apache.org/jira/browse/IGNITE-7825
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Prachi Garg
>Priority: Major
>  Labels: documentation, odbc
> Fix For: 2.4
>
>
> Need to update the following doc 
> [https://apacheignite-sql.readme.io/v2.3/docs/specification] according to the 
> newly implemented features in 2.4.



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

[jira] [Commented] (IGNITE-7517) Get rid of org.jsr166.ConcurrentLinkedDeque8

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7517:
-

[~andrey-kuznetsov], looks good for me. Merged to master branch.

Thanks for your contribution!

> Get rid of org.jsr166.ConcurrentLinkedDeque8
> 
>
> Key: IGNITE-7517
> URL: https://issues.apache.org/jira/browse/IGNITE-7517
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Replace usages of {{ConcurrentLinkedDeque8}} by {{ConcurrentLinkedDeque}} 
> Java 8 implementation.



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

[jira] [Commented] (IGNITE-7077) Spark Data Frame Support. Strategy to convert complete query to Ignite SQL

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-7077:
-

[~NIzhikov], not yet unfortunately. Will do my best to review this week. Thanks 
for following up!

> Spark Data Frame Support. Strategy to convert complete query to Ignite SQL
> --
>
> Key: IGNITE-7077
> URL: https://issues.apache.org/jira/browse/IGNITE-7077
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: bigdata
> Fix For: 2.5
>
>
> Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084.
> We need to implement custom spark strategy that can convert whole Spark SQL 
> query to Ignite SQL Query if query consists of only Ignite tables.
> The strategy does nothing if spark query includes not only Ignite tables.
> Memsql implementation can be taken as an example - 
> https://github.com/memsql/memsql-spark-connector



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

[jira] [Commented] (IGNITE-7816) DataFrame examples: wrong folder, hidden on TeamCity

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7816:
-

Guys, guess this ticket slips to 2.5 release. Changed the version. Roll it back 
to 2.4 if the changes made their way into the current release.

> DataFrame examples: wrong folder, hidden on TeamCity
> 
>
> Key: IGNITE-7816
> URL: https://issues.apache.org/jira/browse/IGNITE-7816
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, examples
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Trivial
> Fix For: 2.5
>
>
> 1. Spark DataFrame examples are in 
> {{examples/src/main/spark/org/apache/ignite/examples/spark}} folder. Should 
> be moved to 
> {{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}}.
> 2. Spark DataFrame examples not tested on Team City under Ignite Examples. 
> https://issues.apache.org/jira/browse/IGNITE-7655?focusedCommentId=16377875=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16377875



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

[jira] [Updated] (IGNITE-7816) DataFrame examples: wrong folder, hidden on TeamCity

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7816:

Fix Version/s: (was: 2.4)
   2.5

> DataFrame examples: wrong folder, hidden on TeamCity
> 
>
> Key: IGNITE-7816
> URL: https://issues.apache.org/jira/browse/IGNITE-7816
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, examples
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Trivial
> Fix For: 2.5
>
>
> 1. Spark DataFrame examples are in 
> {{examples/src/main/spark/org/apache/ignite/examples/spark}} folder. Should 
> be moved to 
> {{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}}.
> 2. Spark DataFrame examples not tested on Team City under Ignite Examples. 
> https://issues.apache.org/jira/browse/IGNITE-7655?focusedCommentId=16377875=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16377875



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

[jira] [Closed] (IGNITE-6400) Document ClientConnectorConfiguration

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-6400.
---

> Document ClientConnectorConfiguration
> -
>
> Key: IGNITE-6400
> URL: https://issues.apache.org/jira/browse/IGNITE-6400
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, thin client
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>




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

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

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7655.
---

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



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

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

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7655:
-

[~NIzhikov], [~abchaudhri] , thanks guys! The doc looks good to me, closing the 
ticket.

 

[~abchaudhri] , please create a new Jira ticket for the examples and set its 
version to 2.5. Place all the examples in respective Ignite examples folders, 
add tests and issue a pull-request. Nikolay and I will be happy to review the 
examples and accept them into the main code base.

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



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

[jira] [Commented] (IGNITE-7642) Ignite fails with OOM if query has "NULLS LAST"

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov commented on IGNITE-7642:
---

[~vozerov] suggested to create h2 index with NULLS LAST modifier:

cols.add(tbl.indexColumn(col.getColumnId(),
(idxDesc.descending(field) ? SortOrder.DESCENDING : SortOrder.ASCENDING)) *| 
SortOrder.NULLS_LAST*)"

 

I checked this approach works fine. I think we should introduce in Ignite API 
configuration for NULLS_LAST.

> Ignite fails with OOM if query has "NULLS LAST"
> ---
>
> Key: IGNITE-7642
> URL: https://issues.apache.org/jira/browse/IGNITE-7642
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
> Attachments: OrderByNullsLastTest.java
>
>
> I have an index for "a" filed of "A" type and the following SQL works fine:
> SELECT * FROM A ORDER BY a LIMIT 0 + 50
>  
> but as soon as I added "NULLS LAST" it starts to fail with OOM error:
> SELECT * FROM A ORDER BY a NULLS LAST LIMIT 0 + 50
> However for both queries, EXPLAIN says that it the uses index, I don't see 
> why it should fail, but looks like ignite tryes to load all memory into heap 
> and sort there, and this leads to OOM.
>  
> A reproducer is attached.



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

[jira] [Updated] (IGNITE-7642) Ignite fails with OOM if query has "NULLS LAST"

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7642:
--
Description: 
I have an index for "a" filed of "A" type and the following SQL works fine:

SELECT * FROM A ORDER BY a LIMIT 0 + 50

 

but as soon as I added "NULLS LAST" it starts to fail with OOM error:

SELECT * FROM A ORDER BY a NULLS LAST LIMIT 0 + 50

However for both queries, EXPLAIN says that it the uses index, I don't see why 
it should fail, but looks like ignite tryes to load all memory into heap and 
sort there, and this leads to OOM.

 

A reproducer is attached.

  was:
I have an index for "a" filed of "A" type and the following SQL works fine:

SELECT * FROM A ORDER BY a LIMIT 0 + 50

 

but as soon as I added "NULLS LAST" it starts to fail with OOM error:

SELECT * FROM A WHERE a ORDER BY a NULLS LAST LIMIT 0 + 50

However for both queries, EXPLAIN says that it the uses index, I don't see why 
it should fail, but looks like ignite tryes to load all memory into heap and 
sort there, and this leads to OOM.

 

A reproducer is attached.


> Ignite fails with OOM if query has "NULLS LAST"
> ---
>
> Key: IGNITE-7642
> URL: https://issues.apache.org/jira/browse/IGNITE-7642
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
> Attachments: OrderByNullsLastTest.java
>
>
> I have an index for "a" filed of "A" type and the following SQL works fine:
> SELECT * FROM A ORDER BY a LIMIT 0 + 50
>  
> but as soon as I added "NULLS LAST" it starts to fail with OOM error:
> SELECT * FROM A ORDER BY a NULLS LAST LIMIT 0 + 50
> However for both queries, EXPLAIN says that it the uses index, I don't see 
> why it should fail, but looks like ignite tryes to load all memory into heap 
> and sort there, and this leads to OOM.
>  
> A reproducer is attached.



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

[jira] [Updated] (IGNITE-7642) Ignite fails with OOM if query has "NULLS LAST"

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7642:
--
Description: 
I have an index for "a" filed of "A" type and the following SQL works fine:

SELECT * FROM A ORDER BY a LIMIT 0 + 50

 

but as soon as I added "NULLS LAST" it starts to fail with OOM error:

SELECT * FROM A WHERE a ORDER BY a NULLS LAST LIMIT 0 + 50

However for both queries, EXPLAIN says that it the uses index, I don't see why 
it should fail, but looks like ignite tryes to load all memory into heap and 
sort there, and this leads to OOM.

 

A reproducer is attached.

  was:
I have an index for "a" filed of "A" type and the following SQL works fine:

SELECT * FROM A ORDER BY a LIMIT 0 + 50

 

but as soon as I added "NULLS LAST" it starts to fail with OOM error:

SELECT * FROM A WHERE a is not null ORDER BY a LIMIT 0 + 50

 

However for both queries, EXPLAIN says that it the uses index, I don't see why 
it should fail, but looks like ignite tryes to load all memory into heap and 
sort there, and this leads to OOM.

 

A reproducer is attached.


> Ignite fails with OOM if query has "NULLS LAST"
> ---
>
> Key: IGNITE-7642
> URL: https://issues.apache.org/jira/browse/IGNITE-7642
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
> Attachments: OrderByNullsLastTest.java
>
>
> I have an index for "a" filed of "A" type and the following SQL works fine:
> SELECT * FROM A ORDER BY a LIMIT 0 + 50
>  
> but as soon as I added "NULLS LAST" it starts to fail with OOM error:
> SELECT * FROM A WHERE a ORDER BY a NULLS LAST LIMIT 0 + 50
> However for both queries, EXPLAIN says that it the uses index, I don't see 
> why it should fail, but looks like ignite tryes to load all memory into heap 
> and sort there, and this leads to OOM.
>  
> A reproducer is attached.



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

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7851:


[~alexey.tank2], why is this ticket resolved? I've reopened it.

The fix is not correct, we can not infer SQL types from ICache generic 
arguments.
Generic arguments can be anything: interfaces, abstract classes, {{object}, etc 
etc. 

There is nothing to fix, user HAS to specify key type as well as value type in 
such cases.

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack 

[jira] [Updated] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6839:
---
Labels: MakeTeamcityGreenAgain Muted_test  (was: MakeTeamcityGreenAgain)

> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> 
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.5
>
>
> Ignite Compatibility: 2 test are flaky:
>   
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
>  (fails: 2/55): 
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta, 
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in 
> https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Reopened] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reopened IGNITE-7851:


> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32 
> stackTraceCharsLen, Void* errData, Int32 errDataLen)
>at 
> 

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7878:


Test disabled with comment: {{18c6b4a5d079874e9c156fa39564970ad3c31914}}.

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

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

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri edited comment on IGNITE-7655 at 3/5/18 4:05 PM:


[~NIzhikov], I think everything is done. I have converted the Scala programs to 
Java. I have added the code snippets to the documentation. I have added a very 
small section about SparkSession to the documentation. It needs [~dmagda] to 
review all this now.


was (Author: abchaudhri):
[~NIzhikov], i think everything is done. I have converted the Scala programs to 
Java. I have added the code snippets to the documentation. I have added a very 
small section about SparkSession to the documentation. It needs [~dmagda] to 
review all this now.

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



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

[jira] [Created] (IGNITE-7883) Cluster can have inconsistent affinity configuration

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7883:
-

 Summary: Cluster can have inconsistent affinity configuration 
 Key: IGNITE-7883
 URL: https://issues.apache.org/jira/browse/IGNITE-7883
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
 Fix For: 2.5


A cluster can have inconsistent affinity configuration if you created two 
nodes, one with affinity key configuration and other without it(in IgniteCfg or 
CacheCfg),  both nodes will work fine with no exceptions, but in the same time 
they will apply different affinity rules to keys:

 
{code:java}
public class Test {
private static int id = 0;

public static void main(String[] args) {
Ignite ignite = Ignition.start(getConfiguration(true, false));
Ignite ignite2 = Ignition.start(getConfiguration(false, false));

Affinity affinity = ignite.affinity("TEST");
Affinity affinity2 = ignite2.affinity("TEST");
for (int i = 0; i < 1_000_000; i++) {
AKey key = new AKey(i);

if(affinity.partition(key) != affinity2.partition(key))
System.out.println("FAILED for: " + key);
}

}

@NotNull private static IgniteConfiguration getConfiguration(boolean 
withAffinityCfg, boolean client) {
IgniteConfiguration cfg = new IgniteConfiguration();

TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder(true);
finder.setAddresses(Arrays.asList("localhost:47500..47600"));

cfg.setClientMode(client);

cfg.setIgniteInstanceName("test" + id++);

if(withAffinityCfg) {
CacheConfiguration cacheCfg = new CacheConfiguration("TEST");

cacheCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cacheCfg.setCacheMode(CacheMode.PARTITIONED);

cacheCfg.setKeyConfiguration(new 
CacheKeyConfiguration("multiplan.AKey", "a"));

cfg.setCacheConfiguration(cacheCfg);
}

cfg.setDiscoverySpi(new TcpDiscoverySpi().setIpFinder(finder));

return cfg;
}
}

class AKey {

int a;

public AKey(int a) {
this.a = a;
}

@Override public String toString() {
return "AKey{" +
"b=" + a +
'}';
}
}


{code}



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

[jira] [Commented] (IGNITE-7531) SQL: Create data load benchmarks

[Pavel Kuznetsov (JIRA)]

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

Pavel Kuznetsov commented on IGNITE-7531:
-

Added NativeStreamerBenchmark
Fixed according to comments
Merged fresh origin/master

[~tledkov-gridgain] , please review

> SQL: Create data load benchmarks
> 
>
> Key: IGNITE-7531
> URL: https://issues.apache.org/jira/browse/IGNITE-7531
> Project: Ignite
>  Issue Type: Task
>  Components: sql, yardstick
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> We need to implement a set of data loading benchmarks to better understand 
> how fast Ignite is able to consume data. This task consists of two steps:
> 1) Extend Yardstick capabilities
> 2) Create set of benchmarks
> 1) Yardstick
> Data load benchmark should be executed in single-shot mode: only one 
> iteration, only total execution time is needed, start callback for setup and 
> warmup, stop callback for cleanup. 
> Currently Yardstick cannot do that, so we need to extend it. Possibly, we can 
> control this through new {{boolean BenchmarkDriver.isSingleShot()}} method.
> 2) Benchmarks 
> At first let's focus on thin JDBC driver. The following cases should be 
> executed:
> 2.1) Normal INSERT
> 2.2) Batched INSERT
> 2.3) Streaming INSERT (when IGNITE-7253 is ready)
> 2.4) P. 1-3 with and without dynamically disabled WAL (ALTER TABLE ... 
> NOLOGGING)
> 2.5) P. 1-3 with additional indexes - either created before data load on 
> empty table, or after load on table with data.



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

[jira] [Commented] (IGNITE-7572) Local cache fails to start on client node

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7572:


[~dkarachentsev], are there any news about this ticket?

> Local cache fails to start on client node
> -
>
> Key: IGNITE-7572
> URL: https://issues.apache.org/jira/browse/IGNITE-7572
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.5
>
>
> Client node doesn't have default configuration for data region and fails to 
> start local cache with the following exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7272)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:232)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:625)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:819)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1041)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 1 more
> Caused by: java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.CacheGroupContext.(CacheGroupContext.java:203)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1971)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:744)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:626)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reproducer:
>  
> {code:java}
> import java.util.Arrays;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.jetbrains.annotations.NotNull;
> public class LocalCache {
> private static int id;
> public static void main(String[] args) throws InterruptedException {
> Ignition.setClientMode(false);
> Ignite server = Ignition.start(getConfiguration());
> System.out.println("Server is up");
> Ignition.setClientMode(true);
> Ignite client = Ignition.start(getConfiguration());
> System.out.println("Client is up");
> }
> @NotNull private static IgniteConfiguration getConfiguration() {
> IgniteConfiguration cfg = new IgniteConfiguration();
> TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder(true);
> finder.setAddresses(Arrays.asList("localhost:47500..47600"));
> cfg.setIgniteInstanceName("test" + id++);
> CacheConfiguration cacheConfiguration = new 
> CacheConfiguration("TEST");
> cacheConfiguration.setCacheMode(CacheMode.LOCAL);
> cfg.setCacheConfiguration(cacheConfiguration);
> cfg.setDiscoverySpi(new TcpDiscoverySpi().setIpFinder(finder));
> return cfg;
> }
> }
> {code}
>  



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

[jira] [Commented] (IGNITE-7881) Add tests for using TreeMap/TreeSet in cache key

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7881:


Please use Run-All for check changes. 1 suite from 98 can't give us 
representative picture of impact of the issue.

> Add tests for using TreeMap/TreeSet in cache key
> 
>
> Key: IGNITE-7881
> URL: https://issues.apache.org/jira/browse/IGNITE-7881
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.5
>
>
> It came to our attention that in Ignite 1.x, [Binary]TreeMap/TreeSet could 
> not be used in cache keys without configuration or code changes, since 
> equality won't work correctly for them.
> It was since fixed by IGNITE-4558, but test cases won't hurt to nail this 
> behaviour fast.



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

[jira] [Commented] (IGNITE-7831) Throw Exceptions instead of AssertionErrors when reading from corrupted persistence

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-7831:
--

[~alex_pl], problems that I encountered and that I'd like to see fixed and 
removed include those you discovered. Making assertions based on ability to 
create directory and throwing explicit AssertionErrors when WAL doesn't have 
enough data to restore page are things that should be fixed.

One of real cases that I encountered quite recently is method 
GridCacheOffheapManager.GridCacheDataStore.getOrAllocatePartitionMetas():
{noformat}
else {
PagePartitionMetaIO io = PageIO.getPageIO(pageAddr);

treeRoot = io.getTreeRoot(pageAddr);
reuseListRoot = io.getReuseListRoot(pageAddr);

assert PageIdUtils.flag(treeRoot) == PageMemory.FLAG_DATA :
U.hexLong(treeRoot) + ", part=" + partId + ", grpId=" + grpId;
assert PageIdUtils.flag(reuseListRoot) == PageMemory.FLAG_DATA :
U.hexLong(reuseListRoot) + ", part=" + partId + ", grpId=" + grpId;
}
{noformat}

Ideally, I'd like to ensure that all assertions for reading data from memory 
pages are properly handled and lead to node invalidation 
(NodeInvalidator.invalidate(...)). Replacing those "assert"s with "throw"s 
might be inconvenient and make code less readable, but making sure that they 
are caught, processed and re-thrown will be beneficial.

> Throw Exceptions instead of AssertionErrors when reading from corrupted 
> persistence
> ---
>
> Key: IGNITE-7831
> URL: https://issues.apache.org/jira/browse/IGNITE-7831
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ilya Lantukh
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: iep-14
> Fix For: 2.5
>
>
> There are a few places in our code where we explicitly throw AssertionErrors 
> due to inability to correctly read data from persistence and many more places 
> where we make assertions based on read values.
> Assertions are used to indicate problems in internal logic, while persistence 
> might also get corrupted by various external reasons. It also makes uniform 
> handling of such issues considerably harder, because exception handling logic 
> in Ignite ignores Errors. If we want to improve stability and minimize 
> consequenses of pesistence corruption, we should replace all those 
> AssertionErrors and asserts with Exceptions, so that current exception 
> handling mechanisms could be reduce. In a number of situations it means that 
> instead of causing cluster-wide hang-up problematic node will be 
> automatically killed.



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

[jira] [Commented] (IGNITE-7882) Atomic update requests should always use topology mappings instead of affinity

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7882:


GitHub user Jokser opened a pull request:

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

IGNITE-7882 Always use topology mapping for atomic updates.



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

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

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

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


commit 1418d83df435f5b5418b97e990365be2504d16d1
Author: Pavel Kovalenko 
Date:   2018-03-05T13:50:00Z

IGNITE-7882 Always use topology mapping for atomic updates.




> Atomic update requests should always use topology mappings instead of affinity
> --
>
> Key: IGNITE-7882
> URL: https://issues.apache.org/jira/browse/IGNITE-7882
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
>
> Currently for mapping cache atomic updates we can use two ways:
> 1) Use nodes reporting status OWNING for partition where we send the update.
> 2) Use only affinity nodes mapping if rebalance is finished.
> Using the second way we may route update request only to affinity node, while 
> there is also node which is still owner and can process read requests.
> It can lead to reading null values for some key, while update for such key 
> was successful a moment ago.



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

[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7718:


Hi [~pvinokurov], I've checked tests run. It seems it is OK now.

But code style has a lot of improvement proposals. I left comments in PR

Could you please install code style from Ignite source code. Also you can 
consult with other Igniters about code style.

Make sure you covered 
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines


> Collections.singleton() and Collections.singletonMap() are not properly 
> serialized by binary marshaller
> ---
>
> Key: IGNITE-7718
> URL: https://issues.apache.org/jira/browse/IGNITE-7718
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Pavel Vinokurov
>Assignee: Pavel Vinokurov
>Priority: Major
>
> After desialization collections obtained by Collections.singleton() and  
> Collections.singletonMap() does not return collection of binary objects, but 
> rather collection of deserialized objects. 



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

[jira] [Created] (IGNITE-7882) Atomic update requests should always use topology mappings instead of affinity

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7882:
---

 Summary: Atomic update requests should always use topology 
mappings instead of affinity
 Key: IGNITE-7882
 URL: https://issues.apache.org/jira/browse/IGNITE-7882
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko


Currently for mapping cache atomic updates we can use two ways:
1) Use nodes reporting status OWNING for partition where we send the update.
2) Use only affinity nodes mapping if rebalance is finished.

Using the second way we may route update request only to affinity node, while 
there is also node which is still owner and can process read requests.

It can lead to reading null values for some key, while update for such key was 
successful a moment ago.



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

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

[Akmal Chaudhri (JIRA)]

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

Akmal Chaudhri commented on IGNITE-7655:


[~NIzhikov], i think everything is done. I have converted the Scala programs to 
Java. I have added the code snippets to the documentation. I have added a very 
small section about SparkSession to the documentation. It needs [~dmagda] to 
review all this now.

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



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

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7851:
--

[~ptupitsyn] Could you please review as well

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32 
> stackTraceCharsLen, Void* errData, Int32 errDataLen)
>

[jira] [Resolved] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[Alexey Popov (JIRA)]

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

Alexey Popov resolved IGNITE-7851.
--
Resolution: Fixed

> .NET: linq query throws "Hexadecimal string with odd number of characters" 
> exception
> 
>
> Key: IGNITE-7851
> URL: https://issues.apache.org/jira/browse/IGNITE-7851
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, sql
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Major
> Attachments: FirstOrDefaultKeyIssue.zip
>
>
> Simple linq query with .Key throws an exception
> {code}
> var models = cache.AsCacheQueryable();
> var entry = models.FirstOrDefault(m => m.Key == @"TST-1/1");
> {code}
> Apache.Ignite.Core.Common.IgniteException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195] ---> 
> Apache.Ignite.Core.Common.JavaException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.platform.utils.PlatformUtils.unwrapQueryException(PlatformUtils.java:519)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1240)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:877)
> at 
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1917)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:368)
> at 
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1234)
> ... 2 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Hexadecimal string 
> with odd number of characters: "TST-1/1" [90003-195]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2468)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> ... 5 more
> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of 
> characters: "TST-1/1" [90003-195]
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at 
> org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:262)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.bindPartitionInfoParameter(IgniteH2Indexing.java:2520)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.calculateQueryPartitions(IgniteH2Indexing.java:2480)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeTwoStepsQuery(IgniteH2Indexing.java:1556)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1500)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> ... 6 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "TST-1/1" [90003-195]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 19 more
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
> target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
> errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32 
> stackTraceCharsLen, Void* errData, Int32 errDataLen)
>at 
> 

[jira] [Updated] (IGNITE-7770) Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 removal

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-7770:

Fix Version/s: 2.5

> Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 
> removal
> 
>
> Key: IGNITE-7770
> URL: https://issues.apache.org/jira/browse/IGNITE-7770
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.5
>
>
> Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 
> removal
> After appying IGNITE-7518 Get rid of org.jsr166.LongAdder8, 
>  IgniteCacheTestSuite6: 
> TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations (fail rate 
> 38,6%) 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3733584033131292028=%3Cdefault%3E=testDetails



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

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

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-6083 at 3/5/18 12:11 PM:
---

[~agoncharuk] Hi!

 

I've fixed test, checked failed tests in TC run and now its ok, plz review it : 
[new TC 
run|https://ci.ignite.apache.org/viewLog.html?buildId=1125362=buildResultsDiv=IgniteTests24Java8_RunAll]


was (Author: alexey kuznetsov):
[~agoncharuk] Hi!

 

I've fixed test, checked failed tests in TC run and now its ok, plz review it : 
[new TC 
run|https://ci.ignite.apache.org/viewQueued.html?itemId=1118525=queuedBuildOverviewTab]

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



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

[jira] [Commented] (IGNITE-7881) Add tests for using TreeMap/TreeSet in cache key

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7881:


GitHub user alamar opened a pull request:

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

IGNITE-7881 Tests for using TreeMap or TreeSet as cache key.



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

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

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

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


commit 567d2007b69884f0448115fd88733e8f9aba0534
Author: Ilya Kasnacheev 
Date:   2018-03-05T12:06:51Z

IGNITE-7881 Tests for using TreeMap or TreeSet as cache key.




> Add tests for using TreeMap/TreeSet in cache key
> 
>
> Key: IGNITE-7881
> URL: https://issues.apache.org/jira/browse/IGNITE-7881
> Project: Ignite
>  Issue Type: Task
>  Components: binary, cache
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.5
>
>
> It came to our attention that in Ignite 1.x, [Binary]TreeMap/TreeSet could 
> not be used in cache keys without configuration or code changes, since 
> equality won't work correctly for them.
> It was since fixed by IGNITE-4558, but test cases won't hurt to nail this 
> behaviour fast.



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

[jira] [Commented] (IGNITE-7844) Transaction incorrect state after client reconnected

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-7844:
--

[~northdragon] , plz review the ticket

> Transaction incorrect state after client reconnected
> 
>
> Key: IGNITE-7844
> URL: https://issues.apache.org/jira/browse/IGNITE-7844
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Transaction is started on client node.
>  Client reconnects, transaction rollbacks, but its state is left ACTIVE, 
> which is incorrect.



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

[jira] [Created] (IGNITE-7881) Add tests for using TreeMap/TreeSet in cache key

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-7881:
---

 Summary: Add tests for using TreeMap/TreeSet in cache key
 Key: IGNITE-7881
 URL: https://issues.apache.org/jira/browse/IGNITE-7881
 Project: Ignite
  Issue Type: Task
  Components: binary, cache
Affects Versions: 2.3
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev
 Fix For: 2.5


It came to our attention that in Ignite 1.x, [Binary]TreeMap/TreeSet could not 
be used in cache keys without configuration or code changes, since equality 
won't work correctly for them.

It was since fixed by IGNITE-4558, but test cases won't hurt to nail this 
behaviour fast.



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

[jira] [Commented] (IGNITE-7860) JDBC thin driver: set default socket buffer sizes to greater value

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-7860:
--

[~vozerov], please review the simple patch.
JDBC tests are OK.

> JDBC thin driver: set default socket buffer sizes to greater value
> --
>
> Key: IGNITE-7860
> URL: https://issues.apache.org/jira/browse/IGNITE-7860
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.3, 2.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> Currently they are set to zero, meaning that OS will use it's default. But 
> tyically these defaults are too pessimistic. Let's set them to 64Kb.



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

[jira] [Assigned] (IGNITE-7459) Web console: do not show result title until query end

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-7459:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Commented] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-7809:
--

After fixing those tests I still observe flaky fails and hang-ups on TC due to 
problems, unrelated to the initial one.
Also, they fail locally on my PC with the following exception:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to initialize WAL 
segment: 
C:\Projects\ignite\work\db\wal\node00-3bc7e86d-8f7d-4930-b5ea-337ceadeb2da\0006.wal
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:320)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$RecordsIterator.initReadHandle(FsyncModeFileWriteAheadLogManager.java:2972)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$RecordsIterator.advanceSegment(FsyncModeFileWriteAheadLogManager.java:3073)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:155)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:112)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:46)
at 
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2173)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1394)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1141)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1120)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:706)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.FileSystemException: 
C:\Projects\ignite\work\db\wal\node00-3bc7e86d-8f7d-4930-b5ea-337ceadeb2da\0006.wal:
 The process cannot access the file because it is being used by another process.

at 
sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at 
sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:90)
at 
sun.nio.fs.WindowsChannelFactory.newAsynchronousFileChannel(WindowsChannelFactory.java:202)
at 
sun.nio.fs.WindowsFileSystemProvider.newAsynchronousFileChannel(WindowsFileSystemProvider.java:140)
at 
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
at 
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:265)
... 14 more
{noformat}
It seems to be Windows-specific problem (I run it on Windows 10).

> Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
> IgniteWalFlushDefaultSelfTest
> 
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
>Ignite PDS 2 (Direct IO) [ tests 2 ]  
>  IgnitePdsNativeIoTestSuite2: 

[jira] [Commented] (IGNITE-7077) Spark Data Frame Support. Strategy to convert complete query to Ignite SQL

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7077:
-

Hello [~vkulichenko]. Did you have a chance to look at my PR?

> Spark Data Frame Support. Strategy to convert complete query to Ignite SQL
> --
>
> Key: IGNITE-7077
> URL: https://issues.apache.org/jira/browse/IGNITE-7077
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: bigdata
> Fix For: 2.5
>
>
> Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084.
> We need to implement custom spark strategy that can convert whole Spark SQL 
> query to Ignite SQL Query if query consists of only Ignite tables.
> The strategy does nothing if spark query includes not only Ignite tables.
> Memsql implementation can be taken as an example - 
> https://github.com/memsql/memsql-spark-connector



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

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

[Roman Guseinov (JIRA)]

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

Roman Guseinov commented on IGNITE-7774:


Sounds good. Thanks

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

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

[Peter Ivanov (JIRA)]

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

Peter Ivanov commented on IGNITE-7774:
--

Sorry, not yet, but this task is next in my list.

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

[jira] [Assigned] (IGNITE-7880) Enum values not shown correctly in Webconsole

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7880:


Assignee: Alexey Kuznetsov  (was: Mikhail Cherkasov)

> Enum values not shown correctly in Webconsole
> -
>
> Key: IGNITE-7880
> URL: https://issues.apache.org/jira/browse/IGNITE-7880
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
> Attachments: image-2018-03-05-13-34-48-992.png
>
>
> Enum values not shown correctly in Webconsole:
>  
> {code:java}
> public enum SomeEnum { ONE, TWO; }{code}
>  
> !image-2018-03-05-13-34-48-992.png!
>  
> expecting value:
> enum value as String like: ONE



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

[jira] [Updated] (IGNITE-7880) Enum values not shown correctly in Webconsole

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7880:
--
Description: 
Enum values not shown correctly in Webconsole:

 
{code:java}
public enum SomeEnum { ONE, TWO; }{code}
 

!image-2018-03-05-13-34-48-992.png!

 

expecting value:

enum value as String like: ONE

  was:
Enum values not shown correctly in Webconsole:

!image-2018-03-05-13-34-48-992.png!


> Enum values not shown correctly in Webconsole
> -
>
> Key: IGNITE-7880
> URL: https://issues.apache.org/jira/browse/IGNITE-7880
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
> Attachments: image-2018-03-05-13-34-48-992.png
>
>
> Enum values not shown correctly in Webconsole:
>  
> {code:java}
> public enum SomeEnum { ONE, TWO; }{code}
>  
> !image-2018-03-05-13-34-48-992.png!
>  
> expecting value:
> enum value as String like: ONE



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

[jira] [Created] (IGNITE-7880) Enum values not shown correctly in Webconsole

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7880:
-

 Summary: Enum values not shown correctly in Webconsole
 Key: IGNITE-7880
 URL: https://issues.apache.org/jira/browse/IGNITE-7880
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
Assignee: Mikhail Cherkasov
 Fix For: 2.5
 Attachments: image-2018-03-05-13-34-48-992.png

Enum values not shown correctly in Webconsole:

!image-2018-03-05-13-34-48-992.png!



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

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

[Roman Guseinov (JIRA)]

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

Roman Guseinov commented on IGNITE-7774:


[~vveider] , did you have the chance to take a look at the PR?

Please let me know if you have any questions.

Thanks.

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

[jira] [Updated] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-3653:
---
Fix Version/s: 2.5

> P2P doesn't work for remote filter and filter factory.
> --
>
> Key: IGNITE-3653
> URL: https://issues.apache.org/jira/browse/IGNITE-3653
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Nikolay Tikhonov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: CCP2PTest.patch
>
>
> Remote filter and filter factory classes were not deployed on nodes which 
> join to cluster after their initialization. Test attached.



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

[jira] [Updated] (IGNITE-7844) Transaction incorrect state after client reconnected

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-7844:
---
Affects Version/s: 2.3

> Transaction incorrect state after client reconnected
> 
>
> Key: IGNITE-7844
> URL: https://issues.apache.org/jira/browse/IGNITE-7844
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Transaction is started on client node.
>  Client reconnects, transaction rollbacks, but its state is left ACTIVE, 
> which is incorrect.



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

[jira] [Updated] (IGNITE-7844) Transaction incorrect state after client reconnected

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-7844:
---
Fix Version/s: 2.5

> Transaction incorrect state after client reconnected
> 
>
> Key: IGNITE-7844
> URL: https://issues.apache.org/jira/browse/IGNITE-7844
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> Transaction is started on client node.
>  Client reconnects, transaction rollbacks, but its state is left ACTIVE, 
> which is incorrect.



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

[jira] [Assigned] (IGNITE-7784) Remove unnessary dependencies from WC front-end

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-7784:
-

Assignee: Alexey Kuznetsov  (was: Alexander Kalinin)

Removed extra dev depencies from frontend. Please reviiew.

> Remove unnessary dependencies from WC front-end
> ---
>
> Key: IGNITE-7784
> URL: https://issues.apache.org/jira/browse/IGNITE-7784
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexander Kalinin
>Assignee: Alexey Kuznetsov
>Priority: Minor
>
> There are some lageacy modules in packages.json (Like phantom.js). These 
> should be deleted.
>  



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

[jira] [Commented] (IGNITE-7860) JDBC thin driver: set default socket buffer sizes to greater value

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7860:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-7860 JDBC thin driver: set default socket buffer sizes to 64Kb



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

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

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

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


commit bd9d6dccc6c176376b2ea629f952f2ff7937f2cd
Author: tledkov-gridgain 
Date:   2018-03-05T09:24:17Z

IGNITE-7860 JDBC thin driver: set default socket buffer sizes to 64Kb




> JDBC thin driver: set default socket buffer sizes to greater value
> --
>
> Key: IGNITE-7860
> URL: https://issues.apache.org/jira/browse/IGNITE-7860
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.3, 2.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> Currently they are set to zero, meaning that OS will use it's default. But 
> tyically these defaults are too pessimistic. Let's set them to 64Kb.



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

[jira] [Updated] (IGNITE-1553) Optimize transaction prepare step when store is enabled

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-1553:
---
Fix Version/s: 2.5

> Optimize transaction prepare step when store is enabled
> ---
>
> Key: IGNITE-1553
> URL: https://issues.apache.org/jira/browse/IGNITE-1553
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
>Priority: Major
>  Labels: important
> Fix For: 2.5
>
>
> Currently entries are enlisted in a database transaction after grid 
> transaction is in PREPARED state. We can do this in parallel in the following 
> fashion (pseudo-code):
> {code}
> fut = tx.prepareAsync();
> db.write(tx.writes());
> fut.get();
> try {
> db.commit();
> 
> tx.commit();
> }
> catch (Exception e) {
> tx.rollback();
> }
> {code}
> If this approach is applied, we should be able to reduce latency for 
> transactions when write-through is enabled.



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

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

[Sergey Stronchinskiy (JIRA)]

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

Sergey Stronchinskiy edited comment on IGNITE-5298 at 3/5/18 8:50 AM:
--

Hi, [~ptupitsyn] 

Can you review this?

[Platform 
tests|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNet_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]

[Inspections|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNetInspections_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]


was (Author: gurustron):
Hi, [~ptupitsyn],

 

Can you review this?

[Platform 
tests|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNet_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]

[Inspections|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNetInspections_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]

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



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

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

[Sergey Stronchinskiy (JIRA)]

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

Sergey Stronchinskiy reassigned IGNITE-5298:


Assignee: Pavel Tupitsyn  (was: Sergey Stronchinskiy)

Hi, [~ptupitsyn],

 

Can you review this?

[Platform 
tests|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNet_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]

[Inspections|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNetInspections_IgniteTests24Java8=pull%2F3599%2Fmerge=buildTypeStatusDiv]

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



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

[jira] [Assigned] (IGNITE-7847) Increase of total owning partition count after rebalance

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin reassigned IGNITE-7847:
--

Assignee: Dmitriy Govorukhin  (was: Alexey Goncharuk)

> Increase of total owning partition count after rebalance
> 
>
> Key: IGNITE-7847
> URL: https://issues.apache.org/jira/browse/IGNITE-7847
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.5
>
>
> 1) Start 3 nodes with persistence enabled
> 2) Activate grid
> 3) Create cache with 1 backup and remember owning partition count on node1
> 4) Stop node2, set BLT and note that local owning partitions on node1 
> increased (to total number of partitions on cache)
> 5) Start node, set BLT and waitRebalance and
> Expected: owning partitions count on node1 became as on step 3
> Actual: owning partitions count on node1 still equals to step 4 value



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

[jira] [Commented] (IGNITE-7756) Streamer fails if IgniteUuid is indexed

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-7756:
-

Hello, [~dpavlov]

I've added compatibility test to check my fix.

Test  - 
https://github.com/apache/ignite/pull/3550/files#diff-9b47c7d5ffc479e86afa207ca319d437
TC - https://ci.ignite.apache.org/viewLog.html?buildId=1125267

So, it seems we are ready to merge the fix. Please, take a look.

> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is 
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer: 
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false, 
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to 
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1, 
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class 
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed 
> [node=57961924-82ec-4d56-81eb-1a4109a0]
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial 
> value for cache entry
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update 
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid, 
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1343)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
>   at 
>