[jira] [Created] (IGNITE-1296) Add to local node metrics new value - up time
Pavel Konstantinov created IGNITE-1296:
--
Summary: Add to local node metrics new value - up time
Key: IGNITE-1296
URL: https://issues.apache.org/jira/browse/IGNITE-1296
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Priority: Trivial
Fix For: ignite-1.4
Currently looking at the node console output I don't understand how many time
node already working. So I suggesting to add this info to the (for example) the
Node section as 'up time=4d 23h 45m 32sec'.
{code}
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=79d693a9, name=tester-DC1]
^-- H/N/C [hosts=2, nodes=2, CPUs=32]
^-- CPU [cur=4.7%, avg=4.84%, GC=0%]
^-- Heap [used=23324MB, free=35.94%, comm=29244MB]
^-- Public thread pool [active=0, idle=32, qSize=0]
^-- System thread pool [active=0, idle=32, qSize=0]
^-- Outbound messages queue [size=0]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710963#comment-14710963
]
Pavel Konstantinov commented on IGNITE-850:
---
XML for "Peer class loading"-"Local class path exclude" generated incorrectly
value "org.test" generated to
{code}
o
r
g
.
t
e
s
t
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710963#comment-14710963
]
Pavel Konstantinov edited comment on IGNITE-850 at 8/25/15 9:19 AM:
1) XML for "Peer class loading"-"Local class path exclude" generated incorrectly
value "org.test" generated to
{code}
o
r
g
.
t
e
s
t
{code}
2) CXlusters-Transactions: XML is not generated for 'Manager lookup:' value
was (Author: pkonstantinov):
XML for "Peer class loading"-"Local class path exclude" generated incorrectly
value "org.test" generated to
{code}
o
r
g
.
t
e
s
t
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710963#comment-14710963
]
Pavel Konstantinov edited comment on IGNITE-850 at 8/26/15 4:40 AM:
1) XML for "Peer class loading"-"Local class path exclude" generated incorrectly
value "org.test" generated to
{code}
o
r
g
.
t
e
s
t
{code}
2) Clusters-Transactions: XML is not generated for 'Manager lookup:' value
was (Author: pkonstantinov):
1) XML for "Peer class loading"-"Local class path exclude" generated incorrectly
value "org.test" generated to
{code}
o
r
g
.
t
e
s
t
{code}
2) CXlusters-Transactions: XML is not generated for 'Manager lookup:' value
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712657#comment-14712657 ] Pavel Konstantinov commented on IGNITE-1177: I suggesting to add possibility to sort Indexed Fields or maybe sort alphabetically always. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712657#comment-14712657 ] Pavel Konstantinov edited comment on IGNITE-1177 at 8/26/15 7:38 AM: - I suggesting to add possibility to sort Indexed Fields or maybe sort alphabetically always. Otherwise it is difficult to find the field if list contains more then 10 fields. was (Author: pkonstantinov): I suggesting to add possibility to sort Indexed Fields or maybe sort alphabetically always. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718005#comment-14718005 ] Pavel Konstantinov commented on IGNITE-850: --- Need to add 'IgniteConfiguration cfg = new IgniteConfiguration();' in Java-snippet for General. > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718045#comment-14718045 ] Pavel Konstantinov edited comment on IGNITE-1177 at 8/28/15 4:36 AM: - Display items count in case when more then 10. E.g.: "Caches (35):" was (Author: pkonstantinov): Display items count in case when more then 10. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718045#comment-14718045 ] Pavel Konstantinov commented on IGNITE-1177: Display items count in case when more then 10. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718045#comment-14718045 ] Pavel Konstantinov edited comment on IGNITE-1177 at 8/28/15 4:37 AM: - Display items count in case when more then 10. E.g.: "Types metadata: (385):" was (Author: pkonstantinov): Display items count in case when more then 10. E.g.: "Caches (35):" > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718045#comment-14718045 ] Pavel Konstantinov edited comment on IGNITE-1177 at 8/28/15 4:37 AM: - Display items count in case when more then 10. E.g.: "Types metadata(385):" was (Author: pkonstantinov): Display items count in case when more then 10. E.g.: "Types metadata: (385):" > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718045#comment-14718045 ] Pavel Konstantinov edited comment on IGNITE-1177 at 8/28/15 4:49 AM: - 1) Display items count in case when more then 10. E.g.: "Types metadata(385):" 2) To do scrolling instead pages in table list for loading metadata from DB 3) Implement batch loading was (Author: pkonstantinov): Display items count in case when more then 10. E.g.: "Types metadata(385):" > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1328) We need to fix OS detection to support Windows 10
Pavel Konstantinov created IGNITE-1328: -- Summary: We need to fix OS detection to support Windows 10 Key: IGNITE-1328 URL: https://issues.apache.org/jira/browse/IGNITE-1328 Project: Ignite Issue Type: Bug Components: general Reporter: Pavel Konstantinov Priority: Trivial Please look at IgniteUtils starting line 320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1155) Implement in web-agent feature to extract metadata from RDBMs and send it to web-server.
[ https://issues.apache.org/jira/browse/IGNITE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723198#comment-14723198 ] Pavel Konstantinov commented on IGNITE-1155: We need to improve errors handling. I'm started agent and set incorrect JDBC driver and JDBC URL and now errors was displayed. > Implement in web-agent feature to extract metadata from RDBMs and send it to > web-server. > > > Key: IGNITE-1155 > URL: https://issues.apache.org/jira/browse/IGNITE-1155 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Evdokimov >Assignee: Sergey Evdokimov > Fix For: ignite-1.4 > > Attachments: IGNITE-1155.patch > > > We need to implement in web-agent feature to extract metadata from RDBMS and > send it to web-server. > Web agent should: > 1) Receive a connection parameters to RDBMS (jdbc url, user, password) > from web-server. > 2) Connect to database, extract metadata. > 3) Send metadata back to web-server. > Actually Ignite already has some code to work with database metadata in > 'ignite-schema-import' module. > But 'ignite-schema-import' module contains UI on javaFX , web-agent must not > depend on javaFX, so UI should be extracted to separated module > 'ignite-schema-import-ui'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1155) Implement in web-agent feature to extract metadata from RDBMs and send it to web-server.
[ https://issues.apache.org/jira/browse/IGNITE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723198#comment-14723198 ] Pavel Konstantinov edited comment on IGNITE-1155 at 8/31/15 8:34 AM: - We need to improve errors handling. I'm started agent and set incorrect JDBC driver and JDBC URL and no errors was displayed. was (Author: pkonstantinov): We need to improve errors handling. I'm started agent and set incorrect JDBC driver and JDBC URL and now errors was displayed. > Implement in web-agent feature to extract metadata from RDBMs and send it to > web-server. > > > Key: IGNITE-1155 > URL: https://issues.apache.org/jira/browse/IGNITE-1155 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Evdokimov >Assignee: Sergey Evdokimov > Fix For: ignite-1.4 > > Attachments: IGNITE-1155.patch > > > We need to implement in web-agent feature to extract metadata from RDBMS and > send it to web-server. > Web agent should: > 1) Receive a connection parameters to RDBMS (jdbc url, user, password) > from web-server. > 2) Connect to database, extract metadata. > 3) Send metadata back to web-server. > Actually Ignite already has some code to work with database metadata in > 'ignite-schema-import' module. > But 'ignite-schema-import' module contains UI on javaFX , web-agent must not > depend on javaFX, so UI should be extracted to separated module > 'ignite-schema-import-ui'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1155) Implement in web-agent feature to extract metadata from RDBMs and send it to web-server.
[ https://issues.apache.org/jira/browse/IGNITE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723198#comment-14723198 ] Pavel Konstantinov edited comment on IGNITE-1155 at 8/31/15 8:35 AM: - We need to improve errors handling. I'm started agent and set incorrect JDBC driver and JDBC URL and no error message was displayed. was (Author: pkonstantinov): We need to improve errors handling. I'm started agent and set incorrect JDBC driver and JDBC URL and no errors was displayed. > Implement in web-agent feature to extract metadata from RDBMs and send it to > web-server. > > > Key: IGNITE-1155 > URL: https://issues.apache.org/jira/browse/IGNITE-1155 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Evdokimov >Assignee: Sergey Evdokimov > Fix For: ignite-1.4 > > Attachments: IGNITE-1155.patch > > > We need to implement in web-agent feature to extract metadata from RDBMS and > send it to web-server. > Web agent should: > 1) Receive a connection parameters to RDBMS (jdbc url, user, password) > from web-server. > 2) Connect to database, extract metadata. > 3) Send metadata back to web-server. > Actually Ignite already has some code to work with database metadata in > 'ignite-schema-import' module. > But 'ignite-schema-import' module contains UI on javaFX , web-agent must not > depend on javaFX, so UI should be extracted to separated module > 'ignite-schema-import-ui'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723222#comment-14723222 ] Pavel Konstantinov commented on IGNITE-843: --- Dmitriy, from now I will test on Mac too. > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723293#comment-14723293 ] Pavel Konstantinov commented on IGNITE-851: --- Cache- Queries & Indexing - Metadata not saved. 0) use t...@test.com\test 1) Remove all caches 2) create new one, link to grid1 3) choose one metadata (Advise_index) 4) save cache 5) open clusters then return ro caches and check > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723293#comment-14723293 ] Pavel Konstantinov edited comment on IGNITE-851 at 8/31/15 10:53 AM: - Cache- Queries & Indexing - Metadata not saved. 0) use t...@test.com\test 1) Remove all caches 2) create new one, link to grid1 3) choose one metadata (Advise_index) 4) save cache 5) open clusters then return to caches and check was (Author: pkonstantinov): Cache- Queries & Indexing - Metadata not saved. 0) use t...@test.com\test 1) Remove all caches 2) create new one, link to grid1 3) choose one metadata (Advise_index) 4) save cache 5) open clusters then return ro caches and check > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724758#comment-14724758
]
Pavel Konstantinov commented on IGNITE-1146:
I'm loaded metadata from DB2 and start node using generated xml and got:
{code}
class org.apache.ignite.IgniteException: Failed to register query type:
TypeDescriptor [name=org.apache.ignite.Comalgorithm, fields={APCSBJCODE=class
java.math.BigDecimal, APCID=class java.math.BigDecimal, AGRSBJCODE=class
java.math.BigDecimal, AGRID=class java.math.BigDecimal, DAOSBJCODE=class
java.math.BigDecimal, DAOID=class java.math.BigDecimal, CTPSBJCODE=class
java.math.BigDecimal, CTPID=class java.math.BigDecimal, apcsbjcode=class
java.math.BigDecimal, apcid=class java.math.BigDecimal, al
gcode=class java.math.BigDecimal, algisversioned=class java.lang.Short,
algtype=class java.lang.Integer, algcalcobjecttype=class java.lang.Integer,
algclasspath=class java.lang.String, algcomment=class java.lang.String,
algopendate=class java.sql.Date, algclosedate=class java.sql.Date,
algentstatus=class java.lang.Integer, agrsbjcode=class java.math.BigDecimal,
agrid=class java.math.BigDecimal, daosbjcode=class java.math.BigDecimal,
daoid=class java.math.BigDecimal, ctpsbjcode=class java.math.Bi
gDecimal, ctpid=class java.math.BigDecimal, algusefields=class
java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
FK3COMALGORITHM=IndexDescriptor [type=SORTED], FK4COMALGORITHM=IndexDescriptor
[type=SORTED], SQL050208183448780=IndexDescriptor [type=SORTED]},
fullTextIdx=null, keyCls=class java.lang.Object, valCls=class java.lang.Object,
valTextIdx=false, registered=false]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:692)
at org.apache.ignite.Ignition.start(Ignition.java:349)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:289)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to register
query type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class java.m
ath.BigDecimal, algcode=class java.math.BigDecimal, algisversioned=class
java.lang.Short, algtype=class java.lang.Integer, algcalcobjecttype=class
java.lang.Integer, algclasspath=class java.lang.String, algcomment=class
java.lang.String, algopendate=class java.sql.Date, algclosedate=class
java.sql.Date, algentstatus=class java.lang.Integer, agrsbjcode=class
java.math.BigDecimal, agrid=class java.math.BigDecimal, daosbjcode=class
java.math.BigDecimal, daoid=class java.math.BigDecimal, ctpsbjcode=
class java.math.BigDecimal, ctpid=class java.math.BigDecimal,
algusefields=class java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor
[type=SORTED], FK3COMALGORITHM=IndexDescriptor [type=SORTED],
FK4COMALGORITHM=IndexDescriptor [type=SORTED],
SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
keyCls=class java.lang.Object, valCls=class java.lang.Object, valTextIdx=false,
registered=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:963)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:157)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:249)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:925)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:782)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1549)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1416)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:916)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:843)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:735)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:527)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:497)
at org.apache.ignite.Ignition.start(Ignition.java:346)
... 1 more
Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
Duplicate column name "APCSBJCODE"; SQL statemen
[jira] [Updated] (IGNITE-1146) Implement summary page with configuration downloads.
[ https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1146: --- Attachment: test-cluster-2.xml > Implement summary page with configuration downloads. > > > Key: IGNITE-1146 > URL: https://issues.apache.org/jira/browse/IGNITE-1146 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Andrey Novikov > Fix For: ignite-1.4 > > Attachments: summary - client.png, summary - server.png, > test-cluster-2.xml > > > Generate: > * sprint xml configuration; > * java class with configuration; > * java snipplet with configuration; > * docker file for run with this configuration. > Download all generated files as zip archive, generate client configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724758#comment-14724758
]
Pavel Konstantinov edited comment on IGNITE-1146 at 9/1/15 4:08 AM:
I'm loaded metadata from DB2 and start node using generated xml and got:
{code}
class org.apache.ignite.IgniteException: Failed to register query type:
TypeDescriptor [name=org.apache.ignite.Comalgorithm, fields={APCSBJCODE=class
java.math.BigDecimal, APCID=class java.math.BigDecimal, AGRSBJCODE=class
java.math.BigDecimal, AGRID=class java.math.BigDecimal, DAOSBJCODE=class
java.math.BigDecimal, DAOID=class java.math.BigDecimal, CTPSBJCODE=class
java.math.BigDecimal, CTPID=class java.math.BigDecimal, apcsbjcode=class
java.math.BigDecimal, apcid=class java.math.BigDecimal, al
gcode=class java.math.BigDecimal, algisversioned=class java.lang.Short,
algtype=class java.lang.Integer, algcalcobjecttype=class java.lang.Integer,
algclasspath=class java.lang.String, algcomment=class java.lang.String,
algopendate=class java.sql.Date, algclosedate=class java.sql.Date,
algentstatus=class java.lang.Integer, agrsbjcode=class java.math.BigDecimal,
agrid=class java.math.BigDecimal, daosbjcode=class java.math.BigDecimal,
daoid=class java.math.BigDecimal, ctpsbjcode=class java.math.Bi
gDecimal, ctpid=class java.math.BigDecimal, algusefields=class
java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
FK3COMALGORITHM=IndexDescriptor [type=SORTED], FK4COMALGORITHM=IndexDescriptor
[type=SORTED], SQL050208183448780=IndexDescriptor [type=SORTED]},
fullTextIdx=null, keyCls=class java.lang.Object, valCls=class java.lang.Object,
valTextIdx=false, registered=false]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:692)
at org.apache.ignite.Ignition.start(Ignition.java:349)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:289)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to register
query type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class java.m
ath.BigDecimal, algcode=class java.math.BigDecimal, algisversioned=class
java.lang.Short, algtype=class java.lang.Integer, algcalcobjecttype=class
java.lang.Integer, algclasspath=class java.lang.String, algcomment=class
java.lang.String, algopendate=class java.sql.Date, algclosedate=class
java.sql.Date, algentstatus=class java.lang.Integer, agrsbjcode=class
java.math.BigDecimal, agrid=class java.math.BigDecimal, daosbjcode=class
java.math.BigDecimal, daoid=class java.math.BigDecimal, ctpsbjcode=
class java.math.BigDecimal, ctpid=class java.math.BigDecimal,
algusefields=class java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor
[type=SORTED], FK3COMALGORITHM=IndexDescriptor [type=SORTED],
FK4COMALGORITHM=IndexDescriptor [type=SORTED],
SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
keyCls=class java.lang.Object, valCls=class java.lang.Object, valTextIdx=false,
registered=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:963)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:157)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:249)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:925)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:782)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1549)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1416)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:916)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:843)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:735)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:527)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:497)
at org.apache.ignite.Ignition.start(Ignition.java:346)
... 1 more
Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
D
[jira] [Comment Edited] (IGNITE-1146) Implement summary page with configuration downloads.
[
https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724758#comment-14724758
]
Pavel Konstantinov edited comment on IGNITE-1146 at 9/1/15 4:13 AM:
I'm loaded metadata from DB2 and start(used 7.3.3-p6) node using generated xml
and got:
{code}
class org.apache.ignite.IgniteException: Failed to register query type:
TypeDescriptor [name=org.apache.ignite.Comalgorithm, fields={APCSBJCODE=class
java.math.BigDecimal, APCID=class java.math.BigDecimal, AGRSBJCODE=class
java.math.BigDecimal, AGRID=class java.math.BigDecimal, DAOSBJCODE=class
java.math.BigDecimal, DAOID=class java.math.BigDecimal, CTPSBJCODE=class
java.math.BigDecimal, CTPID=class java.math.BigDecimal, apcsbjcode=class
java.math.BigDecimal, apcid=class java.math.BigDecimal, al
gcode=class java.math.BigDecimal, algisversioned=class java.lang.Short,
algtype=class java.lang.Integer, algcalcobjecttype=class java.lang.Integer,
algclasspath=class java.lang.String, algcomment=class java.lang.String,
algopendate=class java.sql.Date, algclosedate=class java.sql.Date,
algentstatus=class java.lang.Integer, agrsbjcode=class java.math.BigDecimal,
agrid=class java.math.BigDecimal, daosbjcode=class java.math.BigDecimal,
daoid=class java.math.BigDecimal, ctpsbjcode=class java.math.Bi
gDecimal, ctpid=class java.math.BigDecimal, algusefields=class
java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
FK3COMALGORITHM=IndexDescriptor [type=SORTED], FK4COMALGORITHM=IndexDescriptor
[type=SORTED], SQL050208183448780=IndexDescriptor [type=SORTED]},
fullTextIdx=null, keyCls=class java.lang.Object, valCls=class java.lang.Object,
valTextIdx=false, registered=false]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:692)
at org.apache.ignite.Ignition.start(Ignition.java:349)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:289)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to register
query type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class java.m
ath.BigDecimal, algcode=class java.math.BigDecimal, algisversioned=class
java.lang.Short, algtype=class java.lang.Integer, algcalcobjecttype=class
java.lang.Integer, algclasspath=class java.lang.String, algcomment=class
java.lang.String, algopendate=class java.sql.Date, algclosedate=class
java.sql.Date, algentstatus=class java.lang.Integer, agrsbjcode=class
java.math.BigDecimal, agrid=class java.math.BigDecimal, daosbjcode=class
java.math.BigDecimal, daoid=class java.math.BigDecimal, ctpsbjcode=
class java.math.BigDecimal, ctpid=class java.math.BigDecimal,
algusefields=class java.lang.String}, indexes={FK1COMALGORITHM=IndexDescriptor
[type=SORTED], FK3COMALGORITHM=IndexDescriptor [type=SORTED],
FK4COMALGORITHM=IndexDescriptor [type=SORTED],
SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
keyCls=class java.lang.Object, valCls=class java.lang.Object, valTextIdx=false,
registered=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:963)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:157)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:249)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:925)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:782)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1549)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1416)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:916)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:843)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:735)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:527)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:497)
at org.apache.ignite.Ignition.start(Ignition.java:346)
... 1 more
Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбц
[jira] [Created] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
Pavel Konstantinov created IGNITE-1338: -- Summary: SQL engine doesn't convert query fields name in upper case before using Key: IGNITE-1338 URL: https://issues.apache.org/jira/browse/IGNITE-1338 Project: Ignite Issue Type: Bug Components: SQL Affects Versions: ignite-1.4 Reporter: Pavel Konstantinov Assignee: Sergi Vladykin Priority: Minor Fix For: ignite-1.4 I'm played with Ignite control center and found this bug. I'm attached example xml-file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
[ https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1338: --- Attachment: test-cluster-2.xml > SQL engine doesn't convert query fields name in upper case before using > --- > > Key: IGNITE-1338 > URL: https://issues.apache.org/jira/browse/IGNITE-1338 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: ignite-1.4 >Reporter: Pavel Konstantinov >Assignee: Sergi Vladykin >Priority: Minor > Fix For: ignite-1.4 > > Attachments: test-cluster-2.xml > > > I'm played with Ignite control center and found this bug. > I'm attached example xml-file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
[ https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1338: --- Priority: Trivial (was: Minor) > SQL engine doesn't convert query fields name in upper case before using > --- > > Key: IGNITE-1338 > URL: https://issues.apache.org/jira/browse/IGNITE-1338 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: ignite-1.4 >Reporter: Pavel Konstantinov >Assignee: Sergi Vladykin >Priority: Trivial > Fix For: ignite-1.4 > > Attachments: test-cluster-2.xml > > > I'm played with Ignite control center and found this bug. > I'm attached example xml-file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1338) SQL engine doesn't convert query fields name in upper case before using
[
https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1338:
---
Description:
Node can not be started if query fields name written in lower case and key
fields with the same fields in upper case in cache type metadata.
Please use attached configuration file for reproducing.
{code}
[14:30:28,526][SEVERE][main][IgniteKernal] Got exception while starting (will
rollback startup routine).
class org.apache.ignite.IgniteCheckedException: Failed to register query type:
TypeDescriptor [name=org.apache.ignite.Comalgorithm, fields={APCSBJCODE=class
java.math.BigDecimal, APCID=class java.math.BigDecimal, AGRSBJCODE=class
java.math.BigDecimal, AGRID=class java.math.BigDecimal, DAOSBJCODE=class
java.math.BigDecimal, DAOID=class java.math.BigDecimal, CTPSBJCODE=class
java.math.BigDecimal, CTPID=class java.math.BigDecimal, apcsbjcode=class
java.math.BigDecimal, apcid=class java.math.BigDecimal, algcode=class
java.math.BigDecimal, algisversioned=class java.lang.Short, algtype=class
java.lang.Integer, algcalcobjecttype=class java.lang.Integer,
algclasspath=class java.lang.String, algcomment=class java.lang.String,
algopendate=class java.sql.Date, algclosedate=class java.sql.Date,
algentstatus=class java.lang.Integer, agrsbjcode=class java.math.BigDecimal,
agrid=class java.math.BigDecimal, daosbjcode=class java.math.BigDecimal,
daoid=class java.math.BigDecimal, ctpsbjcode=class java.math.BigDecimal,
ctpid=class java.math.BigDecimal, algusefields=class java.lang.String},
indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
FK3COMALGORITHM=IndexDescriptor [type=SORTED], FK4COMALGORITHM=IndexDescriptor
[type=SORTED], SQL050208183448780=IndexDescriptor [type=SORTED]},
fullTextIdx=null, keyCls=class java.lang.Object, valCls=class java.lang.Object,
valTextIdx=false, registered=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1058)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:194)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:292)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1048)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:820)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:963)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
at org.apache.ignite.Ignition.start(Ignition.java:346)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
Duplicate column name "APCSBJCODE"; SQL statement:
CREATE TABLE "cache2".org_apache_ignite_Comalgorithm (_key OTHER NOT NULL,_val
OTHER,APCSBJCODE DECIMAL,APCID DECIMAL,AGRSBJCODE DECIMAL,AGRID
DECIMAL,DAOSBJCODE DECIMAL,DAOID DECIMAL,CTPSBJCODE DECIMAL,CTPID
DECIMAL,apcsbjcode DECIMAL,apcid DECIMAL,algcode DECIMAL,algisversioned
SMALLINT,algtype INT,algcalcobjecttype INT,algclasspath VARCHAR,algcomment
VARCHAR,algopendate DATE,algclosedate DATE,algentstatus INT,agrsbjcode
DECIMAL,agrid DECIMAL,daosbjcode DECIMAL,daoid DECIMAL,ctpsbjcode DECIMAL,ctpid
DECIMAL,algusefields VARCHAR) engine
"org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine"
[42121-175]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
at org.h2.message.DbException.get(DbException.java:172)
at org.h2.message.DbException.get(DbException.java:149)
at org.h2.table.Table.setColumns(Table.java:394)
at org.h2.table.TableBase.(TableBase.java:44)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.(GridH2Table.java:90)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:618)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:602)
at org.h2.schema.Schema.createTable(Schema.java:584)
at org.h2.command.ddl.CreateTable.update(CreateTable.java
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724981#comment-14724981 ] Pavel Konstantinov commented on IGNITE-843: --- Safari specific bug - top menu panel font becomes thin in undocked state. > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726698#comment-14726698
]
Pavel Konstantinov commented on IGNITE-850:
---
"multicastGroup" must be removed from code generation if it empty (set any
value then clear it).
{code}
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726698#comment-14726698
]
Pavel Konstantinov edited comment on IGNITE-850 at 9/2/15 3:59 AM:
---
"multicastGroup" (and "localAddress" too) must be removed from code generation
if it empty (set any value then clear it).
{code}
{code}
was (Author: pkonstantinov):
"multicastGroup" must be removed from code generation if it empty (set any
value then clear it).
{code}
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726698#comment-14726698
]
Pavel Konstantinov edited comment on IGNITE-850 at 9/2/15 4:02 AM:
---
1) "multicastGroup" (and "localAddress" too) must be removed from code
generation if it empty (set any value then clear it).
{code}
{code}
2) "Atomics configuration"
"backups" should be generated only for partitioned mode
{code}
{code}
was (Author: pkonstantinov):
"multicastGroup" (and "localAddress" too) must be removed from code generation
if it empty (set any value then clear it).
{code}
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726706#comment-14726706 ] Pavel Konstantinov commented on IGNITE-843: --- Background for help tooltip should be not transparent. > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-850) Implement clusters screen
[
https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726698#comment-14726698
]
Pavel Konstantinov edited comment on IGNITE-850 at 9/2/15 4:24 AM:
---
1) "multicastGroup" (and "localAddress" too) must be removed from code
generation if it empty (set any value then clear it).
{code}
{code}
2) "Atomics configuration"
"backups" should be generated only for partitioned mode
{code}
{code}
3) we should escape back slashes in java-code
{code}
swapSpi.setBaseDirectory("c:\swap\base\directory");
{code}
was (Author: pkonstantinov):
1) "multicastGroup" (and "localAddress" too) must be removed from code
generation if it empty (set any value then clear it).
{code}
{code}
2) "Atomics configuration"
"backups" should be generated only for partitioned mode
{code}
{code}
> Implement clusters screen
> -
>
> Key: IGNITE-850
> URL: https://issues.apache.org/jira/browse/IGNITE-850
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: cluster page.png, clusters-page-2.png,
> clusters-page-3.png, clusters.pdf, ig-850-zones.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726737#comment-14726737 ] Pavel Konstantinov commented on IGNITE-851: --- Should any XML-code be generated if I set "Hibernate BLOB store factory"? Currently none code generated. > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-851) Implement caches screen
[
https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726737#comment-14726737
]
Pavel Konstantinov edited comment on IGNITE-851 at 9/2/15 4:48 AM:
---
Should any XML-code be generated if I set "Hibernate BLOB store factory"?
Currently none code generated.
To comparison:
Java-code
{code}
CacheHibernateBlobStoreFactory storeFactoryC1 = new
CacheHibernateBlobStoreFactory();
cache.setCacheStoreFactory(storeFactoryC1);
cache.setReadThrough(true);
cache.setWriteBehindEnabled(true);
{code}
XML
{code}
{code}
was (Author: pkonstantinov):
Should any XML-code be generated if I set "Hibernate BLOB store factory"?
Currently none code generated.
> Implement caches screen
> ---
>
> Key: IGNITE-851
> URL: https://issues.apache.org/jira/browse/IGNITE-851
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: Caches.pdf, caches-page-advanced-2.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-851) Implement caches screen
[
https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726737#comment-14726737
]
Pavel Konstantinov edited comment on IGNITE-851 at 9/2/15 4:49 AM:
---
Should any XML-code be generated if I set "Hibernate BLOB store factory"?
Currently none code generated for factory.
To comparison:
Java-code
{code}
CacheHibernateBlobStoreFactory storeFactoryC1 = new
CacheHibernateBlobStoreFactory();
cache.setCacheStoreFactory(storeFactoryC1);
cache.setReadThrough(true);
cache.setWriteBehindEnabled(true);
{code}
XML
{code}
{code}
was (Author: pkonstantinov):
Should any XML-code be generated if I set "Hibernate BLOB store factory"?
Currently none code generated.
To comparison:
Java-code
{code}
CacheHibernateBlobStoreFactory storeFactoryC1 = new
CacheHibernateBlobStoreFactory();
cache.setCacheStoreFactory(storeFactoryC1);
cache.setReadThrough(true);
cache.setWriteBehindEnabled(true);
{code}
XML
{code}
{code}
> Implement caches screen
> ---
>
> Key: IGNITE-851
> URL: https://issues.apache.org/jira/browse/IGNITE-851
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: Caches.pdf, caches-page-advanced-2.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1145) Implement admin page
[ https://issues.apache.org/jira/browse/IGNITE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1145. -- Assignee: (was: Pavel Konstantinov) > Implement admin page > > > Key: IGNITE-1145 > URL: https://issues.apache.org/jira/browse/IGNITE-1145 > Project: Ignite > Issue Type: Sub-task > Components: UI >Reporter: Andrey Novikov > Fix For: ignite-1.4 > > Attachments: admin panel.png > > > Need implement page with all users. > For every user need display name, email, last login. Implement actions: > remove user, become this user, make admin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1145) Implement admin page
[ https://issues.apache.org/jira/browse/IGNITE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727125#comment-14727125 ] Pavel Konstantinov commented on IGNITE-1145: Successfully tested > Implement admin page > > > Key: IGNITE-1145 > URL: https://issues.apache.org/jira/browse/IGNITE-1145 > Project: Ignite > Issue Type: Sub-task > Components: UI >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov > Fix For: ignite-1.4 > > Attachments: admin panel.png > > > Need implement page with all users. > For every user need display name, email, last login. Implement actions: > remove user, become this user, make admin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1213) Add mark and alert in case of not saved changes
[ https://issues.apache.org/jira/browse/IGNITE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727151#comment-14727151 ] Pavel Konstantinov commented on IGNITE-1213: Tested. > Add mark and alert in case of not saved changes > --- > > Key: IGNITE-1213 > URL: https://issues.apache.org/jira/browse/IGNITE-1213 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: ignite-1.4 > > Attachments: #_IGNITE-1213_Confirm_on_unsaved_changes.patch, > ignite-1213 v1.png, ignite-1213 v2.png, ignite-1213 v3.png > > > We need to add a mark (some icon, usually floppy disk) and alert when user > modify data, but does not hit "Save" button. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1213) Add mark and alert in case of not saved changes
[ https://issues.apache.org/jira/browse/IGNITE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1213. -- Assignee: (was: Pavel Konstantinov) > Add mark and alert in case of not saved changes > --- > > Key: IGNITE-1213 > URL: https://issues.apache.org/jira/browse/IGNITE-1213 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: #_IGNITE-1213_Confirm_on_unsaved_changes.patch, > ignite-1213 v1.png, ignite-1213 v2.png, ignite-1213 v3.png > > > We need to add a mark (some icon, usually floppy disk) and alert when user > modify data, but does not hit "Save" button. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1380) Random eviction policy for near cache works incorrectly
Pavel Konstantinov created IGNITE-1380:
--
Summary: Random eviction policy for near cache works incorrectly
Key: IGNITE-1380
URL: https://issues.apache.org/jira/browse/IGNITE-1380
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Fix For: ignite-1.4
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1380) Random eviction policy for near cache works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1380:
---
Description:
Start node with cache with near cache with configuration below.
Put 200 keys.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
was:
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
>
> Start node with cache with near cache with configuration below.
> Put 200 keys.
> {code}
>
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
>
>
>
>
>
>
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1380) Random eviction policy for near cache works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1380:
---
Description:
Start node with cache with near cache with configuration below.
Put 200 keys, read 200
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
was:
Start node with cache with near cache with configuration below.
Put 200 keys.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
>
> Start node with cache with near cache with configuration below.
> Put 200 keys, read 200
> {code}
>
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
>
>
>
>
>
>
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1380) Random eviction policy for near cache works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1380:
---
Description:
Start two server nodes with cache with near cache with configuration below
(node with load generation and one more data node).
Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first node.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
was:
Start node with cache with near cache with configuration below.
Put 200 keys, read 200
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
>
> Start two server nodes with cache with near cache with configuration below
> (node with load generation and one more data node).
> Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first
> node.
> {code}
>
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
>
>
>
>
>
>
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1380) Random eviction policy for near cache works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1380:
---
Description:
Start two server nodes with cache with near cache with configuration below
(node with load generation and one more data node).
Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first node.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
Others eviction policies works correctly.
was:
Start two server nodes with cache with near cache with configuration below
(node with load generation and one more data node).
Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first node.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
>
> Start two server nodes with cache with near cache with configuration below
> (node with load generation and one more data node).
> Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first
> node.
> {code}
>
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
>
>
>
>
>
>
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
> Others eviction policies works correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1380) Random eviction policy for near cache works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1380:
---
Description:
Start two server nodes with cache with near cache with configuration below
(node with load generation and one more data node).
Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first node.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
Others eviction policies are works correctly.
was:
Start two server nodes with cache with near cache with configuration below
(node with load generation and one more data node).
Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first node.
{code}
{code}
Near cache contains more keys then I set in configuration (maxSize=100).
Others eviction policies works correctly.
> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
>
> Start two server nodes with cache with near cache with configuration below
> (node with load generation and one more data node).
> Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first
> node.
> {code}
>
>
>
>
>
> class="org.apache.ignite.configuration.NearCacheConfiguration">
>
> class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
>
>
>
>
>
>
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
> Others eviction policies are works correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1385) Confused warning about portable marshaller
Pavel Konstantinov created IGNITE-1385:
--
Summary: Confused warning about portable marshaller
Key: IGNITE-1385
URL: https://issues.apache.org/jira/browse/IGNITE-1385
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Denis Magda
Priority: Trivial
Fix For: ignite-1.4
I'm set
{code}
{code}
start the node and got warning:
{code}
[WARNING][main][GridCachePluginProvider]
CacheConfiguration.isKeepPortableInStore() configuration property will be
ignored because PortableMarshaller is not used
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1385) Confused warning about portable marshaller
[
https://issues.apache.org/jira/browse/IGNITE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-1385.
--
Assignee: (was: Pavel Konstantinov)
Successfully tested in version 1.4
> Confused warning about portable marshaller
> --
>
> Key: IGNITE-1385
> URL: https://issues.apache.org/jira/browse/IGNITE-1385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Priority: Trivial
> Fix For: ignite-1.4
>
>
> I'm set
> {code}
>
> class="org.apache.ignite.marshaller.portable.PortableMarshaller"/>
>
> {code}
> start the node and got warning:
> {code}
> [WARNING][main][GridCachePluginProvider]
> CacheConfiguration.isKeepPortableInStore() configuration property will be
> ignored because PortableMarshaller is not used
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738089#comment-14738089 ] Pavel Konstantinov commented on IGNITE-843: --- Preview generates an empty row at the end. > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738133#comment-14738133 ] Pavel Konstantinov commented on IGNITE-851: --- Set cursor to the 'Key Class' field for first created 'Index key-value type' pair. > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.4 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738427#comment-14738427 ] Pavel Konstantinov commented on IGNITE-1177: 'Group indexes' has broken UI > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738427#comment-14738427 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/10/15 8:59 AM: - 1)'Group indexes' has broken UI 2)Need to sort database types drop down list alphabetically was (Author: pkonstantinov): 'Group indexes' has broken UI > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738427#comment-14738427 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/10/15 9:02 AM: - 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically was (Author: pkonstantinov): 1)'Group indexes' has broken UI 2)Need to sort database types drop down list alphabetically > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738427#comment-14738427 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/10/15 10:59 AM: -- 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically 3)I've loaded metadata from DB - single table, this metadata became the active (current) in the list, I'm did not link any caches with this metadata yet, but drop down list shows as marked caches I selected for prev metadata. was (Author: pkonstantinov): 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1405) NPE during node start in coner case
Pavel Konstantinov created IGNITE-1405:
--
Summary: NPE during node start in coner case
Key: IGNITE-1405
URL: https://issues.apache.org/jira/browse/IGNITE-1405
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Fix For: ignite-1.5
I'm tried to establish external connect to node during it starting
{code}
[14:07:29,284][SEVERE][ignite-#45%rest-tester%][GridTcpRestProtocol] Failed to
process client request: GridClientTopologyRequest [includeMetrics=true,
includeAttrs=true]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6978)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.allNodes(GridDiscoveryManager.java:1421)
at
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:100)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
... 4 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1408) Error in schema import code generation
[ https://issues.apache.org/jira/browse/IGNITE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1408: --- Description: Variable for ascending fields define twice (was: Ascending fields defines twice) > Error in schema import code generation > -- > > Key: IGNITE-1408 > URL: https://issues.apache.org/jira/browse/IGNITE-1408 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > > Variable for ascending fields define twice -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1408) Error in schema import code generation
Pavel Konstantinov created IGNITE-1408: -- Summary: Error in schema import code generation Key: IGNITE-1408 URL: https://issues.apache.org/jira/browse/IGNITE-1408 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Ascending fields defines twice -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1405) NPE during node start in corner case
[
https://issues.apache.org/jira/browse/IGNITE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742803#comment-14742803
]
Pavel Konstantinov commented on IGNITE-1405:
"connect to it using GridClientFactory;" - NPE might happen already on this step
> NPE during node start in corner case
>
>
> Key: IGNITE-1405
> URL: https://issues.apache.org/jira/browse/IGNITE-1405
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Denis Magda
> Fix For: ignite-1.5
>
>
> I'm tried to establish external connect to node during it starting
> {code}
> [14:07:29,284][SEVERE][ignite-#45%rest-tester%][GridTcpRestProtocol] Failed
> to process client request: GridClientTopologyRequest [includeMetrics=true,
> includeAttrs=true]
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6978)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.allNodes(GridDiscoveryManager.java:1421)
> at
> org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:100)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743176#comment-14743176 ] Pavel Konstantinov commented on IGNITE-1177: No tooltip for 'Metadata for SQL query', 'Metadata for cache store' > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743354#comment-14743354 ] Pavel Konstantinov commented on IGNITE-1177: 1) still broken under FireFox > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744703#comment-14744703 ] Pavel Konstantinov commented on IGNITE-843: --- Will be useful to print out URL of the site agent connected to. > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744788#comment-14744788 ] Pavel Konstantinov commented on IGNITE-851: --- What about to generate cache definition in XML (cache bean) and Java-preview (CacheConfiguration cache = new CacheConfiguration();) to have a completed code for each section? > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744791#comment-14744791 ] Pavel Konstantinov commented on IGNITE-1177: I think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1485) Improve loading metadat from DB
Pavel Konstantinov created IGNITE-1485: -- Summary: Improve loading metadat from DB Key: IGNITE-1485 URL: https://issues.apache.org/jira/browse/IGNITE-1485 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov I think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744791#comment-14744791 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/15/15 4:19 AM: - I think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. I've created a sub-ticket for this. was (Author: pkonstantinov): I think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1177: --- Comment: was deleted (was: I think will be useful to generate separate cache for each metadata loaded from DB. In this case web console will generate a cache + metadata linked to it. User could point already created cache as a template for generation. I've created a sub-ticket for this.) > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1485: --- Summary: Improve loading metadata from DB (was: Improve loading metadat from DB) > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > > I think will be useful to generate separate cache for each metadata loaded > from DB. > In this case web console will generate a cache + metadata linked to it. > User could point already created cache as a template for generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1408) Error in schema import code generation
[ https://issues.apache.org/jira/browse/IGNITE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1408. -- Assignee: (was: Pavel Konstantinov) Successfully tested in 1.4 > Error in schema import code generation > -- > > Key: IGNITE-1408 > URL: https://issues.apache.org/jira/browse/IGNITE-1408 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov > > Variable for ascending fields define twice -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1489) Usability issiues
Pavel Konstantinov created IGNITE-1489: -- Summary: Usability issiues Key: IGNITE-1489 URL: https://issues.apache.org/jira/browse/IGNITE-1489 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Priority: Minor Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1489: --- Summary: Usability issues (was: Usability issiues) > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745022#comment-14745022 ] Pavel Konstantinov commented on IGNITE-1489: I loaded over 700 matadata from DB selected one of them and linked with a cache. Then I opened this cache to verify my choice and faced with issue that it is very difficult to find selected metadata. So I suggest to show selected items before unselected. > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745022#comment-14745022 ] Pavel Konstantinov edited comment on IGNITE-1489 at 9/15/15 8:00 AM: - I loaded over 700 matadata from DB, selected one of them and linked with a cache. Then I opened this cache to verify my choice and faced with issue that it is very difficult to find selected metadata. So I suggest to show selected items before unselected. was (Author: pkonstantinov): I loaded over 700 matadata from DB selected one of them and linked with a cache. Then I opened this cache to verify my choice and faced with issue that it is very difficult to find selected metadata. So I suggest to show selected items before unselected. > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745539#comment-14745539
]
Pavel Konstantinov commented on IGNITE-973:
---
Cannot reproduce on home laptop. Need to check on office laptop one more time.
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reopened IGNITE-973:
---
Assignee: Yakov Zhdanov (was: Pavel Konstantinov)
I still facing with this issue on my work laptop.
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746748#comment-14746748
]
Pavel Konstantinov edited comment on IGNITE-973 at 9/16/15 3:31 AM:
I still facing with this issue on my work laptop.
In my tester I have thread which removes random entry from the cache.
If I turn off this thread the issue is disappears.
was (Author: pkonstantinov):
I still facing with this issue on my work laptop.
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746767#comment-14746767 ] Pavel Konstantinov commented on IGNITE-1489: Disable Save button on Profile page if nothing to save > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746748#comment-14746748
]
Pavel Konstantinov edited comment on IGNITE-973 at 9/16/15 3:38 AM:
I still facing with this issue on my work laptop.
In my tester I have thread which removes random entry from the cache.
If I turn off this thread the issue is disappears.
{code}
[10:35:12] (err) Failed to execute compound future reducer: Compound future
listener: GridCompoundFuture [lsnrCalls=0, finished=false, rdc=null, init=true,
res=java.util.concurrent.atomic.AtomicMarkab
leReference@6f0c2cfe, err=null, done=false, cancelled=false, err=null,
futs=[true]]class org.apache.ignite.IgniteCheckedException: Failed to get value
for key: 34492. This can happen due to a long GC
pause.
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at
org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
at
org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
at
org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:440)
at
org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:423)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1426)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:289)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to get value for
key: 34492. This can happen due to a long GC pause.
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:235)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:119)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:208)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:48)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1350)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1346)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2102)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
at
org.apache.ignite.internal.util.offheap.unsafe.GridO
[jira] [Reopened] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-1147: Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) Need to verify that new email has valid email format. > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1147: --- Comment: was deleted (was: Need to verify that new email has valid email format.) > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746795#comment-14746795 ] Pavel Konstantinov commented on IGNITE-1147: Periodically I'm faced with 'Internal server error' 1) open profile 2) change password 3) save 4) click to the Configuration menu link > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[
https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747218#comment-14747218
]
Pavel Konstantinov commented on IGNITE-851:
---
I've opened Caches page and clicked New button during loading information about
caches
{code}
prepareNewItem@http://webconsole.gridgain.com/caches-controller.js:375:21
$scope.createItem@http://webconsole.gridgain.com/caches-controller.js:393:46
anonymous/fn@http://ajax.googleapis.com/ajax/libs/angularjs/1.4.5/angular.min.js
line 212 > Function:2:218
Ic[c]http://ajax.googleapis.com/ajax/libs/angularjs/1.4.5/angular.min.js:252:74
{code}
> Implement caches screen
> ---
>
> Key: IGNITE-851
> URL: https://issues.apache.org/jira/browse/IGNITE-851
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.5
>
> Attachments: Caches.pdf, caches-page-advanced-2.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791476#comment-14791476 ] Pavel Konstantinov commented on IGNITE-850: --- Successfully verified > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1146) Implement summary page with configuration downloads.
[ https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1146: --- Description: Generate: * sprint xml configuration; * Java class with configuration; * Java snippet with configuration; * docker file for run with this configuration. Download all generated files as zip archive, generate client configuration. was: Generate: * sprint xml configuration; * java class with configuration; * java snipplet with configuration; * docker file for run with this configuration. Download all generated files as zip archive, generate client configuration. > Implement summary page with configuration downloads. > > > Key: IGNITE-1146 > URL: https://issues.apache.org/jira/browse/IGNITE-1146 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: summary - client.png, summary - server.png, > test-cluster-2.xml > > > Generate: > * sprint xml configuration; > * Java class with configuration; > * Java snippet with configuration; > * docker file for run with this configuration. > Download all generated files as zip archive, generate client configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-1147: Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) I'm facing with issue when I trying to change my password. I'm setting a new password and Confirm then clicking on Save button, but nothing happens. Then I clicking 'Configuration' link and getting 'Internal system error'. > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791569#comment-14791569 ] Pavel Konstantinov commented on IGNITE-1147: Verified > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791573#comment-14791573 ] Pavel Konstantinov commented on IGNITE-851: --- Verified > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791574#comment-14791574 ] Pavel Konstantinov commented on IGNITE-850: --- Verified > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791576#comment-14791576 ] Pavel Konstantinov commented on IGNITE-850: --- I think we should add validation of 'Local class path exclude' value (that it contain package name) > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1498) Add support for specifying config via command line option
[ https://issues.apache.org/jira/browse/IGNITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802726#comment-14802726 ] Pavel Konstantinov commented on IGNITE-1498: Successfully tested in 1.4 > Add support for specifying config via command line option > - > > Key: IGNITE-1498 > URL: https://issues.apache.org/jira/browse/IGNITE-1498 > Project: Ignite > Issue Type: Bug > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Blocker > Fix For: ignite-1.4 > > > Add support for "-cfg path" for command line Visor . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1498) Add support for specifying config via command line option
[ https://issues.apache.org/jira/browse/IGNITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1498. -- Assignee: (was: Pavel Konstantinov) > Add support for specifying config via command line option > - > > Key: IGNITE-1498 > URL: https://issues.apache.org/jira/browse/IGNITE-1498 > Project: Ignite > Issue Type: Bug > Components: UI >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Priority: Blocker > Fix For: ignite-1.4 > > > Add support for "-cfg path" for command line Visor . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804880#comment-14804880 ] Pavel Konstantinov commented on IGNITE-1489: Web agent - print out user e-mail after success connection > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804880#comment-14804880 ] Pavel Konstantinov edited comment on IGNITE-1489 at 9/18/15 2:37 AM: - Web agent - print out user e-mail after successful connection was (Author: pkonstantinov): Web agent - print out user e-mail after success connection > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1503) Do not ask user to provide node ID8 for cache details
Pavel Konstantinov created IGNITE-1503:
--
Summary: Do not ask user to provide node ID8 for cache details
Key: IGNITE-1503
URL: https://issues.apache.org/jira/browse/IGNITE-1503
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Trivial
Fix For: ignite-1.5
Currently user must set -id8=NODE_ID8 option to get detailed cache configuration
{code}
cache -c=cache1 -id8=12345678 -a
{code}
Since now cache starts with identical configuration on all nodes we can discard
option '-id8' for getting detailed cache configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1503) visorcmd: Do not ask user to provide node ID8 for cache details
[
https://issues.apache.org/jira/browse/IGNITE-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1503:
---
Summary: visorcmd: Do not ask user to provide node ID8 for cache details
(was: Do not ask user to provide node ID8 for cache details )
> visorcmd: Do not ask user to provide node ID8 for cache details
>
>
> Key: IGNITE-1503
> URL: https://issues.apache.org/jira/browse/IGNITE-1503
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> Currently user must set -id8=NODE_ID8 option to get detailed cache
> configuration
> {code}
> cache -c=cache1 -id8=12345678 -a
> {code}
> Since now cache starts with identical configuration on all nodes we can
> discard option '-id8' for getting detailed cache configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1504) Add cache name to the warning
Pavel Konstantinov created IGNITE-1504:
--
Summary: Add cache name to the warning
Key: IGNITE-1504
URL: https://issues.apache.org/jira/browse/IGNITE-1504
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Priority: Trivial
Fix For: ignite-1.5
I got this warning but I don't understand what cache this warning is about.
Please add cache name.
{code}
[10:58:21,931][WARNING][ignite-#21%sys-tester%][GridDhtPartitionsExchangeFuture]
Retrying preload partition exchange due to timeout [done=false, dummy=false,
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=0], nodeId=2135f8b4, evt=NODE_JOINED], rcvdIds=[],
rmtIds=[dec935df, 0237a5ca], remaining=[dec935df, 0237a5ca], init=true,
initFut=true, ready=true, replied=false, added=true, oldest=dec935df,
oldestOrder=1, evtLatch=0, locNodeOrder=4, locNodeId=2135f8b
4-9633-447e-be13-b7285e76bab3]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804950#comment-14804950 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/18/15 4:31 AM: - Load metadata from DB: 1) Need to validate package name 2) Load only matched items if filter is set. was (Author: pkonstantinov): 1) Need to validate package name 2) Load only matched items if filter is set. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804950#comment-14804950 ] Pavel Konstantinov commented on IGNITE-1177: 1) Need to validate package name 2) Load only matched items if filter is set. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1505) Error on stopping cache in visorcmd
Pavel Konstantinov created IGNITE-1505:
--
Summary: Error on stopping cache in visorcmd
Key: IGNITE-1505
URL: https://issues.apache.org/jira/browse/IGNITE-1505
Project: Ignite
Issue Type: Bug
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Minor
Fix For: ignite-1.5
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+-+-+---+
| 2 | dcp_1(@c6) | PARTITIONED | min: 0|
| | | | avg: 2700.00 |
| | | | max: 3773 |
+---+-+-+---+
| 3 | dcp_2(@c7) | PARTITIONED | min: 2496 |
| | | | avg: 2672.00 |
| | | | max: 2809 |
+---+-+-+---+
| 4 | dcr_1(@c8) | REPLICATED | min: 0|
| | | | avg: 8075.50 |
| | | | max: 10768|
+---+-+-+---+
| 5 | dcr_2(@c9) | REPLICATED | min: 0|
| | | | avg: 8039.75 |
| | | | max: 10720|
+---+-+-+---+
| 6 | local-nid(@c10) | LOCAL | min: 10792|
| | | | avg: 10792.00 |
| | | | max: 10792|
+---+
Choose cache number ('c' to cancel) [c]: 6
java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not be
empty.
at
org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
at
org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
at
org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
at scala.Option.foreach(Option.scala:245)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
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:315)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1505) Error on stopping cache in visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1505:
---
Description:
I'm start my tester and trying to stop cache created only on one node and got
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+-+-+---+
| 2 | dcp_1(@c6) | PARTITIONED | min: 0|
| | | | avg: 2700.00 |
| | | | max: 3773 |
+---+-+-+---+
| 3 | dcp_2(@c7) | PARTITIONED | min: 2496 |
| | | | avg: 2672.00 |
| | | | max: 2809 |
+---+-+-+---+
| 4 | dcr_1(@c8) | REPLICATED | min: 0|
| | | | avg: 8075.50 |
| | | | max: 10768|
+---+-+-+---+
| 5 | dcr_2(@c9) | REPLICATED | min: 0|
| | | | avg: 8039.75 |
| | | | max: 10720|
+---+-+-+---+
| 6 | local-nid(@c10) | LOCAL | min: 10792|
| | | | avg: 10792.00 |
| | | | max: 10792|
+---+
Choose cache number ('c' to cancel) [c]: 6
java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not be
empty.
at
org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
at
org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
at
org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
at scala.Option.foreach(Option.scala:245)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
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:315)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
{code}
was:
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+---
[jira] [Created] (IGNITE-1506) visorcmd: inconsistent result of 'disco' command
Pavel Konstantinov created IGNITE-1506: -- Summary: visorcmd: inconsistent result of 'disco' command Key: IGNITE-1506 URL: https://issues.apache.org/jira/browse/IGNITE-1506 Project: Ignite Issue Type: Bug Components: UI Affects Versions: ignite-1.4 Reporter: Pavel Konstantinov Assignee: Vasiliy Sisko Priority: Minor Fix For: ignite-1.5 Currently 'disco' command shows at least on event (from node which executes the task) in result even if discovery events are not configured - this is a bit confuses. I think would be better to print out something like 'discovery events are not configured'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
