[jira] [Commented] (IGNITE-9189) IgniteSparkSession can only execute sql in local mode
[ https://issues.apache.org/jira/browse/IGNITE-9189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569746#comment-16569746 ] Valentin Kulichenko commented on IGNITE-9189: - [~lidonghai], can you please describe the issue in more detail? Is there any particular case that is not working correctly? Do you have a unit test for it? > IgniteSparkSession can only execute sql in local mode > - > > Key: IGNITE-9189 > URL: https://issues.apache.org/jira/browse/IGNITE-9189 > Project: Ignite > Issue Type: Bug >Reporter: lidonghai >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9176. -- > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: web-console-cluster-selector > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9176: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: web-console-cluster-selector > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569731#comment-16569731 ] Pavel Konstantinov commented on IGNITE-9176: Re-tested. > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-cluster-selector > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8988) Web console: error in Readme.txt of generated project
[
https://issues.apache.org/jira/browse/IGNITE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569721#comment-16569721
]
Pavel Konstantinov commented on IGNITE-8988:
Re-tested.
> Web console: error in Readme.txt of generated project
> -
>
> Key: IGNITE-8988
> URL: https://issues.apache.org/jira/browse/IGNITE-8988
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: 2.7
>
> Attachments: screenshot-1.png
>
>
> 1. Readme.txt says XML configuration files are located in /config folder, but
> actually its located in src/main/resources/META-INF
> !screenshot-1.png! 2. Error in log on opening of README.txt,
> jdbc-drivers/README.txt and .dockerignore file preview:
> {code:java}
> Uncaught SyntaxError: Unexpected token <{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8988) Web console: error in Readme.txt of generated project
[
https://issues.apache.org/jira/browse/IGNITE-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-8988:
--
Assignee: Alexey Kuznetsov (was: Pavel Konstantinov)
> Web console: error in Readme.txt of generated project
> -
>
> Key: IGNITE-8988
> URL: https://issues.apache.org/jira/browse/IGNITE-8988
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Trivial
> Fix For: 2.7
>
> Attachments: screenshot-1.png
>
>
> 1. Readme.txt says XML configuration files are located in /config folder, but
> actually its located in src/main/resources/META-INF
> !screenshot-1.png! 2. Error in log on opening of README.txt,
> jdbc-drivers/README.txt and .dockerignore file preview:
> {code:java}
> Uncaught SyntaxError: Unexpected token <{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8989) Web console: incorrect initial state of some checkboxes on Client Connector Configuration panel
[ https://issues.apache.org/jira/browse/IGNITE-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8989. -- > Web console: incorrect initial state of some checkboxes on Client Connector > Configuration panel > --- > > Key: IGNITE-8989 > URL: https://issues.apache.org/jira/browse/IGNITE-8989 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > These checkboxes should be ON on UI due to its default value in the source > code is true. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8989) Web console: incorrect initial state of some checkboxes on Client Connector Configuration panel
[ https://issues.apache.org/jira/browse/IGNITE-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569710#comment-16569710 ] Pavel Konstantinov commented on IGNITE-8989: Re-tested. > Web console: incorrect initial state of some checkboxes on Client Connector > Configuration panel > --- > > Key: IGNITE-8989 > URL: https://issues.apache.org/jira/browse/IGNITE-8989 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > These checkboxes should be ON on UI due to its default value in the source > code is true. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8989) Web console: incorrect initial state of some checkboxes on Client Connector Configuration panel
[ https://issues.apache.org/jira/browse/IGNITE-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-8989: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: incorrect initial state of some checkboxes on Client Connector > Configuration panel > --- > > Key: IGNITE-8989 > URL: https://issues.apache.org/jira/browse/IGNITE-8989 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > These checkboxes should be ON on UI due to its default value in the source > code is true. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9118. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9118) Web console: something wrong with Load balancing configuration
[ https://issues.apache.org/jira/browse/IGNITE-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569708#comment-16569708 ] Pavel Konstantinov commented on IGNITE-9118: Re-tested. > Web console: something wrong with Load balancing configuration > -- > > Key: IGNITE-9118 > URL: https://issues.apache.org/jira/browse/IGNITE-9118 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Please see attachment > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9137. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Labels: web-console-UI-UX, web-console-select-node-modal > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569706#comment-16569706 ] Pavel Konstantinov commented on IGNITE-9137: Re-tested. > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Labels: web-console-UI-UX, web-console-select-node-modal > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9163) Web console: incorrect cluster state for clusters of version 1.x
[ https://issues.apache.org/jira/browse/IGNITE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9163. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: incorrect cluster state for clusters of version 1.x > > > Key: IGNITE-9163 > URL: https://issues.apache.org/jira/browse/IGNITE-9163 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Labels: web-console-UI-UX > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Clusters of version 1.x always active -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9163) Web console: incorrect cluster state for clusters of version 1.x
[ https://issues.apache.org/jira/browse/IGNITE-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569705#comment-16569705 ] Pavel Konstantinov commented on IGNITE-9163: Re-tested. > Web console: incorrect cluster state for clusters of version 1.x > > > Key: IGNITE-9163 > URL: https://issues.apache.org/jira/browse/IGNITE-9163 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Labels: web-console-UI-UX > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Clusters of version 1.x always active -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7255) SQL: Failed to execute explain via new "non-caches" API
[
https://issues.apache.org/jira/browse/IGNITE-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-7255.
--
Assignee: Alexey Kuznetsov (was: Pavel Konstantinov)
> SQL: Failed to execute explain via new "non-caches" API
> ---
>
> Key: IGNITE-7255
> URL: https://issues.apache.org/jira/browse/IGNITE-7255
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
>
> I'm executing code via querySqlFieldsNoCache API:
> {code:java}
> qryCursor = ignite.context().query().querySqlFieldsNoCache(qry, true);
> {code}
> And got exception:
> {noformat}
> [CacheException] class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> parse query: EXPLAIN select count(*) from Person
>[IgniteSQLException] Failed to parse query: EXPLAIN select count(*) from
> Person
>[JdbcSQLException] Table "PERSON" not found; SQL statement: EXPLAIN select
> count(*) from Person [42102-195]
> {noformat}
> Second way to reproduce is execution of Explain in Web console when
> *{color:#393939}Use selected cache as default schema name{color}* checkbox is
> disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8979) Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query
[ https://issues.apache.org/jira/browse/IGNITE-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8979. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: Unable to choose the item by the mouse in 'Refresh rate' > dropdown in the Query > --- > > Key: IGNITE-8979 > URL: https://issues.apache.org/jira/browse/IGNITE-8979 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: image-2018-07-11-15-21-02-606.png > > > Open Query screen. > Click on the 'Refresh rate' button and try to select another measurement by > the mouse. > !image-2018-07-11-15-21-02-606.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7255) SQL: Failed to execute explain via new "non-caches" API
[
https://issues.apache.org/jira/browse/IGNITE-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569703#comment-16569703
]
Pavel Konstantinov commented on IGNITE-7255:
Re-tested.
> SQL: Failed to execute explain via new "non-caches" API
> ---
>
> Key: IGNITE-7255
> URL: https://issues.apache.org/jira/browse/IGNITE-7255
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.7
>
>
> I'm executing code via querySqlFieldsNoCache API:
> {code:java}
> qryCursor = ignite.context().query().querySqlFieldsNoCache(qry, true);
> {code}
> And got exception:
> {noformat}
> [CacheException] class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> parse query: EXPLAIN select count(*) from Person
>[IgniteSQLException] Failed to parse query: EXPLAIN select count(*) from
> Person
>[JdbcSQLException] Table "PERSON" not found; SQL statement: EXPLAIN select
> count(*) from Person [42102-195]
> {noformat}
> Second way to reproduce is execution of Explain in Web console when
> *{color:#393939}Use selected cache as default schema name{color}* checkbox is
> disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8979) Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query
[ https://issues.apache.org/jira/browse/IGNITE-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569702#comment-16569702 ] Pavel Konstantinov commented on IGNITE-8979: Re-tested. > Web console: Unable to choose the item by the mouse in 'Refresh rate' > dropdown in the Query > --- > > Key: IGNITE-8979 > URL: https://issues.apache.org/jira/browse/IGNITE-8979 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: image-2018-07-11-15-21-02-606.png > > > Open Query screen. > Click on the 'Refresh rate' button and try to select another measurement by > the mouse. > !image-2018-07-11-15-21-02-606.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8990) Web console: unexpected 'Unsaved changes' warning
[ https://issues.apache.org/jira/browse/IGNITE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569701#comment-16569701 ] Pavel Konstantinov commented on IGNITE-8990: Re-tested. > Web console: unexpected 'Unsaved changes' warning > - > > Key: IGNITE-8990 > URL: https://issues.apache.org/jira/browse/IGNITE-8990 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: ignite-8990.png, screenshot-1.png > > > My steps were: > # Create a new cluster configuration > # Change Client connector configuration > # Save & Download > # Change the cluster name > # Save & Download > # Go to the Monitoring > I getting the warning about unsaved changes > !screenshot-1.png! > The same issue if I select just Save w\o download. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8990) Web console: unexpected 'Unsaved changes' warning
[ https://issues.apache.org/jira/browse/IGNITE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8990. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: unexpected 'Unsaved changes' warning > - > > Key: IGNITE-8990 > URL: https://issues.apache.org/jira/browse/IGNITE-8990 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: ignite-8990.png, screenshot-1.png > > > My steps were: > # Create a new cluster configuration > # Change Client connector configuration > # Save & Download > # Change the cluster name > # Save & Download > # Go to the Monitoring > I getting the warning about unsaved changes > !screenshot-1.png! > The same issue if I select just Save w\o download. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9085) Web console: Actualize Login page carousel images
[ https://issues.apache.org/jira/browse/IGNITE-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9085. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: Actualize Login page carousel images > - > > Key: IGNITE-9085 > URL: https://issues.apache.org/jira/browse/IGNITE-9085 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9085) Web console: Actualize Login page carousel images
[ https://issues.apache.org/jira/browse/IGNITE-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569699#comment-16569699 ] Pavel Konstantinov commented on IGNITE-9085: Re-tested. > Web console: Actualize Login page carousel images > - > > Key: IGNITE-9085 > URL: https://issues.apache.org/jira/browse/IGNITE-9085 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9139) Web console: item from dropdown cannot be selected
[ https://issues.apache.org/jira/browse/IGNITE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9139. -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: item from dropdown cannot be selected > -- > > Key: IGNITE-9139 > URL: https://issues.apache.org/jira/browse/IGNITE-9139 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Query - Result - Chart - Chart Settings - Y axis settings -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9139) Web console: item from dropdown cannot be selected
[ https://issues.apache.org/jira/browse/IGNITE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569695#comment-16569695 ] Pavel Konstantinov commented on IGNITE-9139: Re-tested. > Web console: item from dropdown cannot be selected > -- > > Key: IGNITE-9139 > URL: https://issues.apache.org/jira/browse/IGNITE-9139 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Query - Result - Chart - Chart Settings - Y axis settings -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9176: - Labels: web-console-cluster-selector (was: web-console-monitoring-baseline) > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-cluster-selector > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9176: Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Merged to master. > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-monitoring-baseline > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9151) Web console: incorrect caches list in 'Import from DB' modal
[ https://issues.apache.org/jira/browse/IGNITE-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9151. -- > Web console: incorrect caches list in 'Import from DB' modal > > > Key: IGNITE-9151 > URL: https://issues.apache.org/jira/browse/IGNITE-9151 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: web-console-import-from-db > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Caches list contains already removed caches. > # import from DB, save > # remove all caches > # create cache manually > # import from DB again > - caches list for template contains removed caches -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9151) Web console: incorrect caches list in 'Import from DB' modal
[ https://issues.apache.org/jira/browse/IGNITE-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9151: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: incorrect caches list in 'Import from DB' modal > > > Key: IGNITE-9151 > URL: https://issues.apache.org/jira/browse/IGNITE-9151 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: web-console-import-from-db > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Caches list contains already removed caches. > # import from DB, save > # remove all caches > # create cache manually > # import from DB again > - caches list for template contains removed caches -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9151) Web console: incorrect caches list in 'Import from DB' modal
[ https://issues.apache.org/jira/browse/IGNITE-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569690#comment-16569690 ] Pavel Konstantinov commented on IGNITE-9151: Re-tested. > Web console: incorrect caches list in 'Import from DB' modal > > > Key: IGNITE-9151 > URL: https://issues.apache.org/jira/browse/IGNITE-9151 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-import-from-db > Fix For: 2.7 > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Caches list contains already removed caches. > # import from DB, save > # remove all caches > # create cache manually > # import from DB again > - caches list for template contains removed caches -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9177) Web console: full screen UI issues under Edge
[ https://issues.apache.org/jira/browse/IGNITE-9177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-9177. -- > Web console: full screen UI issues under Edge > - > > Key: IGNITE-9177 > URL: https://issues.apache.org/jira/browse/IGNITE-9177 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-UI-UX, web-console-configuration > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > (1) Basic tab, discovery addresses > !screenshot-1.png! > (2) Advanced tab, User attributes > !screenshot-2.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9177) Web console: full screen UI issues under Edge
[ https://issues.apache.org/jira/browse/IGNITE-9177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569663#comment-16569663 ] Pavel Konstantinov commented on IGNITE-9177: Re-tested. OK. > Web console: full screen UI issues under Edge > - > > Key: IGNITE-9177 > URL: https://issues.apache.org/jira/browse/IGNITE-9177 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-UI-UX, web-console-configuration > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > (1) Basic tab, discovery addresses > !screenshot-1.png! > (2) Advanced tab, User attributes > !screenshot-2.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9189) IgniteSparkSession can only execute sql in local mode
lidonghai created IGNITE-9189: - Summary: IgniteSparkSession can only execute sql in local mode Key: IGNITE-9189 URL: https://issues.apache.org/jira/browse/IGNITE-9189 Project: Ignite Issue Type: Bug Reporter: lidonghai -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov resolved IGNITE-9176. Resolution: Fixed Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: web-console-monitoring-baseline > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
[ https://issues.apache.org/jira/browse/IGNITE-9176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569657#comment-16569657 ] Pavel Konstantinov commented on IGNITE-9176: Tested. Now the error message is shown. > Web console: show authorization exception if user hasn't permission to > activate a cluster > - > > Key: IGNITE-9176 > URL: https://issues.apache.org/jira/browse/IGNITE-9176 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Labels: web-console-monitoring-baseline > Fix For: 2.7 > > > I've faced with an issue that we don't show any error if a user has no > permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8980) Web console: regression on Queries screen
[ https://issues.apache.org/jira/browse/IGNITE-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569649#comment-16569649 ] Pavel Konstantinov commented on IGNITE-8980: Tested. Closed. > Web console: regression on Queries screen > - > > Key: IGNITE-8980 > URL: https://issues.apache.org/jira/browse/IGNITE-8980 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > check box is too small > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8980) Web console: regression on Queries screen
[ https://issues.apache.org/jira/browse/IGNITE-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-8980. -- > Web console: regression on Queries screen > - > > Key: IGNITE-8980 > URL: https://issues.apache.org/jira/browse/IGNITE-8980 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > check box is too small > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569562#comment-16569562 ] Oleg Ignatenko commented on IGNITE-9146: (/) completed low hanging fruits, IDEA coverage report for the branch attached: [^20180805.IgniteMLTestSuite.coverage.zip] > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip, > 20180805.IgniteMLTestSuite.coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-9146: --- Attachment: 20180805.IgniteMLTestSuite.coverage.zip > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip, > 20180805.IgniteMLTestSuite.coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9188) Unexpected eviction leading to data loss in a scenario with stopping/restarting nodes during rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-9188:
--
Description:
Scenario:
1. Split grid nodes in two groups with distinct partition mapping. One group
holds even partitions, other - odd. Rebalancing of "odd" partitions is only
triggered when number of nodes in grid exceeds n/2 threshold.
2. Start n/2 nodes, activate, put data into "even" partitions.
3. Start other n/2 nodes, change BLT, delay rebalancing of "odd" partitions.
4. Stop newly started nodes before rebalancing is finished.
Expected behavior: parttiions in "odd" group will keep owning state.
Actual behavior: "odd" partitions are evicted leading to data loss.
Unit test reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.distributed;
import java.util.ArrayList;
import java.util.Collection;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.UUID;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.affinity.AffinityFunctionContext;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.WALMode;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.processors.cache.GridCacheUtils;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition;
import
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.internal.util.typedef.internal.CU;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.jetbrains.annotations.Nullable;
import static
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionState.OWNING;
/**
*
*/
public class CacheLostPartitionsRestoreStateTest extends GridCommonAbstractTest
{
/** */
public static final long MB = 1024 * 1024L;
/** */
public static final String GRP_ATTR = "grp";
/** */
public static final int GRIDS_CNT = 6;
/** */
public static final String CACHE_1 = "filled";
/** */
public static final String CACHE_2 = "empty";
/** */
public static final String EVEN_GRP = "event";
/** */
public static final String ODD_GRP = "odd";
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
CacheConfiguration ccfg = new CacheConfiguration("default");
ccfg.setAffinity(new RendezvousAffinityFunction(false,
CacheConfiguration.MAX_PARTITIONS_COUNT));
cfg.setCacheConfiguration(ccfg);
cfg.setPeerClassLoadingEnabled(true);
Map attrs = new HashMap<>();
attrs.put(GRP_ATTR,
grp(getTestIgniteInstanceIndex(igniteInstanceName)));
cfg.setUserAttributes(attrs);
DataStorageConfiguration memCfg = new DataStorageConfiguration()
.setDefaultDataRegionConfiguration(
new
DataRegionConfiguration().setPersistenceEnabled(true).setInitialSize(50 *
MB).setMaxSize(50 * MB))
.setWalMode(WALMode.LOG_ONLY);
cfg.setDataStorageConfiguration(memCfg);
cfg.setCacheConfiguration(configuration(CACHE_1),
configuration(CACHE_2));
return cfg;
}
/**
*
[jira] [Updated] (IGNITE-9188) Unexpected eviction leading to data loss in a scenario with stopping/restarting nodes during rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-9188:
--
Description:
Scenario:
1. Split grid nodes in two groups with distinct partition mapping. One group
holds even partitions, other - odd. Rebalancing of "odd" partitions is only
triggered when number of nodes in grid exceeds n/2 threshold.
2. Start n/2 nodes, activate, put data into even partitions.
3. Start other n/2 nodes, change BLT, delay rebalancing of "odd" partitions.
4. Stop newly started nodes before rebalancing is finished.
Expected behavior: parttiions in "odd" group will keep owning state.
Actual behavior: "odd" partitions are evicted leading to data loss.
Unit test reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.distributed;
import java.util.ArrayList;
import java.util.Collection;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.UUID;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.affinity.AffinityFunctionContext;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.WALMode;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.processors.cache.GridCacheUtils;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition;
import
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.internal.util.typedef.internal.CU;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.jetbrains.annotations.Nullable;
import static
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionState.OWNING;
/**
*
*/
public class CacheLostPartitionsRestoreStateTest extends GridCommonAbstractTest
{
/** */
public static final long MB = 1024 * 1024L;
/** */
public static final String GRP_ATTR = "grp";
/** */
public static final int GRIDS_CNT = 6;
/** */
public static final String CACHE_1 = "filled";
/** */
public static final String CACHE_2 = "empty";
/** */
public static final String EVEN_GRP = "event";
/** */
public static final String ODD_GRP = "odd";
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
CacheConfiguration ccfg = new CacheConfiguration("default");
ccfg.setAffinity(new RendezvousAffinityFunction(false,
CacheConfiguration.MAX_PARTITIONS_COUNT));
cfg.setCacheConfiguration(ccfg);
cfg.setPeerClassLoadingEnabled(true);
Map attrs = new HashMap<>();
attrs.put(GRP_ATTR,
grp(getTestIgniteInstanceIndex(igniteInstanceName)));
cfg.setUserAttributes(attrs);
DataStorageConfiguration memCfg = new DataStorageConfiguration()
.setDefaultDataRegionConfiguration(
new
DataRegionConfiguration().setPersistenceEnabled(true).setInitialSize(50 *
MB).setMaxSize(50 * MB))
.setWalMode(WALMode.LOG_ONLY);
cfg.setDataStorageConfiguration(memCfg);
cfg.setCacheConfiguration(configuration(CACHE_1),
configuration(CACHE_2));
return cfg;
}
/**
*
[jira] [Created] (IGNITE-9188) Unexpected eviction leading to data lost in a scenario with stopping/restarting nodes during rebalancing
Alexei Scherbakov created IGNITE-9188:
-
Summary: Unexpected eviction leading to data lost in a scenario
with stopping/restarting nodes during rebalancing
Key: IGNITE-9188
URL: https://issues.apache.org/jira/browse/IGNITE-9188
Project: Ignite
Issue Type: Bug
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
Fix For: 2.7
Scenario:
1. Split grid nodes in two groups with distinct partition mapping. One group
holds even partitions, other - odd. Rebalancing of even partitions is only
triggered when number of nodes in grid exceeds n/2 threshold.
2. Start n/2 nodes, activate, put data into even partitions.
3. Start other n/2 nodes, change BLT, delay rebalancing of even partitions.
4. Stop newly started nodes before rebalancing is finished.
Expected behavior: parttiions in "even" group will keep owning state.
Actual behavior: even partitions are evicted leading to data loss.
Unit test reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.distributed;
import java.util.ArrayList;
import java.util.Collection;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.UUID;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.affinity.AffinityFunctionContext;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.WALMode;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.processors.cache.GridCacheUtils;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition;
import
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage;
import org.apache.ignite.internal.util.typedef.G;
import org.apache.ignite.internal.util.typedef.internal.CU;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.jetbrains.annotations.Nullable;
import static
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionState.OWNING;
/**
*
*/
public class CacheLostPartitionsRestoreStateTest extends GridCommonAbstractTest
{
/** */
public static final long MB = 1024 * 1024L;
/** */
public static final String GRP_ATTR = "grp";
/** */
public static final int GRIDS_CNT = 6;
/** */
public static final String CACHE_1 = "filled";
/** */
public static final String CACHE_2 = "empty";
/** */
public static final String EVEN_GRP = "event";
/** */
public static final String ODD_GRP = "odd";
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
CacheConfiguration ccfg = new CacheConfiguration("default");
ccfg.setAffinity(new RendezvousAffinityFunction(false,
CacheConfiguration.MAX_PARTITIONS_COUNT));
cfg.setCacheConfiguration(ccfg);
cfg.setPeerClassLoadingEnabled(true);
Map attrs = new HashMap<>();
attrs.put(GRP_ATTR,
grp(getTestIgniteInstanceIndex(igniteInstanceName)));
cfg.setUserAttributes(attrs);
DataStorageConfiguration memCfg = new DataStorageConfiguration()
.setDefaultDataRegionConfiguration(
new
DataRegionConfiguration().setPersistenceEnabled(true).setInitialSize(50
[jira] [Updated] (IGNITE-9188) Unexpected eviction leading to data loss in a scenario with stopping/restarting nodes during rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-9188:
--
Summary: Unexpected eviction leading to data loss in a scenario with
stopping/restarting nodes during rebalancing (was: Unexpected eviction leading
to data lost in a scenario with stopping/restarting nodes during rebalancing)
> Unexpected eviction leading to data loss in a scenario with
> stopping/restarting nodes during rebalancing
>
>
> Key: IGNITE-9188
> URL: https://issues.apache.org/jira/browse/IGNITE-9188
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.7
>
>
> Scenario:
> 1. Split grid nodes in two groups with distinct partition mapping. One group
> holds even partitions, other - odd. Rebalancing of even partitions is only
> triggered when number of nodes in grid exceeds n/2 threshold.
> 2. Start n/2 nodes, activate, put data into even partitions.
> 3. Start other n/2 nodes, change BLT, delay rebalancing of even partitions.
> 4. Stop newly started nodes before rebalancing is finished.
> Expected behavior: parttiions in "even" group will keep owning state.
> Actual behavior: even partitions are evicted leading to data loss.
> Unit test reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.internal.processors.cache.distributed;
> import java.util.ArrayList;
> import java.util.Collection;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import java.util.UUID;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.affinity.AffinityFunctionContext;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cluster.ClusterNode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.DataRegionConfiguration;
> import org.apache.ignite.configuration.DataStorageConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.WALMode;
> import org.apache.ignite.internal.TestRecordingCommunicationSpi;
> import org.apache.ignite.internal.processors.cache.GridCacheUtils;
> import
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition;
> import
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage;
> import org.apache.ignite.internal.util.typedef.G;
> import org.apache.ignite.internal.util.typedef.internal.CU;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.lang.IgniteBiPredicate;
> import org.apache.ignite.plugin.extensions.communication.Message;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.jetbrains.annotations.Nullable;
> import static
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionState.OWNING;
> /**
> *
> */
> public class CacheLostPartitionsRestoreStateTest extends
> GridCommonAbstractTest {
> /** */
> public static final long MB = 1024 * 1024L;
> /** */
> public static final String GRP_ATTR = "grp";
> /** */
> public static final int GRIDS_CNT = 6;
> /** */
> public static final String CACHE_1 = "filled";
> /** */
> public static final String CACHE_2 = "empty";
> /** */
> public static final String EVEN_GRP = "event";
> /** */
> public static final String ODD_GRP = "odd";
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setCommunicationSpi(new TestRecordingCommunicationSpi());
>
[jira] [Assigned] (IGNITE-7054) S3 IP finder: support client side encryption
[
https://issues.apache.org/jira/browse/IGNITE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uday Kale reassigned IGNITE-7054:
-
Assignee: Uday Kale
> S3 IP finder: support client side encryption
>
>
> Key: IGNITE-7054
> URL: https://issues.apache.org/jira/browse/IGNITE-7054
> Project: Ignite
> Issue Type: Improvement
> Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.7
>
>
> In case client side encryption [1] is used, it may be required to use
> {{AmazonS3EncryptionClient}} instead of regular {{AmazonS3Client}}. We need
> to add this option to the S3 IP finder, along with any applicable
> configuration parameters.
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7054) S3 IP finder: support client side encryption
[
https://issues.apache.org/jira/browse/IGNITE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569480#comment-16569480
]
Uday Kale commented on IGNITE-7054:
---
[~vkulichenko] is the intention of this task to encryption the node addresses?
> S3 IP finder: support client side encryption
>
>
> Key: IGNITE-7054
> URL: https://issues.apache.org/jira/browse/IGNITE-7054
> Project: Ignite
> Issue Type: Improvement
> Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Priority: Major
> Fix For: 2.7
>
>
> In case client side encryption [1] is used, it may be required to use
> {{AmazonS3EncryptionClient}} instead of regular {{AmazonS3Client}}. We need
> to add this option to the S3 IP finder, along with any applicable
> configuration parameters.
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8915) NPE during executing local SqlQuery from client node
[
https://issues.apache.org/jira/browse/IGNITE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569419#comment-16569419
]
Nikolay Izhikov commented on IGNITE-8915:
-
[~zstan] Did you have a chance to look at patch?
> NPE during executing local SqlQuery from client node
>
>
> Key: IGNITE-8915
> URL: https://issues.apache.org/jira/browse/IGNITE-8915
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Vyacheslav Daradur
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
>
>
> NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
> node.
> [Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
> UPD:
> Right behavior:
> Local query should be forbidden and a sensible exception should be thrown if
> it is executed on client node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8490) Web Console: Update to AngularJS 1.7.x
[ https://issues.apache.org/jira/browse/IGNITE-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8490: - Component/s: wizards > Web Console: Update to AngularJS 1.7.x > -- > > Key: IGNITE-8490 > URL: https://issues.apache.org/jira/browse/IGNITE-8490 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > AngularJS 1.7.0 was released. > We can try to upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9187) Ignite spring data 2.7.0-SNAPSGOT not printing logs
Lokesh Sharma created IGNITE-9187: - Summary: Ignite spring data 2.7.0-SNAPSGOT not printing logs Key: IGNITE-9187 URL: https://issues.apache.org/jira/browse/IGNITE-9187 Project: Ignite Issue Type: Bug Components: spring Affects Versions: 2.7 Environment: Linux Intelij Idea Reporter: Lokesh Sharma I built the "ignite-spring-data_2.0" from source to run it with Spring Boot 2.0.2-RELEASE. The app is running fine but my spring application logging stops working after a few seconds when I run the project. Also "system.out.println" doesn't print anything on the console. Here's my code: [https://github.com/lokeshh/ignite_with_spring_boot_2] I would be very grateful to the community if you fix this issue or help me fix as this is the only that stands in my way to use ignite spring data with spring boot 2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8477) Web console: duration is empty
[ https://issues.apache.org/jira/browse/IGNITE-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8477: - Fix Version/s: (was: 2.7) > Web console: duration is empty > -- > > Key: IGNITE-8477 > URL: https://issues.apache.org/jira/browse/IGNITE-8477 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexander Kalinin >Priority: Major > Attachments: screenshot-1.png > > > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
