[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-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-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-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-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-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-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-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-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-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-4610) Please add explicity recomendation to check "ignite-rest-http" is present in "libs" folder
Pavel Konstantinov created IGNITE-4610: -- Summary: Please add explicity recomendation to check "ignite-rest-http" is present in "libs" folder Key: IGNITE-4610 URL: https://issues.apache.org/jira/browse/IGNITE-4610 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Currently it is not clear what I need to check in case when I got error about executing REST command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4744) visorcmd: task command doesn't show any tasks running on grid
Pavel Konstantinov created IGNITE-4744: -- Summary: visorcmd: task command doesn't show any tasks running on grid Key: IGNITE-4744 URL: https://issues.apache.org/jira/browse/IGNITE-4744 Project: Ignite Issue Type: Bug Components: visor Affects Versions: 1.9 Reporter: Pavel Konstantinov I faced that visorcmd doesn't show any tasks that I running using my test load. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4816) Issue with refresh rate on queries
Pavel Konstantinov created IGNITE-4816: -- Summary: Issue with refresh rate on queries Key: IGNITE-4816 URL: https://issues.apache.org/jira/browse/IGNITE-4816 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Next query execution start before previous one is finished -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4855) Error when switching between notebooks
Pavel Konstantinov created IGNITE-4855:
--
Summary: Error when switching between notebooks
Key: IGNITE-4855
URL: https://issues.apache.org/jira/browse/IGNITE-4855
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
{code}
TypeError: Cannot redefine property: ace
at Function.defineProperty ()
at https://staging-console.my-host.com/app.9102c5d071fa1be61279.js:13:17181
at https://staging-console.my-host.com/app.9102c5d071fa1be61279.js:7:22481
at u
(https://staging-console.my-host.com/vendor.ceecd70bedaaa641a449.js:1:1909)
at Function.gs
(https://staging-console.my-host.com/vendor.ceecd70bedaaa641a449.js:2:11302)
at r
(https://staging-console.my-host.com/app.9102c5d071fa1be61279.js:7:22424)
at y
(https://staging-console.my-host.com/app.9102c5d071fa1be61279.js:7:23641)
at Object.link
(https://staging-console.my-host.com/app.9102c5d071fa1be61279.js:7:23679)
at
https://staging-console.my-host.com/vendor.ceecd70bedaaa641a449.js:103:5660
at we
(https://staging-console.myhost.com/vendor.ceecd70bedaaa641a449.js:104:11056)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4996) Queries: show Node selection modal in case if user execute SCAN on local cache
Pavel Konstantinov created IGNITE-4996: -- Summary: Queries: show Node selection modal in case if user execute SCAN on local cache Key: IGNITE-4996 URL: https://issues.apache.org/jira/browse/IGNITE-4996 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Priority: Minor Also we need to filter nodes list and show only nodes where selected cache is configured -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5011) Add validation of input params of disco command
Pavel Konstantinov created IGNITE-5011:
--
Summary: Add validation of input params of disco command
Key: IGNITE-5011
URL: https://issues.apache.org/jira/browse/IGNITE-5011
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Trivial
{code}
visor> disco -t=0h
java.lang.IllegalArgumentException: Time frame size is not positive in: 0h
at org.apache.ignite.visor.visor$.timeFilter(visor.scala:2671)
at
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand.disco(VisorDiscoveryCommand.scala:127)
at
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
at
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
at
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:381)
at
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
at scala.App$class.main(App.scala:76)
at
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
(wrn) : Invalid command name: 'disco -t=0h'
(wrn) : Type 'help' to print commands list.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5020) Client node failed with NPE
Pavel Konstantinov created IGNITE-5020:
--
Summary: Client node failed with NPE
Key: IGNITE-5020
URL: https://issues.apache.org/jira/browse/IGNITE-5020
Project: Ignite
Issue Type: Bug
Affects Versions: 2.0
Reporter: Pavel Konstantinov
Priority: Blocker
Fix For: 2.0
{code}
[11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi]
Client node disconnected from cluster, will try to reconnect with new id
[newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571,
prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode
[id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0,
/127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0,
lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d,
isClient=true]]
[11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache:
igfs-data
[11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache:
offheap-sorted-100
[11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache:
c_replicated
[11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache:
c_partitioned2
[11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache:
offheap-fifo-100
[11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache:
oh_partitioned
[11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache:
near-lru-100
[11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache:
ttl_partitioned
[11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache:
c_partitioned3
[11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache:
offheap-lru-100
[11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache:
near-sorted-100
[11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache:
c_partitioned
[11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7,
minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5021) visorcmd: log command - incorrect chronology in file
Pavel Konstantinov created IGNITE-5021:
--
Summary: visorcmd: log command - incorrect chronology in file
Key: IGNITE-5021
URL: https://issues.apache.org/jira/browse/IGNITE-5021
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor
Events are configured in the grid
{code}
{code}
log -l -t=1
{code}
04/19/17, 11:42:25 | Log started.
04/19/17, 11:42:26 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:27 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:28 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:29 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:30 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:31 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:32 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:33 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:34 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:35 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:36:57 | => NODE_LEFT: id8=66e8fb9f, ip=0:0:0:0:0:0:0:1
04/19/17, 11:37:05 | => NODE_JOINED: id8=c0031666, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:02 | => NODE_LEFT: id8=be032f32, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:07 | => CLIENT_NODE_DISCONNECTED: id8=12dfc0d3,
ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:14 | => CLIENT_NODE_RECONNECTED: id8=12dfc0d3,
ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:18 | => NODE_JOINED: id8=f9466d50, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:19 | => NODE_JOINED: id8=3a0dadb7, ip=0:0:0:0:0:0:0:1
04/19/17, 11:42:36 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:37 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:38 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:39 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:40 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:41 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:42 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:43 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:44 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:45 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:46 | H/N/C|1 |3 |8 |^...|
04/19/17, 11:42:47 | H/N/C|1 |3 |8 |^...|
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5034) visorcmd: we need to fix cache info visor prints
Pavel Konstantinov created IGNITE-5034:
--
Summary: visorcmd: we need to fix cache info visor prints
Key: IGNITE-5034
URL: https://issues.apache.org/jira/browse/IGNITE-5034
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 2.0
Reporter: Pavel Konstantinov
Look at example of cache command result in AI 2.0
{code}
visor> cache -c=c_partitioned -a
Time of the snapshot: 04/20/17, 14:18:30
+==+
| Name(@) |Mode | Nodes | Entries (Heap / Off-heap)
| Hits| Misses | Reads | Writes |
+==+
| c_partitioned(@c0) | PARTITIONED | 2 | min: 134588 (11 / 34587)
| min: 0| min: 0| min: 0| min: 0|
|| | | avg: 150001.50 (11.00 /
5.50) | avg: 0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00 |
|| | | max: 165415 (11 / 65414)
| max: 0| max: 0| max: 0| max: 0|
+--+
Cache 'c_partitioned(@c0)':
+---+
| Name(@) | c_partitioned(@c0) |
| Nodes | 2 |
| Total size Min/Avg/Max | 134588 / 150001.50 / 165415 |
| Heap size Min/Avg/Max | 11 / 11.00 / 11 |
| Off-heap size Min/Avg/Max | 34587 / 5.50 / 65414|
+---+
Nodes for: c_partitioned(@c0)
+===+
| Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time|
Size | Hi/Mi/Rd/Wr |
+===+
| AF7CAEFE(@n0), 192.168.1.40 | 8| 23.76 % | 8.20 % | 00:01:19:153 |
Total: 165415| Hi: 0 |
| | | | | |
Heap: 11 | Mi: 0 |
| | | | | |
Off-Heap: 65414| Rd: 0 |
| | | | | |
Off-Heap Memory: 0 | Wr: 0 |
+-+--+---+--+--+--+-+
| C36C23B3(@n1), 192.168.1.40 | 8| 11.62 % | 8.80 % | 00:01:19:209 |
Total: 134588| Hi: 0 |
| | | | | |
Heap: 11 | Mi: 0 |
| | | | | |
Off-Heap: 34587| Rd: 0 |
| | | | | |
Off-Heap Memory: 0 | Wr: 0 |
+---+
{code}
This cache has onheapCacheEnabled = false and it means that all data should be
in off-heap by default but visor shows wrong info.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5035) visorcmd doesn't show all new properties that were added in AI 2.0 in CacheConfiguration
Pavel Konstantinov created IGNITE-5035: -- Summary: visorcmd doesn't show all new properties that were added in AI 2.0 in CacheConfiguration Key: IGNITE-5035 URL: https://issues.apache.org/jira/browse/IGNITE-5035 Project: Ignite Issue Type: Bug Components: visor Reporter: Pavel Konstantinov We need to update output of config command related to cache configuration -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5088) problems with trying OSGi
Pavel Konstantinov created IGNITE-5088:
--
Summary: problems with trying OSGi
Key: IGNITE-5088
URL: https://issues.apache.org/jira/browse/IGNITE-5088
Project: Ignite
Issue Type: Bug
Components: osgi
Reporter: Pavel Konstantinov
I've tried to execute test suit from AI 2.0 source build but faced with error.
I went through apache-ignite-2.0.0-src/modules/osgi/README.txt and stuck on
this step
{code}
You may then run the OSGi test suite:
mvn test -Dtest=IgniteOsgiTestSuite
{code}
Actually I ran such command
{code}
mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false
{code}
and got the following result
{code}
Results :
Tests in error:
IgniteOsgiServiceTest.testServiceExposedAndCallbacksInvoked » MalformedURL
unk...
IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled
» MalformedURL
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ignite-apache-license-gen .. SUCCESS [ 1.054 s]
[INFO] ignite-tools ... SUCCESS [ 2.244 s]
[INFO] ignite-core SUCCESS [ 46.015 s]
[INFO] ignite-log4j ... SUCCESS [ 0.530 s]
[INFO] ignite-indexing SUCCESS [ 1.589 s]
[INFO] ignite-urideploy ... SUCCESS [ 0.933 s]
[INFO] ignite-spring .. SUCCESS [ 0.959 s]
[INFO] ignite-hadoop .. SUCCESS [ 2.595 s]
[INFO] ignite-extdata-p2p . SUCCESS [ 0.384 s]
[INFO] ignite-extdata-uri-dep . SUCCESS [ 0.126 s]
[INFO] ignite-extdata-uri . SUCCESS [ 0.454 s]
[INFO] ignite-rest-http ... SUCCESS [ 0.799 s]
[INFO] ignite-clients . SUCCESS [ 0.284 s]
[INFO] ignite-spring-data . SUCCESS [ 0.297 s]
[INFO] ignite-web . SUCCESS [ 0.544 s]
[INFO] ignite-aop . SUCCESS [ 0.616 s]
[INFO] ignite-ssh . SUCCESS [ 0.395 s]
[INFO] ignite-jta . SUCCESS [ 0.552 s]
[INFO] ignite-aws . SUCCESS [ 0.904 s]
[INFO] ignite-log4j2 .. SUCCESS [ 0.702 s]
[INFO] ignite-slf4j ... SUCCESS [ 0.412 s]
[INFO] ignite-jcl . SUCCESS [ 0.563 s]
[INFO] ignite-codegen . SUCCESS [ 0.116 s]
[INFO] ignite-gce . SUCCESS [ 0.334 s]
[INFO] ignite-cloud ... SUCCESS [ 2.381 s]
[INFO] ignite-mesos ... SUCCESS [ 0.223 s]
[INFO] ignite-kafka ... SUCCESS [ 1.443 s]
[INFO] ignite-flume ... SUCCESS [ 0.894 s]
[INFO] ignite-yarn SUCCESS [ 0.628 s]
[INFO] ignite-jms11 ... SUCCESS [ 0.753 s]
[INFO] ignite-twitter . SUCCESS [ 0.589 s]
[INFO] ignite-mqtt SUCCESS [ 1.343 s]
[INFO] ignite-zookeeper ... SUCCESS [ 0.558 s]
[INFO] ignite-camel ... SUCCESS [ 1.086 s]
[INFO] ignite-storm ... SUCCESS [ 0.312 s]
[INFO] ignite-osgi-paxlogging . SUCCESS [ 0.109 s]
[INFO] ignite-osgi-karaf .. SUCCESS [ 0.049 s]
[INFO] ignite-osgi FAILURE [ 1.273 s]
[INFO] ignite-appserver-test .. SKIPPED
[INFO] ignite-websphere-test .. SKIPPED
[INFO] ignite-cassandra ... SKIPPED
[INFO] ignite-cassandra-store . SKIPPED
[INFO] ignite-cassandra-serializers ... SKIPPED
[INFO] ignite-flink ... SKIPPED
[INFO] ignite-kubernetes .. SKIPPED
[INFO] ignite-zeromq .. SKIPPED
[INFO] ignite-scalar .. SKIPPED
[INFO] ignite-spark ... SKIPPED
[INFO] ignite-visor-console ... SKIPPED
[INFO] ignite-visor-plugins ... SKIPPED
[INFO] apache-i
[jira] [Created] (IGNITE-5402) Errors related to multi-version support
Pavel Konstantinov created IGNITE-5402: -- Summary: Errors related to multi-version support Key: IGNITE-5402 URL: https://issues.apache.org/jira/browse/IGNITE-5402 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov 1) eviction policy for server and client is the same, but should be different 2) Marshaller on Summary is not changed when version is changed on Cluster set version 1.x and set OptimizedMarshaller go to Summary and look at preview - it shows Optimized change version to 2.0 - look at preview - marshaller is still Optimized -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5472) Web Console: replace 'username' to 'email'
Pavel Konstantinov created IGNITE-5472: -- Summary: Web Console: replace 'username' to 'email' Key: IGNITE-5472 URL: https://issues.apache.org/jira/browse/IGNITE-5472 Project: Ignite Issue Type: Bug Components: UI Reporter: Pavel Konstantinov Priority: Trivial I think we should use the word 'Email' instead of 'username' in error message in case if user with such email already registered. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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-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-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-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-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-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-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-10618) Web console: exclude daemon node from cluster size on Connected Clusters modal
Pavel Konstantinov created IGNITE-10618: --- Summary: Web console: exclude daemon node from cluster size on Connected Clusters modal Key: IGNITE-10618 URL: https://issues.apache.org/jira/browse/IGNITE-10618 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Attachments: image-2018-12-10-17-37-10-334.png !image-2018-12-10-17-37-10-334.png! -- 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-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-5657) Web Console: add apropriate placeholder in case if no columns are selected in table
Pavel Konstantinov created IGNITE-5657: -- Summary: Web Console: add apropriate placeholder in case if no columns are selected in table Key: IGNITE-5657 URL: https://issues.apache.org/jira/browse/IGNITE-5657 Project: Ignite Issue Type: Bug Components: UI Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5726) Duplicate dependencies in POM
Pavel Konstantinov created IGNITE-5726: -- Summary: Duplicate dependencies in POM Key: IGNITE-5726 URL: https://issues.apache.org/jira/browse/IGNITE-5726 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Import models from database Look at POM on Summary page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5746) Node mustn't start if memory policy is not configured
Pavel Konstantinov created IGNITE-5746:
--
Summary: Node mustn't start if memory policy is not configured
Key: IGNITE-5746
URL: https://issues.apache.org/jira/browse/IGNITE-5746
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
I faced with NPE in case if memory policy that set in cache is not configured
{code}
[11:27:30,979][SEVERE][srvc-deploy-#46%tester%][GridServiceProcessor] Failed to
do service reassignment (will retry): Test service: Key affinity singleton
class org.apache.ignite.IgniteCheckedException: Failed to get affinity mapping
from node: TcpDiscoveryNode [id=0882b08d-21e8-4fd1-add0-91c48fc8a15a,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1499919956746, loc=true,
ver=2.1.2#20170712-sha1:0cb6ac06, isClient=false]
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:476)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.keysToNodes(GridAffinityProcessor.java:347)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.mapKeyToNode(GridAffinityProcessor.java:259)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.reassign(GridServiceProcessor.java:974)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onDeployment(GridServiceProcessor.java:1484)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.processDeployment(GridServiceProcessor.java:1437)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1398)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:119)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1374)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:1806)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7229)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityInfoFromNode(GridAffinityProcessor.java:501)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:459)
... 12 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.affinity.GridAffinityUtils$AffinityJob.call(GridAffinityUtils.java:175)
at
org.apache.ignite.internal.processors.affinity.GridAffinityUtils$AffinityJob.call(GridAffinityUtils.java:130)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6608)
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:1115)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1385)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:640)
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:749)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:428)
at
org.apache.ignite.internal.processors.closure.GridClosureProc
[jira] [Created] (IGNITE-5760) web console: improve demo mode - add new features in demo that was added into product
Pavel Konstantinov created IGNITE-5760: -- Summary: web console: improve demo mode - add new features in demo that was added into product Key: IGNITE-5760 URL: https://issues.apache.org/jira/browse/IGNITE-5760 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5764) web console: delete sql command doesn't work
Pavel Konstantinov created IGNITE-5764: -- Summary: web console: delete sql command doesn't work Key: IGNITE-5764 URL: https://issues.apache.org/jira/browse/IGNITE-5764 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5876) Web console: error on opening Hadoop Configuration
Pavel Konstantinov created IGNITE-5876:
--
Summary: Web console: error on opening Hadoop Configuration
Key: IGNITE-5876
URL: https://issues.apache.org/jira/browse/IGNITE-5876
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
{code}
"Error: [$parse:syntax] Syntax Error: Token 'Object' is unexpected, expecting
[]] at column 9 of the expression [[object Object]] starting at [Object]].
http://errors.angularjs.org/1.5.11/$parse/syntax?p0=Object&p1=is%20unexpected%2C%20expecting%20%5B%5D%5D&p2=9&p3=%5Bobject%20Object%5D&p4=Object%5D
minErr/<@https://staging-console.gridgain.com/vendor.ba700f32d508b24fa354.js:1:761642
throwError@https://staging-console.gridgain.com
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5877) Web console: 'Execute query' doesn't work
Pavel Konstantinov created IGNITE-5877: -- Summary: Web console: 'Execute query' doesn't work Key: IGNITE-5877 URL: https://issues.apache.org/jira/browse/IGNITE-5877 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov For example just start Demo and try to execute its query. Query result panel doesn't appear after clicking Execute or Explain button. Query history is empty as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5878) Add memory policy name into IgniteOOM exception
Pavel Konstantinov created IGNITE-5878:
--
Summary: Add memory policy name into IgniteOOM exception
Key: IGNITE-5878
URL: https://issues.apache.org/jira/browse/IGNITE-5878
Project: Ignite
Issue Type: Wish
Reporter: Pavel Konstantinov
Priority: Minor
I got OOM exception but I was not able to understand what policy exactly I need
to tune
It will be more informative to add memory policy name into exception text
{code}
[14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
Runtime error caught during grid runnable execution: GridWorker
[name=db-checkpoint-thread, igniteInstanceName=tester, finished=false,
hashCode=392861026, interrupted=false, runner=db-checkpoint-thread-#41%tester%]
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find
a page for eviction [segmentCapacity=1580, loaded=622, maxDirtyPages=415,
dirtyPages=622, cpPages=0, pinnedInSegment=0, failedToPrepare=623]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
at
org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
at
org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
[14:25:24,964][WARNING][visor-tester-populate-cache-task-0][] Populating
cache: c_partitioned
[14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl]
Data streamer will not overwrite existing cache entries for better performance
(to change, set allowOverwrite to true)
[14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][] Query
execution (Query): c_partitioned
[14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query execution
task error
class org.apache.ignite.IgniteException: Runtime failure on bounds:
[lower=null, upper=null]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:965)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.cursor(IgniteCacheOffheapManagerImpl.java:1515)
at
org.apache.ignite.internal.processors.cach
[jira] [Created] (IGNITE-5888) Web console: Incorrect dependency 'undefined' with value 'null'
Pavel Konstantinov created IGNITE-5888:
--
Summary: Web console: Incorrect dependency 'undefined' with value
'null'
Key: IGNITE-5888
URL: https://issues.apache.org/jira/browse/IGNITE-5888
Project: Ignite
Issue Type: Bug
Reporter: Pavel Konstantinov
Changed store dialect from Generic to IBM DB2
{code}
org.apache.ignite
undefined
null
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5907) Add validation to Basic screen for Off-heap size
Pavel Konstantinov created IGNITE-5907: -- Summary: Add validation to Basic screen for Off-heap size Key: IGNITE-5907 URL: https://issues.apache.org/jira/browse/IGNITE-5907 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Pavel Konstantinov Fix For: 2.2 Off-heap size must be greater then initial off-heap size -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5908) Web console: may failed to open non-root if user is not authorized
Pavel Konstantinov created IGNITE-5908: -- Summary: Web console: may failed to open non-root if user is not authorized Key: IGNITE-5908 URL: https://issues.apache.org/jira/browse/IGNITE-5908 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov For example try to open http://localhost/configuration/basic Expected: should redirect to home page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5913) Web console: code (spring\java) is not generated for field 'Long query timeout:' on cluster level in Miscellaneous group
Pavel Konstantinov created IGNITE-5913: -- Summary: Web console: code (spring\java) is not generated for field 'Long query timeout:' on cluster level in Miscellaneous group Key: IGNITE-5913 URL: https://issues.apache.org/jira/browse/IGNITE-5913 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Pavel Konstantinov Priority: Minor Fix For: 2.2 It exists in Summary but not generated in Miscellaneous group -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB
Pavel Konstantinov created IGNITE-5914: -- Summary: Web console: incorrect cache mode in case if cache was created during importing model from DB Key: IGNITE-5914 URL: https://issues.apache.org/jira/browse/IGNITE-5914 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Pavel Konstantinov Fix For: 2.2 I set mode = Replicated, but after import cache has Partitioned mode -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5916) Web console: incorrect default value for Cache-Queries & Indexing-SQL index max inline size = -1
Pavel Konstantinov created IGNITE-5916: -- Summary: Web console: incorrect default value for Cache-Queries & Indexing-SQL index max inline size = -1 Key: IGNITE-5916 URL: https://issues.apache.org/jira/browse/IGNITE-5916 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov If I set -1 as real value then field become incorrect (red border) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5917) Fields have no error-triangle in case of incorrect value
Pavel Konstantinov created IGNITE-5917: -- Summary: Fields have no error-triangle in case of incorrect value Key: IGNITE-5917 URL: https://issues.apache.org/jira/browse/IGNITE-5917 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Pavel Konstantinov Fix For: 2.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5987) visorcmd: add possibility do not close visorcmd in batch mode
Pavel Konstantinov created IGNITE-5987: -- Summary: visorcmd: add possibility do not close visorcmd in batch mode Key: IGNITE-5987 URL: https://issues.apache.org/jira/browse/IGNITE-5987 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov That possibility will be useful for alert command which works only while visorcmd is active -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6447) Web console: the panel with text 'Demo mode' hides buttons on Query screen
Pavel Konstantinov created IGNITE-6447: -- Summary: Web console: the panel with text 'Demo mode' hides buttons on Query screen Key: IGNITE-6447 URL: https://issues.apache.org/jira/browse/IGNITE-6447 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6482) Add support for groups count
Pavel Konstantinov created IGNITE-6482: -- Summary: Add support for groups count Key: IGNITE-6482 URL: https://issues.apache.org/jira/browse/IGNITE-6482 Project: Ignite Issue Type: Improvement Components: yardstick Reporter: Pavel Konstantinov Assignee: Pavel Konstantinov Priority: Minor Current implementation supports only one group for caches. We need improve it to support more then one group. Each group will have / caches inside. Applicable only if option -cc (caches count) is set. Default groups count = 1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6508) Web console: chart has no labels on X axis in some cases
Pavel Konstantinov created IGNITE-6508: -- Summary: Web console: chart has no labels on X axis in some cases Key: IGNITE-6508 URL: https://issues.apache.org/jira/browse/IGNITE-6508 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Priority: Minor I'm noticed that in some cases X-axis has no lables -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen
Pavel Konstantinov created IGNITE-6617: -- Summary: Web console: there is no error message that cluster is not active on Queries screen Key: IGNITE-6617 URL: https://issues.apache.org/jira/browse/IGNITE-6617 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 2.1 Reporter: Pavel Konstantinov Fix For: 2.4 start cluster with persistent start web agent connected to this cluster open Queries on web console try to execute any 'select' query there is no error message that cluster is not active -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6618) Do not show client nodes in node selection modal
Pavel Konstantinov created IGNITE-6618:
--
Summary: Do not show client nodes in node selection modal
Key: IGNITE-6618
URL: https://issues.apache.org/jira/browse/IGNITE-6618
Project: Ignite
Issue Type: Bug
Components: wizards
Affects Versions: 2.1
Reporter: Pavel Konstantinov
Fix For: 2.3
I tried to 'Execute on Selected Node' the following query
{code}
SELECT c.id, d.id, p.id, p.salary
FROM "c_partitioned".City c
inner join "c_partitioned".Department d
on c.id=d.CTYID
inner join "c_partitioned".Person p
on d.id=p.depID and p.salary > 5000
inner join "c_partitioned".PersonBonus pb
on p.id=pb.perID and pb.COUNT < 5000
where exists (select * from "c_partitioned".Person where rank > 0)
{code}
and selected a client node in the list of nodes
and got exception
{code}
General error: "java.lang.NullPointerException"; SQL statement: SELECT c.id,
d.id, p.id, p.salary
FROM "c_partitioned".City c
inner join "c_partitioned".Department d
on c.id=d.CTYID
inner join "c_partitioned".Person p
on d.id=p.depID and p.salary > 5000
inner join "c_partitioned".PersonBonus pb
on p.id=pb.perID and pb.COUNT < 5000
where exists (select * from "c_partitioned".Person where rank > 0) [5-195]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6622) User defined function doesn't work if query executed via ignite.context().query().querySqlFieldsNoCache(qry, true);
Pavel Konstantinov created IGNITE-6622: -- Summary: User defined function doesn't work if query executed via ignite.context().query().querySqlFieldsNoCache(qry, true); Key: IGNITE-6622 URL: https://issues.apache.org/jira/browse/IGNITE-6622 Project: Ignite Issue Type: Bug Affects Versions: 2.3 Reporter: Pavel Konstantinov User defined function doesn't work if query executed via ignite.context().query().querySqlFieldsNoCache(qry, true); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6623) Web console: export query result set doesn't work on Edge
Pavel Konstantinov created IGNITE-6623: -- Summary: Web console: export query result set doesn't work on Edge Key: IGNITE-6623 URL: https://issues.apache.org/jira/browse/IGNITE-6623 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Execute any query and try to Export\ExportAll in result table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6771) Insert query failed if kye field is present in value fields
Pavel Konstantinov created IGNITE-6771:
--
Summary: Insert query failed if kye field is present in value
fields
Key: IGNITE-6771
URL: https://issues.apache.org/jira/browse/IGNITE-6771
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Components: sql
Affects Versions: 2.2
Reporter: Pavel Konstantinov
Priority: Minor
Fix For: 2.3
I'm imported model from DB where a table hasn't a primary key.
Then using web console I added key field manually (the first field in the
table).
Note:
{code}
{code}
Then I generated the project and started one server node.
I'm opened query in web console and tried to execute insert query
and got an error
{code}
...duplicate field
{code}
The issue disappeared only after I removed the same field from value fields.
I guess it is possible to handle that automatically in POJO logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6795) Web console: Make default file name for saving scan results more informative
Pavel Konstantinov created IGNITE-6795: -- Summary: Web console: Make default file name for saving scan results more informative Key: IGNITE-6795 URL: https://issues.apache.org/jira/browse/IGNITE-6795 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Components: wizards Reporter: Pavel Konstantinov Priority: Minor Currently file name is '' + '-all' in case if I want to save all result set. (export all) I suggest to use 'scan--all' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6796) GridClusterStateProcessor$5 has no @GridInternal annotation
Pavel Konstantinov created IGNITE-6796: -- Summary: GridClusterStateProcessor$5 has no @GridInternal annotation Key: IGNITE-6796 URL: https://issues.apache.org/jira/browse/IGNITE-6796 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-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)
[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-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-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-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-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-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-2950) Incorrect params list in secret.properties for PostgreSQL
Pavel Konstantinov created IGNITE-2950:
--
Summary: Incorrect params list in secret.properties for PostgreSQL
Key: IGNITE-2950
URL: https://issues.apache.org/jira/browse/IGNITE-2950
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Currently we generate the following parameters:
{code}
dsPostgreSQL.jdbc.server_name=YOUR_DATABASE_SERVER_NAME
dsPostgreSQL.jdbc.database_name=YOUR_DATABASE_NAME
dsPostgreSQL.jdbc.username=YOUR_USER_NAME
dsPostgreSQL.jdbc.password=YOUR_PASSWORD
{code}
But in XML configuration we use
{code}
{code}
Please fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2956) visorcmd: add possibility to enable\disable of alerts
Pavel Konstantinov created IGNITE-2956: -- Summary: visorcmd: add possibility to enable\disable of alerts Key: IGNITE-2956 URL: https://issues.apache.org/jira/browse/IGNITE-2956 Project: Ignite Issue Type: Improvement Environment: Currently user has ability only register and unregister of alerts. Will be more useful to add ability to enable and disable of alerts. Reporter: Pavel Konstantinov Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2960) The field Package is emplty in Import Model dialog
Pavel Konstantinov created IGNITE-2960: -- Summary: The field Package is emplty in Import Model dialog Key: IGNITE-2960 URL: https://issues.apache.org/jira/browse/IGNITE-2960 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Andrey Novikov It should contain a package name in format e.g. com.gridgain.pkonstantinov.model -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2961) Need to implement integer number validator
Pavel Konstantinov created IGNITE-2961: -- Summary: Need to implement integer number validator Key: IGNITE-2961 URL: https://issues.apache.org/jira/browse/IGNITE-2961 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov For example now it is allowable to enter 0.123 into Cache>Concurrency control>Max async operations and Save. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2962) 'Invalidate near cache' should appear only for partitioned cache
Pavel Konstantinov created IGNITE-2962: -- Summary: 'Invalidate near cache' should appear only for partitioned cache Key: IGNITE-2962 URL: https://issues.apache.org/jira/browse/IGNITE-2962 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2976) Close 'Import model from DB' if user answer Cancel in 'Unsaved changes' dialog
Pavel Konstantinov created IGNITE-2976: -- Summary: Close 'Import model from DB' if user answer Cancel in 'Unsaved changes' dialog Key: IGNITE-2976 URL: https://issues.apache.org/jira/browse/IGNITE-2976 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Priority: Minor # Open existent model # change cache and DO NOT SAVE # click 'Import from DB' # 'Unsaved changes' appear # click Cancel Observing: empty Import dialog Expecting: Import dialog should close -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2984) Need to add validation that Alias and Index fields are present in Fields list
Pavel Konstantinov created IGNITE-2984: -- Summary: Need to add validation that Alias and Index fields are present in Fields list Key: IGNITE-2984 URL: https://issues.apache.org/jira/browse/IGNITE-2984 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2985) error in dev-console after deleting all IPs from Addresses list
Pavel Konstantinov created IGNITE-2985:
--
Summary: error in dev-console after deleting all IPs from
Addresses list
Key: IGNITE-2985
URL: https://issues.apache.org/jira/browse/IGNITE-2985
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Priority: Minor
# error in dev-console after deleting all IPs from Addresses list
{code}
11:28:26.928 TypeError: element is null
stripCommentsFromElement() vendors.js:42722
queueAnimation() vendors.js:44159
$$AnimateQueueProvider
[jira] [Created] (IGNITE-2987) validation doesn't work for Binary configuration > Type configurations > Item >ID mapper | Name mapper | Serializer
Pavel Konstantinov created IGNITE-2987: -- Summary: validation doesn't work for Binary configuration > Type configurations > Item >ID mapper | Name mapper | Serializer Key: IGNITE-2987 URL: https://issues.apache.org/jira/browse/IGNITE-2987 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2986) now the field with incorrect value is scrolled to the top of the page even if it is visible
Pavel Konstantinov created IGNITE-2986: -- Summary: now the field with incorrect value is scrolled to the top of the page even if it is visible Key: IGNITE-2986 URL: https://issues.apache.org/jira/browse/IGNITE-2986 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2988) It is allowable to Save cluster with incorrect Local address (IP address too) in Multicast discovery settings
Pavel Konstantinov created IGNITE-2988: -- Summary: It is allowable to Save cluster with incorrect Local address (IP address too) in Multicast discovery settings Key: IGNITE-2988 URL: https://issues.apache.org/jira/browse/IGNITE-2988 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2989) Error on Save swap > Maximum sparsity: set value to 222
Pavel Konstantinov created IGNITE-2989:
--
Summary: Error on Save swap > Maximum sparsity: set value to 222
Key: IGNITE-2989
URL: https://issues.apache.org/jira/browse/IGNITE-2989
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
swap > Maximum sparsity: set value to 222 and Save
No error triangle was showed
{code}
14:53:54.837 Error: Syntax error, unrecognized expression: #
Sizzlehttps://staging-console.gridgain.com/vendors.js:121839:17
Sizzlehttps://staging-console.gridgain.com/vendors.js:122268:53
Sizzle@https://staging-console.gridgain.com/vendors.js:121509:28
.find@https://staging-console.gridgain.com/vendors.js:122709:13
showPopoverMessage@https://staging-console.gridgain.com/app.js:18348:30
validate@https://staging-console.gridgain.com/app.js:15565:1
.execute/https://staging-console.gridgain.com/app.js:15711:25
anonymous/fn@https://staging-console.gridgain.com/vendors.js line 110814 >
Function:2:450
expensiveCheckFn@https://staging-console.gridgain.com/vendors.js:111705:24
ngEventHandler/https://staging-console.gridgain.com/vendors.js:114672:21
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/vendors.js:112483:22
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/vendors.js:112506:26
ngEventHandler/<@https://staging-console.gridgain.com/vendors.js:114677:21
jQuery.event.dispatch@https://staging-console.gridgain.com/vendors.js:123860:25
jQuery.event.add/elemData.handle@https://staging-console.gridgain.com/vendors.js:123731:91
1 vendors.js:110029:24
consoleLog/<() vendors.js:110029
$ExceptionHandlerProvider/this.$get
[jira] [Created] (IGNITE-2990) Undo button doesn't hide after undoing
Pavel Konstantinov created IGNITE-2990: -- Summary: Undo button doesn't hide after undoing Key: IGNITE-2990 URL: https://issues.apache.org/jira/browse/IGNITE-2990 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2991) It is allowable to set incorrect big valu for Port range
Pavel Konstantinov created IGNITE-2991: -- Summary: It is allowable to set incorrect big valu for Port range Key: IGNITE-2991 URL: https://issues.apache.org/jira/browse/IGNITE-2991 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov I think the maximum possible value should be set to 65536 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2992) For some fields the red border does not appper in case of invalid value
Pavel Konstantinov created IGNITE-2992: -- Summary: For some fields the red border does not appper in case of invalid value Key: IGNITE-2992 URL: https://issues.apache.org/jira/browse/IGNITE-2992 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov For example Manager factory: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2994) IGFS > Put executor service > has no red border in case of invalid value
Pavel Konstantinov created IGNITE-2994: -- Summary: IGFS > Put executor service > has no red border in case of invalid value Key: IGNITE-2994 URL: https://issues.apache.org/jira/browse/IGNITE-2994 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2993) Different messages in error triangle and on Save
Pavel Konstantinov created IGNITE-2993: -- Summary: Different messages in error triangle and on Save Key: IGNITE-2993 URL: https://issues.apache.org/jira/browse/IGNITE-2993 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov I found that in Manager factory field -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2998) Total Max heap and Total Commited heap shows the same numbers in the tooltip in demo mode
Pavel Konstantinov created IGNITE-2998: -- Summary: Total Max heap and Total Commited heap shows the same numbers in the tooltip in demo mode Key: IGNITE-2998 URL: https://issues.apache.org/jira/browse/IGNITE-2998 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Andrey Novikov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2999) Prepared the invalid SQL query if user inserts it text by double clicking in metadata dialog
Pavel Konstantinov created IGNITE-2999:
--
Summary: Prepared the invalid SQL query if user inserts it text by
double clicking in metadata dialog
Key: IGNITE-2999
URL: https://issues.apache.org/jira/browse/IGNITE-2999
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov
I'm created the following query:
{code}
select c.ID,c.NAME,c.PARKINGID,p.NAME,p.CAPACITY from "CarCache".Car c inner
join "ParkingCache".Parking p on p.id = c.PARKINGID
{code}
But when I execute EXPLAIN I got the following error
{code}
Error: {"message":"class org.apache.ignite.IgniteException: Failed to parse
query: EXPLAIN select c.ID,c.NAME,c.PARKINGID,p.NAME,p. from \"CarCache\".Car c
inner join \"ParkingCache\".Parking p on p.id = c.PARKINGID","code":1}
{code}
As you can see the query text doesn't contain 'CAPACITY' before 'from'. The
word 'CAPACITY' was added by double clicking in metadata dialog.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3000) SQL: scan doesn't work for default cache
Pavel Konstantinov created IGNITE-3000:
--
Summary: SQL: scan doesn't work for default cache
Key: IGNITE-3000
URL: https://issues.apache.org/jira/browse/IGNITE-3000
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov
{code}
Error: {"message":"Failed to find cache with name: ","code":1}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3001) SQL: 'show query' doesn't work after SCAN
Pavel Konstantinov created IGNITE-3001:
--
Summary: SQL: 'show query' doesn't work after SCAN
Key: IGNITE-3001
URL: https://issues.apache.org/jira/browse/IGNITE-3001
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov
# select any cache
# execute SCAN
dev-console populated with error:
{code}
09:44:58.667 Error: paragraph.queryArgs.query is undefined
.execute/https://staging-console.gridgain.com/app.js:21196:1
anonymous/fn@https://staging-console.gridgain.com/vendors.js line 111736 >
Function:2:341
expensiveCheckFn@https://staging-console.gridgain.com/vendors.js:112627:24
ngEventHandler/https://staging-console.gridgain.com/vendors.js:115594:21
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/vendors.js:113405:22
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/vendors.js:113428:26
ngEventHandler/<@https://staging-console.gridgain.com/vendors.js:115599:21
jQuery.event.dispatch@https://staging-console.gridgain.com/vendors.js:124782:25
jQuery.event.add/elemData.handle@https://staging-console.gridgain.com/vendors.js:124653:91
1 vendors.js:110951:24
consoleLog/<() vendors.js:110951
$ExceptionHandlerProvider/this.$get
[jira] [Created] (IGNITE-3002) We need to do some explanation for user what is demo
Pavel Konstantinov created IGNITE-3002: -- Summary: We need to do some explanation for user what is demo Key: IGNITE-3002 URL: https://issues.apache.org/jira/browse/IGNITE-3002 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov This may be a tooltip for 'Start demo' or some dialog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3003) We need to add two new properties to FileSystemConfiguration
Pavel Konstantinov created IGNITE-3003: -- Summary: We need to add two new properties to FileSystemConfiguration Key: IGNITE-3003 URL: https://issues.apache.org/jira/browse/IGNITE-3003 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov FileSystemConfiguration.setColocateMetadata ( boolean colocateMeta ) : void FileSystemConfiguration.setRelaxedConsistency ( boolean relaxedConsistency ) : void -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3005) visorcmd: we need to improve alert command
Pavel Konstantinov created IGNITE-3005: -- Summary: visorcmd: we need to improve alert command Key: IGNITE-3005 URL: https://issues.apache.org/jira/browse/IGNITE-3005 Project: Ignite Issue Type: Improvement Components: visor Affects Versions: 1.5.0.final Reporter: Pavel Konstantinov Priority: Trivial Fix For: 1.6 Presently per-node alert prints in log it's info without node ID and user cannot understand on what node that alert was triggered. So we need to print out node ID8 in alert info for per-node alerts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3012) Filtration of defualt cache doesn't work
Pavel Konstantinov created IGNITE-3012: -- Summary: Filtration of defualt cache doesn't work Key: IGNITE-3012 URL: https://issues.apache.org/jira/browse/IGNITE-3012 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Priority: Minor If grid contains default cache (cache without a name, name=null) then user have no ability to find it using Filter. The default cache displayed as , but it could not be found by entering into the Filter the same string ''. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3016) Unexpected 'Unsaved changes' when switching between a caches in demo mode
Pavel Konstantinov created IGNITE-3016: -- Summary: Unexpected 'Unsaved changes' when switching between a caches in demo mode Key: IGNITE-3016 URL: https://issues.apache.org/jira/browse/IGNITE-3016 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Andrey Novikov Start demo mode Open caches Press f5 Choose another cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3026) Import model generates incorrect type for blob field
Pavel Konstantinov created IGNITE-3026:
--
Summary: Import model generates incorrect type for blob field
Key: IGNITE-3026
URL: https://issues.apache.org/jira/browse/IGNITE-3026
Project: Ignite
Issue Type: Sub-task
Components: UI
Affects Versions: 1.5.0.final
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
Fix For: 1.6
If table contains a field of blob type then such fields imported as Object and
console generates incorrect java code
{code}
import Object;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3031) 'Domain model for SQL query' section shows the old values for new Type
Pavel Konstantinov created IGNITE-3031: -- Summary: 'Domain model for SQL query' section shows the old values for new Type Key: IGNITE-3031 URL: https://issues.apache.org/jira/browse/IGNITE-3031 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov 1) import some types from DB 2) remove all 3) add new type observed: 'Domain model for SQL query' section shows the old values for new Type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3032) 'Domain model for SQL query' section doesn't expand if 'Fields' contains invalid field
Pavel Konstantinov created IGNITE-3032: -- Summary: 'Domain model for SQL query' section doesn't expand if 'Fields' contains invalid field Key: IGNITE-3032 URL: https://issues.apache.org/jira/browse/IGNITE-3032 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov 1) expand the 'Domain model for SQL query' section 2) set invalid type for field 3) collapse the section 4) click Save -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3033) Domain model for SQL query: Name field and Type field do not have red border and triangle in case of invalid value
Pavel Konstantinov created IGNITE-3033: -- Summary: Domain model for SQL query: Name field and Type field do not have red border and triangle in case of invalid value Key: IGNITE-3033 URL: https://issues.apache.org/jira/browse/IGNITE-3033 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Name field = 7 Type field = !!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3034) Domain model for SQL query: Undo button not hide after undo
Pavel Konstantinov created IGNITE-3034: -- Summary: Domain model for SQL query: Undo button not hide after undo Key: IGNITE-3034 URL: https://issues.apache.org/jira/browse/IGNITE-3034 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov the button is hidden only on the second click -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3036) We need to set red border to empty mandatory fields after Save
Pavel Konstantinov created IGNITE-3036: -- Summary: We need to set red border to empty mandatory fields after Save Key: IGNITE-3036 URL: https://issues.apache.org/jira/browse/IGNITE-3036 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3037) we need to enable read-through or write-through if cache generated during importing model from DB
Pavel Konstantinov created IGNITE-3037: -- Summary: we need to enable read-through or write-through if cache generated during importing model from DB Key: IGNITE-3037 URL: https://issues.apache.org/jira/browse/IGNITE-3037 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov In case when cache created from a template which doesn't have these properties enabled we must enable at least one of its. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3044) Save doesn't become enabled after type configuration was deleted
Pavel Konstantinov created IGNITE-3044: -- Summary: Save doesn't become enabled after type configuration was deleted Key: IGNITE-3044 URL: https://issues.apache.org/jira/browse/IGNITE-3044 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Cluster > Binary Configuration Delete Type Configuration Save is still disabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
