[jira] [Closed] (IGNITE-4995) Web Console: Multi-cluster support

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-4995.


> Web Console: Multi-cluster support
> --
>
> Key: IGNITE-4995
> URL: https://issues.apache.org/jira/browse/IGNITE-4995
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> There should be an ability to connect to several clusters from one Web 
> Console interfaces managing and monitoring them from there.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5008) Page Memory Throws Meaningless OOM exception if there is an issue in config

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5008:
---

 Summary: Page Memory Throws Meaningless OOM exception if there is 
an issue in config
 Key: IGNITE-5008
 URL: https://issues.apache.org/jira/browse/IGNITE-5008
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Sergey Chugunov
Priority: Blocker


The ticket was created as a result of this discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Memory-policies-examples-fails-td16717.html

Presently a page memory can throw an OOM exception due to a misconfiguration. 
The message of the exception has to point out to a problematic place directly 
(size, ect.) so that the user can quickly fix it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5007) Clarify some parameters of MemoryConfiguration and MemoryPolicyConfiguration

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5007:
---

 Summary: Clarify some parameters of MemoryConfiguration and 
MemoryPolicyConfiguration
 Key: IGNITE-5007
 URL: https://issues.apache.org/jira/browse/IGNITE-5007
 Project: Ignite
  Issue Type: Sub-task
Reporter: Denis Magda
Assignee: Alexey Goncharuk
Priority: Blocker


Alex, please look for TODOs in the javadoc of {{MemoryConfiguration}} and 
{{MemoryPolicyConfiguratino}} files. Once your provide more information for the 
marked parameters assign the ticket back to me.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4961) Document Page Memory API, Architecture and Behavior

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4961:
-

[~agoncharuk], as a page memory architect, please do a primary review of the 
documentation. 

> Document Page Memory API, Architecture and Behavior
> ---
>
> Key: IGNITE-4961
> URL: https://issues.apache.org/jira/browse/IGNITE-4961
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.0
>
>
> The goal of this ticket is to provide extensive documentation around the new 
> page memory architecture introduced in Apache Ignite 2.0.
> Refer to IGNITE-3477 and do the following as a part of this ticket:
> * page memory architecture, advantages, and usage.
> * page memory policies (IGNITE-4960).
> * rework or discontinue Off-Heap Memory page 
> (https://apacheignite.readme.io/docs/off-heap-memory) that lists all the 
> memory tiers supported in versions 1.x. For instance, the swap space is no 
> longer available (IGNITE-4736) and the Java heap is no more a default one and 
> used just as a cache of the page memory (IGNITE-4535).
> Once the Java documentation is ready, assign the ticket to [~ptupitsyn] and 
> [~isapego] who will create .NET and C++ counterparts following a Java 
> template.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4961) Document Page Memory API, Architecture and Behavior

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-4961:
---

Assignee: Alexey Goncharuk  (was: Denis Magda)

> Document Page Memory API, Architecture and Behavior
> ---
>
> Key: IGNITE-4961
> URL: https://issues.apache.org/jira/browse/IGNITE-4961
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.0
>
>
> The goal of this ticket is to provide extensive documentation around the new 
> page memory architecture introduced in Apache Ignite 2.0.
> Refer to IGNITE-3477 and do the following as a part of this ticket:
> * page memory architecture, advantages, and usage.
> * page memory policies (IGNITE-4960).
> * rework or discontinue Off-Heap Memory page 
> (https://apacheignite.readme.io/docs/off-heap-memory) that lists all the 
> memory tiers supported in versions 1.x. For instance, the swap space is no 
> longer available (IGNITE-4736) and the Java heap is no more a default one and 
> used just as a cache of the page memory (IGNITE-4535).
> Once the Java documentation is ready, assign the ticket to [~ptupitsyn] and 
> [~isapego] who will create .NET and C++ counterparts following a Java 
> template.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Denis Magda (JIRA)]

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

Denis Magda edited comment on IGNITE-5000 at 4/17/17 5:17 PM:
--

[~avinogradov], the maven profile has to be renamed from {{math}} to {{ml}}. 
[~chief], consider this in the next pull-request.


was (Author: dmagda):
[~avinogradov], the maven profile has to be renamed from {{math}} to {{ml}}.

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5000:
-

[~avinogradov], the maven profile has to be renamed from {{math}} to {{ml}}.

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5000:
-

[~chief], the default package has to be renamed as well from 
{{org.apache.ignite.math}} to {{org.apache.ignite.ml}}. If needed under 
{{org.apache.ignite.ml}} you can have {{org.apache.ignite.ml.math}}. Do this 
for ML sources, tests and examples whenever applicable. If you're aware of 
other places that have to be renamed from {{math}} to {{ml}} then please do 
this in advance.

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Denis Magda (JIRA)]

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

Denis Magda reopened IGNITE-5000:
-

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-3488:
-
Description: 
Need to create a list of all the affected components.

2.0 migration guide has to be updated: 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide

Check REST API and update documentation (cacheName becomes mandatory)

  was:
Need to create a list of all the affected components.

2.0 migration guide has to be updated: 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide


> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
> Check REST API and update documentation (cacheName becomes mandatory)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4501) Improvement of connection in a cluster of new node

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-4501:
-

[~yzhdanov],

I can't find the best way. I can send message across the ring more times, but 
it's not optimal. Or I can send the message to coordinator in the first place 
and skip new node, after reaching the coordinator in second time I can send 
message from coordinator to new node, and finally send the message to 
coordinator in third time. But it's too complex change.

What do you think?

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4964) Document Machine Learning Grid (Distributed Algebra Implementation)

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-4964:
---
Attachment: ignite-ml.readme-io.txt

(i) I haven't yet got permission to edit at readme.io - attaching first version 
of preliminary doc draft as a plain text here: [^ignite-ml.readme-io.txt]

> Document Machine Learning Grid (Distributed Algebra Implementation)
> ---
>
> Key: IGNITE-4964
> URL: https://issues.apache.org/jira/browse/IGNITE-4964
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Nikita Ivanov
> Fix For: 2.0
>
> Attachments: ignite-ml.readme-io.txt
>
>
> In Apache Ignite 2.0 we introduce support for distributed algebra on top of 
> Ignite. This considered to be a foundation of Ignite's Machine Learning 
> framework discussed here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-td13936.html
> Let's make an overview of the current implementation, its usage, and refer to 
> developed examples as a part of the readme.io documentation. Here is an 
> invisible page created for this purpose:
> https://dash.readme.io/project/apacheignite/v1.9/docs/distributed-algebra
> Please assign the ticket on [~dmagda] for the final review.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

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

Yury Babak commented on IGNITE-5000:


[~avinogradov], could you please review this pull request?
https://github.com/apache/ignite/pull/1811

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5006) .NET: SQL does not work with F# record types

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5006:
---
Description: 
The following code returns null results:

{code}
type Person = 
{ 
[]
id : int; 
[]
name : String 
}

...

cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
{code}

F# record fields have {{@}} symbol in the end. We should clean up or escape 
these.

{{Person [idHash=59332389, id@=1, name@=John]}}

Make sure other F#-specific types do not cause problems (tuples, structs, 
classes, nested types).

  was:
The following code returns null results:

{code}
type Person = 
{ 
[]
id : int; 
[]
name : String 
}

...

cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
{code}

F# record fields have {{@}} symbol in the end. We should clean up or escape 
these.

{{Person [idHash=59332389, id@=1, name@=John]}}

Make sure other F#-specific types do not cause problems (tuples, structs, 
classes).


> .NET: SQL does not work with F# record types
> 
>
> Key: IGNITE-5006
> URL: https://issues.apache.org/jira/browse/IGNITE-5006
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> The following code returns null results:
> {code}
> type Person = 
> { 
> []
> id : int; 
> []
> name : String 
> }
> ...
> cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
> {code}
> F# record fields have {{@}} symbol in the end. We should clean up or escape 
> these.
> {{Person [idHash=59332389, id@=1, name@=John]}}
> Make sure other F#-specific types do not cause problems (tuples, structs, 
> classes, nested types).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5006) .NET: SQL does not work with F# record types

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5006:
---
Description: 
The following code returns null results:

{code}
type Person = 
{ 
[]
id : int; 
[]
name : String 
}

...

cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
{code}

F# record fields have {{@}} symbol in the end. We should clean up or escape 
these.

{{Person [idHash=59332389, id@=1, name@=John]}}

Make sure other F#-specific types do not cause problems (tuples, structs, 
classes).

  was:
The following code returns null results:

{code}
type Person = 
{ 
[]
id : int; 
[]
name : String 
}

...

cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
{code}

F# record fields have {{@}} symbol in the end. We should clean up or escape 
these.

{{Person [idHash=59332389, id@=1, name@=John]}}


> .NET: SQL does not work with F# record types
> 
>
> Key: IGNITE-5006
> URL: https://issues.apache.org/jira/browse/IGNITE-5006
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> The following code returns null results:
> {code}
> type Person = 
> { 
> []
> id : int; 
> []
> name : String 
> }
> ...
> cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
> {code}
> F# record fields have {{@}} symbol in the end. We should clean up or escape 
> these.
> {{Person [idHash=59332389, id@=1, name@=John]}}
> Make sure other F#-specific types do not cause problems (tuples, structs, 
> classes).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

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

Yury Babak reassigned IGNITE-5000:
--

Assignee: Yury Babak  (was: Anton Vinogradov)

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

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

Yury Babak reassigned IGNITE-5000:
--

Assignee: Anton Vinogradov  (was: Yury Babak)

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Anton Vinogradov
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5006) .NET: SQL does not work with F# record types

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5006:
--

 Summary: .NET: SQL does not work with F# record types
 Key: IGNITE-5006
 URL: https://issues.apache.org/jira/browse/IGNITE-5006
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


The following code returns null results:

{code}
type Person = 
{ 
[]
id : int; 
[]
name : String 
}

...

cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()
{code}

F# record fields have {{@}} symbol in the end. We should clean up or escape 
these.

{{cache.QueryFields(new SqlFieldsQuery("from person select id")).GetAll()}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4944) Web Console: Highlight hovered line in table

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-4944:


Assignee: Dmitriy Shabalin

> Web Console: Highlight hovered line in table
> 
>
> Key: IGNITE-4944
> URL: https://issues.apache.org/jira/browse/IGNITE-4944
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Andrey Novikov
>Assignee: Dmitriy Shabalin
>
> Should work for tables with grouping and pinned columns.
> Hovered line should have color: #ededed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev reassigned IGNITE-4939:
-

Assignee: Evgenii Zhuravlev

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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4936) Web Console: Minor UI fixes for tables.

[Vica Abramova (JIRA)]

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

Vica Abramova commented on IGNITE-4936:
---

2 - see attach
3 - see zeplin
4 - sсrolls need to be transparent and over the tables (without margins)

> Web Console: Minor UI fixes for tables.
> ---
>
> Key: IGNITE-4936
> URL: https://issues.apache.org/jira/browse/IGNITE-4936
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
> Attachments: 2.png
>
>
> We need to finalize the tables:
> # Add icons for actions in table (export, ...)
> # freeze the main column and add the divider to it (with shadow). And scroll 
> the content behind it!
> # redesign the advanced tables (collapsed strokes)
> # improve the scroll behavior



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4936) Web Console: Minor UI fixes for tables.

[Vica Abramova (JIRA)]

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

Vica Abramova reassigned IGNITE-4936:
-

Assignee: Dmitriy Shabalin  (was: Vica Abramova)

> Web Console: Minor UI fixes for tables.
> ---
>
> Key: IGNITE-4936
> URL: https://issues.apache.org/jira/browse/IGNITE-4936
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
> Attachments: 2.png
>
>
> We need to finalize the tables:
> # Add icons for actions in table (export, ...)
> # freeze the main column and add the divider to it (with shadow). And scroll 
> the content behind it!
> # redesign the advanced tables (collapsed strokes)
> # improve the scroll behavior



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4211) Update Spring dependency to latest stable version

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-4211 at 4/17/17 2:41 PM:
---

[~daradurvs]
We should not use synchronized by SpringCache Instance. This will cause 
bottleneck 


was (Author: avinogradov):
[~daradurvs]
We should not use synchronized by SpringCache Instance. This will cause 
starvation.

> Update Spring dependency to latest stable version
> -
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still 
> uses 4.1.0 released two years ago. Could we to update to latest stable 
> version (4.3.4 at the moment)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4936) Web Console: Minor UI fixes for tables.

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-4936:
--
Attachment: 2.png

> Web Console: Minor UI fixes for tables.
> ---
>
> Key: IGNITE-4936
> URL: https://issues.apache.org/jira/browse/IGNITE-4936
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
> Attachments: 2.png
>
>
> We need to finalize the tables:
> # Add icons for actions in table (export, ...)
> # freeze the main column and add the divider to it (with shadow). And scroll 
> the content behind it!
> # redesign the advanced tables (collapsed strokes)
> # improve the scroll behavior



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4669) .NET: Sort binary object fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4669:


Github user asfgit closed the pull request at:

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


> .NET: Sort binary object fields
> ---
>
> Key: IGNITE-4669
> URL: https://issues.apache.org/jira/browse/IGNITE-4669
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Make sure that fields are sorted by name in all cases:
> * Reflective serializer
> * {{IBinarizable}} serialization
> * {{[Serializable]}} serialization
> * Custom serializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4669) .NET: Sort binary object fields

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4669:


Merged to master.

> .NET: Sort binary object fields
> ---
>
> Key: IGNITE-4669
> URL: https://issues.apache.org/jira/browse/IGNITE-4669
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Make sure that fields are sorted by name in all cases:
> * Reflective serializer
> * {{IBinarizable}} serialization
> * {{[Serializable]}} serialization
> * Custom serializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4669) .NET: Sort binary object fields

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4669:
-

[~ptupitsyn], LGTM.

> .NET: Sort binary object fields
> ---
>
> Key: IGNITE-4669
> URL: https://issues.apache.org/jira/browse/IGNITE-4669
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Make sure that fields are sorted by name in all cases:
> * Reflective serializer
> * {{IBinarizable}} serialization
> * {{[Serializable]}} serialization
> * Custom serializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4211:
--

[~daradurvs]
We should not use synchronized by SpringCache Instance. This will cause 
starvation.

> Update Spring dependency to latest stable version
> -
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still 
> uses 4.1.0 released two years ago. Could we to update to latest stable 
> version (4.3.4 at the moment)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4883) Web Console: Fix grouping in tables on Admin Panel Screen

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-4883:
--
Description: 
Tab Countries:
- don't show number on Country column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')
- fix the bug: when user click in the Exclude input and then press Enter btn, 
we do not need to download .csv

Companies Tab:
- don't show number on Company column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')

It is necessary to fix the main column when scrolling:
- Users - user
- Companies - company and user
- Contries - country and user

  was:
Tab Countries:
- don't show number on Country column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')
- fix the bug: when user click in the Exclude input and then press Enter btn, 
we do not need to download .csv

Companies Tab:
- don't show number on Company column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')


> Web Console: Fix grouping in tables on Admin Panel Screen
> -
>
> Key: IGNITE-4883
> URL: https://issues.apache.org/jira/browse/IGNITE-4883
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
>
> Tab Countries:
> - don't show number on Country column
> - by default, do sorting by number of users (descendingly), not by alphabet
> - show only number on User column (delete the title 'total rows')
> - fix the bug: when user click in the Exclude input and then press Enter btn, 
> we do not need to download .csv
> Companies Tab:
> - don't show number on Company column
> - by default, do sorting by number of users (descendingly), not by alphabet
> - show only number on User column (delete the title 'total rows')
> It is necessary to fix the main column when scrolling:
> - Users - user
> - Companies - company and user
> - Contries - country and user



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-4211:


[~avinogradov]
It's not necessary.
I just wanted to make sure that tests results is correct.
Now all nodes are in one JVM, and 'synchronized' block may have an impact on 
test results.

> Update Spring dependency to latest stable version
> -
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still 
> uses 4.1.0 released two years ago. Could we to update to latest stable 
> version (4.3.4 at the moment)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5005) WriteBehindStore - split flusher's to different classes by writeCoalescing

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5005:


 Summary: WriteBehindStore - split flusher's to different classes 
by writeCoalescing
 Key: IGNITE-5005
 URL: https://issues.apache.org/jira/browse/IGNITE-5005
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Belyak


In GridCacheWriteBehindStore.Flusher too many if statements, because its  
behavior depends of writeCoalescing flag too much. Need to split this class 
into two different (with one abstract base Flusher class).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4211:
--

[~daradurvs]

Is there any reason to start new grid at another JVM?


> Update Spring dependency to latest stable version
> -
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still 
> uses 4.1.0 released two years ago. Could we to update to latest stable 
> version (4.3.4 at the moment)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-5000:
---
Description: 
We want to rename math module to ml(machine learning) because it's a main 
planned functionality for this module.

Update: also we want to extract math related examples to separate source 
folder/profile for tests convenience.

  was:We want to rename math module to ml(machine learning) because it's a main 
planned functionality for this module.


> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5004) GridCacheWriteBegindStore - remove StatefulValue

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5004:


 Summary: GridCacheWriteBegindStore - remove StatefulValue
 Key: IGNITE-5004
 URL: https://issues.apache.org/jira/browse/IGNITE-5004
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.9
Reporter: Alexander Belyak


If writeCoalescing=false - GridCacheWriteBehindStore doesn't need to create 
StatefulValue for each KV entry. Need to implement WBStore without this wrapper 
at all (if it is possible to solve ABA problem in cacheMap's) or with thinner 
wrapper without unnecesarry syncronizations/state.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-3488:
--

I've merged the brunch with current master (lots of conflicts) and rerun tests 
after changes, waiting for results.

> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5001:
---
Fix Version/s: (was: 2.0.1)
   2.1

> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Fix For: 2.1
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node 
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5001:
---
Fix Version/s: (was: 2.0)
   2.0.1

> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Fix For: 2.1
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node 
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5003) Parallel write same key in CacheWriteBehindStore

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5003:


 Summary: Parallel write same key in CacheWriteBehindStore
 Key: IGNITE-5003
 URL: https://issues.apache.org/jira/browse/IGNITE-5003
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.9
Reporter: Alexander Belyak


Now GridCacheWriteBehindStore.updateCache wait for writeLock in StatefulValue 
and, moreover, waitForFlush() if value is in pending (flushing) state. We need 
to remove waiting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5002) fix tests in master

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-5002:
---

done minor fix in IgniteServiceDynamicCachesSelfTest

> fix tests in master
> ---
>
> Key: IGNITE-5002
> URL: https://issues.apache.org/jira/browse/IGNITE-5002
> Project: Ignite
>  Issue Type: Task
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov updated IGNITE-4982:
--
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-5002

> GridCacheAbstractRemoveFailureTest fail
> ---
>
> Key: IGNITE-4982
> URL: https://issues.apache.org/jira/browse/IGNITE-4982
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.0
>
>
> GridCacheAbstractRemoveFailureTest (and some child tests) fails. Reproducer:
> {code:java}
> import java.util.Collection;
> import java.util.HashSet;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.CyclicBarrier;
> import java.util.concurrent.ThreadLocalRandom;
> import java.util.concurrent.TimeUnit;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicBoolean;
> import java.util.concurrent.atomic.AtomicLong;
> import java.util.concurrent.atomic.AtomicReference;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.IgniteTransactions;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.NearCacheConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.cluster.ClusterTopologyCheckedException;
> import org.apache.ignite.internal.util.lang.GridTuple;
> import org.apache.ignite.internal.util.typedef.F;
> import org.apache.ignite.internal.util.typedef.T2;
> import org.apache.ignite.internal.util.typedef.X;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import org.jsr166.ConcurrentHashMap8;
> import static 
> org.apache.ignite.IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.SERIALIZABLE;
> /**
>  * Tests that removes are not lost when topology changes.
>  */
> public abstract class GridCacheAbstractRemoveFailureTest extends 
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** Keys count. */
> private static final int KEYS_CNT = 10_000;
> /** Test duration. */
> private static final long DUR = 90 * 1000L;
> /** Cache data assert frequency. */
> private static final long ASSERT_FREQ = 10_000;
> /** Kill delay. */
> private static final T2 KILL_DELAY = new T2<>(2000, 
> 5000);
> /** Start delay. */
> private static final T2 START_DELAY = new T2<>(2000, 
> 5000);
> /** */
> private static String sizePropVal;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> 
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER).setForceServerMode(true);
> if (testClientNode() && 
> getTestIgniteInstanceName(0).equals(igniteInstanceName))
> cfg.setClientMode(true);
> 
> ((TcpCommunicationSpi)cfg.getCommunicationSpi()).setSharedMemoryPort(-1);
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void beforeTestsStarted() throws Exception {
> // Need to increase value set 

[jira] [Created] (IGNITE-5002) fix tests in master

[Konstantin Dudkov (JIRA)]

Konstantin Dudkov created IGNITE-5002:
-

 Summary: fix tests in master
 Key: IGNITE-5002
 URL: https://issues.apache.org/jira/browse/IGNITE-5002
 Project: Ignite
  Issue Type: Task
Reporter: Konstantin Dudkov
Assignee: Konstantin Dudkov






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5001:
---
Description: 
* Use {{GetTestConfiguration}} where possible
* Make sure {{Localhost}} is set in all other cases to avoid external node 
discovery
* Remove binary type configuration where it is not necessary
* Get rid of Spring XML where it is not needed (Events, Messaging, etc)

> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Priority: Trivial
> Fix For: 2.0
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node 
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5001) .NET: Tests cleanup

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5001:
--

 Summary: .NET: Tests cleanup
 Key: IGNITE-5001
 URL: https://issues.apache.org/jira/browse/IGNITE-5001
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Priority: Trivial
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4587) Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4587:


Github user asfgit closed the pull request at:

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


> Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
> ---
>
> Key: IGNITE-4587
> URL: https://issues.apache.org/jira/browse/IGNITE-4587
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Fix For: 2.0
>
>
> {{CacheAtomicWriteOrderMode.CLOCK}} proved to be harmful in production due to 
> timing issues.
> It makes sense to remove it completely in 2.0 release. Migration guide has be 
> updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4995) Web Console: Multi-cluster support

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-4995:


Hi [~kuaw26],
I reviewed you changes, looks good for me. But i found that querySql task was 
modified in master, please add to UI.

> Web Console: Multi-cluster support
> --
>
> Key: IGNITE-4995
> URL: https://issues.apache.org/jira/browse/IGNITE-4995
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.0
>
>
> There should be an ability to connect to several clusters from one Web 
> Console interfaces managing and monitoring them from there.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4995) Web Console: Multi-cluster support

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-4995:
--

Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console: Multi-cluster support
> --
>
> Key: IGNITE-4995
> URL: https://issues.apache.org/jira/browse/IGNITE-4995
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> There should be an ability to connect to several clusters from one Web 
> Console interfaces managing and monitoring them from there.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4998) Add more dynamic indexing tests for various cache modes

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-4998:
-

Patch available: https://github.com/apache/ignite/pull/1809

> Add more dynamic indexing tests for various cache modes
> ---
>
> Key: IGNITE-4998
> URL: https://issues.apache.org/jira/browse/IGNITE-4998
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5000:
--

 Summary: Rename Ignite Math module to Ignite ML module
 Key: IGNITE-5000
 URL: https://issues.apache.org/jira/browse/IGNITE-5000
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.0
Reporter: Yury Babak
Assignee: Yury Babak
 Fix For: 2.0


We want to rename math module to ml(machine learning) because it's a main 
planned functionality for this module.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4999) Use one thread pool to flush all CacheWriteBehindStore

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-4999:


 Summary: Use one thread pool to flush all CacheWriteBehindStore
 Key: IGNITE-4999
 URL: https://issues.apache.org/jira/browse/IGNITE-4999
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.9
Reporter: Alexander Belyak


For now we have flusher threads for each CacheWriteBehindStore so we can't 
create many caches with this mechanism (too many threads).
We should use single thread pool for all CacheWriteBehindStore instances (as 
for TTL).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4982:
---

[TC 
tests|http://ci.ignite.apache.org/project.html?projectId=IgniteTests_IgniteTests=pull/1792/head]
 nothing new comparing to master

> GridCacheAbstractRemoveFailureTest fail
> ---
>
> Key: IGNITE-4982
> URL: https://issues.apache.org/jira/browse/IGNITE-4982
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.0
>
>
> GridCacheAbstractRemoveFailureTest (and some child tests) fails. Reproducer:
> {code:java}
> import java.util.Collection;
> import java.util.HashSet;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.CyclicBarrier;
> import java.util.concurrent.ThreadLocalRandom;
> import java.util.concurrent.TimeUnit;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicBoolean;
> import java.util.concurrent.atomic.AtomicLong;
> import java.util.concurrent.atomic.AtomicReference;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.IgniteTransactions;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.NearCacheConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.cluster.ClusterTopologyCheckedException;
> import org.apache.ignite.internal.util.lang.GridTuple;
> import org.apache.ignite.internal.util.typedef.F;
> import org.apache.ignite.internal.util.typedef.T2;
> import org.apache.ignite.internal.util.typedef.X;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import org.jsr166.ConcurrentHashMap8;
> import static 
> org.apache.ignite.IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.SERIALIZABLE;
> /**
>  * Tests that removes are not lost when topology changes.
>  */
> public abstract class GridCacheAbstractRemoveFailureTest extends 
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** Keys count. */
> private static final int KEYS_CNT = 10_000;
> /** Test duration. */
> private static final long DUR = 90 * 1000L;
> /** Cache data assert frequency. */
> private static final long ASSERT_FREQ = 10_000;
> /** Kill delay. */
> private static final T2 KILL_DELAY = new T2<>(2000, 
> 5000);
> /** Start delay. */
> private static final T2 START_DELAY = new T2<>(2000, 
> 5000);
> /** */
> private static String sizePropVal;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> 
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER).setForceServerMode(true);
> if (testClientNode() && 
> getTestIgniteInstanceName(0).equals(igniteInstanceName))
> cfg.setClientMode(true);
> 
> ((TcpCommunicationSpi)cfg.getCommunicationSpi()).setSharedMemoryPort(-1);
> return cfg;
> }
> /** {@inheritDoc} */
> 

[jira] [Assigned] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken

[Vadim Opolski (JIRA)]

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

Vadim Opolski reassigned IGNITE-1084:
-

Assignee: Vadim Opolski  (was: Milap Wadhwa)

> [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
> --
>
> Key: IGNITE-1084
> URL: https://issues.apache.org/jira/browse/IGNITE-1084
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Sergey Evdokimov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: Muted_test
>
> Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and 
> fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4587) Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4587:


GitHub user glukos opened a pull request:

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

IGNITE-4587: Found bug - CacheVersionIO is changed, but size isn't



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

$ git pull https://github.com/gridgain/apache-ignite IGNITE-4587-version-fix

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

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


commit 3590a6796dc440d49223b8c94e9bac53e4d51e6c
Author: Ivan Rakov 
Date:   2017-04-17T12:34:14Z

IGNITE-4587: Found bug - CacheVersionIO is changed, but size isn't




> Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
> ---
>
> Key: IGNITE-4587
> URL: https://issues.apache.org/jira/browse/IGNITE-4587
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Fix For: 2.0
>
>
> {{CacheAtomicWriteOrderMode.CLOCK}} proved to be harmful in production due to 
> timing issues.
> It makes sense to remove it completely in 2.0 release. Migration guide has be 
> updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4998) Add more dynamic indexing tests for various cache modes

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4998:
---

 Summary: Add more dynamic indexing tests for various cache modes
 Key: IGNITE-4998
 URL: https://issues.apache.org/jira/browse/IGNITE-4998
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4997) Make sure dynamic schema state is re-created properly after client re-connect

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4997:
-

Considerations:
1) When disconnect happens, we must clear all schemas and H2 stuff;
2) When reconnect happens, we must re-create all schemas from existing cache 
descriptors received during discovery exchange;
3) Make sure that any concurrent events operate on current schema. Probably we 
will have to introduce some unique ID of "current state" to distinguish client 
before and after re-connect.

> Make sure dynamic schema state is re-created properly after client re-connect
> -
>
> Key: IGNITE-4997
> URL: https://issues.apache.org/jira/browse/IGNITE-4997
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4997) Make sure dynamic schema state is re-created properly after client re-connect

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4997:

Fix Version/s: 2.0

> Make sure dynamic schema state is re-created properly after client re-connect
> -
>
> Key: IGNITE-4997
> URL: https://issues.apache.org/jira/browse/IGNITE-4997
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4997) Make sure dynamic schema state is re-created properly after client re-connect

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4997:

Affects Version/s: (was: 2.0)

> Make sure dynamic schema state is re-created properly after client re-connect
> -
>
> Key: IGNITE-4997
> URL: https://issues.apache.org/jira/browse/IGNITE-4997
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4997) Make sure dynamic schema state is re-created properly after client re-connect

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4997:
---

 Summary: Make sure dynamic schema state is re-created properly 
after client re-connect
 Key: IGNITE-4997
 URL: https://issues.apache.org/jira/browse/IGNITE-4997
 Project: Ignite
  Issue Type: Task
  Components: SQL
Affects Versions: 2.0
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4565) Support CREATE INDEX DDL statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4565:
-

Outstanding issues:
1) Fix client reconnect schema consistency issue.

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (IGNITE-4565) Support CREATE INDEX DDL statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4565:

Comment: was deleted

(was: Outstanding issues:
1) Fix client reconnect schema consistency issue.)

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4565) Support CREATE INDEX DDL statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-4565 at 4/17/17 12:26 PM:
---

Outstanding issues:
1) Fix client reconnect schema consistency issue.


was (Author: vozerov):
Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Additional test for local cache, replicated cache, near+dht and near caches
3) Add rebalance consistency tests

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4669) .NET: Sort binary object fields

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4669 at 4/17/17 11:55 AM:
--

As discussed on dev list 
(http://apache-ignite-developers.2346864.n4.nabble.com/Sorting-fields-of-Binarilyzable-objects-on-write-td16357.html),
 {{IBinarizable}} sorting has been removed.


was (Author: ptupitsyn):
As discussed on dev list 
(http://apache-ignite-developers.2346864.n4.nabble.com/Sorting-fields-of-Binarilyzable-objects-on-write-td16357.html),
 let's remove {{IBinarizable}} sorting.

> .NET: Sort binary object fields
> ---
>
> Key: IGNITE-4669
> URL: https://issues.apache.org/jira/browse/IGNITE-4669
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Make sure that fields are sorted by name in all cases:
> * Reflective serializer
> * {{IBinarizable}} serialization
> * {{[Serializable]}} serialization
> * Custom serializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4669) .NET: Sort binary object fields

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4669:


As discussed on dev list 
(http://apache-ignite-developers.2346864.n4.nabble.com/Sorting-fields-of-Binarilyzable-objects-on-write-td16357.html),
 let's remove {{IBinarizable}} sorting.

> .NET: Sort binary object fields
> ---
>
> Key: IGNITE-4669
> URL: https://issues.apache.org/jira/browse/IGNITE-4669
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Make sure that fields are sorted by name in all cases:
> * Reflective serializer
> * {{IBinarizable}} serialization
> * {{[Serializable]}} serialization
> * Custom serializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-2398) .NET: Change default mapper behavior

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2398:


Removed automatic mappers configuration from 
{{PlatformDotNetConfigurationClosure}}, because now defaults are the same for 
Java and .NET.

This way .NET and Java nodes can join without any config tweaks (IGNITE-3267).

> .NET: Change default mapper behavior
> 
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net, important
> Fix For: 2.0
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4460) .NET: Unhelpful error message for same-table SelectMany in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4460:


Simple validation added: all FROM clauses must be {{IQueryable}}

> .NET: Unhelpful error message for same-table SelectMany in LINQ
> ---
>
> Key: IGNITE-4460
> URL: https://issues.apache.org/jira/browse/IGNITE-4460
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET, LINQ
> Fix For: 2.0
>
>
> The following LINQ is not supported ({{RegionToRole}} is a collection, which 
> is not understood by SQL):
> {code}
> users.Where(w => w.Value.ID == userId && !w.Value.IsDeleted)
> .SelectMany(sm => sm.Value.RegionToRole)
> {code}
> However, LINQ engine proceeds to generate an invalid query, which fails later 
> in SQL engine:
> {code}
> Failed to parse query: select _T0._key, _T0._val from "User".User as _T0 , 
> "User".User as _T0 where  ...
> {code}
> We should detect invalid LINQ early and throw an error with explanation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-4460) .NET: Unhelpful error message for same-table SelectMany in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4460.

Resolution: Fixed

> .NET: Unhelpful error message for same-table SelectMany in LINQ
> ---
>
> Key: IGNITE-4460
> URL: https://issues.apache.org/jira/browse/IGNITE-4460
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET, LINQ
> Fix For: 2.0
>
>
> The following LINQ is not supported ({{RegionToRole}} is a collection, which 
> is not understood by SQL):
> {code}
> users.Where(w => w.Value.ID == userId && !w.Value.IsDeleted)
> .SelectMany(sm => sm.Value.RegionToRole)
> {code}
> However, LINQ engine proceeds to generate an invalid query, which fails later 
> in SQL engine:
> {code}
> Failed to parse query: select _T0._key, _T0._val from "User".User as _T0 , 
> "User".User as _T0 where  ...
> {code}
> We should detect invalid LINQ early and throw an error with explanation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4988) Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4988:


{code}
visor> cache -c=tx_partitioned -scan
(wrn) : Ouch! Argument cannot be null: sql
(wrn) : Type 'help cache' to see how to use this command.
{code}

> Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0
> ---
>
> Key: IGNITE-4988
> URL: https://issues.apache.org/jira/browse/IGNITE-4988
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin commented on IGNITE-4949:


[~vkulichenko] What do you think? I corrected the comments, take a look at the 
new changes.

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-4949:
--

https://github.com/apache/ignite/pull/1803
Looks good for me.

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4900) org.apache.ignite.spi.discovery.tcp.TcpDiscoverySelfTest#testFailedNodes4 periodically fails in master

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-4900:


Can't reproduce the problem so far.

> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySelfTest#testFailedNodes4 
> periodically fails in master
> --
>
> Key: IGNITE-4900
> URL: https://issues.apache.org/jira/browse/IGNITE-4900
> Project: Ignite
>  Issue Type: Test
>Reporter: Yakov Zhdanov
>Assignee: Ivan Rakov
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: log.txt
>
>
> See attached log



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4956) Stabilize the test on partition reservation during affinity call

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4956:
-
Summary: Stabilize the test on partition reservation during affinity call  
(was: Stabilize  the test 
IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp)

> Stabilize the test on partition reservation during affinity call
> 
>
> Key: IGNITE-4956
> URL: https://issues.apache.org/jira/browse/IGNITE-4956
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Stabilize  the test 
> *IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp*
> The test periodically failed with the message:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed partition reservation. 
> Partition is not primary on the node. [partition=12, cacheName=Person, 
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion 
> [topVer=9, minorTopVer=0]] at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7172) at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
>  at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:95)
>  at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:271)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:259)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:389)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:355)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:343)
>  at 
> org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:858) 
> at 
> org.apache.ignite.testframework.GridTestUtils$8.call(GridTestUtils.java:1149) 
> at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86) 
> Caused by: org.apache.ignite.IgniteException: Failed partition reservation. 
> Partition is not primary on the node. [partition=12, cacheName=Person, 
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion 
> [topVer=9, minorTopVer=0]] at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$PartitionsReservation.reserve(GridJobProcessor.java:1572)
>  at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:504)
>  at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
>  at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1228)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:856)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:111)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:798)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  at java.lang.Thread.run(Thread.java:745) --- Stdout: ---
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4990:


Assignee: Vladimir Ozerov  (was: Alexey Kuznetsov)

I fixed WebConsole and Visor part.

> Remove deprecated properties from FileSystemConfiguration
> -
>
> Key: IGNITE-4990
> URL: https://issues.apache.org/jira/browse/IGNITE-4990
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3920:

Labels: important  (was: )

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4699) Introduce custom configurable executors.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4699:
-

[~tledkov-gridgain], my comments:
1) {{IgniteComputeImpl.readResolve}} - looks like we should apply executor here 
as well.
2) {{GridIoManager}} - call to {{pools.customExecutor(execName)}} could throw 
NPE.

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-3488:
--

Lots of tests failed, fixing each of them...

> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4460) .NET: Unhelpful error message for same-table SelectMany in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4460:
--

Assignee: Pavel Tupitsyn

> .NET: Unhelpful error message for same-table SelectMany in LINQ
> ---
>
> Key: IGNITE-4460
> URL: https://issues.apache.org/jira/browse/IGNITE-4460
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET, LINQ
> Fix For: 2.0
>
>
> The following LINQ is not supported ({{RegionToRole}} is a collection, which 
> is not understood by SQL):
> {code}
> users.Where(w => w.Value.ID == userId && !w.Value.IsDeleted)
> .SelectMany(sm => sm.Value.RegionToRole)
> {code}
> However, LINQ engine proceeds to generate an invalid query, which fails later 
> in SQL engine:
> {code}
> Failed to parse query: select _T0._key, _T0._val from "User".User as _T0 , 
> "User".User as _T0 where  ...
> {code}
> We should detect invalid LINQ early and throw an error with explanation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4546) .NET: BinaryConfiguration handles nested type names incorrectly

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4546:


Fixed as part of IGNITE-2398

> .NET: BinaryConfiguration handles nested type names incorrectly
> ---
>
> Key: IGNITE-4546
> URL: https://issues.apache.org/jira/browse/IGNITE-4546
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Type name is resolved incorrectly for nested types (class in class).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4460) .NET: Unhelpful error message for same-table SelectMany in LINQ

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4460:
---
Fix Version/s: (was: 2.1)
   2.0

> .NET: Unhelpful error message for same-table SelectMany in LINQ
> ---
>
> Key: IGNITE-4460
> URL: https://issues.apache.org/jira/browse/IGNITE-4460
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET, LINQ
> Fix For: 2.0
>
>
> The following LINQ is not supported ({{RegionToRole}} is a collection, which 
> is not understood by SQL):
> {code}
> users.Where(w => w.Value.ID == userId && !w.Value.IsDeleted)
> .SelectMany(sm => sm.Value.RegionToRole)
> {code}
> However, LINQ engine proceeds to generate an invalid query, which fails later 
> in SQL engine:
> {code}
> Failed to parse query: select _T0._key, _T0._val from "User".User as _T0 , 
> "User".User as _T0 where  ...
> {code}
> We should detect invalid LINQ early and throw an error with explanation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3689:


Github user asfgit closed the pull request at:

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


> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3689:


Merged to master

> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3689:


Injected Ignite instance may be serialized due to {{MessageListenerHolder}} 
behavior, among other things.
So we should keep a null-valued field in serialized form.

However, simple system type write handler is a better solution than a proxy 
class.

> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4955) Correctly execute SQL queries started on replicated cache.

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin closed IGNITE-4955.
--

> Correctly execute SQL queries started on replicated cache.
> --
>
> Key: IGNITE-4955
> URL: https://issues.apache.org/jira/browse/IGNITE-4955
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-4955) Correctly execute SQL queries started on replicated cache.

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin resolved IGNITE-4955.

Resolution: Fixed

Merged to master

> Correctly execute SQL queries started on replicated cache.
> --
>
> Key: IGNITE-4955
> URL: https://issues.apache.org/jira/browse/IGNITE-4955
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4996) Queries: show Node selection modal in case if user execute SCAN on local cache

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-4996:
--

 Summary: Queries: show Node selection modal in case if user 
execute SCAN on local cache
 Key: IGNITE-4996
 URL: https://issues.apache.org/jira/browse/IGNITE-4996
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor


Also we need to filter nodes list and show only nodes where selected cache is 
configured



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3536) IGFS: Implement async methods for all base file system operations.

[Alexei Kaigorodov (JIRA)]

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

Alexei Kaigorodov commented on IGNITE-3536:
---

In order to avoid waiting for time consuming operations, they should be 
parallelised. Parallelisation can be done in 2 forms: synchronous (using 
threads and both blocking and non-blocking operations) and asynchronous (using 
tasks executed by thread pool and non-blocking operations only).
Asynchronous parallelisation is a hard task: blocking operations must be 
eliminated totally. Program code bloats and become less readable. New 
challenges like back-pressure should be resolved. The only advantage of 
asynchronous parallelisation is saving memory for thread's stacks.
That is, I want to make sure we definitely want asynchronous parallelisation 
and not synchronous one.

> IGFS: Implement async methods for all base file system operations.
> --
>
> Key: IGNITE-3536
> URL: https://issues.apache.org/jira/browse/IGNITE-3536
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
>
> 1) Remove {{IgniteAsyncSupport}} interface
> 2) Implement async counterparts for all FS operations.
> Justification: some structure file system operations might be very 
> time-consuming, so having async counterparts sounds like a good idea.
> The questions is what thread pool will host these tasks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4068.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4068:


Tested Remove button.

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4871.
--

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-4871:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4871:


Tested.

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)