[jira] [Created] (IGNITE-11636) Web console: incorrect value is restored after Refresh
Pavel Konstantinov created IGNITE-11636: --- Summary: Web console: incorrect value is restored after Refresh Key: IGNITE-11636 URL: https://issues.apache.org/jira/browse/IGNITE-11636 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Start two clusters with the same caches. Load some data in the first. Leave caches in the second cluster empty. Open SQL, select the first cluster, execute any select Press F5 to refresh the page Expected - the first cluster must be selected Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11602) Web console: Do not show the 'Download JDBC driver' label for MS SQL due to it available via maven
Pavel Konstantinov created IGNITE-11602: --- Summary: Web console: Do not show the 'Download JDBC driver' label for MS SQL due to it available via maven Key: IGNITE-11602 URL: https://issues.apache.org/jira/browse/IGNITE-11602 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11601) The 'Save and Download' action saves wrong cluster
Pavel Konstantinov created IGNITE-11601: --- Summary: 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 Attachments: screenshot-1.png Create the first cluster, save and download - all works right Create a second cluster, save and download - a first cluster actually saved -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11403) Web console: 'export all' for scan ignores a filter value
Pavel Konstantinov created IGNITE-11403: --- Summary: 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 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 (v7.6.3#76005)
[jira] [Created] (IGNITE-11220) Web console: NPE in web agent in case of using SSL and trust manager is not set
Pavel Konstantinov created IGNITE-11220:
---
Summary: Web console: NPE in web agent in case of using SSL and
trust manager is not set
Key: IGNITE-11220
URL: https://issues.apache.org/jira/browse/IGNITE-11220
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
To reproduce you need to set in default.properties 'node-key-store' and
'node-key-store-password' and not set 'node-trust-store' and
'node-trust-store-password'
After you start web agent you will get
{code}
Exception in thread "main" java.lang.NullPointerException: trustManager == null
at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:805)
at
org.apache.ignite.console.agent.rest.RestExecutor.(RestExecutor.java:118)
at
org.apache.ignite.console.agent.AgentLauncher.main(AgentLauncher.java:391)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11167) Web console: web agent doesn't work properly via '3proxy' proxy server in case if autentication is ON on proxy
Pavel Konstantinov created IGNITE-11167: --- Summary: Web console: web agent doesn't work properly via '3proxy' proxy server in case if autentication is ON on proxy Key: IGNITE-11167 URL: https://issues.apache.org/jira/browse/IGNITE-11167 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov I found that web agent can't work via '3proxy' proxy server, because that server sends a 'body' part in the answer, but agent expects the only header. The agent works properly only if authentication on proxy is OFF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11132) Web console: scrolling to invalid field works incorrectly under the MS Edge
Pavel Konstantinov created IGNITE-11132: --- Summary: Web console: scrolling to invalid field works incorrectly under the MS Edge Key: IGNITE-11132 URL: https://issues.apache.org/jira/browse/IGNITE-11132 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Ilya Borisov Cluster - Advanced - General(panel) - Attempts count Enter the -1 value Save An invalid value will be placed behind the viewport -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11101) Web console: validation does not work properly in corner case in Firefox
Pavel Konstantinov created IGNITE-11101: --- Summary: Web console: validation does not work properly in corner case in Firefox Key: IGNITE-11101 URL: https://issues.apache.org/jira/browse/IGNITE-11101 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Ilya Borisov Attachments: screenshot-1.png You should use Firefox Configuration - Cluster - Advanced - Data storage configuration Enter a literal value into System region / Initial size Save -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11097) Web console: UI bug on Queries
Pavel Konstantinov created IGNITE-11097: --- Summary: Web console: UI bug on Queries Key: IGNITE-11097 URL: https://issues.apache.org/jira/browse/IGNITE-11097 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov Attachments: image-2019-01-28-14-25-30-403.png !image-2019-01-28-14-25-30-403.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10915) Web console: error message is out of screen
Pavel Konstantinov created IGNITE-10915: --- Summary: Web console: error message is out of screen Key: IGNITE-10915 URL: https://issues.apache.org/jira/browse/IGNITE-10915 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: image-2019-01-14-14-07-26-877.png !image-2019-01-14-14-07-26-877.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10847) Web console: failed to download the mongodb on Ubuntu 18.04
Pavel Konstantinov created IGNITE-10847: --- Summary: Web console: failed to download the mongodb on Ubuntu 18.04 Key: IGNITE-10847 URL: https://issues.apache.org/jira/browse/IGNITE-10847 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov I tried to run 'web console direct install' and faced with an error downloading of MongoDB due to there is no corresponding version for that OS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10667) Web console: 'key store file' field is uneditable in SSL configuration
Pavel Konstantinov created IGNITE-10667: --- Summary: Web console: 'key store file' field is uneditable in SSL configuration Key: IGNITE-10667 URL: https://issues.apache.org/jira/browse/IGNITE-10667 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Attachments: image-2018-12-13-13-23-15-844.png !image-2018-12-13-13-23-15-844.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10616) Web console: new security token must be applied immediately
Pavel Konstantinov created IGNITE-10616: --- Summary: Web console: new security token must be applied immediately Key: IGNITE-10616 URL: https://issues.apache.org/jira/browse/IGNITE-10616 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Fix For: 2.8 I found that after changing of user's security token it not applied immediately - expected: web agent must lose connection - actually: web agent still be connected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10432) regression on sqlline
Pavel Konstantinov created IGNITE-10432:
---
Summary: regression on sqlline
Key: IGNITE-10432
URL: https://issues.apache.org/jira/browse/IGNITE-10432
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Pavel Konstantinov
Assignee: Vladimir Ozerov
Fix For: 2.7
{code}
2787/5325INSERT INTO City(ID, Name, CountryCode, District, Population)
VALUES (2769,'Sokoto','NGA','Sokoto & Kebbi & Zam',204900);
Error: Value for a column 'DISTRICT' is too long. Maximum length: 20, actual
length: 21 (state=23000,code=4008)
Aborting command set because "force" is false and command failed: "INSERT INTO
City(ID, Name, CountryCode, District, Population) VALUES
(2769,'Sokoto','NGA','Sokoto & Kebbi & Zam',204900);"
0: jdbc:ignite:thin://127.0.0.1:10800>
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10373) Web console: we need to fix docker-compose.yml
Pavel Konstantinov created IGNITE-10373:
---
Summary: Web console: we need to fix docker-compose.yml
Key: IGNITE-10373
URL: https://issues.apache.org/jira/browse/IGNITE-10373
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Pavel Konstantinov
It located here 'modules/web-console/docker/compose' and it doesn't work
{code}
Version in "./docker-compose.yml" is invalid - it should be a string.
{code}
after I've fixed that I've got the next one
{code}
Version in "./docker-compose.yml" is invalid. You might be seeing this error
because you're using the wrong Compose file version. Either specify a supported
version (e.g "2.2" or "3.3") and place your service definitions under the
`services` key, or omit the `version` key and place your service definitions at
the root of the file to use version 1.
{code}
after I've fixed that I've got the next one
{code}
ERROR: Service 'frontend' depends on service 'testenv' which is undefined.
{code}
So, please make it workable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10363) Web console: unexpected unsaved changes confirmation
Pavel Konstantinov created IGNITE-10363: --- Summary: Web console: unexpected unsaved changes confirmation Key: IGNITE-10363 URL: https://issues.apache.org/jira/browse/IGNITE-10363 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: image-2018-11-21-17-33-17-545.png # create a new cluster # do not save # click Import form DB # go through all steps # Save !image-2018-11-21-17-33-17-545.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10357) Check web console in version 2.7
Pavel Konstantinov created IGNITE-10357: --- Summary: Check web console in version 2.7 Key: IGNITE-10357 URL: https://issues.apache.org/jira/browse/IGNITE-10357 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10214) Web console: dependency to open source JDBS driver is not generated in the project's pom file
Pavel Konstantinov created IGNITE-10214: --- Summary: Web console: dependency to open source JDBS driver is not generated in the project's pom file Key: IGNITE-10214 URL: https://issues.apache.org/jira/browse/IGNITE-10214 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Steps to reproduce: # import caches from for example MySql DB # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9967) Web console: an error in browser console on opepning Readme.txt in Project Structure modal
Pavel Konstantinov created IGNITE-9967: -- Summary: Web console: an error in browser console on opepning Readme.txt in Project Structure modal Key: IGNITE-9967 URL: https://issues.apache.org/jira/browse/IGNITE-9967 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9641) Web console: inconsistent 'question' icon behaviour
Pavel Konstantinov created IGNITE-9641: -- Summary: Web console: inconsistent 'question' icon behaviour Key: IGNITE-9641 URL: https://issues.apache.org/jira/browse/IGNITE-9641 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Alexander Kalinin Attachments: screenshot-1.png I've noticed that 'question' icons on the last page of the 'Import model from DB' has some other behaviour than on the previous pages of this wizard. Please make it the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9571) Web console: update Project Structure UI to a new style
Pavel Konstantinov created IGNITE-9571: -- Summary: Web console: update Project Structure UI to a new style Key: IGNITE-9571 URL: https://issues.apache.org/jira/browse/IGNITE-9571 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9568) Web console: fields are not visible under Firefox
Pavel Konstantinov created IGNITE-9568: -- Summary: Web console: fields are not visible under Firefox Key: IGNITE-9568 URL: https://issues.apache.org/jira/browse/IGNITE-9568 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9566) Make possible execute Explain by selected part of the query
Pavel Konstantinov created IGNITE-9566: -- Summary: Make possible execute Explain by selected part of the query Key: IGNITE-9566 URL: https://issues.apache.org/jira/browse/IGNITE-9566 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Currently, it is possible to execute a query by a selected part, but not possible make explain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9554) Web console demo: do not auto-populate caches created via SQL
Pavel Konstantinov created IGNITE-9554: -- Summary: Web console demo: do not auto-populate caches created via SQL Key: IGNITE-9554 URL: https://issues.apache.org/jira/browse/IGNITE-9554 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov If I executing an example SQL quires CREATE TABLE Person(ID INTEGER PRIMARY KEY, NAME VARCHAR(100)); INSERT INTO Person(ID, NAME) VALUES (1, 'Ed'), (2, 'Ann'), (3, 'Emma'); SELECT * FROM Person; I got 'result set is empty' due to inserted data were replaced with auto-generated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9177) Web console: full screen UI issues under Edge
Pavel Konstantinov created IGNITE-9177: -- Summary: Web console: full screen UI issues under Edge Key: IGNITE-9177 URL: https://issues.apache.org/jira/browse/IGNITE-9177 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Dmitriy Shabalin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9176) Web console: show authorization exception if user hasn't permission to activate a cluster
Pavel Konstantinov created IGNITE-9176: -- Summary: Web console: show authorization exception if user hasn't permission to activate a cluster Key: IGNITE-9176 URL: https://issues.apache.org/jira/browse/IGNITE-9176 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov I've faced with an issue that we don't show any error if a user has no permission to activate a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9166) Web console: do not disable the Save button on changing password in user profile
Pavel Konstantinov created IGNITE-9166: -- Summary: Web console: do not disable the Save button on changing password in user profile Key: IGNITE-9166 URL: https://issues.apache.org/jira/browse/IGNITE-9166 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9164) Web console: issue with cluster authentication
Pavel Konstantinov created IGNITE-9164: -- Summary: Web console: issue with cluster authentication Key: IGNITE-9164 URL: https://issues.apache.org/jira/browse/IGNITE-9164 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: screenshot-1.png Start a cluster with authentication Enabled = true Open Monitoring - authentication modal has appeared Click Cancel - it is impossible to switch to another cluster if a user forgot a password (for example) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9163) Web console: incorrect cluster state for clusters of version 7.x
Pavel Konstantinov created IGNITE-9163: -- Summary: Web console: incorrect cluster state for clusters of version 7.x Key: IGNITE-9163 URL: https://issues.apache.org/jira/browse/IGNITE-9163 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9152) Web console: add a checkbox 'include in generated project'
Pavel Konstantinov created IGNITE-9152: -- Summary: Web console: add a checkbox 'include in generated project' Key: IGNITE-9152 URL: https://issues.apache.org/jira/browse/IGNITE-9152 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9151) Web console: incorrect caches list in 'Import from DB' modal
Pavel Konstantinov created IGNITE-9151: -- Summary: Web console: incorrect caches list in 'Import from DB' modal Key: IGNITE-9151 URL: https://issues.apache.org/jira/browse/IGNITE-9151 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
Pavel Konstantinov created IGNITE-9150: -- Summary: Web console: incorrect text of cluster acivation component in corner case Key: IGNITE-9150 URL: https://issues.apache.org/jira/browse/IGNITE-9150 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
Pavel Konstantinov created IGNITE-9143: -- Summary: Web console: SQL buttons are disabled in case when it must be enabled Key: IGNITE-9143 URL: https://issues.apache.org/jira/browse/IGNITE-9143 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Create a new notebook. Start writing a new query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9140) Web console: incorrect X-axis lebel format for TIME_LINE
Pavel Konstantinov created IGNITE-9140: -- Summary: Web console: incorrect X-axis lebel format for TIME_LINE Key: IGNITE-9140 URL: https://issues.apache.org/jira/browse/IGNITE-9140 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Attachments: screenshot-1.png Start Demo Open the Demo notebook Open the Chart Settings Change the value for X-axis to ROW_ID and then return to TIME_LINE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9139) Web console: item from dropdown cannot be selected
Pavel Konstantinov created IGNITE-9139: -- Summary: Web console: item from dropdown cannot be selected Key: IGNITE-9139 URL: https://issues.apache.org/jira/browse/IGNITE-9139 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Dmitriy Shabalin Attachments: image-2018-07-31-15-44-30-099.png Query - Result - Chart - Chart Settings - Y axis settings !image-2018-07-31-15-44-30-099.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
Pavel Konstantinov created IGNITE-9137: -- Summary: Web console: UI of 'select node' modal a little bit broken Key: IGNITE-9137 URL: https://issues.apache.org/jira/browse/IGNITE-9137 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Dmitriy Shabalin Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
Pavel Konstantinov created IGNITE-9136:
--
Summary: Web console: hide\disable cluster activation switcher if
cluster has no persistent configuration
Key: IGNITE-9136
URL: https://issues.apache.org/jira/browse/IGNITE-9136
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
I faced with exception when tried to activate a cluster of version 7.x due to
that version of ignite has no persistent at all.
{code}
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
... 21 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9118) Web console: something wrong with Load balancing configuration
Pavel Konstantinov created IGNITE-9118: -- Summary: Web console: something wrong with Load balancing configuration Key: IGNITE-9118 URL: https://issues.apache.org/jira/browse/IGNITE-9118 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Please see attchment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8990) Web console: unexpected 'Unsaved changes' warning
Pavel Konstantinov created IGNITE-8990: -- Summary: Web console: unexpected 'Unsaved changes' warning Key: IGNITE-8990 URL: https://issues.apache.org/jira/browse/IGNITE-8990 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov # Create a new cluster configuration # Save # Change the cluster name # Save & Download # Go to the Monitoring I getting the warning about unsaved changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8989) Web console: incorrect initial state of some checkboxes on Client Configuration panel
Pavel Konstantinov created IGNITE-8989: -- Summary: Web console: incorrect initial state of some checkboxes on Client Configuration panel Key: IGNITE-8989 URL: https://issues.apache.org/jira/browse/IGNITE-8989 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8988) Web console: error in Readme.txt of generated project
Pavel Konstantinov created IGNITE-8988: -- Summary: Web console: error in Readme.txt of generated project Key: IGNITE-8988 URL: https://issues.apache.org/jira/browse/IGNITE-8988 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Attachments: screenshot-1.png Readme.txt says XML configuration files are located in /config folder, but actually its located in src/main/resources/META-INF -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8980) Web console: regression on Queries screen
Pavel Konstantinov created IGNITE-8980: -- Summary: Web console: regression on Queries screen Key: IGNITE-8980 URL: https://issues.apache.org/jira/browse/IGNITE-8980 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Assignee: Dmitriy Shabalin Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8979) Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query
Pavel Konstantinov created IGNITE-8979: -- Summary: Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query Key: IGNITE-8979 URL: https://issues.apache.org/jira/browse/IGNITE-8979 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: image-2018-07-11-15-21-02-606.png Open Query screen. Click on the 'Refresh rate' button and try to select another measurement by the mouse. !image-2018-07-11-15-21-02-606.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8970) Web Console: Add the Clone action to a new configuration UI
Pavel Konstantinov created IGNITE-8970: -- Summary: Web Console: Add the Clone action to a new configuration UI Key: IGNITE-8970 URL: https://issues.apache.org/jira/browse/IGNITE-8970 Project: Ignite Issue Type: Task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov A new configuration UI has no the Clone action for all cluster's components (caches, schemas,...). We need to add that action due to it was on 'old' UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8758) Web console: Broken UI under Firefox in case of long user name
Pavel Konstantinov created IGNITE-8758: -- Summary: Web console: Broken UI under Firefox in case of long user name Key: IGNITE-8758 URL: https://issues.apache.org/jira/browse/IGNITE-8758 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Jaust change a user name in the profile to 1 and check how it looks under Firefox -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8744) Incorrect behavior of cluster activation control
Pavel Konstantinov created IGNITE-8744: -- Summary: Incorrect behavior of cluster activation control Key: IGNITE-8744 URL: https://issues.apache.org/jira/browse/IGNITE-8744 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Andrey Novikov # start node # activate # go to Queries history tab, click Refresh # deactivate cluster using component- after several seconds component gets switched to 'Activating...' stage and hangs in this state for about minute -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8686) Web console: 'Get started' point to the wrong page
Pavel Konstantinov created IGNITE-8686: -- Summary: Web console: 'Get started' point to the wrong page Key: IGNITE-8686 URL: https://issues.apache.org/jira/browse/IGNITE-8686 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: screenshot-1.png I'm noticed that 'Get started' button on the landing page points to 'signin' page, but should point to 'signup' page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8569) Web console: incorrect user activities amount on admin page
Pavel Konstantinov created IGNITE-8569: -- Summary: Web console: incorrect user activities amount on admin page Key: IGNITE-8569 URL: https://issues.apache.org/jira/browse/IGNITE-8569 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov # create a cluster configuration on basic page, save # open admin panel and check Cfg counter -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8555) Web console - Admin panel: the users table is partially empty
Pavel Konstantinov created IGNITE-8555: -- Summary: Web console - Admin panel: the users table is partially empty Key: IGNITE-8555 URL: https://issues.apache.org/jira/browse/IGNITE-8555 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: image-2018-05-22-16-27-52-342.png !image-2018-05-22-16-27-52-342.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8551) Web console - User -profile: do not disable the 'Save Changes' button
Pavel Konstantinov created IGNITE-8551: -- Summary: Web console - User -profile: do not disable the 'Save Changes' button Key: IGNITE-8551 URL: https://issues.apache.org/jira/browse/IGNITE-8551 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Currently, we disable the Save Changes button in case of an invalid field. It will be better make the button always enabled and show an error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8488) Web console: scroll bar doesn't work inside cluster selector component
Pavel Konstantinov created IGNITE-8488: -- Summary: Web console: scroll bar doesn't work inside cluster selector component Key: IGNITE-8488 URL: https://issues.apache.org/jira/browse/IGNITE-8488 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov List of clusters can be scrolled by mouse wheel but can't by dragging the scrollbar. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8479) Web console: query text is empty on opening query section
Pavel Konstantinov created IGNITE-8479: -- Summary: Web console: query text is empty on opening query section Key: IGNITE-8479 URL: https://issues.apache.org/jira/browse/IGNITE-8479 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Attachments: image-2018-05-14-16-39-34-686.png On the first second the query text is empty and then it appears. !image-2018-05-14-16-39-34-686.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8477) Web console: duration is empty on first query
Pavel Konstantinov created IGNITE-8477: -- Summary: Web console: duration is empty on first query Key: IGNITE-8477 URL: https://issues.apache.org/jira/browse/IGNITE-8477 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8307) Web console: panel with buttons Cancel, Save doesn't float at the bottom of the screen under Safari 11.1
Pavel Konstantinov created IGNITE-8307: -- Summary: Web console: panel with buttons Cancel, Save doesn't float at the bottom of the screen under Safari 11.1 Key: IGNITE-8307 URL: https://issues.apache.org/jira/browse/IGNITE-8307 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8274) Wrong invoking of java in sqlline.sh
Pavel Konstantinov created IGNITE-8274: -- Summary: Wrong invoking of java in sqlline.sh Key: IGNITE-8274 URL: https://issues.apache.org/jira/browse/IGNITE-8274 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Oleg Ostanin Currently java invoked w\o using JAVA_HOME variable Need to be fixed using $JAVA_HOME/bin/java as in others ignite sh scripts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8215) Web console: some fields are not generated
Pavel Konstantinov created IGNITE-8215: -- Summary: Web console: some fields are not generated Key: IGNITE-8215 URL: https://issues.apache.org/jira/browse/IGNITE-8215 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Data Region Configuration - Metrics sub interval count - Metrics rate time interval -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8214) Web console: add validation for Persistent + Swap file for data region configuration
Pavel Konstantinov created IGNITE-8214: -- Summary: Web console: add validation for Persistent + Swap file for data region configuration Key: IGNITE-8214 URL: https://issues.apache.org/jira/browse/IGNITE-8214 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko The 'Swap file' option can be set only if 'Persistent Enable' is OFF. Please add corresponding validation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8213) control.sh: make a correct error message in case of adding non-existen node to baseline
Pavel Konstantinov created IGNITE-8213:
--
Summary: control.sh: make a correct error message in case of
adding non-existen node to baseline
Key: IGNITE-8213
URL: https://issues.apache.org/jira/browse/IGNITE-8213
Project: Ignite
Issue Type: Improvement
Reporter: Pavel Konstantinov
We need to print out a readable error message with a corresponding error code
instead of this
{code}
PS C:\work\master\bin> .\control.bat --baseline add 121212
Warning: the command will perform changes in baseline.
Press 'y' to continue...y
Failed to add nodes to baseline.
Error: Failed to reduce job results due to undeclared user exception
[task=org.apache.ignite.internal.visor.baseline.VisorBaselineTask@71e96f24,
err=class org.apache.ignite.compute.ComputeUserUndeclaredException: Failed to
execute job due to unexpected runtime exception
[jobId=3064672b261-df38f2fd-ca81-423c-b4c3-dd002a77f0af, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=org.apache.ignite.internal.visor.baseline.VisorBaselineTask,
dep=LocalDeployment [super=GridDeployment [ts=1523412519601, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@764c12b6,
clsLdrId=ba54672b261-df38f2fd-ca81-423c-b4c3-dd002a77f0af, userVer=0, loc=true,
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false,
usage=0]],
taskClsName=org.apache.ignite.internal.visor.baseline.VisorBaselineTask,
sesId=2064672b261-df38f2fd-ca81-423c-b4c3-dd002a77f0af,
startTime=1523412552937, endTime=9223372036854775807,
taskNodeId=df38f2fd-ca81-423c-b4c3-dd002a77f0af,
clsLdr=sun.misc.Launcher$AppClassLoader@764c12b6, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=true,
topPred=null, subjId=df38f2fd-ca81-423c-b4c3-dd002a77f0af, mapFut=IgniteFuture
[orig=GridFutureAdapter [ignoreInterrupts=false, state=INIT, res=null,
hash=1531276047]], execName=null],
jobId=3064672b261-df38f2fd-ca81-423c-b4c3-dd002a77f0af], err=Node not found for
consistent ID: 121212]]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8200) Web console: unexpected confirmation
Pavel Konstantinov created IGNITE-8200: -- Summary: Web console: unexpected confirmation Key: IGNITE-8200 URL: https://issues.apache.org/jira/browse/IGNITE-8200 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov # initial state - there are no clusters # create a new one, do not save # open Advanced screen, save # import from DB, save # open Caches screen - unexpected confirmation about unsaved changes appear # click Cancel, save, open Caches again - unexpected confirmation again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8199) Make the Confirmation dialog a more clear
Pavel Konstantinov created IGNITE-8199: -- Summary: Make the Confirmation dialog a more clear Key: IGNITE-8199 URL: https://issues.apache.org/jira/browse/IGNITE-8199 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Attachments: screenshot-1.png In case of unsaved changes, we show the following confirmation It is unclear what I have to do to see the changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8144) Web console: UI issue in tables
Pavel Konstantinov created IGNITE-8144: -- Summary: Web console: UI issue in tables Key: IGNITE-8144 URL: https://issues.apache.org/jira/browse/IGNITE-8144 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Dmitriy Shabalin Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8140) Web console: "integer number too large" in generated project
Pavel Konstantinov created IGNITE-8140:
--
Summary: Web console: "integer number too large" in generated
project
Key: IGNITE-8140
URL: https://issues.apache.org/jira/browse/IGNITE-8140
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Some methods expected Long type but we set Integer, please fix
{code}
dataStorageCfg.setSystemRegionMaxSize(2147483648);
eventStorage.setExpireAgeMs(2323232323232323);
cfg.setMetricsExpireTime(2323232323);
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8132) A little re-design of Checkpointing section
Pavel Konstantinov created IGNITE-8132: -- Summary: A little re-design of Checkpointing section Key: IGNITE-8132 URL: https://issues.apache.org/jira/browse/IGNITE-8132 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Assignee: Ilya Borisov Attachments: screenshot-1.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8126) Web console: the method 'LoadCaches' should not be generated if cache doesn't contain cache store configuration
Pavel Konstantinov created IGNITE-8126: -- Summary: Web console: the method 'LoadCaches' should not be generated if cache doesn't contain cache store configuration Key: IGNITE-8126 URL: https://issues.apache.org/jira/browse/IGNITE-8126 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko # create cluster, save # create cache, save # see project structure -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8124) Web console: incorrect text after all clusters have been deleted
Pavel Konstantinov created IGNITE-8124: -- Summary: Web console: incorrect text after all clusters have been deleted Key: IGNITE-8124 URL: https://issues.apache.org/jira/browse/IGNITE-8124 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov Attachments: screenshot-1.png # create two clusters # delete all clusters # see attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8123) Web console: incorrect text after all clusters have been deleted
Pavel Konstantinov created IGNITE-8123: -- Summary: Web console: incorrect text after all clusters have been deleted Key: IGNITE-8123 URL: https://issues.apache.org/jira/browse/IGNITE-8123 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov # create two clusters # delete all clusters # see attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8121) Web console: import cluster from database doesn't work correctly for second import
Pavel Konstantinov created IGNITE-8121: -- Summary: Web console: import cluster from database doesn't work correctly for second import Key: IGNITE-8121 URL: https://issues.apache.org/jira/browse/IGNITE-8121 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Ilya Borisov # initial state - no one cluster exists # import from any DB - the first time all imported correctly # import the second time - error "Cluster ... already exists" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8118) sqlline.bat throws NPE under PowerShell
Pavel Konstantinov created IGNITE-8118:
--
Summary: sqlline.bat throws NPE under PowerShell
Key: IGNITE-8118
URL: https://issues.apache.org/jira/browse/IGNITE-8118
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
{code}
.\sqlline.bat -u
"'jdbc:ignite:thin://18.17.12.22:9652?user=ignite=111'"
No known driver to handle "'jdbc:ignite:thin://18.17.12.22:9652?user=ignite".
Searching for known drivers...
java.lang.NullPointerException
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8099) Web console: wrong editing behavior in case of incorrect field value
Pavel Konstantinov created IGNITE-8099: -- Summary: Web console: wrong editing behavior in case of incorrect field value Key: IGNITE-8099 URL: https://issues.apache.org/jira/browse/IGNITE-8099 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov For reproduce just try to edit 'Key Type' field of Model -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8029) Web console: wrong behaviour of cluster activation component
Pavel Konstantinov created IGNITE-8029: -- Summary: Web console: wrong behaviour of cluster activation component Key: IGNITE-8029 URL: https://issues.apache.org/jira/browse/IGNITE-8029 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov I've noticed that during activation the text 'Deactivation' is printed for ~0.5 second and else - during deactivation, the text 'Activation' is printed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8015) NPE on adding node to baseline
Pavel Konstantinov created IGNITE-8015:
--
Summary: NPE on adding node to baseline
Key: IGNITE-8015
URL: https://issues.apache.org/jira/browse/IGNITE-8015
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
# start ignite.sh
# execute .\control.sh --baseline add 111
{code}
[17:05:37,396][SEVERE][rest-#68][GridRestProcessor] Failed to handle request:
EXE
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7273)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:257)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsync(GridTaskCommandHandler.java:163)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:266)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:89)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:155)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.currentBaseLine(VisorBaselineTask.java:100)
at
org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.add(VisorBaselineTask.java:148)
at
org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:203)
at
org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:52)
at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6652)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1407)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:660)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:760)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:489)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:227)
... 8 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8008) Web console: Add a link to the SQL documentation in Notebook title
Pavel Konstantinov created IGNITE-8008: -- Summary: Web console: Add a link to the SQL documentation in Notebook title Key: IGNITE-8008 URL: https://issues.apache.org/jira/browse/IGNITE-8008 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Add a link to the documentation in Notebook title https://apacheignite-sql.readme.io/docs/sql-reference-overview -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8001) Web console: show more userfriendly error instead of 'Internal error'
Pavel Konstantinov created IGNITE-8001: -- Summary: Web console: show more userfriendly error instead of 'Internal error' Key: IGNITE-8001 URL: https://issues.apache.org/jira/browse/IGNITE-8001 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Attachments: screenshot-1.png In case if the backend is down we display the 'Internal error' message. I suggest displaying some other more user-friendly text. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7929) Web console: error frame too long on sign in
Pavel Konstantinov created IGNITE-7929: -- Summary: Web console: error frame too long on sign in Key: IGNITE-7929 URL: https://issues.apache.org/jira/browse/IGNITE-7929 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Fix For: 2.5 Attachments: screenshot-1.png To reproduce enter incorrect email and click 'Sign in' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7927) Web console: failed to execute query in demo
Pavel Konstantinov created IGNITE-7927:
--
Summary: Web console: failed to execute query in demo
Key: IGNITE-7927
URL: https://issues.apache.org/jira/browse/IGNITE-7927
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
If I set 'Allow non-collocated joins' then I got the following error
{code}
Error: Failed to prepare distributed join query: join condition does not use
index [joinedCache=CarCache, plan=SELECT P__Z0.NAME AS __C0_0, COUNT(*) AS
__C0_1 FROM "ParkingCache".PARKING P__Z0 /* "ParkingCache".PARKING.__SCAN_ */
INNER JOIN "CarCache".CAR C__Z1 /* batched:broadcast "CarCache".CAR.__SCAN_ */
ON 1=1 WHERE P__Z0.ID = C__Z1.PARKINGID GROUP BY P__Z0.NAME]
{code}
Please add necessary indices
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7926) Web console: demo faled to start under java 9
Pavel Konstantinov created IGNITE-7926: -- Summary: Web console: demo faled to start under java 9 Key: IGNITE-7926 URL: https://issues.apache.org/jira/browse/IGNITE-7926 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Pavel Konstantinov Fix For: 2.5 We need to add support for Java 9 to web console demo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7757) Unable to create a new cache via REST
Pavel Konstantinov created IGNITE-7757:
--
Summary: Unable to create a new cache via REST
Key: IGNITE-7757
URL: https://issues.apache.org/jira/browse/IGNITE-7757
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
# try to start a new cache with non-existing cache group name
{code}
localhost:8080/ignite?cmd=getorcreate=cache1=
{code}
# then edit your request and make it correct and try again
{code}
localhost:8080/ignite?cmd=getorcreate=cache1
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7658) visorcmd: add ability to get configuration of certain cache
Pavel Konstantinov created IGNITE-7658: -- Summary: visorcmd: add ability to get configuration of certain cache Key: IGNITE-7658 URL: https://issues.apache.org/jira/browse/IGNITE-7658 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Currently 'config' command returns only full configuration from a node. config -id8=@n0 It is inconvenient in case if a user wants to get the configuration for one certain cache. I suggesting to add a new option to 'config' command to set cache, like: config -id8=@n0 -c=@c0 - get configuration of cache @c0 from node @n0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7600) visorcmd: add column 'type' for 'mlist' result
Pavel Konstantinov created IGNITE-7600: -- Summary: visorcmd: add column 'type' for 'mlist' result Key: IGNITE-7600 URL: https://issues.apache.org/jira/browse/IGNITE-7600 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov It should print type of variable. F.e. n0..nX - node, h0..hX - host -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7597) visorcmd: remove cache variable (@c) after cache was stopped
Pavel Konstantinov created IGNITE-7597: -- Summary: visorcmd: remove cache variable (@c) after cache was stopped Key: IGNITE-7597 URL: https://issues.apache.org/jira/browse/IGNITE-7597 Project: Ignite Issue Type: Bug Affects Versions: 2.3, 2.4 Reporter: Pavel Konstantinov Fix For: 2.5 # start node with several caches # start visorcmd and connect to grid # execute cache command to set cache variables (@c0..@cX) # stop cache @c0 # execute mlist - cache @c0 is still in the list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7497) Web console should check connection to cluster before sending any task
Pavel Konstantinov created IGNITE-7497: -- Summary: Web console should check connection to cluster before sending any task Key: IGNITE-7497 URL: https://issues.apache.org/jira/browse/IGNITE-7497 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7459) Web console: do not show result title until query end
Pavel Konstantinov created IGNITE-7459: -- Summary: Web console: do not show result title until query end Key: IGNITE-7459 URL: https://issues.apache.org/jira/browse/IGNITE-7459 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Currently we print result title (below result table) for scan before it was actually ended. It looks confusing if scan with filter is executing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7392) visorcmd: missed word 'factory' in the lables
Pavel Konstantinov created IGNITE-7392: -- Summary: visorcmd: missed word 'factory' in the lables Key: IGNITE-7392 URL: https://issues.apache.org/jira/browse/IGNITE-7392 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Priority: Trivial Fix For: 2.4 We need to add 'factory' into label 'Eviction policy' and 'Near eviction policy' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7391) Web console: ClientConfigurationFactory class name is missing in generated project
Pavel Konstantinov created IGNITE-7391: -- Summary: Web console: ClientConfigurationFactory class name is missing in generated project Key: IGNITE-7391 URL: https://issues.apache.org/jira/browse/IGNITE-7391 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Priority: Blocker It present in Java preview but absent in downloaded project -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7381) visorcmd: improve output of 'modify' command - show Value Class info
Pavel Konstantinov created IGNITE-7381: -- Summary: visorcmd: improve output of 'modify' command - show Value Class info Key: IGNITE-7381 URL: https://issues.apache.org/jira/browse/IGNITE-7381 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Priority: Trivial In case if cache contains several keys with the same value but different type it is unclear what type of returned value in the result of command -get and -remove -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7298) Web console: error on web agent start
Pavel Konstantinov created IGNITE-7298:
--
Summary: Web console: error on web agent start
Key: IGNITE-7298
URL: https://issues.apache.org/jira/browse/IGNITE-7298
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
{code}
[ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
config/java.util.logging.properties
Console logging handler is not configured.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7294) Web console: show warning on start in case of wrong version of MongoDb installed on host
Pavel Konstantinov created IGNITE-7294: -- Summary: Web console: show warning on start in case of wrong version of MongoDb installed on host Key: IGNITE-7294 URL: https://issues.apache.org/jira/browse/IGNITE-7294 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Currently, we have no verification of version of MongoDB it may lead to a various issue at runtime. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7273) Web console: Profile in "main work tab" doesn't see changes of Profile made in another tab
Pavel Konstantinov created IGNITE-7273: -- Summary: Web console: Profile in "main work tab" doesn't see changes of Profile made in another tab Key: IGNITE-7273 URL: https://issues.apache.org/jira/browse/IGNITE-7273 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor # open two tabs with web console # in the second tab open User\Profile page and make any changes, Save # open Profile in the first tab - it doesn't show changes you made -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7121) visorcmd: there is no output for last command in batch mode in case of using -nq option
Pavel Konstantinov created IGNITE-7121:
--
Summary: visorcmd: there is no output for last command in batch
mode in case of using -nq option
Key: IGNITE-7121
URL: https://issues.apache.org/jira/browse/IGNITE-7121
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 2.3
Reporter: Pavel Konstantinov
Fix For: 2.4
To reproduce try to execute visorcmd in batch mode
{code}
ignitevisorcmd.bat "-nq -b=commands.visor"
{code}
with command file
{code}
open -cpath=config/your-config.xml
config
{code}
output of 'config' command will not displayed
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7084) It is possible to generate incorrect configuration using Basic configuration screen
Pavel Konstantinov created IGNITE-7084:
--
Summary: It is possible to generate incorrect configuration using
Basic configuration screen
Key: IGNITE-7084
URL: https://issues.apache.org/jira/browse/IGNITE-7084
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
Open Basic configuration screen
Create a new cluster
Set StaticIPFinder as a discovery
Remove address (127.0.0.1)
Save project, download and try to start a node using generated config
{code}
class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=60, forceSrvMode=false,
clientReconnectDisabled=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:876)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1823)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:993)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1903)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1646)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1074)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:992)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:878)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:777)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:647)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:616)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Non-shared IP finder
must have IP addresses specified in
TcpDiscoveryIpFinder.getRegisteredAddresses() configuration property (specify
list of IP addresses in configuration).
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:346)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1868)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7067) web agent throws SocketTimeoutException instead of userfriendly error message
Pavel Konstantinov created IGNITE-7067:
--
Summary: web agent throws SocketTimeoutException instead of
userfriendly error message
Key: IGNITE-7067
URL: https://issues.apache.org/jira/browse/IGNITE-7067
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
This happens on Ubuntu on OpenJDK "1.8.0_151"
{code}
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.16.04.2-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
[2017-11-29 16:49:33,546][INFO ][main][AgentLauncher] Starting Apache Ignite
Web Console Agent...
...
[2017-11-29 16:49:33,950][INFO ][main][AgentLauncher] Connecting to:
http://localhost
[2017-11-29 16:49:34,079][INFO ][EventThread][AgentLauncher] Connection
established.
[2017-11-29 16:49:34,143][INFO ][EventThread][AgentLauncher] Authentication
success.
[2017-11-29 16:49:44,152][ERROR][pool-1-thread-1][ClusterListener] WatchTask
failed
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at okhttp3.internal.platform.Platform.connectSocket(Platform.java:124)
at
okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:221)
at
okhttp3.internal.connection.RealConnection.connect(RealConnection.java:147)
at
okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:192)
at
okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)
at
okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:100)
at
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at
okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at
okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
at okhttp3.RealCall.execute(RealCall.java:69)
at
org.apache.ignite.console.agent.rest.RestExecutor.sendRequest(RestExecutor.java:153)
at
org.apache.ignite.console.agent.rest.RestExecutor.topology(RestExecutor.java:220)
at
org.apache.ignite.console.agent.handlers.ClusterListener$WatchTask.run(ClusterListener.java:257)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7066) Web console: add ability to select web agent for importing model from DB
Pavel Konstantinov created IGNITE-7066: -- Summary: Web console: add ability to select web agent for importing model from DB Key: IGNITE-7066 URL: https://issues.apache.org/jira/browse/IGNITE-7066 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov In case if a user has two web agents on two different hosts he can't select particular agent for importing model from DB. It will be useful to add such ability. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7063) Web console: improve error handling in case of custom SMTP server
Pavel Konstantinov created IGNITE-7063: -- Summary: Web console: improve error handling in case of custom SMTP server Key: IGNITE-7063 URL: https://issues.apache.org/jira/browse/IGNITE-7063 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Add an error message in case if settings.json can't be read (contains error) Add an error message in case if 'forgot password' message failed to be sent -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7041) Web Console: Incorrect code generation in case if cache has eviction policy and near cache with eviction policy
Pavel Konstantinov created IGNITE-7041:
--
Summary: Web Console: Incorrect code generation in case if cache
has eviction policy and near cache with eviction policy
Key: IGNITE-7041
URL: https://issues.apache.org/jira/browse/IGNITE-7041
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Pavel Konstantinov
In case if cache has eviction policy and also near cache configuration with
eviction policy then generated code contains an error - the same variable is
used to define two different eviction policy types
{code}
public static CacheConfiguration cacheDepartmentCache() throws Exception {
CacheConfiguration ccfg = new CacheConfiguration();
.
LruEvictionPolicy evictionPlc = new LruEvictionPolicy();
evictionPlc.setBatchSize(5);
evictionPlc.setMaxSize(100);
ccfg.setEvictionPolicy(evictionPlc);
.
NearCacheConfiguration nearConfiguration = new NearCacheConfiguration();
nearConfiguration.setNearStartSize(4545);
evictionPlc = new SortedEvictionPolicy();- THIS ROW IS
INCORRECT
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7018) Web console: make warning more clear
Pavel Konstantinov created IGNITE-7018:
--
Summary: Web console: make warning more clear
Key: IGNITE-7018
URL: https://issues.apache.org/jira/browse/IGNITE-7018
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Pavel Konstantinov
Priority: Trivial
Start a backend
Console output says
{code}
There are no Ignite migrations to run.
{code}
It is unclear what is about. I suggest to change it to something like "There
are no Ignite Configurations found in MongoDB for migration."
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6943) Web console: LoadCahces method should activate cluster if persistent is configured, otherwise method doesn't work due to cluster is inactive
Pavel Konstantinov created IGNITE-6943: -- Summary: Web console: LoadCahces 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 Security Level: Public (Viewable by anyone) Components: wizards Affects Versions: 2.3 Reporter: Pavel Konstantinov Fix For: 2.4 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6919) Web console: incorrect character in tab name under IE11
Pavel Konstantinov created IGNITE-6919: -- Summary: Web console: incorrect character in tab name under IE11 Key: IGNITE-6919 URL: https://issues.apache.org/jira/browse/IGNITE-6919 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Reporter: Pavel Konstantinov Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6915) SQL: Failed to invoke getter method (type=class java.lang.String)
Pavel Konstantinov created IGNITE-6915:
--
Summary: SQL: Failed to invoke getter method (type=class
java.lang.String)
Key: IGNITE-6915
URL: https://issues.apache.org/jira/browse/IGNITE-6915
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Reporter: Pavel Konstantinov
{code}
Caused by: org.h2.jdbc.JdbcSQLException: ┬эєЄЁхээ ю°шсър: "class
org.apache.ignite.IgniteCheckedException: Failed to invoke getter method
[type=class java.lang.String, property=firstName]"
General error: "class org.apache.ignite.IgniteCheckedException: Failed to
invoke getter method [type=class java.lang.String, property=firstName]"; SQL
statement:
SELECT
__Z0.FIRSTNAME __C0_0,
__Z0.LASTNAME __C0_1,
__Z0.RANK __C0_2,
__Z0.TITLE __C0_3,
__Z0.AGE __C0_4,
__Z0.SALARY __C0_5,
__Z0.ID __C0_6,
__Z0.DEPID __C0_7
FROM "c_partitioned".PERSON __Z0 [5-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at
org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.columnValue(H2RowDescriptor.java:348)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:236)
at org.h2.table.TableFilter.getValue(TableFilter.java:1083)
at
org.h2.expression.ExpressionColumn.getValue(ExpressionColumn.java:186)
at org.h2.expression.Alias.getValue(Alias.java:36)
at
org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1459)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
at
org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:967)
... 31 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to invoke
getter method [type=class java.lang.String, property=firstName]
at
org.apache.ignite.internal.processors.query.property.QueryReadOnlyMethodsAccessor.getValue(QueryReadOnlyMethodsAccessor.java:51)
at
org.apache.ignite.internal.processors.query.property.QueryClassProperty.value(QueryClassProperty.java:82)
at
org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.columnValue(H2RowDescriptor.java:345)
... 47 more
Caused by: java.lang.IllegalArgumentException: object is not an instance of
declaring class
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.ignite.internal.processors.query.property.QueryReadOnlyMethodsAccessor.getValue(QueryReadOnlyMethodsAccessor.java:48)
... 49 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox
Pavel Konstantinov created IGNITE-6914: -- Summary: Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox Key: IGNITE-6914 URL: https://issues.apache.org/jira/browse/IGNITE-6914 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Reporter: Pavel Konstantinov I populated a cache with 100K of data. Then I opened Query screen and execute Scan for that cache. Then I executed Export All - under Chrome it stuck -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6808) Web console: display full text in tooltip for case if row content text takes more then 1 row
Pavel Konstantinov created IGNITE-6808: -- Summary: Web console: display full text in tooltip for case if row content text takes more then 1 row Key: IGNITE-6808 URL: https://issues.apache.org/jira/browse/IGNITE-6808 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Reporter: Pavel Konstantinov I noticed that sometimes event text doesn't fit in the visible part of the cell. And I wasn't able to see what text is hidden. So we need to show full text in the tooltip. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
