[jira] [Resolved] (IGNITE-13262) Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow
[ https://issues.apache.org/jira/browse/IGNITE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-13262. --- Fix Version/s: (was: 2.10) Resolution: Won't Fix This PR conflicts with control utility. > Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow > --- > > Key: IGNITE-13262 > URL: https://issues.apache.org/jira/browse/IGNITE-13262 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 2.8.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Minor > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > Method o.a.i.internal.client.util.GridClientUtils#shutdownNow is a full > duplicate of U#shutdownNow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13262) Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow
[ https://issues.apache.org/jira/browse/IGNITE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-13262. - > Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow > --- > > Key: IGNITE-13262 > URL: https://issues.apache.org/jira/browse/IGNITE-13262 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 2.8.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Minor > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > Method o.a.i.internal.client.util.GridClientUtils#shutdownNow is a full > duplicate of U#shutdownNow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13038) Phase out Ignite Web Console
[ https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172032#comment-17172032 ] Alexey Kuznetsov commented on IGNITE-13038: --- [~dmagda] Web Console issues closed. > Phase out Ignite Web Console > > > Key: IGNITE-13038 > URL: https://issues.apache.org/jira/browse/IGNITE-13038 > Project: Ignite > Issue Type: Improvement >Reporter: Denis A. Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.9 > > Time Spent: 40m > Remaining Estimate: 0h > > The community voted to stop the development and maintenance of Ignite Web > Console: > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html > The following needs to be done: > * Move the tool's source code from the Ignite core to its own repository > (https://github.com/apache/ignite-web-console) > * Update the repository description highlighting that the tool is no longer > supported by the community. > * Unlist Web Console documentation from the navigation and main menus. Do NOT > remove as long as there are many pages referring to the docs. Just hide. > * Put a callout on all the hidden documentation pages saying that the tool's > source code is archived (provide a reference to the repo). > * Close all the JIRA tickets created for Web Console with the notice that the > tool is discontinued and no longer supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-1829) We must use short name for packages in metadata dropdown list
[ https://issues.apache.org/jira/browse/IGNITE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1829. > We must use short name for packages in metadata dropdown list > - > > Key: IGNITE-1829 > URL: https://issues.apache.org/jira/browse/IGNITE-1829 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Pavel Konstantinov >Priority: Critical > Attachments: ig-1829.png > > > Current view is uncomfortable because user don't see class name. > Please see attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-3217) Text input in number field
[ https://issues.apache.org/jira/browse/IGNITE-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3217. > Text input in number field > -- > > Key: IGNITE-3217 > URL: https://issues.apache.org/jira/browse/IGNITE-3217 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Priority: Major > > Create new cluster and try to input text into number field (f.e. Cluster - > General - Port number): > # Field is empty (Chrome) or show text with error message (Firefox or Chrome > for 'e' symbol), > # field in model (backupItem) is not set, > # Buttons "Save" and "Undo all" and "Undo" is available (For empty fields in > chrome), > # On undo of section "Save" and "Undo all" still available. > # Undo does not revert text in number fields. > Also following scenario should be tested: > # Remove all clusters. > # Create new cluster. Save. > # Change some field to "-1" (invalid). DO NOT Save. > # Click "Add cluster" - new cluster created, but invalid field with "-1" is > not cleared. > On cluster page in failover configuration: > Configure custom failover configuration and stay SPI implementation field > empty. > That configuration is saved without any errors. > Also reproduced in cluster binary type configuration for type configuration > table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-1829) We must use short name for packages in metadata dropdown list
[ https://issues.apache.org/jira/browse/IGNITE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1829. -- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > We must use short name for packages in metadata dropdown list > - > > Key: IGNITE-1829 > URL: https://issues.apache.org/jira/browse/IGNITE-1829 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Pavel Konstantinov >Priority: Critical > Attachments: ig-1829.png > > > Current view is uncomfortable because user don't see class name. > Please see attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-2040) Please generate java classes for all metadata linked with caches
[ https://issues.apache.org/jira/browse/IGNITE-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-2040. > Please generate java classes for all metadata linked with caches > > > Key: IGNITE-2040 > URL: https://issues.apache.org/jira/browse/IGNITE-2040 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > > Currently we generates java classes only if cache has store settings. Will be > much useful to generate them always if they are linked to cluster cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-2040) Please generate java classes for all metadata linked with caches
[ https://issues.apache.org/jira/browse/IGNITE-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-2040. -- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Please generate java classes for all metadata linked with caches > > > Key: IGNITE-2040 > URL: https://issues.apache.org/jira/browse/IGNITE-2040 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > > Currently we generates java classes only if cache has store settings. Will be > much useful to generate them always if they are linked to cluster cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-3219) Not work validation of nested forms on save.
[ https://issues.apache.org/jira/browse/IGNITE-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3219. > Not work validation of nested forms on save. > > > Key: IGNITE-3219 > URL: https://issues.apache.org/jira/browse/IGNITE-3219 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Priority: Minor > > # On cluster page add type in binary configuration. > # Input valid type name. > # Input invalid id mapper, name mapper, serializer > # Save cluster. > Cluster saved successfully, fields marked as wrong and validation do not show > them. > Also problem reproduced for Failover configuration -> Custom -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-3217) Text input in number field
[ https://issues.apache.org/jira/browse/IGNITE-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-3217. -- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Text input in number field > -- > > Key: IGNITE-3217 > URL: https://issues.apache.org/jira/browse/IGNITE-3217 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Priority: Major > > Create new cluster and try to input text into number field (f.e. Cluster - > General - Port number): > # Field is empty (Chrome) or show text with error message (Firefox or Chrome > for 'e' symbol), > # field in model (backupItem) is not set, > # Buttons "Save" and "Undo all" and "Undo" is available (For empty fields in > chrome), > # On undo of section "Save" and "Undo all" still available. > # Undo does not revert text in number fields. > Also following scenario should be tested: > # Remove all clusters. > # Create new cluster. Save. > # Change some field to "-1" (invalid). DO NOT Save. > # Click "Add cluster" - new cluster created, but invalid field with "-1" is > not cleared. > On cluster page in failover configuration: > Configure custom failover configuration and stay SPI implementation field > empty. > That configuration is saved without any errors. > Also reproduced in cluster binary type configuration for type configuration > table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-3219) Not work validation of nested forms on save.
[ https://issues.apache.org/jira/browse/IGNITE-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-3219. -- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Not work validation of nested forms on save. > > > Key: IGNITE-3219 > URL: https://issues.apache.org/jira/browse/IGNITE-3219 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Priority: Minor > > # On cluster page add type in binary configuration. > # Input valid type name. > # Input invalid id mapper, name mapper, serializer > # Save cluster. > Cluster saved successfully, fields marked as wrong and validation do not show > them. > Also problem reproduced for Failover configuration -> Custom -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-5494) Web console: Improve admin panel load.
[ https://issues.apache.org/jira/browse/IGNITE-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-5494. -- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Web console: Improve admin panel load. > -- > > Key: IGNITE-5494 > URL: https://issues.apache.org/jira/browse/IGNITE-5494 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.0 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > > * users list requests twice on page load > * incorrect metrics calculation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature
[ https://issues.apache.org/jira/browse/IGNITE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3915. > Web console: add 'copy to clipboard' button in Preview of each section if > browser is supports such feature > -- > > Key: IGNITE-3915 > URL: https://issues.apache.org/jira/browse/IGNITE-3915 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > Labels: web-console-configuration > > https://clipboardjs.com/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-5494) Web console: Improve admin panel load.
[ https://issues.apache.org/jira/browse/IGNITE-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5494. > Web console: Improve admin panel load. > -- > > Key: IGNITE-5494 > URL: https://issues.apache.org/jira/browse/IGNITE-5494 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.0 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > > * users list requests twice on page load > * incorrect metrics calculation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-3915) Web console: add 'copy to clipboard' button in Preview of each section if browser is supports such feature
[ https://issues.apache.org/jira/browse/IGNITE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-3915. -- Web Console was phased out from Ignite in IGNITE-13038. > Web console: add 'copy to clipboard' button in Preview of each section if > browser is supports such feature > -- > > Key: IGNITE-3915 > URL: https://issues.apache.org/jira/browse/IGNITE-3915 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > Labels: web-console-configuration > > https://clipboardjs.com/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8878) Make WebConsole agent logging more verbose.
[ https://issues.apache.org/jira/browse/IGNITE-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8878: - Fix Version/s: (was: 2.10) > Make WebConsole agent logging more verbose. > --- > > Key: IGNITE-8878 > URL: https://issues.apache.org/jira/browse/IGNITE-8878 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Andrey Mashenkov >Priority: Major > > For now it is impossible to debug ssl handshake failures in console agent > as it just log meaningless message with no cause and stacktrace and call > System.exit(1). > > We have to make logging more verbose at debug level at least. > > This is full log of failure: > > [2018-06-26 15:01:54,060][INFO ][main][AgentLauncher] Connecting to: > [https://|https://10.44.38.53/] [x|http://10.44.38.53:8080/] > [.x.x.x|https://10.44.38.53/] > [2018-06-26 15:01:54,233][ERROR][EventThread][AgentLauncher] Failed to > establish SSL connection to server, due to errors with SSL handshake. > [2018-06-26 15:01:54,233][ERROR][EventThread][AgentLauncher] Add to > environment variable JVM_OPTS parameter "-Dtrust.all=true" to skip > certificate validation in case of using self-signed certificate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-4043) Visor CMD: cache scan - support execution on selected node only
[ https://issues.apache.org/jira/browse/IGNITE-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reopened IGNITE-4043: -- > Visor CMD: cache scan - support execution on selected node only > --- > > Key: IGNITE-4043 > URL: https://issues.apache.org/jira/browse/IGNITE-4043 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: RISHIKESH BANSOD >Priority: Major > > See: > http://stackoverflow.com/questions/39887651/get-cache-entrieskeys-values-list-on-particular-node-in-apache-ignite# -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-4043) Visor CMD: cache scan - support execution on selected node only
[ https://issues.apache.org/jira/browse/IGNITE-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4043: - Comment: was deleted (was: Web Console was phased out from Ignite in IGNITE-13038.) > Visor CMD: cache scan - support execution on selected node only > --- > > Key: IGNITE-4043 > URL: https://issues.apache.org/jira/browse/IGNITE-4043 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: RISHIKESH BANSOD >Priority: Major > > See: > http://stackoverflow.com/questions/39887651/get-cache-entrieskeys-values-list-on-particular-node-in-apache-ignite# -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11375) Web console: Show appropriate message in no data component when demo is disabled on agent
[ https://issues.apache.org/jira/browse/IGNITE-11375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11375. --- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Web console: Show appropriate message in no data component when demo is > disabled on agent > - > > Key: IGNITE-11375 > URL: https://issues.apache.org/jira/browse/IGNITE-11375 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Major > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > If the demo is opened and stay only an agent with disabled demo The no data > component should show appropriate message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11375) Web console: Show appropriate message in no data component when demo is disabled on agent
[ https://issues.apache.org/jira/browse/IGNITE-11375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11375. - > Web console: Show appropriate message in no data component when demo is > disabled on agent > - > > Key: IGNITE-11375 > URL: https://issues.apache.org/jira/browse/IGNITE-11375 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Major > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > If the demo is opened and stay only an agent with disabled demo The no data > component should show appropriate message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11403) Web console: 'export all' for scan ignores a filter value
[ https://issues.apache.org/jira/browse/IGNITE-11403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11403. --- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Web console: 'export all' for scan ignores a filter value > - > > Key: IGNITE-11403 > URL: https://issues.apache.org/jira/browse/IGNITE-11403 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > Create a new 'scan', > set some valid filter, > make a scan, > make 'Export All' > Expected - exported file should contain the filtered data only > Actual - all data are exported -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11403) Web console: 'export all' for scan ignores a filter value
[ https://issues.apache.org/jira/browse/IGNITE-11403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11403. - > Web console: 'export all' for scan ignores a filter value > - > > Key: IGNITE-11403 > URL: https://issues.apache.org/jira/browse/IGNITE-11403 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > Create a new 'scan', > set some valid filter, > make a scan, > make 'Export All' > Expected - exported file should contain the filtered data only > Actual - all data are exported -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11556) Add color legend into series selection panel
[ https://issues.apache.org/jira/browse/IGNITE-11556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11556. - > Add color legend into series selection panel > > > Key: IGNITE-11556 > URL: https://issues.apache.org/jira/browse/IGNITE-11556 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Time Spent: 59m > Remaining Estimate: 0h > > Currently we have a series selector for charts, but it lacks color indication > for matching series. Let's add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11556) Add color legend into series selection panel
[ https://issues.apache.org/jira/browse/IGNITE-11556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11556. --- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Add color legend into series selection panel > > > Key: IGNITE-11556 > URL: https://issues.apache.org/jira/browse/IGNITE-11556 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Time Spent: 59m > Remaining Estimate: 0h > > Currently we have a series selector for charts, but it lacks color indication > for matching series. Let's add them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11713) Web console: cluster configuration events content fit issue
[ https://issues.apache.org/jira/browse/IGNITE-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11713. - > Web console: cluster configuration events content fit issue > --- > > Key: IGNITE-11713 > URL: https://issues.apache.org/jira/browse/IGNITE-11713 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Priority: Minor > Attachments: image-2019-04-10-15-46-39-859.png, screenshot-1.png > > > *What happens:* > In master, cluster configuration (2.8) / events / local events listeners > individual event listnered item sub form controls don't fit well when > viewport width is under 1420px: > !image-2019-04-10-15-46-39-859.png! > !screenshot-1.png! > *Expected behavior:* > Form controls should be laid out such they look don't overflow/wrap. > As a solution, I propose to put each control into separate row. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11713) Web console: cluster configuration events content fit issue
[ https://issues.apache.org/jira/browse/IGNITE-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11713. --- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Web console: cluster configuration events content fit issue > --- > > Key: IGNITE-11713 > URL: https://issues.apache.org/jira/browse/IGNITE-11713 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Priority: Minor > Attachments: image-2019-04-10-15-46-39-859.png, screenshot-1.png > > > *What happens:* > In master, cluster configuration (2.8) / events / local events listeners > individual event listnered item sub form controls don't fit well when > viewport width is under 1420px: > !image-2019-04-10-15-46-39-859.png! > !screenshot-1.png! > *Expected behavior:* > Form controls should be laid out such they look don't overflow/wrap. > As a solution, I propose to put each control into separate row. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11714) Web console: multiple select items overflow
[ https://issues.apache.org/jira/browse/IGNITE-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11714. --- Resolution: Won't Fix Web Console was phased out from Ignite in IGNITE-13038. > Web console: multiple select items overflow > --- > > Key: IGNITE-11714 > URL: https://issues.apache.org/jira/browse/IGNITE-11714 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Priority: Minor > Attachments: image-2019-04-10-16-00-55-734.png > > > *What happens:* > !image-2019-04-10-16-00-55-734.png! > *Expected behavior:* > Overflow is handled gracefully, value is contained in control. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11714) Web console: multiple select items overflow
[ https://issues.apache.org/jira/browse/IGNITE-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11714. - > Web console: multiple select items overflow > --- > > Key: IGNITE-11714 > URL: https://issues.apache.org/jira/browse/IGNITE-11714 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Priority: Minor > Attachments: image-2019-04-10-16-00-55-734.png > > > *What happens:* > !image-2019-04-10-16-00-55-734.png! > *Expected behavior:* > Overflow is handled gracefully, value is contained in control. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13321) Control utility doesn't print results to stdout.
[
https://issues.apache.org/jira/browse/IGNITE-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170731#comment-17170731
]
Alexey Kuznetsov commented on IGNITE-13321:
---
[~ivandasch] I revrted my commit. Please close this issue.
I will rework my fix to not break control utility.
> Control utility doesn't print results to stdout.
>
>
> Key: IGNITE-13321
> URL: https://issues.apache.org/jira/browse/IGNITE-13321
> Project: Ignite
> Issue Type: Bug
> Components: control.sh
>Affects Versions: 2.10
>Reporter: Ivan Daschinskiy
>Assignee: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 2.10
>
>
> After merging
> [IGNITE-13262|https://issues.apache.org/jira/browse/IGNITE-13262 ]
> {{control.sh}} doesn't work properly either in dev mode, or in release mode.
> Specifically, no output printed in stdout.
> For example, incorrect output for {{control.sh -baseline set}} after commit
> is:
> {code:sh}
> Control utility [ver. 2.10.0-SNAPSHOT#20200803-sha1:DEV],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:24:33.193,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
>
> {code}
> Correct output for {{control.sh -baseline set}} before commit is:
> {code}
> Control utility [ver. 2.8.1#20200521-sha1:86422096],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:23:55.793,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
> ,
>
> Cluster state: active,
> Current topology version: 3,
> Baseline auto adjustment disabled: softTimeout=30
>Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
> Baseline nodes:
>ConsistentId=ducker02, State=ONLINE, Order=1,
>ConsistentId=ducker03, State=ONLINE, Order=2,
>ConsistentId=ducker04, State=ONLINE, Order=3,
> ,
>
> Number of baseline nodes: 3,
> Other nodes not found.,
> Command [BASELINE] finished with code: 0,
> Control utility has completed execution at: 2020-08-03T14:23:57.351,
> Execution time: 1558 ms
> {code}
> However, command seems to execute and baseline actually changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-13262) Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow
[ https://issues.apache.org/jira/browse/IGNITE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reopened IGNITE-13262: --- > Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow > --- > > Key: IGNITE-13262 > URL: https://issues.apache.org/jira/browse/IGNITE-13262 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 2.8.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.10 > > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > Method o.a.i.internal.client.util.GridClientUtils#shutdownNow is a full > duplicate of U#shutdownNow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13321) Control utility doesn't print results to stdout.
[
https://issues.apache.org/jira/browse/IGNITE-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170683#comment-17170683
]
Alexey Kuznetsov commented on IGNITE-13321:
---
I'll investigate and fix this issue.
> Control utility doesn't print results to stdout.
>
>
> Key: IGNITE-13321
> URL: https://issues.apache.org/jira/browse/IGNITE-13321
> Project: Ignite
> Issue Type: Bug
> Components: control.sh
>Affects Versions: 2.10
>Reporter: Ivan Daschinskiy
>Assignee: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 2.10
>
>
> After merging
> [IGNITE-13262|https://issues.apache.org/jira/browse/IGNITE-13262 ]
> {{control.sh}} doesn't work properly either in dev mode, or in release mode.
> Specifically, no output printed in stdout.
> For example, incorrect output for {{control.sh -baseline set}} after commit
> is:
> {code:sh}
> Control utility [ver. 2.10.0-SNAPSHOT#20200803-sha1:DEV],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:24:33.193,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
>
> {code}
> Correct output for {{control.sh -baseline set}} before commit is:
> {code}
> Control utility [ver. 2.8.1#20200521-sha1:86422096],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:23:55.793,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
> ,
>
> Cluster state: active,
> Current topology version: 3,
> Baseline auto adjustment disabled: softTimeout=30
>Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
> Baseline nodes:
>ConsistentId=ducker02, State=ONLINE, Order=1,
>ConsistentId=ducker03, State=ONLINE, Order=2,
>ConsistentId=ducker04, State=ONLINE, Order=3,
> ,
>
> Number of baseline nodes: 3,
> Other nodes not found.,
> Command [BASELINE] finished with code: 0,
> Control utility has completed execution at: 2020-08-03T14:23:57.351,
> Execution time: 1558 ms
> {code}
> However, command seems to execute and baseline actually changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13303) Update mockito from 1.10.19 to 3.x
[
https://issues.apache.org/jira/browse/IGNITE-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169572#comment-17169572
]
Alexey Kuznetsov edited comment on IGNITE-13303 at 8/2/20, 4:27 PM:
Updated Mockito to 3.4.6. Fixed failed tests. Replaced deprecated classes with
new ones.
[~dmagda] & [~ilyak], please review my PR
was (Author: kuaw26):
Updated Mockito to 3.4.6. Fixed failed tests. Replaced deprecated classes with
new ones.
> Update mockito from 1.10.19 to 3.x
> --
>
> Key: IGNITE-13303
> URL: https://issues.apache.org/jira/browse/IGNITE-13303
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: 2.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.10
>
> Original Estimate: 24h
> Time Spent: 10m
> Remaining Estimate: 23h 50m
>
> We are using very old version of Mockito: 1.10.19
> {panel:title=According to Mockito GitHub:}
> Still on Mockito 1.x? See what's new in Mockito 2!
> Mockito 3 does not introduce any breaking API changes, but now requires Java
> 8 over Java 6 for Mockito 2.{panel}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13303) Update mockito from 1.10.19 to 3.x
[
https://issues.apache.org/jira/browse/IGNITE-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169572#comment-17169572
]
Alexey Kuznetsov commented on IGNITE-13303:
---
Updated Mockito to 3.4.6. Fixed failed tests. Replaced deprecated classes with
new ones.
> Update mockito from 1.10.19 to 3.x
> --
>
> Key: IGNITE-13303
> URL: https://issues.apache.org/jira/browse/IGNITE-13303
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: 2.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.10
>
> Original Estimate: 24h
> Time Spent: 10m
> Remaining Estimate: 23h 50m
>
> We are using very old version of Mockito: 1.10.19
> {panel:title=According to Mockito GitHub:}
> Still on Mockito 1.x? See what's new in Mockito 2!
> Mockito 3 does not introduce any breaking API changes, but now requires Java
> 8 over Java 6 for Mockito 2.{panel}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-6546) Update faveicon.ico in rest-htttp module
[ https://issues.apache.org/jira/browse/IGNITE-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168526#comment-17168526 ] Alexey Kuznetsov commented on IGNITE-6546: -- [~vveider] ignite-rest-http.jar > Update faveicon.ico in rest-htttp module > > > Key: IGNITE-6546 > URL: https://issues.apache.org/jira/browse/IGNITE-6546 > Project: Ignite > Issue Type: Improvement > Components: rest >Reporter: Alexey Kuznetsov >Priority: Major > Fix For: 2.10 > > > Correct icon: https://svn.apache.org/repos/asf/ignite/site/trunk/favicon.ico -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13303) Update mockito from 1.10.19 to 3.x
Alexey Kuznetsov created IGNITE-13303:
-
Summary: Update mockito from 1.10.19 to 3.x
Key: IGNITE-13303
URL: https://issues.apache.org/jira/browse/IGNITE-13303
Project: Ignite
Issue Type: Task
Components: general
Affects Versions: 2.9
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Fix For: 2.10
We are using very old version of Mockito: 1.10.19
{panel:title=According to Mockito GitHub:}
Still on Mockito 1.x? See what's new in Mockito 2!
Mockito 3 does not introduce any breaking API changes, but now requires Java 8
over Java 6 for Mockito 2.{panel}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11942) IGFS and Hadoop Accelerator Discontinuation
[ https://issues.apache.org/jira/browse/IGNITE-11942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165548#comment-17165548 ] Alexey Kuznetsov edited comment on IGNITE-11942 at 7/27/20, 8:57 AM: - [~akalashnikov] Web Console was moved to separate repository (see IGNITE-13038) Looks good to me. was (Author: kuaw26): [~akalashnikov] Looks good to me. > IGFS and Hadoop Accelerator Discontinuation > --- > > Key: IGNITE-11942 > URL: https://issues.apache.org/jira/browse/IGNITE-11942 > Project: Ignite > Issue Type: Task >Reporter: Denis A. Magda >Assignee: Anton Kalashnikov >Priority: Blocker > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > The community has voted for the following decision: > * IGFS and In-Memory Hadoop Accelerator components are to be discontinued and > no longer supported by the community > * The existing source code of IGFS and In-Memory Hadoop Accelerator is to be > removed from Ignite master. Before that, a special branch like > "ignite-igfs-and-hadoop-accelerator" to be forked off the master in order to > preserve the sources in Git history for those who might need it. > The voting thread: > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html > Once the changes are made for Ignite 2.8, please contact Denis Magda to > update a public documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11942) IGFS and Hadoop Accelerator Discontinuation
[ https://issues.apache.org/jira/browse/IGNITE-11942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165548#comment-17165548 ] Alexey Kuznetsov commented on IGNITE-11942: --- [~akalashnikov] Looks good to me. > IGFS and Hadoop Accelerator Discontinuation > --- > > Key: IGNITE-11942 > URL: https://issues.apache.org/jira/browse/IGNITE-11942 > Project: Ignite > Issue Type: Task >Reporter: Denis A. Magda >Assignee: Anton Kalashnikov >Priority: Blocker > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > The community has voted for the following decision: > * IGFS and In-Memory Hadoop Accelerator components are to be discontinued and > no longer supported by the community > * The existing source code of IGFS and In-Memory Hadoop Accelerator is to be > removed from Ignite master. Before that, a special branch like > "ignite-igfs-and-hadoop-accelerator" to be forked off the master in order to > preserve the sources in Git history for those who might need it. > The voting thread: > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html > Once the changes are made for Ignite 2.8, please contact Denis Magda to > update a public documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13262) Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow
[ https://issues.apache.org/jira/browse/IGNITE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-13262: -- Fix Version/s: 2.10 > Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow > --- > > Key: IGNITE-13262 > URL: https://issues.apache.org/jira/browse/IGNITE-13262 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 2.8.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.10 > > Original Estimate: 4h > Time Spent: 10m > Remaining Estimate: 3h 50m > > Method o.a.i.internal.client.util.GridClientUtils#shutdownNow is a full > duplicate of U#shutdownNow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13038) Phase out Ignite Web Console
[
https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163243#comment-17163243
]
Alexey Kuznetsov edited comment on IGNITE-13038 at 7/23/20, 7:02 AM:
-
{panel:title=Branch: [pull/8065/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#cc|titleBGColor=#f7d6c1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit
Code|https://ci.ignite.apache.org/viewLog.html?buildId=5484140]]
{panel}
was (Author: ignitetcbot):
{panel:title=Branch: [pull/8065/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5484140]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5480154buildTypeId=IgniteTests24Java8_RunAll]
> Phase out Ignite Web Console
>
>
> Key: IGNITE-13038
> URL: https://issues.apache.org/jira/browse/IGNITE-13038
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis A. Magda
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.10
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The community voted to stop the development and maintenance of Ignite Web
> Console:
> http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html
> The following needs to be done:
> * Move the tool's source code from the Ignite core to its own repository
> (https://github.com/apache/ignite-web-console)
> * Update the repository description highlighting that the tool is no longer
> supported by the community.
> * Unlist Web Console documentation from the navigation and main menus. Do NOT
> remove as long as there are many pages referring to the docs. Just hide.
> * Put a callout on all the hidden documentation pages saying that the tool's
> source code is archived (provide a reference to the repo).
> * Close all the JIRA tickets created for Web Console with the notice that the
> tool is discontinued and no longer supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13038) Phase out Ignite Web Console
[
https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163243#comment-17163243
]
Alexey Kuznetsov edited comment on IGNITE-13038 at 7/23/20, 7:02 AM:
-
{panel:title=Branch: [pull/8065/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5484140]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5480154buildTypeId=IgniteTests24Java8_RunAll]
was (Author: ignitetcbot):
{panel:title=Branch: [pull/8065/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5484140]]
{panel}
{panel:title=Branch: [pull/8065/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5480132]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=8a3b11fe-afad-4542-aafd-b85539350602, topVer=0,
msgTemplate=null, span=null, nodeId8=dccc70c0, msg=, type=NODE_JOINED,
tstamp=1595311810821], val2=AffinityTopologyVersion
[topVer=1521064462771258804, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=8a3b11fe-afad-4542-aafd-b85539350602, topVer=0,
msgTemplate=null, span=null, nodeId8=dccc70c0, msg=, type=NODE_JOINED,
tstamp=1595311810821], val2=AffinityTopologyVersion
[topVer=1521064462771258804, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=9096eff6371-4217c0ad-0a0e-40c0-9f6b-ed800ad90593, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=e8a9d277-d6f2-4fbb-953a-f1b04bde86e4, topVer=0, msgTemplate=null,
span=null, nodeId8=e8a9d277, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595311810821]], val2=AffinityTopologyVersion
[topVer=-5543092273419277411, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=9096eff6371-4217c0ad-0a0e-40c0-9f6b-ed800ad90593, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=e8a9d277-d6f2-4fbb-953a-f1b04bde86e4, topVer=0, msgTemplate=null,
span=null, nodeId8=e8a9d277, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595311810821]], val2=AffinityTopologyVersion
[topVer=-5543092273419277411, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5480131]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=47c18007371-e3d2ef27-d673-4761-a871-b506cdfba8f4, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=a902d926-053c-47f2-9975-2bd374667c62, topVer=0, msgTemplate=null,
span=null, nodeId8=a902d926, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1595311781229]], val2=AffinityTopologyVersion
[topVer=8312076667784893398, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=287a82da-8ffc-4f1e-a56f-172c71c19557, topVer=0,
msgTemplate=null, span=null, nodeId8=b0714866, msg=, type=NODE_JOINED,
tstamp=1595311781229], val2=AffinityTopologyVersion
[topVer=-6264468474552593226, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=287a82da-8ffc-4f1e-a56f-172c71c19557, topVer=0,
msgTemplate=null, span=null, nodeId8=b0714866, msg=, type=NODE_JOINED,
tstamp=1595311781229], val2=AffinityTopologyVersion
[topVer=-6264468474552593226, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=47c18007371-e3d2ef27-d673-4761-a871-b506cdfba8f4, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[jira] [Commented] (IGNITE-13038) Phase out Ignite Web Console
[ https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163269#comment-17163269 ] Alexey Kuznetsov commented on IGNITE-13038: --- PDS (indexing) also failed in master. > Phase out Ignite Web Console > > > Key: IGNITE-13038 > URL: https://issues.apache.org/jira/browse/IGNITE-13038 > Project: Ignite > Issue Type: Improvement >Reporter: Denis A. Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The community voted to stop the development and maintenance of Ignite Web > Console: > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html > The following needs to be done: > * Move the tool's source code from the Ignite core to its own repository > (https://github.com/apache/ignite-web-console) > * Update the repository description highlighting that the tool is no longer > supported by the community. > * Unlist Web Console documentation from the navigation and main menus. Do NOT > remove as long as there are many pages referring to the docs. Just hide. > * Put a callout on all the hidden documentation pages saying that the tool's > source code is archived (provide a reference to the repo). > * Close all the JIRA tickets created for Web Console with the notice that the > tool is discontinued and no longer supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13038) Phase out Ignite Web Console
[ https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161730#comment-17161730 ] Alexey Kuznetsov edited comment on IGNITE-13038 at 7/21/20, 5:53 AM: - [~dmagda], [~anovikov] and [~vveider] Please review PR. Code of Web Console itself was successfully moved to https://github.com/apache/ignite-web-console with commits history. was (Author: kuaw26): [~dmagda] [~anovikov] [~vveider] Please review PR. Code of Web Console itself was successfully moved to https://github.com/apache/ignite-web-console with commits history. > Phase out Ignite Web Console > > > Key: IGNITE-13038 > URL: https://issues.apache.org/jira/browse/IGNITE-13038 > Project: Ignite > Issue Type: Improvement >Reporter: Denis A. Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > The community voted to stop the development and maintenance of Ignite Web > Console: > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html > The following needs to be done: > * Move the tool's source code from the Ignite core to its own repository > (https://github.com/apache/ignite-web-console) > * Update the repository description highlighting that the tool is no longer > supported by the community. > * Unlist Web Console documentation from the navigation and main menus. Do NOT > remove as long as there are many pages referring to the docs. Just hide. > * Put a callout on all the hidden documentation pages saying that the tool's > source code is archived (provide a reference to the repo). > * Close all the JIRA tickets created for Web Console with the notice that the > tool is discontinued and no longer supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13038) Phase out Ignite Web Console
[ https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161730#comment-17161730 ] Alexey Kuznetsov commented on IGNITE-13038: --- [~dmagda] [~anovikov] [~vveider] Please review PR. Code of Web Console itself was successfully moved to https://github.com/apache/ignite-web-console with commits history. > Phase out Ignite Web Console > > > Key: IGNITE-13038 > URL: https://issues.apache.org/jira/browse/IGNITE-13038 > Project: Ignite > Issue Type: Improvement >Reporter: Denis A. Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > The community voted to stop the development and maintenance of Ignite Web > Console: > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html > The following needs to be done: > * Move the tool's source code from the Ignite core to its own repository > (https://github.com/apache/ignite-web-console) > * Update the repository description highlighting that the tool is no longer > supported by the community. > * Unlist Web Console documentation from the navigation and main menus. Do NOT > remove as long as there are many pages referring to the docs. Just hide. > * Put a callout on all the hidden documentation pages saying that the tool's > source code is archived (provide a reference to the repo). > * Close all the JIRA tickets created for Web Console with the notice that the > tool is discontinued and no longer supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13262) Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow
Alexey Kuznetsov created IGNITE-13262: - Summary: Remove GridClientUtils#shutdownNow() as full duplicate of U#shutdownNow Key: IGNITE-13262 URL: https://issues.apache.org/jira/browse/IGNITE-13262 Project: Ignite Issue Type: Task Components: general Affects Versions: 2.8.1 Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Method o.a.i.internal.client.util.GridClientUtils#shutdownNow is a full duplicate of U#shutdownNow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13246) Implement EVT_BASELINE_XXX events
[ https://issues.apache.org/jira/browse/IGNITE-13246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157109#comment-17157109 ] Alexey Kuznetsov commented on IGNITE-13246: --- LGTM merged to master. > Implement EVT_BASELINE_XXX events > - > > Key: IGNITE-13246 > URL: https://issues.apache.org/jira/browse/IGNITE-13246 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In order to notify external tools we need events EVT_BASELINE_CHANGED, > EVT_BASELINE_AUTO_ADJUST_ENABLED_CHANGED and > EVT_BASELINE_AUTO_ADJUST_AWAITING_TIME_CHANGED to correctly update baseline > info on UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-10914) Web Console: Account email should be unique
[ https://issues.apache.org/jira/browse/IGNITE-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10914. - > Web Console: Account email should be unique > --- > > Key: IGNITE-10914 > URL: https://issues.apache.org/jira/browse/IGNITE-10914 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Attachments: screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > I found that if user click several times on "Sign up" it will result in > several identical accounts created, but only one is allowed. > > To fix we need add unique index for "email" field and prepare migration that > will remove possible duplicates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11166) Web Agent: Host name verifier should be disabled in case of "-Dtrust.all=true".
[ https://issues.apache.org/jira/browse/IGNITE-11166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11166. - > Web Agent: Host name verifier should be disabled in case of > "-Dtrust.all=true". > --- > > Key: IGNITE-11166 > URL: https://issues.apache.org/jira/browse/IGNITE-11166 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > This is a regression after IGNITE-9845 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13105) Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor leak
[
https://issues.apache.org/jira/browse/IGNITE-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13105:
--
Issue Type: Bug (was: Improvement)
> Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor
> leak
> ---
>
> Key: IGNITE-13105
> URL: https://issues.apache.org/jira/browse/IGNITE-13105
> Project: Ignite
> Issue Type: Bug
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This code produce cursor leak in RunningQueryManager:
> If result set contains one ore more rows.
> {code}
> case ONE_VALUE:
> Iterator iter = qryIter.iterator();
> if (iter.hasNext())
> return iter.next().get(0);
> return null;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-11338) Web Console: Current cache "jump" after edit on "Basic configuration" screen
[ https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11338. - > Web Console: Current cache "jump" after edit on "Basic configuration" screen > > > Key: IGNITE-11338 > URL: https://issues.apache.org/jira/browse/IGNITE-11338 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 4h 19m > Remaining Estimate: 0h > > Steps to reproduce: > # Create new cluster. > # Add 3 caches (just click 3 times on "Add new cache") > # Click on first cache with name "Cache" and add a letter "x" to the end of > its name. > # It will "jump" to the end of list. > # And current "editable" item become cache with name "Cache1" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
[
https://issues.apache.org/jira/browse/IGNITE-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13104:
--
Issue Type: Bug (was: Improvement)
> Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
> --
>
> Key: IGNITE-13104
> URL: https://issues.apache.org/jira/browse/IGNITE-13104
> Project: Ignite
> Issue Type: Bug
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> {code}
> /** {@inheritDoc} */
> @Override public void deleteAllById(Iterable ids) {
> if (ids instanceof Set)
> cache.removeAll((Set)ids);
> if (ids instanceof Collection)
> cache.removeAll(new HashSet<>((Collection)ids));
> TreeSet keys = new TreeSet<>();
> for (ID id : ids)
> keys.add(id);
> cache.removeAll(keys);
> }
> {code}
> As you can see cache.removeAll may be executed THREE times in some situations.
> Also this method can throw ClassCast exception if ids collection contains
> objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-10609) Failed to remove cache from service configuration.
[ https://issues.apache.org/jira/browse/IGNITE-10609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10609. - > Failed to remove cache from service configuration. > -- > > Key: IGNITE-10609 > URL: https://issues.apache.org/jira/browse/IGNITE-10609 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > # Add service configuration for some cluster with caches. > # Select any cache > There are not possibility to remove cache selection from service > configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-10433) Web Console: "Import models" dialog doesn't unsubscribe from watching agent after closing
[ https://issues.apache.org/jira/browse/IGNITE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10433. - > Web Console: "Import models" dialog doesn't unsubscribe from watching agent > after closing > - > > Key: IGNITE-10433 > URL: https://issues.apache.org/jira/browse/IGNITE-10433 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > Noticed the next behaviour: > # Open configuration page or cluster edit page. > # Click import when agent is not run. > # Click *Back* button to close *Connection to Ignite Web Agent is not > established* dialog. > # Start and stop web-agent. > *Connection to Ignite Web Agent is not established* dialog is shown. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-10552) Web Agent: Improve logging when cluster topology changed
[ https://issues.apache.org/jira/browse/IGNITE-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10552. - > Web Agent: Improve logging when cluster topology changed > > > Key: IGNITE-10552 > URL: https://issues.apache.org/jira/browse/IGNITE-10552 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > Web Agent can be configured with several URLs of REST addresses in order to > try connect to next address if current address no longer available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-10245) o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid SSL Cipher suite name specified
[ https://issues.apache.org/jira/browse/IGNITE-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10245. - > o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid > SSL Cipher suite name specified > - > > Key: IGNITE-10245 > URL: https://issues.apache.org/jira/browse/IGNITE-10245 > Project: Ignite > Issue Type: Task >Reporter: Alexey Kuznetsov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > This issue is related to IGNITE-10189. > In case of invalid cipher suite name GridNioSslFilter failed with assertion > in org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter#sslHandler method. > Need to investigate and fix. > > See test: ClientSslParametersTest.testNonExistentCipherSuite() -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-9887) A lot of exceptions on cluster deactivation.
[
https://issues.apache.org/jira/browse/IGNITE-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-9887.
> A lot of exceptions on cluster deactivation.
>
>
> Key: IGNITE-9887
> URL: https://issues.apache.org/jira/browse/IGNITE-9887
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexey Kuznetsov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.7
>
>
> Start node with caches configured via config.
> Activate cluster.
> Deactivate cluster - got following exception for almost for all caches.
> {code}
> [2018-10-15
> 10:31:56,715][ERROR][exchange-worker-#44%tester%][IgniteH2Indexing] Failed to
> drop schema on cache stop (will ignore): c_partitioned
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to execute statement: DROP SCHEMA IF EXISTS "c_partitioned"
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:763)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dropSchema(IgniteH2Indexing.java:715)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:3577)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1693)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:885)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1375)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2336)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2488)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2557)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1921)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3265)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2973)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1321)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Невозможно удалить "c_partitioned",
> пока существует зависимый объект "SLEEP, SQUARE, UPPERCASE, _LENGTH_, _CUBE_"
> Cannot drop "c_partitioned" because "SLEEP, SQUARE, UPPERCASE, _LENGTH_,
> _CUBE_" depends on it; SQL statement:
> DROP SCHEMA IF EXISTS "c_partitioned" [90107-197]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.command.ddl.DropSchema.update(DropSchema.java:59)
> at org.h2.command.CommandContainer.update(CommandContainer.java:102)
> at org.h2.command.Command.executeUpdate(Command.java:261)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:169)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:126)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:758)
> ... 17 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys
[ https://issues.apache.org/jira/browse/IGNITE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8554. > Cache metrics: expose metrics with rebalance info about keys > > > Key: IGNITE-8554 > URL: https://issues.apache.org/jira/browse/IGNITE-8554 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexey Kuznetsov >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.7 > > > In order to show info about rebalance progress we need to expose > estimatedRebalancingKeys and rebalancedKeys metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9839. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Time Spent: 7h 7m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog
[ https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8518. > Web Console: Auto focus "Confirm" button in Confirmation dialog > --- > > Key: IGNITE-8518 > URL: https://issues.apache.org/jira/browse/IGNITE-8518 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > > This will allow to confirm from keyboard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-6464) ignite.active() == true, but ignite.utilityCache() may return null
[ https://issues.apache.org/jira/browse/IGNITE-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-6464. > ignite.active() == true, but ignite.utilityCache() may return null > -- > > Key: IGNITE-6464 > URL: https://issues.apache.org/jira/browse/IGNITE-6464 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Kuznetsov >Assignee: Dmitriy Govorukhin >Priority: Major > Fix For: 2.4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-5539) MemoryMetrics.getTotalAllocatedPages return 0 when persistence is enabled
[ https://issues.apache.org/jira/browse/IGNITE-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5539. > MemoryMetrics.getTotalAllocatedPages return 0 when persistence is enabled > - > > Key: IGNITE-5539 > URL: https://issues.apache.org/jira/browse/IGNITE-5539 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov >Assignee: Sergey Chugunov >Priority: Major > Labels: iep-6 > > In memory only mode metrics show some not zero values. > With persistence it shows zero. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-5095) NULL strings in REST-HTTP should be serialized as null
[ https://issues.apache.org/jira/browse/IGNITE-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5095. > NULL strings in REST-HTTP should be serialized as null > -- > > Key: IGNITE-5095 > URL: https://issues.apache.org/jira/browse/IGNITE-5095 > Project: Ignite > Issue Type: Task > Components: clients >Reporter: Alexey Kuznetsov >Assignee: Sergey Kozlov >Priority: Major > Fix For: 2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-4350) Cache JDBC POJO store: improve default data transformation
[ https://issues.apache.org/jira/browse/IGNITE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-4350. > Cache JDBC POJO store: improve default data transformation > -- > > Key: IGNITE-4350 > URL: https://issues.apache.org/jira/browse/IGNITE-4350 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.7 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.0 > > > Improve JdbcTypesDefaultTransformer logic in case when in database column > declared as some TYPE1 and in POJO store same column declared as some TYPE2. > We could try to handle such cases out of the box. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-3964) SQL: implement support for custom table name
[ https://issues.apache.org/jira/browse/IGNITE-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3964. > SQL: implement support for custom table name > > > Key: IGNITE-3964 > URL: https://issues.apache.org/jira/browse/IGNITE-3964 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 1.9 > > > We have ability to specify aliases for columns via > org.apache.ignite.cache.QueryEntity#getAliases. > But how about alias for table name? This could be useful in case of moving > legacy application to Ignite with a lot of SQL statements. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-1178) NPE in GridCacheProcessor.onKernalStop()
[
https://issues.apache.org/jira/browse/IGNITE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-1178.
> NPE in GridCacheProcessor.onKernalStop()
>
>
> Key: IGNITE-1178
> URL: https://issues.apache.org/jira/browse/IGNITE-1178
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.0
>
>
> If user start node with incorrectly configured cache type metadata for
> JdbcPojoStore NPE is raised in onKernalStop. See attached stacktrace:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to initialize property
> 'exceptionOid' for key class 'class
> org.apache.ignite.examples.algofusion.ExceptionMasterKey' and value class
> 'class org.apache.ignite.examples.algofusion.ExceptionMaster'. Make sure
> that one of these classes contains respective getter method or field.
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.buildClassProperty(GridQueryProcessor.java:1342)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processClassMeta(GridQueryProcessor.java:1148)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:149)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:249)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:922)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:779)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at org.apache.ignite.examples.algofusion.AlgoDB.main(AlgoDB.java:89)
> [15:45:29,007][ERROR][main][IgniteKernal] Failed to pre-stop processor:
> GridProcessorAdapter []
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.GridCacheEventManager.isRecordable(GridCacheEventManager.java:342)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1089)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:896)
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1706)
> at
> org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1650)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:852)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at org.apache.ignite.examples.algofusion.AlgoDB.main(AlgoDB.java:89)
> [15:45:29] Ignite node stopped wih ERRORS [uptime=00:00:02:515]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-3592) Provide some kind of pluggable compression SPI support
[ https://issues.apache.org/jira/browse/IGNITE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-3592. > Provide some kind of pluggable compression SPI support > -- > > Key: IGNITE-3592 > URL: https://issues.apache.org/jira/browse/IGNITE-3592 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Alexey Kuznetsov >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.3 > > > It may be useful in some cases to compress data stored in cache. > And in order to give access to compressed data from SQL engine this support > should be implemented in ignite-core level. > See discussion on dev-list: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-1152) Distribution of backup partitions is not uniform
[ https://issues.apache.org/jira/browse/IGNITE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1152. > Distribution of backup partitions is not uniform > > > Key: IGNITE-1152 > URL: https://issues.apache.org/jira/browse/IGNITE-1152 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Goncharuk >Priority: Minor > Attachments: CacheBackupPartitionsTest.java > > > I started 4 nodes with partitioned cache with 1 backup. > And found that primary parts more or less uniform, but backup parts - not: > Node n1: : pri=244, bak=367 > Node n2: : pri=260, bak=590 > Node n3: : pri=244, bak=367 > Node n4: : pri=260, bak=590 > Code to test this issue attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-844) Create tests for queries configured via CacheTypeMetadata
[ https://issues.apache.org/jira/browse/IGNITE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-844. --- > Create tests for queries configured via CacheTypeMetadata > - > > Key: IGNITE-844 > URL: https://issues.apache.org/jira/browse/IGNITE-844 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-755) Add example for Query + CacheTypeMetadata
[ https://issues.apache.org/jira/browse/IGNITE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-755. --- > Add example for Query + CacheTypeMetadata > - > > Key: IGNITE-755 > URL: https://issues.apache.org/jira/browse/IGNITE-755 > Project: Ignite > Issue Type: Task >Reporter: Alexey Kuznetsov >Priority: Major > Attachments: > 0001-IGNITE-755-Implemented-example-of-cache-type-metadat.patch > > > Check content for page > https://dash.readme.io/project/apacheignite/v1.3/suggested/update/556e697efc3aa80d00e1a8f2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-735) Need to add support for dynamic indexes
[ https://issues.apache.org/jira/browse/IGNITE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-735. --- > Need to add support for dynamic indexes > --- > > Key: IGNITE-735 > URL: https://issues.apache.org/jira/browse/IGNITE-735 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexey Kuznetsov >Assignee: Sergei Vladykin >Priority: Major > Fix For: 2.0 > > > We should support dynamic index creation and deletion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-369) Cache manager should switch cache statisticsEnabled property globaly
[ https://issues.apache.org/jira/browse/IGNITE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-369. --- Feature released. > Cache manager should switch cache statisticsEnabled property globaly > > > Key: IGNITE-369 > URL: https://issues.apache.org/jira/browse/IGNITE-369 > Project: Ignite > Issue Type: Task >Affects Versions: sprint-2 >Reporter: Alexey Kuznetsov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-6 > Fix For: 2.4 > > > Also you should take care about new nodes that joining grid. > New node could have statisticsEnabled with opposite value that nodes in grid. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-186) Access to IgniteFS via Visorcmd
[ https://issues.apache.org/jira/browse/IGNITE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-186. - Resolution: Won't Fix IGFS was dropped from Ignite. > Access to IgniteFS via Visorcmd > --- > > Key: IGNITE-186 > URL: https://issues.apache.org/jira/browse/IGNITE-186 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Major > > Now IgniteFS is part of Ignite-fabric and doesn't need hadoop libs anymore. > But hadoop provided access to IgniteFS via hadoop fs. > I suggest to introduce following: > 1. Add support filesystem commands by visorcmd similar hadoop fs > 2. Add command-line option to visorcmd to execute an one command and exit, > for instance: > bin/visorcmd.sh -e mkdir /123 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-186) Access to IgniteFS via Visorcmd
[ https://issues.apache.org/jira/browse/IGNITE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-186. --- > Access to IgniteFS via Visorcmd > --- > > Key: IGNITE-186 > URL: https://issues.apache.org/jira/browse/IGNITE-186 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Major > > Now IgniteFS is part of Ignite-fabric and doesn't need hadoop libs anymore. > But hadoop provided access to IgniteFS via hadoop fs. > I suggest to introduce following: > 1. Add support filesystem commands by visorcmd similar hadoop fs > 2. Add command-line option to visorcmd to execute an one command and exit, > for instance: > bin/visorcmd.sh -e mkdir /123 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns
[ https://issues.apache.org/jira/browse/IGNITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-184. --- > visorcmd: improve auto-calculation of width of table columns > > > Key: IGNITE-184 > URL: https://issues.apache.org/jira/browse/IGNITE-184 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Major > Attachments: gg-8723.png > > > I suggest to use following logic: > if parameter value is a set of values separated by space then print this > separated values from new line > Use terminal width to determine table columns maximum width > see attached screenshot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns
[ https://issues.apache.org/jira/browse/IGNITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-184. - Resolution: Won't Fix VisorCMD will be replaced by control.sh soon > visorcmd: improve auto-calculation of width of table columns > > > Key: IGNITE-184 > URL: https://issues.apache.org/jira/browse/IGNITE-184 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Major > Attachments: gg-8723.png > > > I suggest to use following logic: > if parameter value is a set of values separated by space then print this > separated values from new line > Use terminal width to determine table columns maximum width > see attached screenshot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13038) Phase out Ignite Web Console
[ https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17133322#comment-17133322 ] Alexey Kuznetsov commented on IGNITE-13038: --- [~dmagda] It is OK or not if I move Ignite Web Console source code to (https://github.com/apache/ignite-web-console) as a single commit? The history of commits will be lost. However history will remain in original repository in branches of previous releases. Please confirm. > Phase out Ignite Web Console > > > Key: IGNITE-13038 > URL: https://issues.apache.org/jira/browse/IGNITE-13038 > Project: Ignite > Issue Type: Improvement >Reporter: Denis A. Magda >Assignee: Alexey Kuznetsov >Priority: Critical > Fix For: 2.9 > > > The community voted to stop the development and maintenance of Ignite Web > Console: > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html > The following needs to be done: > * Move the tool's source code from the Ignite core to its own repository > (https://github.com/apache/ignite-web-console) > * Update the repository description highlighting that the tool is no longer > supported by the community. > * Unlist Web Console documentation from the navigation and main menus. Do NOT > remove as long as there are many pages referring to the docs. Just hide. > * Put a callout on all the hidden documentation pages saying that the tool's > source code is archived (provide a reference to the repo). > * Close all the JIRA tickets created for Web Console with the notice that the > tool is discontinued and no longer supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13105) Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor leak
[
https://issues.apache.org/jira/browse/IGNITE-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13105:
--
Release Note: Fixed cursors leakage in RunningQueryManager when executing
queries via spring-data repositories. (was: Fixed cursors leakage in
RunningQueryManager when executing queries vis spring-data repositories. )
> Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor
> leak
> ---
>
> Key: IGNITE-13105
> URL: https://issues.apache.org/jira/browse/IGNITE-13105
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This code produce cursor leak in RunningQueryManager:
> If result set contains one ore more rows.
> {code}
> case ONE_VALUE:
> Iterator iter = qryIter.iterator();
> if (iter.hasNext())
> return iter.next().get(0);
> return null;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13105) Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor leak
[
https://issues.apache.org/jira/browse/IGNITE-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13105:
--
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor
> leak
> ---
>
> Key: IGNITE-13105
> URL: https://issues.apache.org/jira/browse/IGNITE-13105
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code produce cursor leak in RunningQueryManager:
> If result set contains one ore more rows.
> {code}
> case ONE_VALUE:
> Iterator iter = qryIter.iterator();
> if (iter.hasNext())
> return iter.next().get(0);
> return null;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
[
https://issues.apache.org/jira/browse/IGNITE-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13104:
--
Release Note: Fixed incorrect processing of non-comparable keys in
spring-data for repository methods: findAllById(ids) and deleteAllById(ids).
> Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
> --
>
> Key: IGNITE-13104
> URL: https://issues.apache.org/jira/browse/IGNITE-13104
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> /** {@inheritDoc} */
> @Override public void deleteAllById(Iterable ids) {
> if (ids instanceof Set)
> cache.removeAll((Set)ids);
> if (ids instanceof Collection)
> cache.removeAll(new HashSet<>((Collection)ids));
> TreeSet keys = new TreeSet<>();
> for (ID id : ids)
> keys.add(id);
> cache.removeAll(keys);
> }
> {code}
> As you can see cache.removeAll may be executed THREE times in some situations.
> Also this method can throw ClassCast exception if ids collection contains
> objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
[
https://issues.apache.org/jira/browse/IGNITE-13104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-13104:
--
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
> --
>
> Key: IGNITE-13104
> URL: https://issues.apache.org/jira/browse/IGNITE-13104
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
>Affects Versions: 2.8.1
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> /** {@inheritDoc} */
> @Override public void deleteAllById(Iterable ids) {
> if (ids instanceof Set)
> cache.removeAll((Set)ids);
> if (ids instanceof Collection)
> cache.removeAll(new HashSet<>((Collection)ids));
> TreeSet keys = new TreeSet<>();
> for (ID id : ids)
> keys.add(id);
> cache.removeAll(keys);
> }
> {code}
> As you can see cache.removeAll may be executed THREE times in some situations.
> Also this method can throw ClassCast exception if ids collection contains
> objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-5617) Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent storage
[ https://issues.apache.org/jira/browse/IGNITE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-5617. -- Resolution: Won't Fix Web Console was discontinued. > Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent > storage > - > > Key: IGNITE-5617 > URL: https://issues.apache.org/jira/browse/IGNITE-5617 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 2.25h > Remaining Estimate: 0h > > As of new persistent storage donated to Ignite it make sense to > migrate from MongoDB+NodeJS to use some Java-based Web Server + Ignite+PS. > This will give fault tolerance Out Of The Box and minimize third-party > dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-5617) Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent storage
[ https://issues.apache.org/jira/browse/IGNITE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-5617. > Web Console: Rework backend from MongoDB+NodeJS to Java + Ignite + Persistent > storage > - > > Key: IGNITE-5617 > URL: https://issues.apache.org/jira/browse/IGNITE-5617 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 2.25h > Remaining Estimate: 0h > > As of new persistent storage donated to Ignite it make sense to > migrate from MongoDB+NodeJS to use some Java-based Web Server + Ignite+PS. > This will give fault tolerance Out Of The Box and minimize third-party > dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13105) Spring data 2.0 IgniteRepositoryQuery#transformQueryCursor contains cursor leak
Alexey Kuznetsov created IGNITE-13105:
-
Summary: Spring data 2.0
IgniteRepositoryQuery#transformQueryCursor contains cursor leak
Key: IGNITE-13105
URL: https://issues.apache.org/jira/browse/IGNITE-13105
Project: Ignite
Issue Type: Improvement
Components: springdata
Affects Versions: 2.8.1
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Fix For: 2.9
This code produce cursor leak in RunningQueryManager:
If result set contains one ore more rows.
{code}
case ONE_VALUE:
Iterator iter = qryIter.iterator();
if (iter.hasNext())
return iter.next().get(0);
return null;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13104) Spring data 2.0 IgniteRepositoryImpl#deleteAllById contains wrong code
Alexey Kuznetsov created IGNITE-13104:
-
Summary: Spring data 2.0 IgniteRepositoryImpl#deleteAllById
contains wrong code
Key: IGNITE-13104
URL: https://issues.apache.org/jira/browse/IGNITE-13104
Project: Ignite
Issue Type: Improvement
Components: springdata
Affects Versions: 2.8.1
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Fix For: 2.9
{code}
/** {@inheritDoc} */
@Override public void deleteAllById(Iterable ids) {
if (ids instanceof Set)
cache.removeAll((Set)ids);
if (ids instanceof Collection)
cache.removeAll(new HashSet<>((Collection)ids));
TreeSet keys = new TreeSet<>();
for (ID id : ids)
keys.add(id);
cache.removeAll(keys);
}
{code}
As you can see cache.removeAll may be executed THREE times in some situations.
Also this method can throw ClassCast exception if ids collection contains
objects that are not implement Comparable interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12630) Remove developers sections from parent pom.xml
[ https://issues.apache.org/jira/browse/IGNITE-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031867#comment-17031867 ] Alexey Kuznetsov commented on IGNITE-12630: --- Looks good to me. > Remove developers sections from parent pom.xml > -- > > Key: IGNITE-12630 > URL: https://issues.apache.org/jira/browse/IGNITE-12630 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We have a section in parent/pom.xml. Listed info in fact is > outdated and it is not practical and useful to enumerate everyone in this > section. Moreover the proper position here is that the project is developed > by Apache Ignite Community. > Let's remove this section. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12613) Scala (Visor Console) test failed on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-12613: -- Fix Version/s: 2.9 > Scala (Visor Console) test failed on Java 9+ > > > Key: IGNITE-12613 > URL: https://issues.apache.org/jira/browse/IGNITE-12613 > Project: Ignite > Issue Type: Improvement > Components: visor >Affects Versions: mas >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Failed test on TC agents with Java 9+ > [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] > Noticed that Scala libraries and scalatest library are different for > different java versions. > Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12613) Scala (Visor Console) test failed on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-12613: -- Fix Version/s: (was: mas) > Scala (Visor Console) test failed on Java 9+ > > > Key: IGNITE-12613 > URL: https://issues.apache.org/jira/browse/IGNITE-12613 > Project: Ignite > Issue Type: Improvement > Components: visor >Affects Versions: mas >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Failed test on TC agents with Java 9+ > [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] > Noticed that Scala libraries and scalatest library are different for > different java versions. > Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12613) Scala (Visor Console) test failed on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028879#comment-17028879 ] Alexey Kuznetsov commented on IGNITE-12613: --- Looks good to me. > Scala (Visor Console) test failed on Java 9+ > > > Key: IGNITE-12613 > URL: https://issues.apache.org/jira/browse/IGNITE-12613 > Project: Ignite > Issue Type: Improvement > Components: visor >Affects Versions: mas >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: mas > > Time Spent: 10m > Remaining Estimate: 0h > > Failed test on TC agents with Java 9+ > [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaVisorConsole/4975900] > Noticed that Scala libraries and scalatest library are different for > different java versions. > Scala libraries and scalatest library should be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11906) Scalar examples fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023461#comment-17023461 ] Alexey Kuznetsov commented on IGNITE-11906: --- [~ilyak] Looks good to me. > Scalar examples fails on TC > --- > > Key: IGNITE-11906 > URL: https://issues.apache.org/jira/browse/IGNITE-11906 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Nikolay Izhikov >Assignee: Ilya Kasnacheev >Priority: Major > Labels: scala > Time Spent: 10m > Remaining Estimate: 0h > > Scalar examples tests fails in master. > https://ci.ignite.apache.org/viewLog.html?buildId=4085544=buildResultsDiv=IgniteTests24Java8_ScalaExamples -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11601) The 'Save and Download' action saves wrong cluster
[ https://issues.apache.org/jira/browse/IGNITE-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-11601: - Assignee: (was: Ilya Borisov) > The 'Save and Download' action saves wrong cluster > -- > > Key: IGNITE-11601 > URL: https://issues.apache.org/jira/browse/IGNITE-11601 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Priority: Major > Fix For: 2.9 > > Attachments: screenshot-1.png > > Time Spent: 0.25h > Remaining Estimate: 0h > > Create the first cluster, save and download - all works right > Create a second cluster, save and download - a first cluster actually saved > !screenshot-1.png! > The workaround is to click on 'See project structure' before saving the > project -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
[ https://issues.apache.org/jira/browse/IGNITE-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947135#comment-16947135 ] Alexey Kuznetsov commented on IGNITE-10032: --- [~mmuzaf] I closed this issue as "Won't Fix". It is turned out that correct fix is not so easy to implement and test. > Web Agent: Optimize collecting topology from cluster > > > Key: IGNITE-10032 > URL: https://issues.apache.org/jira/browse/IGNITE-10032 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In current implementation Web Agent collect every 5 seconds topology via REST > with attributes. But attributes are immutable and can be collected only when > topology changed. > We can cache node IDs and collect lightweight topology on every 5 seconds and > if we detected that topology changed - collect full topology with attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
[ https://issues.apache.org/jira/browse/IGNITE-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-10032: - Assignee: Alexey Kuznetsov Resolution: Won't Fix > Web Agent: Optimize collecting topology from cluster > > > Key: IGNITE-10032 > URL: https://issues.apache.org/jira/browse/IGNITE-10032 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In current implementation Web Agent collect every 5 seconds topology via REST > with attributes. But attributes are immutable and can be collected only when > topology changed. > We can cache node IDs and collect lightweight topology on every 5 seconds and > if we detected that topology changed - collect full topology with attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
[ https://issues.apache.org/jira/browse/IGNITE-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10032. - > Web Agent: Optimize collecting topology from cluster > > > Key: IGNITE-10032 > URL: https://issues.apache.org/jira/browse/IGNITE-10032 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In current implementation Web Agent collect every 5 seconds topology via REST > with attributes. But attributes are immutable and can be collected only when > topology changed. > We can cache node IDs and collect lightweight topology on every 5 seconds and > if we detected that topology changed - collect full topology with attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
[ https://issues.apache.org/jira/browse/IGNITE-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-10032: -- Fix Version/s: (was: 2.8) > Web Agent: Optimize collecting topology from cluster > > > Key: IGNITE-10032 > URL: https://issues.apache.org/jira/browse/IGNITE-10032 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In current implementation Web Agent collect every 5 seconds topology via REST > with attributes. But attributes are immutable and can be collected only when > topology changed. > We can cache node IDs and collect lightweight topology on every 5 seconds and > if we detected that topology changed - collect full topology with attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
[ https://issues.apache.org/jira/browse/IGNITE-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-10032: - Assignee: (was: Alexey Kuznetsov) > Web Agent: Optimize collecting topology from cluster > > > Key: IGNITE-10032 > URL: https://issues.apache.org/jira/browse/IGNITE-10032 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In current implementation Web Agent collect every 5 seconds topology via REST > with attributes. But attributes are immutable and can be collected only when > topology changed. > We can cache node IDs and collect lightweight topology on every 5 seconds and > if we detected that topology changed - collect full topology with attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-4677) Incorrect connectable node detection in router mode for Java thin client
[
https://issues.apache.org/jira/browse/IGNITE-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov resolved IGNITE-4677.
--
Resolution: Won't Fix
No one interested.
> Incorrect connectable node detection in router mode for Java thin client
>
>
> Key: IGNITE-4677
> URL: https://issues.apache.org/jira/browse/IGNITE-4677
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Major
>
> * In case of connect using Java client to localhost: in router mode all
> nodes listen same localhost: on other hosts will be marked as
> connectable.
> {code}
> boolean noAttrsAndMetrics = (metricsCache && attrCache) ||
> (node.attributes().isEmpty() && node.metrics() == null);
> boolean reachable = noAttrsAndMetrics || ...
> {code}
> * Under Windows org.apache.ignite.internal.util.IgniteUtils#allLocalIps
> return same mac: 00-00-00-00-00-00-00-E0 on different hosts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-4677) Incorrect connectable node detection in router mode for Java thin client
[
https://issues.apache.org/jira/browse/IGNITE-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-4677.
> Incorrect connectable node detection in router mode for Java thin client
>
>
> Key: IGNITE-4677
> URL: https://issues.apache.org/jira/browse/IGNITE-4677
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Major
>
> * In case of connect using Java client to localhost: in router mode all
> nodes listen same localhost: on other hosts will be marked as
> connectable.
> {code}
> boolean noAttrsAndMetrics = (metricsCache && attrCache) ||
> (node.attributes().isEmpty() && node.metrics() == null);
> boolean reachable = noAttrsAndMetrics || ...
> {code}
> * Under Windows org.apache.ignite.internal.util.IgniteUtils#allLocalIps
> return same mac: 00-00-00-00-00-00-00-E0 on different hosts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-6943) Web console: LoadCaches method should activate cluster if persistent is configured, otherwise method doesn't work due to cluster is inactive
[ https://issues.apache.org/jira/browse/IGNITE-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-6943: Assignee: (was: Vasiliy Sisko) > Web console: LoadCaches method should activate cluster if persistent is > configured, otherwise method doesn't work due to cluster is inactive > > > Key: IGNITE-6943 > URL: https://issues.apache.org/jira/browse/IGNITE-6943 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.3 >Reporter: Pavel Konstantinov >Priority: Major > > Web console can generate sample project. > Now we have a persistence feature. > Cluster with persistence started inactive and generated LoadCaches will not > work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-8333) Web console: Editors for table values have wrong baseline
[ https://issues.apache.org/jira/browse/IGNITE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8333. > Web console: Editors for table values have wrong baseline > - > > Key: IGNITE-8333 > URL: https://issues.apache.org/jira/browse/IGNITE-8333 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Vasiliy Sisko >Assignee: Ilya Borisov >Priority: Minor > Attachments: Selection_120.png, Selection_121.png > > > Baseline for table editor is higher than label baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-8333) Web console: Editors for table values have wrong baseline
[ https://issues.apache.org/jira/browse/IGNITE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-8333. -- Resolution: Won't Fix This very minor issue we can leave it as is. > Web console: Editors for table values have wrong baseline > - > > Key: IGNITE-8333 > URL: https://issues.apache.org/jira/browse/IGNITE-8333 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Vasiliy Sisko >Assignee: Ilya Borisov >Priority: Major > Attachments: Selection_120.png, Selection_121.png > > > Baseline for table editor is higher than label baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8333) Web console: Editors for table values have wrong baseline
[ https://issues.apache.org/jira/browse/IGNITE-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8333: - Priority: Minor (was: Major) > Web console: Editors for table values have wrong baseline > - > > Key: IGNITE-8333 > URL: https://issues.apache.org/jira/browse/IGNITE-8333 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Vasiliy Sisko >Assignee: Ilya Borisov >Priority: Minor > Attachments: Selection_120.png, Selection_121.png > > > Baseline for table editor is higher than label baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
