[jira] [Assigned] (IGNITE-7225) Web console: improve CSV export

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-7225:


Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Commented] (IGNITE-6873) Web console: some error messages are too technical

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6873:


Tested

> Web console: some error messages are too technical
> --
>
> Key: IGNITE-6873
> URL: https://issues.apache.org/jira/browse/IGNITE-6873
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
> Environment: Chrome 29
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
>
> *What happens:*
> Chrome 29 throws an error about missing {{atob}} and {{btoa}} global 
> functions (used in the frontend AgentManager service). The error gets 
> succesfully displayed to user in a default error notification, but ambiguous 
> message "Reference error: can't find atob" provides very little useful info 
> for most of users without advanced JS background.
> *What should happen:*
> Web console should relay this and similar errors in a more accessible manner.
> *Possible solutions:*
> 1. Consider missing API errors as operational, add explicit handler to 
> generate better messages, detect features and polyfill when possible. Pros: 
> better UX, increases supported browsers percentage. Cons: very high 
> maintenance cost.
> 2. Notify user about unsupported/outdated browser. Pros: easy to implement, 
> simultaneously covers lots of potential issues. Cons: very non-specific, UX 
> worse than option #1.



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

[jira] [Closed] (IGNITE-6873) Web console: some error messages are too technical

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6873.
--

> Web console: some error messages are too technical
> --
>
> Key: IGNITE-6873
> URL: https://issues.apache.org/jira/browse/IGNITE-6873
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
> Environment: Chrome 29
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
>
> *What happens:*
> Chrome 29 throws an error about missing {{atob}} and {{btoa}} global 
> functions (used in the frontend AgentManager service). The error gets 
> succesfully displayed to user in a default error notification, but ambiguous 
> message "Reference error: can't find atob" provides very little useful info 
> for most of users without advanced JS background.
> *What should happen:*
> Web console should relay this and similar errors in a more accessible manner.
> *Possible solutions:*
> 1. Consider missing API errors as operational, add explicit handler to 
> generate better messages, detect features and polyfill when possible. Pros: 
> better UX, increases supported browsers percentage. Cons: very high 
> maintenance cost.
> 2. Notify user about unsupported/outdated browser. Pros: easy to implement, 
> simultaneously covers lots of potential issues. Cons: very non-specific, UX 
> worse than option #1.



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

[jira] [Commented] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7229:


Github user asfgit closed the pull request at:

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


> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Resolved] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-7229.

Resolution: Fixed

> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Commented] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7229:


Merged to master: {{8f327a18bea8cd4efda0d9ffea1acf7a11d56f90}}

> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Assigned] (IGNITE-6094) Web console: Implement persistent store in demo mode.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6094:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: Implement persistent store in demo mode.
> -
>
> Key: IGNITE-6094
> URL: https://issues.apache.org/jira/browse/IGNITE-6094
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
>




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

[jira] [Commented] (IGNITE-6094) Web console: Implement persistent store in demo mode.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6094:
---

Metrics enabled.

> Web console: Implement persistent store in demo mode.
> -
>
> Key: IGNITE-6094
> URL: https://issues.apache.org/jira/browse/IGNITE-6094
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Minor
>




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

[jira] [Commented] (IGNITE-6873) Web console: some error messages are too technical

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-6873:
--

[~pkonstantinov] how to test:
1. Open web console in Chrome.
2. Open Chrome Developer Tools.
3. Open "Network conditions" tab.
4. Change useragent, reload the page – you should see an "unsupported browser" 
message if the browser is not in the supported list and no message for 
supported browsers.

> Web console: some error messages are too technical
> --
>
> Key: IGNITE-6873
> URL: https://issues.apache.org/jira/browse/IGNITE-6873
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
> Environment: Chrome 29
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
>
> *What happens:*
> Chrome 29 throws an error about missing {{atob}} and {{btoa}} global 
> functions (used in the frontend AgentManager service). The error gets 
> succesfully displayed to user in a default error notification, but ambiguous 
> message "Reference error: can't find atob" provides very little useful info 
> for most of users without advanced JS background.
> *What should happen:*
> Web console should relay this and similar errors in a more accessible manner.
> *Possible solutions:*
> 1. Consider missing API errors as operational, add explicit handler to 
> generate better messages, detect features and polyfill when possible. Pros: 
> better UX, increases supported browsers percentage. Cons: very high 
> maintenance cost.
> 2. Notify user about unsupported/outdated browser. Pros: easy to implement, 
> simultaneously covers lots of potential issues. Cons: very non-specific, UX 
> worse than option #1.



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

[jira] [Closed] (IGNITE-4835) Add ability to start rebalancing from management console

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4835.
--

> Add ability to start rebalancing from management console
> 
>
> Key: IGNITE-4835
> URL: https://issues.apache.org/jira/browse/IGNITE-4835
> Project: Ignite
>  Issue Type: New Feature
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Alexandr Fedotov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Management console should allow for starting rebalancing manually.



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

[jira] [Commented] (IGNITE-4835) Add ability to start rebalancing from management console

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4835:


Tested

> Add ability to start rebalancing from management console
> 
>
> Key: IGNITE-4835
> URL: https://issues.apache.org/jira/browse/IGNITE-4835
> Project: Ignite
>  Issue Type: New Feature
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Alexandr Fedotov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Management console should allow for starting rebalancing manually.



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

[jira] [Closed] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4454.
--

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



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

[jira] [Commented] (IGNITE-4454) Web console: add information on query panel UI about node query was executed on

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4454:


Tested

> Web console: add information on query panel  UI about node query was executed 
> on
> 
>
> Key: IGNITE-4454
> URL: https://issues.apache.org/jira/browse/IGNITE-4454
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Currently we show only query text  and do not show node in case of 'Execute 
> on selected node'



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

[jira] [Assigned] (IGNITE-7224) Web console: Remove deprecated fields from configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7224:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: Remove deprecated fields from configuration
> 
>
> Key: IGNITE-7224
> URL: https://issues.apache.org/jira/browse/IGNITE-7224
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>
> Ignite configuration:
> # setMarshaller is deprecated since 2.1.
> # setLateAffinityAssignment is always enabled since 2.1.



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

[jira] [Closed] (IGNITE-5407) Web console: Wrong generation of marshaller on version switch

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko closed IGNITE-5407.
-

> Web console: Wrong generation of marshaller on version switch
> -
>
> Key: IGNITE-5407
> URL: https://issues.apache.org/jira/browse/IGNITE-5407
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>
> 2) Marshaller on Summary is not changed when version is changed
> on Cluster set version 1.x and set OptimizedMarshaller
> go to Summary and look at preview - it shows Optimized
> change version to 2.0 - look at preview - marshaller is still Optimized



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

[jira] [Resolved] (IGNITE-5407) Web console: Wrong generation of marshaller on version switch

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-5407.
---
Resolution: Duplicate
  Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

Fixed in IGNITE-7224

> Web console: Wrong generation of marshaller on version switch
> -
>
> Key: IGNITE-5407
> URL: https://issues.apache.org/jira/browse/IGNITE-5407
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>
> 2) Marshaller on Summary is not changed when version is changed
> on Cluster set version 1.x and set OptimizedMarshaller
> go to Summary and look at preview - it shows Optimized
> change version to 2.0 - look at preview - marshaller is still Optimized



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

[jira] [Commented] (IGNITE-7224) Web console: Remove deprecated fields from configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-7224:
---

Marshaller and late affinity assignment properties are hidden in Ignite 2.1 
version.
Fixed generation of OptimisedMarshaller from IGNITE-5704 issue. 

> Web console: Remove deprecated fields from configuration
> 
>
> Key: IGNITE-7224
> URL: https://issues.apache.org/jira/browse/IGNITE-7224
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Ignite configuration:
> # setMarshaller is deprecated since 2.1.
> # setLateAffinityAssignment is always enabled since 2.1.



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

[jira] [Commented] (IGNITE-6919) Web console: incorrect character in tab name under IE11

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6919:


Tested

> Web console: incorrect character in tab name under IE11
> ---
>
> Key: IGNITE-6919
> URL: https://issues.apache.org/jira/browse/IGNITE-6919
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Commented] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4398:


Tested

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



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

[jira] [Closed] (IGNITE-4398) Web console: incorrect authentication under IE 11 (windows 10)

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4398.
--

> Web console: incorrect authentication under IE 11 (windows 10)
> --
>
> Key: IGNITE-4398
> URL: https://issues.apache.org/jira/browse/IGNITE-4398
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>  Time Spent: 0.1m
>  Remaining Estimate: 0h
>
> To reproduce:
> 1) log in as User1
> 2) create some cluster and save
> 3) log out
> 4) log in as User2
> You will see the cluster from User1.
> Note: IE specific only



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

[jira] [Commented] (IGNITE-6390) [IGNITE-6390] Web console: Implement component for cluster selection on pages where it make sense

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6390:


Tested

> [IGNITE-6390] Web console: Implement component for cluster selection on pages 
> where it make sense
> -
>
> Key: IGNITE-6390
> URL: https://issues.apache.org/jira/browse/IGNITE-6390
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> 1. add cluster-selector to pages.
> 2. add update information of cluster data in page after change cluster.



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

[jira] [Closed] (IGNITE-6390) [IGNITE-6390] Web console: Implement component for cluster selection on pages where it make sense

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6390.
--

> [IGNITE-6390] Web console: Implement component for cluster selection on pages 
> where it make sense
> -
>
> Key: IGNITE-6390
> URL: https://issues.apache.org/jira/browse/IGNITE-6390
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> 1. add cluster-selector to pages.
> 2. add update information of cluster data in page after change cluster.



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

[jira] [Commented] (IGNITE-7020) Web Console: add column resizer to pinned columns

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7020:


Tested

> Web Console: add column resizer to pinned columns
> -
>
> Key: IGNITE-7020
> URL: https://issues.apache.org/jira/browse/IGNITE-7020
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




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

[jira] [Closed] (IGNITE-7147) Implement connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7147.
--

> Implement connected clusters component
> --
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




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

[jira] [Commented] (IGNITE-7147) Implement connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7147:


Tested.

> Implement connected clusters component
> --
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




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

[jira] [Closed] (IGNITE-7172) Web console: Add example to queries page

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7172.
--

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>




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

[jira] [Commented] (IGNITE-7172) Web console: Add example to queries page

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7172:


Tested

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>




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

[jira] [Assigned] (IGNITE-7224) Web console: Remove deprecated fields from configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7224:
-

Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

> Web console: Remove deprecated fields from configuration
> 
>
> Key: IGNITE-7224
> URL: https://issues.apache.org/jira/browse/IGNITE-7224
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> Ignite configuration:
> # setMarshaller is deprecated since 2.1.
> # setLateAffinityAssignment is always enabled since 2.1.



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

[jira] [Assigned] (IGNITE-5407) Web console: Wrong generation of marshaller on version switch

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5407:
-

Assignee: Vasiliy Sisko

> Web console: Wrong generation of marshaller on version switch
> -
>
> Key: IGNITE-5407
> URL: https://issues.apache.org/jira/browse/IGNITE-5407
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> 2) Marshaller on Summary is not changed when version is changed
> on Cluster set version 1.x and set OptimizedMarshaller
> go to Summary and look at preview - it shows Optimized
> change version to 2.0 - look at preview - marshaller is still Optimized



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

[jira] [Commented] (IGNITE-3464) Possible race between partition exchange and prepare/finish requests

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3464:


GitHub user BiryukovVA opened a pull request:

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

IGNITE-3464

Fixed bug - race between partition exchange and prepare/finish requests.

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

$ git pull https://github.com/BiryukovVA/ignite IGNITE-3464

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

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


commit a370e2f30008b244f26fcdda0eb0a30e8132f04a
Author: Vitaliy Biryukov 
Date:   2017-12-18T23:15:24Z

IGNITE-3464: Fixed bug - race between partition exchange and prepare/finish 
requests.




> Possible race between partition exchange and prepare/finish requests
> 
>
> Key: IGNITE-3464
> URL: https://issues.apache.org/jira/browse/IGNITE-3464
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Vitaliy Biryukov
>
> Consider the following scenario:
> Two nodes A (coordinator), B. Node C is joining the grid. Current topology 
> version is 2.
>  - Node A starts a transaction on version 2 and sends a prepare request to 
> node B
>  - Discovery event happens on node A. Exchange future is created, captures 
> the transaction and waits for this transaction to finish.
>  - Discovery event happens on node B. Exchange future is created, but since 
> there is no transaction on this node (the request has not been processed 
> yet), partition release future is completed and exchange waits for an ACK 
> from coordinator.
>  - Prepare request is processed on node B
>  - Node A commits the transaction locally, partition release future is 
> completed. Both finish request and exchange message are sent to the node B.
>  - Node B processes the exchange message first and completes exchange.
>  - Node C starts rebalancing from node B and acquires stale value of the key 
> which was supposed to be updated in the transaction.
>  - Node B processes finish request and commits the transaction.
> As a result, node B and C have different values stored in the cache.



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

[jira] [Commented] (IGNITE-6785) Affinity field name forced to be upper-case

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6785:


GitHub user dolphin1414 opened a pull request:

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

IGNITE-6785: Affinity key field ignore case.

Fix for an affinity field name upper-case issue.

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

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

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

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


commit acf0e7dada672e6cd0027d46977279a7c0ab9f91
Author: rkondakov 
Date:   2017-12-18T20:29:32Z

IGNITE-6785: Changed affinity key fields names comparison from the equals() 
to equalsIgnoreCase().




> Affinity field name forced to be upper-case
> ---
>
> Key: IGNITE-6785
> URL: https://issues.apache.org/jira/browse/IGNITE-6785
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Roman Kondakov
>  Labels: important, usability
> Fix For: 2.4
>
> Attachments: sql_bug.zip
>
>
> If an SQL schema and cache is created with CREATE TABLE command and a user 
> wants to use key-value APIs creating its own custom key class, then (at 
> least) the key  class's affinity field forced to be written in upper-case.
> Steps to reproduce using the project attached:
> * start a node with {{./ignite.sh ../examples/config/example-ignite.xml}}.
> * create {{City}} table using {{ignite_world.sql}}. SQLline is one of the 
> quickest ways: https://apacheignite-sql.readme.io/docs/sqlline
> * Run {{KeyValueDataProcessing}} to catch the exception below
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Binary type has different 
> affinity key fields [typeName=demo.model.CityKey, 
> affKeyFieldName1=COUNTRYCODE, affKeyFieldName2=countryCode]
>   at 
> org.apache.ignite.internal.binary.BinaryUtils.mergeMetadata(BinaryUtils.java:987)
> {noformat} 
> If fact {{CityKey}} names the affinity field in the same way as in CREATE 
> TABLE - {{countryCode}}.
> Next, run {{KeyValueBinaryDataProcessing}} to spot another weird thing:
> * BinaryObject key accepts `countryCode` as the affinity field name.
> * If to print our a binary object value then all the fields are in the 
> upper-case (they were not defined this way in CREATE TABLE):
> {noformat}
> demo.model.City [idHash=1613627715, hash=-1386587499, DISTRICT=Noord-Holland, 
> POPULATION=711200, NAME=Amsterdam]
> {noformat}



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

[jira] [Commented] (IGNITE-6994) Need to document PartitionLossPolicy

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6994:
-

Discussion on @dev list: 
http://apache-ignite-developers.2346864.n4.nabble.com/Partition-loss-policy-how-to-use-td25341.html

> Need to document PartitionLossPolicy
> 
>
> Key: IGNITE-6994
> URL: https://issues.apache.org/jira/browse/IGNITE-6994
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Prachi Garg
>Priority: Critical
>  Labels: documentation
> Fix For: 2.4
>
>
> Since 2.0 we have a feature that makes cache(s) unavailable in case of data 
> loss; exact behavior is controlled by {{PartitionLossPolicy}}: 
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/PartitionLossPolicy.html
> However, there is no mentioning in documentation about this. Need to provide 
> explanation of how and when it should be used and provide configuration 
> examples.



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

[jira] [Closed] (IGNITE-5171) Show how to index fields of embedded objects

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-5171.
---

> Show how to index fields of embedded objects
> 
>
> Key: IGNITE-5171
> URL: https://issues.apache.org/jira/browse/IGNITE-5171
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Document and demonstrate how to index and use fields of embedded objects:
> https://apacheignite-sql.readme.io/docs/schema-and-indexes
> For instance, if we have this object
> Person {
> int age;
> int id;
> Addrees addr;
> }
> where Address includes {street and zip} fileds.
> Show how to index {{street}} and {{zip}} and use from SQL.



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

[jira] [Resolved] (IGNITE-5171) Show how to index fields of embedded objects

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-5171.
-
Resolution: Fixed

Thanks!

> Show how to index fields of embedded objects
> 
>
> Key: IGNITE-5171
> URL: https://issues.apache.org/jira/browse/IGNITE-5171
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Document and demonstrate how to index and use fields of embedded objects:
> https://apacheignite-sql.readme.io/docs/schema-and-indexes
> For instance, if we have this object
> Person {
> int age;
> int id;
> Addrees addr;
> }
> where Address includes {street and zip} fileds.
> Show how to index {{street}} and {{zip}} and use from SQL.



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

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

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-1553:
--

[~agoncharuk] Currently we have a couple of CacheStore implementations : 
GridCacheWriteBehindStore, and GridCacheLoaderWriterStore which don't support 
sessionEnd() method(No-op implementation). This means that we cannot commit to 
database as you described in ticket description above, instead data is 
persisted right after calling write\delete etc.
Additionally, we cannot guarantee that custom CacheStore prepares data for 
commit when write\delete etc. is called (and we cannot guarantee that data is 
flushed when sessionEnd is called)

So, I would propose to optimize prepare step only if CacheStore is instance of 
CacheAbstractJdbcStore or CacheJdbcBlobStore(only these stores guarantee 
autocommit==false)

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



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

[jira] [Updated] (IGNITE-7235) Add warning with with a list of restrictions when Ignite native persistence is used with write-though cache store

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-7235:
-
Description: We should remove any validations (if any) for native 
persistence and CacheStore.

> Add warning with with a list of restrictions when Ignite native persistence 
> is used with write-though cache store
> -
>
> Key: IGNITE-7235
> URL: https://issues.apache.org/jira/browse/IGNITE-7235
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.4
>
>
> We should remove any validations (if any) for native persistence and 
> CacheStore.



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

[jira] [Created] (IGNITE-7235) Add warning with with a list of restrictions when Ignite native persistence is used with write-though cache store

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7235:


 Summary: Add warning with with a list of restrictions when Ignite 
native persistence is used with write-though cache store
 Key: IGNITE-7235
 URL: https://issues.apache.org/jira/browse/IGNITE-7235
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.4






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

[jira] [Commented] (IGNITE-6615) .NET: Thin client: XML configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6615:


* {{IgniteClientConfigurationSection}}
* {{IgniteClientConfiguration.ToXml}} and {{FromXml}}
* {{xsd}} schema file (include in Schema nuget)

> .NET: Thin client: XML configuration
> 
>
> Key: IGNITE-6615
> URL: https://issues.apache.org/jira/browse/IGNITE-6615
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
>
> Provide a way to configure {{IgniteClientConfiguration}} in XML, similar to 
> {{IgniteConfiguration}}.



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

[jira] [Closed] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Peter Ivanov (JIRA)]

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

Peter Ivanov closed IGNITE-7233.


> Problems with classpath on Windows when IGNITE_HOME contains spaces
> ---
>
> Key: IGNITE-7233
> URL: https://issues.apache.org/jira/browse/IGNITE-7233
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows, cmd, batch files
>Reporter: Ilya Kasnacheev
>Assignee: Peter Ivanov
>  Labels: windows
>
> {code}
> C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
> REM note the white space in directory name ^
> C:\releases\apache-ignite-fabric-2.3.0 bin>set 
> IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
> C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
> %IGNITE_HOME%\config\default.xml
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
> class org.apache.ignite.IgniteException: Failed to create Ignite component 
> (consider adding ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> Ignite component (consider adding ignite-spring module to classpath) 
> [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at 
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding 
> ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your classpath.
> Press any key to continue . . .
> {code}



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

[jira] [Assigned] (IGNITE-7183) SQL TX: Implicit transactions

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov reassigned IGNITE-7183:


Assignee: Igor Seliverstov

> SQL TX: Implicit transactions
> -
>
> Key: IGNITE-7183
> URL: https://issues.apache.org/jira/browse/IGNITE-7183
> Project: Ignite
>  Issue Type: Task
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>  Labels: iep-3, sql
>
> Implicit transaction has to be started on any SQL update in a transactional 
> cache.



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

[jira] [Commented] (IGNITE-6736) Java 9: rework GridCacheMapEntry synchronization logic to avoid Unsafe.monitor* methods

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6736:


GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6736: Switched GridCacheMapEntry synchronization to locks.

For test purpose

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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6736

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

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


commit 009e8710779355feb375ce63a60a24f12900c761
Author: Andrey Kuznetsov 
Date:   2017-12-18T15:36:01Z

IGNITE-6736: Switched GridCacheMapEntry synchronization to locks.




> Java 9: rework GridCacheMapEntry synchronization logic to avoid 
> Unsafe.monitor* methods
> ---
>
> Key: IGNITE-6736
> URL: https://issues.apache.org/jira/browse/IGNITE-6736
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> {{GridCacheMapEntry}} class rely on {{synchronized}} on itself heavily. In 
> {{ATOMIC}} caches we lock multiple entries at once using 
> {{Unsafe.monitorEnter/Exit}} methods. Unfortunately these methods were 
> removed in Java 9. Recursion is not an option, as it would cause stack 
> overflow for {{putAll}} operations with multiple entries.
> Possible fixes:
> 1) Rework {{synchronized}} to {{ReentrantLock}}. Easy, but may cause 
> additional memory pressure.
> 2) Have different implementations for Java 8 ({{synchronzied}}) and Java 9 
> ({{ReentrantLock}}) - much more complex solution, because we will require 
> separate module for Java 8 and Java 9.
> 3) Rework {{ATOMIC}} caches, so that {{putAll}} operation updates entries 
> one-by-one. As a side effect it will eliminate deadlocks.



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

[jira] [Resolved] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev resolved IGNITE-7233.
-
Resolution: Duplicate

> Problems with classpath on Windows when IGNITE_HOME contains spaces
> ---
>
> Key: IGNITE-7233
> URL: https://issues.apache.org/jira/browse/IGNITE-7233
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows, cmd, batch files
>Reporter: Ilya Kasnacheev
>Assignee: Peter Ivanov
>  Labels: windows
>
> {code}
> C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
> REM note the white space in directory name ^
> C:\releases\apache-ignite-fabric-2.3.0 bin>set 
> IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
> C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
> %IGNITE_HOME%\config\default.xml
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
> class org.apache.ignite.IgniteException: Failed to create Ignite component 
> (consider adding ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> Ignite component (consider adding ignite-spring module to classpath) 
> [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at 
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding 
> ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your classpath.
> Press any key to continue . . .
> {code}



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

[jira] [Resolved] (IGNITE-7232) .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET examples with standalone node

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-7232.

Resolution: Fixed

> .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET 
> examples with standalone node
> ---
>
> Key: IGNITE-7232
> URL: https://issues.apache.org/jira/browse/IGNITE-7232
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> need to remove localhost="127.0.0.1" from App.config to run cross-platform 
> .NET examples with standalone node with default config



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

[jira] [Commented] (IGNITE-7232) .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET examples with standalone node

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7232:


Java examples do not have {{localhost}} in config probably for the same reason.

Fixed in master: {{a2b195ced34af644117fde7cbe43f1fd2cbf9db3}}

> .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET 
> examples with standalone node
> ---
>
> Key: IGNITE-7232
> URL: https://issues.apache.org/jira/browse/IGNITE-7232
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> need to remove localhost="127.0.0.1" from App.config to run cross-platform 
> .NET examples with standalone node with default config



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

[jira] [Commented] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin commented on IGNITE-7233:
--

[~ilyak], [~vveider],
I think this is a duplicate for https://issues.apache.org/jira/browse/IGNITE-898

> Problems with classpath on Windows when IGNITE_HOME contains spaces
> ---
>
> Key: IGNITE-7233
> URL: https://issues.apache.org/jira/browse/IGNITE-7233
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows, cmd, batch files
>Reporter: Ilya Kasnacheev
>Assignee: Peter Ivanov
>  Labels: windows
>
> {code}
> C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
> REM note the white space in directory name ^
> C:\releases\apache-ignite-fabric-2.3.0 bin>set 
> IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
> C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
> %IGNITE_HOME%\config\default.xml
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
> class org.apache.ignite.IgniteException: Failed to create Ignite component 
> (consider adding ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> Ignite component (consider adding ignite-spring module to classpath) 
> [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at 
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding 
> ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your classpath.
> Press any key to continue . . .
> {code}



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

[jira] [Assigned] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Peter Ivanov (JIRA)]

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

Peter Ivanov reassigned IGNITE-7233:


Assignee: Peter Ivanov

> Problems with classpath on Windows when IGNITE_HOME contains spaces
> ---
>
> Key: IGNITE-7233
> URL: https://issues.apache.org/jira/browse/IGNITE-7233
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows, cmd, batch files
>Reporter: Ilya Kasnacheev
>Assignee: Peter Ivanov
>  Labels: windows
>
> {code}
> C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
> REM note the white space in directory name ^
> C:\releases\apache-ignite-fabric-2.3.0 bin>set 
> IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
> C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
> %IGNITE_HOME%\config\default.xml
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
> class org.apache.ignite.IgniteException: Failed to create Ignite component 
> (consider adding ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> Ignite component (consider adding ignite-spring module to classpath) 
> [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at 
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding 
> ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your classpath.
> Press any key to continue . . .
> {code}



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

[jira] [Created] (IGNITE-7234) Optimize TC suites

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-7234:
-

 Summary: Optimize TC suites
 Key: IGNITE-7234
 URL: https://issues.apache.org/jira/browse/IGNITE-7234
 Project: Ignite
  Issue Type: Task
  Components: build
Affects Versions: 2.3
Reporter: Sergey Kozlov


The current organization of test suites on CI servers looks like inefficient. 
We've 90+ test suites and the number of tests is permanently growing.

The plan of optimization might look following:
# Analyze and join short executed suites into single(s) suite
# Analyze execution time of suites (tests) to check ability to split tests into 
regular and long running suites (e.g. Basic and Basic Long, Cache and Cache 
Long, etc)
# Check the approach to compile binaries at once and the run tests against them
# Make the report of distribution of time-execution of tests, for instance:
0-10%: X tests
11-20%: Y tests 
...





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

[jira] [Assigned] (IGNITE-6953) OOM on the client node freezes the whole cluster

[Vitaliy Biryukov (JIRA)]

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

Vitaliy Biryukov reassigned IGNITE-6953:


Assignee: Vitaliy Biryukov

> OOM on the client node freezes the whole cluster
> 
>
> Key: IGNITE-6953
> URL: https://issues.apache.org/jira/browse/IGNITE-6953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Vitaliy Biryukov
>  Labels: iep-5
> Fix For: 2.4
>
>
> It's reported that if an OOM happens on the client side the whole cluster 
> becomes unresponsive:
> http://apache-ignite-users.70518.x6.nabble.com/Out-of-memory-in-client-node-freezes-complete-cluster-td18044.html
> Let's reproduce and prevent this by bringing the client node down 
> automatically.  



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

[jira] [Commented] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7229:


Done, waiting for TC run.

> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Comment Edited] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-7229 at 12/18/17 2:05 PM:
--

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7229 .NET: Rename ICache.QueryFields to Query, add FieldNames



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7229

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

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


was (Author: githubbot):
GitHub user ptupitsyn opened a pull request:

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

IGNITE-7229 .NET: Rename ICache.QueryFields to Query, add FieldNames



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7229

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

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


commit 8abf09fcdcec0a259fcab4345e64db2f5f133f3d
Author: Pavel Tupitsyn 
Date:   2017-12-18T11:37:27Z

IGNITE-7229 .NET: Rename ICache query methods to Query

commit 6758d728b33b53033261011ef8ea7a9a96d5fd46
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:07:49Z

wip

commit 85ec136958c41ac03af585d39e42284e868d4ca3
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:10:42Z

wip

commit 3f55d7383ed0e07269ebfcda472ae9d9642d6e25
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:11:43Z

wip

commit dca634c9173aef0414e661f8b59719a2bb6a69cc
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:13:20Z

Fix obsolete usages

commit 387553edbd69708b0b18afbfe9c7dd877e0fd4f4
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:33:11Z

Fix usages in examples

commit 75d427ef3621d9e2da764221987a019ba68c0816
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:34:45Z

Rename internal method

commit 8ca35ba2a88ccf691af11eb8499ea59b33d13648
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:36:05Z

Fixing all usages

commit ce6e299a89a8e97236c95507f5e24783b03eb350
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:37:41Z

Fixing tests

commit 0b0b02ae4e22408ee47d8d82879399600b6312f1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:00:54Z

Adding FieldNames tests

commit de38b92477b8c3b8f0addc1034904201d6ca2804
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:02:55Z

wip

commit 393d9f2460205a8688556c91163b195c24cedb0f
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:05:12Z

wip

commit dc9376e6c540c51a4e568f574c490de845e4dd10
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:12:41Z

wip

commit 48abd84fe6e19471ed707ec27992621dd5cc5b06
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:18:50Z

Adding field meta call

commit 951adccd0796fa6a955fbdd3356933c042f3b9cf
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:23:43Z

fieldNames done

commit 51c1898b561d73a3e9341c7166705ea06336ac9b
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:31:36Z

wip tests

commit 2b804743787b9e389e864758739516c4dc672ab1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:43:46Z

TestFieldNames done




> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Updated] (IGNITE-7229) .NET: Rename ICache.QueryFields to Query, add FieldNames

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7229:
---
Summary: .NET: Rename ICache.QueryFields to Query, add FieldNames  (was: 
.NET: Rename ICache query methods to Query)

> .NET: Rename ICache.QueryFields to Query, add FieldNames
> 
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Commented] (IGNITE-7229) .NET: Rename ICache query methods to Query

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7229:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-7229 .NET: Rename ICache.QueryFields to Query, add FieldNames



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7229

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

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


commit 8abf09fcdcec0a259fcab4345e64db2f5f133f3d
Author: Pavel Tupitsyn 
Date:   2017-12-18T11:37:27Z

IGNITE-7229 .NET: Rename ICache query methods to Query

commit 6758d728b33b53033261011ef8ea7a9a96d5fd46
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:07:49Z

wip

commit 85ec136958c41ac03af585d39e42284e868d4ca3
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:10:42Z

wip

commit 3f55d7383ed0e07269ebfcda472ae9d9642d6e25
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:11:43Z

wip

commit dca634c9173aef0414e661f8b59719a2bb6a69cc
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:13:20Z

Fix obsolete usages

commit 387553edbd69708b0b18afbfe9c7dd877e0fd4f4
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:33:11Z

Fix usages in examples

commit 75d427ef3621d9e2da764221987a019ba68c0816
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:34:45Z

Rename internal method

commit 8ca35ba2a88ccf691af11eb8499ea59b33d13648
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:36:05Z

Fixing all usages

commit ce6e299a89a8e97236c95507f5e24783b03eb350
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:37:41Z

Fixing tests

commit 0b0b02ae4e22408ee47d8d82879399600b6312f1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:00:54Z

Adding FieldNames tests

commit de38b92477b8c3b8f0addc1034904201d6ca2804
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:02:55Z

wip

commit 393d9f2460205a8688556c91163b195c24cedb0f
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:05:12Z

wip

commit dc9376e6c540c51a4e568f574c490de845e4dd10
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:12:41Z

wip

commit 48abd84fe6e19471ed707ec27992621dd5cc5b06
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:18:50Z

Adding field meta call

commit 951adccd0796fa6a955fbdd3356933c042f3b9cf
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:23:43Z

fieldNames done

commit 51c1898b561d73a3e9341c7166705ea06336ac9b
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:31:36Z

wip tests

commit 2b804743787b9e389e864758739516c4dc672ab1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:43:46Z

TestFieldNames done




> .NET: Rename ICache query methods to Query
> --
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Updated] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-7233:

Labels: windows  (was: )

> Problems with classpath on Windows when IGNITE_HOME contains spaces
> ---
>
> Key: IGNITE-7233
> URL: https://issues.apache.org/jira/browse/IGNITE-7233
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows, cmd, batch files
>Reporter: Ilya Kasnacheev
>  Labels: windows
>
> {code}
> C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
> REM note the white space in directory name ^
> C:\releases\apache-ignite-fabric-2.3.0 bin>set 
> IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
> C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
> %IGNITE_HOME%\config\default.xml
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> Error: Could not find or load main class 
> bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
> bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
> class org.apache.ignite.IgniteException: Failed to create Ignite component 
> (consider adding ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at 
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> Ignite component (consider adding ignite-spring module to classpath) 
> [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at 
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at 
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at 
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding 
> ignite-spring module to classpath) [component=SPRING, 
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your classpath.
> Press any key to continue . . .
> {code}



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

[jira] [Updated] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-7233:

Description: 
{code}
C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
REM note the white space in directory name ^
C:\releases\apache-ignite-fabric-2.3.0 bin>set 
IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
%IGNITE_HOME%\config\default.xml
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
class org.apache.ignite.IgniteException: Failed to create Ignite component 
(consider adding ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
Ignite component (consider adding ignite-spring module to classpath) 
[component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
... 8 more
Failed to start grid: Failed to create Ignite component (consider adding 
ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
Note! You may use 'USER_LIBS' environment variable to specify your classpath.
Press any key to continue . . .
{code}

  was:
{code}
C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
REM note the white space in folder name ^
C:\releases\apache-ignite-fabric-2.3.0 bin>set 
IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
%IGNITE_HOME%\config\default.xml
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
class org.apache.ignite.IgniteException: Failed to create Ignite component 
(consider adding ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
Ignite component (consider adding ignite-spring module to classpath) 
[component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at 

[jira] [Created] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-7233:
---

 Summary: Problems with classpath on Windows when IGNITE_HOME 
contains spaces
 Key: IGNITE-7233
 URL: https://issues.apache.org/jira/browse/IGNITE-7233
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
 Environment: Windows, cmd, batch files
Reporter: Ilya Kasnacheev


{code}
C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
REM note the white space in folder name ^
C:\releases\apache-ignite-fabric-2.3.0 bin>set 
IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
%IGNITE_HOME%\config\default.xml
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
class org.apache.ignite.IgniteException: Failed to create Ignite component 
(consider adding ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
Ignite component (consider adding ignite-spring module to classpath) 
[component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
... 8 more
Failed to start grid: Failed to create Ignite component (consider adding 
ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
Note! You may use 'USER_LIBS' environment variable to specify your classpath.
Press any key to continue . . .
{code}



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

[jira] [Assigned] (IGNITE-7232) .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET examples with standalone node

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-7232:
--

Assignee: Pavel Tupitsyn

> .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET 
> examples with standalone node
> ---
>
> Key: IGNITE-7232
> URL: https://issues.apache.org/jira/browse/IGNITE-7232
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> need to remove localhost="127.0.0.1" from App.config to run cross-platform 
> .NET examples with standalone node with default config



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

[jira] [Created] (IGNITE-7232) .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET examples with standalone node

[Irina Zaporozhtseva (JIRA)]

Irina Zaporozhtseva created IGNITE-7232:
---

 Summary: .NET: remove localhost="127.0.0.1" from App.config to run 
cross-platform .NET examples with standalone node
 Key: IGNITE-7232
 URL: https://issues.apache.org/jira/browse/IGNITE-7232
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.4
Reporter: Irina Zaporozhtseva
 Fix For: 2.4


need to remove localhost="127.0.0.1" from App.config to run cross-platform .NET 
examples with standalone node with default config



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

[jira] [Updated] (IGNITE-4862) NPE in reading data from IGFS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4862:

Fix Version/s: 2.4

> NPE in reading data from IGFS
> -
>
> Key: IGNITE-4862
> URL: https://issues.apache.org/jira/browse/IGNITE-4862
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.9
>Reporter: Dmitry Karachentsev
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.4
>
>
> {noformat}
> D:\app\CodexRT.CodexRT_20170314-1>hadoop\bin\hadoop fs -copyToLocal 
> igfs:///cacheLink/test3.orc D:\test3.orc
> -copyToLocal: Fatal internal error
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$FetchBufferPart.flatten(HadoopIgfsInputStream.java:458)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$DoubleFetchBuffer.flatten(HadoopIgfsInputStream.java:511)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream.read(HadoopIgfsInputStream.java:177)
> at java.io.DataInputStream.read(DataInputStream.java:100)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:91)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:59)
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:119)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination$TargetFileSystem.writeStreamToFile(CommandWithDestination.java:466)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.copyStreamToTarget(CommandWithDestination.java:391)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.copyFileToTarget(CommandWithDestination.java:328)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPath(CommandWithDestination.java:263)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPath(CommandWithDestination.java:248)
> at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:317)
> at 
> org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:289)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processPathArgument(CommandWithDestination.java:243)
> at 
> org.apache.hadoop.fs.shell.Command.processArgument(Command.java:271)
> at 
> org.apache.hadoop.fs.shell.Command.processArguments(Command.java:255)
> at 
> org.apache.hadoop.fs.shell.CommandWithDestination.processArguments(CommandWithDestination.java:220)
> at 
> org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:201)
> at org.apache.hadoop.fs.shell.Command.run(Command.java:165)
> at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
> {noformat}
> Details in discussion: 
> [http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-when-using-IGFS-td11328.html]



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

[jira] [Commented] (IGNITE-7174) Local MLP

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7174:


GitHub user artemmalykh opened a pull request:

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

IGNITE-7174: Local MLP



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

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

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

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


commit b8744c201860b2a5a79982445e27304b6b9c176a
Author: Artem Malykh 
Date:   2017-12-18T11:13:19Z

IGNITE-7174: WIP.

commit 16921b14b5e384e1e15ac91de2e231d52aab24fe
Author: Artem Malykh 
Date:   2017-12-18T11:14:59Z

IGNITE-7174: First version of local MLP.

commit e5ef258e31eff165a0cc754b6c907bfa5b390b44
Author: Artem Malykh 
Date:   2017-12-18T11:27:18Z

IGNITE-7174: Moved zipFolders from matrix api to utils.

commit 0275a58b5565eaff892def5767bba76939d8fb7e
Author: Artem Malykh 
Date:   2017-12-18T11:45:45Z

IGNITE-7174: Some refactorings.

commit 0be2300776ee064ad7d3f84deedd27e1a8f8583f
Author: Artem Malykh 
Date:   2017-12-18T11:52:07Z

IGNITE-7174: Added bias and weight getters.




> Local MLP
> -
>
> Key: IGNITE-7174
> URL: https://issues.apache.org/jira/browse/IGNITE-7174
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
> Fix For: 2.4
>
>
> local version of MLP



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

[jira] [Resolved] (IGNITE-5253) .NET: Fields query cursor metadata

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5253.

   Resolution: Won't Fix
 Assignee: Pavel Tupitsyn
Fix Version/s: 2.4

Done as part of IGNITE-7229

> .NET: Fields query cursor metadata
> --
>
> Key: IGNITE-5253
> URL: https://issues.apache.org/jira/browse/IGNITE-5253
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, sql
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
> Fix For: 2.4
>
>
> Same as IGNITE-5252 for .NET:
> Provide a way to get fields information from the query cursor.



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

[jira] [Commented] (IGNITE-7229) .NET: Rename ICache query methods to Query

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7229:


Let's combine this with IGNITE-5253: new method should return 
{{IFieldsQueryCursor}} (which is already implemented for the thin client).

> .NET: Rename ICache query methods to Query
> --
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Updated] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7231:
--
Attachment: ThreadDump.txt

> Cassandra-sessions-pool is running after Ignition.stop
> --
>
> Key: IGNITE-7231
> URL: https://issues.apache.org/jira/browse/IGNITE-7231
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
> Fix For: 2.4
>
> Attachments: ThreadDump.txt
>
>
> Cassandra-sessions-pool is running after Ignition.stop.



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

[jira] [Created] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7231:
-

 Summary: Cassandra-sessions-pool is running after Ignition.stop
 Key: IGNITE-7231
 URL: https://issues.apache.org/jira/browse/IGNITE-7231
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
Assignee: Mikhail Cherkasov
 Fix For: 2.4


Cassandra-sessions-pool is running after Ignition.stop.




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

[jira] [Assigned] (IGNITE-7230) Improve rebalance logging and metrics

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-7230:


Assignee: Anton Vinogradov

> Improve rebalance logging and metrics
> -
>
> Key: IGNITE-7230
> URL: https://issues.apache.org/jira/browse/IGNITE-7230
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>
> 1) Node's log should contain messages that
> - local node finished rebalancing from other nodes
> - whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)
> 2) We should be able to turn on same logging per cache group.
> - local node finished cache group rebalancing 
> - whole cluster finished cache group rebalancing
> Since cache group is not public. We should log cache names.
> 3) We should update MBean to show progress 
> - % of partitions rebalanced locally 
> - % of partitions rebalanced at cluster



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

[jira] [Updated] (IGNITE-7230) Improve rebalance logging and metrics

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-7230:
-
Description: 
1) Node's log should contain messages that
- local node finished rebalancing from other nodes
- whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)

2) We should be able to turn on same logging per cache group.
- local node finished cache group rebalancing 
- whole cluster finished cache group rebalancing

Since cache group is not public. We should log cache names.

3) We should update MBean to show progress 
- % of partitions rebalanced locally 
- % of partitions rebalanced at cluster

  was:
1) Node's log should contain messages that
- local node finished rebalancing from other nodes
- whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)

2) We should be able to turn on same logging per cache group.
- local node finished cache group rebalancing 
- whole cluster finished cache group rebalancing

3) We should update MBean to show progress 
- % of partitions rebalanced locally 
- % of partitions rebalanced at cluster


> Improve rebalance logging and metrics
> -
>
> Key: IGNITE-7230
> URL: https://issues.apache.org/jira/browse/IGNITE-7230
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Anton Vinogradov
>
> 1) Node's log should contain messages that
> - local node finished rebalancing from other nodes
> - whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)
> 2) We should be able to turn on same logging per cache group.
> - local node finished cache group rebalancing 
> - whole cluster finished cache group rebalancing
> Since cache group is not public. We should log cache names.
> 3) We should update MBean to show progress 
> - % of partitions rebalanced locally 
> - % of partitions rebalanced at cluster



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

[jira] [Comment Edited] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7225 at 12/18/17 11:07 AM:
-

[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts]
 to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number converter to a locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.

Affected pages:
1. Everything that uses grid-export directive to export uigrid data to CSV.
2. page-queries, which uses a custom CSV exporter.


was (Author: klaster_1):
[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts]
 to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number converter to a locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Comment Edited] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7225 at 12/18/17 11:06 AM:
-

[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts]
 to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number converter to a locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.


was (Author: klaster_1):
[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts]
 to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number conver to locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Comment Edited] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7225 at 12/18/17 11:05 AM:
-

[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts]
 to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number conver to locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.


was (Author: klaster_1):
[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts|this
 method] to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number conver to locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Comment Edited] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7225 at 12/18/17 11:05 AM:
-

[~Dmitriyff] please review.

There were two options to go with:
1. Use 
[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat/formatToParts|this
 method] to programmatically access current locale decimal delimeter.
2. Do a simplified, manual parsing of number conver to locale string.

I chose #2 because it was substantially simplier and did not require big 
polyfills.


was (Author: klaster_1):
[~Dmitriyff] please review.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Assigned] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7225:


Assignee: Dmitriy Shabalin  (was: Ilya Borisov)

[~Dmitriyff] please review.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Dmitriy Shabalin
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Commented] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-7225:
--

List of registered users won't use separator behavior implemented in 
IGNITE-7225 until IGNITE-7036 is merged into master.

> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Created] (IGNITE-7230) Improve rebalance logging and metrics

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-7230:


 Summary: Improve rebalance logging and metrics
 Key: IGNITE-7230
 URL: https://issues.apache.org/jira/browse/IGNITE-7230
 Project: Ignite
  Issue Type: New Feature
Reporter: Anton Vinogradov


1) Node's log should contain messages that
- local node finished rebalancing from other nodes
- whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)

2) We should be able to turn on same logging per cache group.
- local node finished cache group rebalancing 
- whole cluster finished cache group rebalancing

3) We should update MBean to show progress 
- % of partitions rebalanced locally 
- % of partitions rebalanced at cluster



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

[jira] [Commented] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-6740:
--

[~avinogradov], I beg for your review.

> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



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

[jira] [Updated] (IGNITE-7229) .NET: Rename ICache query methods to Query

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7229:
---
Description: 
Currently some queries share a single method, while others use a different name.
Rename {{QueryFields}} to {{Query}} to have a more consistent API.
Leave {{QueryContinuous}} as is because it is very different semantically (like 
an event subscription).
Keep old methods and mark them with {{[Obsolete]}}.

* {{ICacheClient}} uses same method name for all queries
* {{IgniteCache}} in Java uses same method name for all queries


  was:
Currently some queries share a single method, while others use a different name.
Rename {{QueryFields}} and {{QueryContinuous}} to {{Query}} to have a more 
consistent API.
Keep old methods and mark them with {{[Obsolete]}}.

* {{ICacheClient}} uses same method name for all queries
* {{IgniteCache}} in Java uses same method name for all queries



> .NET: Rename ICache query methods to Query
> --
>
> Key: IGNITE-7229
> URL: https://issues.apache.org/jira/browse/IGNITE-7229
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Currently some queries share a single method, while others use a different 
> name.
> Rename {{QueryFields}} to {{Query}} to have a more consistent API.
> Leave {{QueryContinuous}} as is because it is very different semantically 
> (like an event subscription).
> Keep old methods and mark them with {{[Obsolete]}}.
> * {{ICacheClient}} uses same method name for all queries
> * {{IgniteCache}} in Java uses same method name for all queries



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

[jira] [Created] (IGNITE-7229) .NET: Rename ICache query methods to Query

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7229:
--

 Summary: .NET: Rename ICache query methods to Query
 Key: IGNITE-7229
 URL: https://issues.apache.org/jira/browse/IGNITE-7229
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Currently some queries share a single method, while others use a different name.
Rename {{QueryFields}} and {{QueryContinuous}} to {{Query}} to have a more 
consistent API.
Keep old methods and mark them with {{[Obsolete]}}.

* {{ICacheClient}} uses same method name for all queries
* {{IgniteCache}} in Java uses same method name for all queries




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

[jira] [Assigned] (IGNITE-5171) Show how to index fields of embedded objects

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5171:
--

Assignee: Denis Magda  (was: Pavel Tupitsyn)

> Show how to index fields of embedded objects
> 
>
> Key: IGNITE-5171
> URL: https://issues.apache.org/jira/browse/IGNITE-5171
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Document and demonstrate how to index and use fields of embedded objects:
> https://apacheignite-sql.readme.io/docs/schema-and-indexes
> For instance, if we have this object
> Person {
> int age;
> int id;
> Addrees addr;
> }
> where Address includes {street and zip} fileds.
> Show how to index {{street}} and {{zip}} and use from SQL.



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

[jira] [Commented] (IGNITE-5171) Show how to index fields of embedded objects

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5171:


[~dmagda] done: 
https://apacheignite-sql.readme.io/v2.3/docs/net-schema-and-indexes#section-indexing-nested-objects

> Show how to index fields of embedded objects
> 
>
> Key: IGNITE-5171
> URL: https://issues.apache.org/jira/browse/IGNITE-5171
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.4
>
>
> Document and demonstrate how to index and use fields of embedded objects:
> https://apacheignite-sql.readme.io/docs/schema-and-indexes
> For instance, if we have this object
> Person {
> int age;
> int id;
> Addrees addr;
> }
> where Address includes {street and zip} fileds.
> Show how to index {{street}} and {{zip}} and use from SQL.



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6625:


SslContextFactory is a non-trivial thing, I've created a ticket instead 
(properties added to ignore list with comment in test): IGNITE-7228

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



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-6625:
--

Assignee: Taras Ledkov  (was: Pavel Tupitsyn)

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



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

[jira] [Created] (IGNITE-7228) .NET: SSL in ClientConnectorConfiguration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7228:
--

 Summary: .NET: SSL in ClientConnectorConfiguration
 Key: IGNITE-7228
 URL: https://issues.apache.org/jira/browse/IGNITE-7228
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Add SSL configuration properties to {{ClientConnectorConfiguration}}.
We should support predefined {{SslContextFactory}} on .NET side.



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

[jira] [Assigned] (IGNITE-7031) Web console: Error on cancellation of comfirm dialog

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-7031:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Added handlers to prevent console errors. Please verify.

> Web console: Error on cancellation of comfirm dialog
> 
>
> Key: IGNITE-7031
> URL: https://issues.apache.org/jira/browse/IGNITE-7031
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>
> On cancellation of confirm dialog error message showed in log of browser.
> F.e. Clone dialog or remove all dialog.



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

[jira] [Assigned] (IGNITE-6785) Affinity field name forced to be upper-case

[Roman Kondakov (JIRA)]

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

Roman Kondakov reassigned IGNITE-6785:
--

Assignee: Roman Kondakov  (was: Vladimir Ozerov)

> Affinity field name forced to be upper-case
> ---
>
> Key: IGNITE-6785
> URL: https://issues.apache.org/jira/browse/IGNITE-6785
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Roman Kondakov
>  Labels: important, usability
> Fix For: 2.4
>
> Attachments: sql_bug.zip
>
>
> If an SQL schema and cache is created with CREATE TABLE command and a user 
> wants to use key-value APIs creating its own custom key class, then (at 
> least) the key  class's affinity field forced to be written in upper-case.
> Steps to reproduce using the project attached:
> * start a node with {{./ignite.sh ../examples/config/example-ignite.xml}}.
> * create {{City}} table using {{ignite_world.sql}}. SQLline is one of the 
> quickest ways: https://apacheignite-sql.readme.io/docs/sqlline
> * Run {{KeyValueDataProcessing}} to catch the exception below
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Binary type has different 
> affinity key fields [typeName=demo.model.CityKey, 
> affKeyFieldName1=COUNTRYCODE, affKeyFieldName2=countryCode]
>   at 
> org.apache.ignite.internal.binary.BinaryUtils.mergeMetadata(BinaryUtils.java:987)
> {noformat} 
> If fact {{CityKey}} names the affinity field in the same way as in CREATE 
> TABLE - {{countryCode}}.
> Next, run {{KeyValueBinaryDataProcessing}} to spot another weird thing:
> * BinaryObject key accepts `countryCode` as the affinity field name.
> * If to print our a binary object value then all the fields are in the 
> upper-case (they were not defined this way in CREATE TABLE):
> {noformat}
> demo.model.City [idHash=1613627715, hash=-1386587499, DISTRICT=Noord-Holland, 
> POPULATION=711200, NAME=Amsterdam]
> {noformat}



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

[jira] [Commented] (IGNITE-3111) .NET: Configure SSL without Spring

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3111:


Provide a way to configure predefined {{SslContextFactory}} from .NET

> .NET: Configure SSL without Spring
> --
>
> Key: IGNITE-3111
> URL: https://issues.apache.org/jira/browse/IGNITE-3111
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> User should be able to configure SLL in .NET terms without Spring and Java 
> KeyStore.
> See https://apacheignite.readme.io/docs/ssltls.



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

[jira] [Created] (IGNITE-7227) Web console: Wrong count of user in filtered table

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7227:
-

 Summary: Web console: Wrong count of user in filtered table
 Key: IGNITE-7227
 URL: https://issues.apache.org/jira/browse/IGNITE-7227
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Open Admin panel
# Select some user
# Filter table.
In label with selected user count showed wrong count of showed rows in table.



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

[jira] [Updated] (IGNITE-7226) Web console: Norification placeholder on empty user table

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-7226:
--
Summary: Web console: Norification placeholder on empty user table  (was: 
Web console: Stub on empty user table)

> Web console: Norification placeholder on empty user table
> -
>
> Key: IGNITE-7226
> URL: https://issues.apache.org/jira/browse/IGNITE-7226
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>
> # Open Admin panel
> # Filter all data in table.
> Table showed without data and any information message.



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

[jira] [Created] (IGNITE-7226) Web console: Stub on empty user table

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7226:
-

 Summary: Web console: Stub on empty user table
 Key: IGNITE-7226
 URL: https://issues.apache.org/jira/browse/IGNITE-7226
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Open Admin panel
# Filter all data in table.
Table showed without data and any information message.



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-6625:
--

Assignee: Pavel Tupitsyn  (was: Taras Ledkov)

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



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6625:


[~tledkov-gridgain] ok I'll add them today.

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



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

[jira] [Commented] (IGNITE-4490) Optimize DML for fast INSERT and MERGE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4490:
-

Test run for latest state (with refactoring): 
https://ci.ignite.apache.org/viewQueued.html?itemId=1003497

> Optimize DML for fast INSERT and MERGE
> --
>
> Key: IGNITE-4490
> URL: https://issues.apache.org/jira/browse/IGNITE-4490
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: performance
>
> It's possible to avoid any SQL querying and map some INSERT and MERGE 
> statements to cache operations in a way similar to that of UPDATE and DELETE 
> - i.e. don't make queries when there are no expressions to evaluate in the 
> query and enhance update plans to perform direct cache operations when INSERT 
> and MERGE affect columns {{_key}} and {{_val}} only.



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

[jira] [Updated] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7225:
-
Description: 
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru_  locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.

  was:
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru_  locale and dot/comma respectively for _en_ . After 
resolving this issue, CSV export will become more aware of user's environment.


> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Updated] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7225:
-
Description: 
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru_  locale and dot/comma respectively for _en_ . After 
resolving this issue, CSV export will become more aware of user's environment.

  was:
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _  locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.


> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru_  locale and dot/comma respectively for 
> _en_ . After resolving this issue, CSV export will become more aware of 
> user's environment.



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

[jira] [Updated] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7225:
-
Description: 
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _  locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.

  was:
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _ locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.


> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru _  locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Updated] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7225:
-
Description: 
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _ locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.

  was:
*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.


> Web console: improve CSV export
> ---
>
> Key: IGNITE-7225
> URL: https://issues.apache.org/jira/browse/IGNITE-7225
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
> Environment: Browsers with ru and en locales.
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>
> *What to do:*
> When exporting to CSV, rely on user's locale and number decimal separator 
> symbol to determine what to use as a CSV separator.
> *Motivation:*
> During export to CSV, numbers are formatted depending on user's locale. In 
> _non-import mode_, MS Excel requires comma as a decimal separator and 
> semicolon as a CSV separator for _ru _ locale and dot/comma respectively for 
> _en_. After resolving this issue, CSV export will become more aware of user's 
> environment.



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

[jira] [Created] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7225:


 Summary: Web console: improve CSV export
 Key: IGNITE-7225
 URL: https://issues.apache.org/jira/browse/IGNITE-7225
 Project: Ignite
  Issue Type: Bug
  Components: wizards
 Environment: Browsers with ru and en locales.
Reporter: Ilya Borisov
Assignee: Ilya Borisov


*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.



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

[jira] [Assigned] (IGNITE-5302) Empty LOST partition may be used as OWNING after resetting lost partitions

[Dmitriy Sorokin (JIRA)]

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

Dmitriy Sorokin reassigned IGNITE-5302:
---

Assignee: (was: Dmitriy Sorokin)

> Empty LOST partition may be used as OWNING after resetting lost partitions
> --
>
> Key: IGNITE-5302
> URL: https://issues.apache.org/jira/browse/IGNITE-5302
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Priority: Blocker
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.4
>
>
> h2. Notes
> Test *testPartitionLossAndRecover* reproducing the issue can be found in 
> ignite-5267 branch with PDS functionality.
> h2. Steps to reproduce
> # Four nodes are started, some key is added to partitioned cache
> # Primary and backup nodes for the key are stopped, key's partition is 
> declared LOST on remaining nodes
> # Primary and backup nodes are started again, cache's lost partitions are 
> reset
> # Key is requested from cache
> h2. Expected behavior
> Correct value is returned from primary for this partition
> h2. Actual behavior
> Request for value is sent to node where partition is empty (not to primary 
> node), null is returned
> h2. Latest findings
> # The main problem with the scenario is that request for key gets mapped not 
> only to P/B nodes with real value but also to the node where that partition 
> existed only in LOST state after P/B shutdown on step #2
> # It was found that on step #3 after primary and backup are joined partition 
> counter is increased for empty partition in LOST state which looks wrong



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

[jira] [Created] (IGNITE-7224) Web console: Remove deprecated fields from configuration

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7224:
-

 Summary: Web console: Remove deprecated fields from configuration
 Key: IGNITE-7224
 URL: https://issues.apache.org/jira/browse/IGNITE-7224
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov


Ignite configuration:
# setMarshaller is deprecated since 2.1.
# setLateAffinityAssignment is always enabled since 2.1.




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

[jira] [Created] (IGNITE-7223) Web console: Double unsaved changes check on import of model

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7223:
-

 Summary: Web console: Double unsaved changes check on import of 
model
 Key: IGNITE-7223
 URL: https://issues.apache.org/jira/browse/IGNITE-7223
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov


# Open model configuration page.
# Make some changes without saving.
# Open import from database dialog.
# Click "Ok" on dialog about unsaved changes.
Dialog about unsaved changes showed second time.
Data is reset to last saved state after first dialog.



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