[jira] [Updated] (IGNITE-6047) Need to support "show" SQL commands

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-6047:
--
Description: 
I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute "show" commands, I get an error. 

We need to support all or most {{SHOW}} commands in H2, as described here:
http://www.h2database.com/html/grammar.html?highlight=show=show#show

Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should 
give a message to use the {{SHOW}} command, if possible, and provide a link to 
the correct syntax.


  was:
I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute "show" commands, I get an error. 

We need to support all or most {{SHOW}} commands in H2, as described here:
http://www.h2database.com/html/grammar.html?highlight=show=show#show

Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should 
give a message to use the {{SHOW}} command, if possible.



> Need to support "show" SQL commands
> ---
>
> Key: IGNITE-6047
> URL: https://issues.apache.org/jira/browse/IGNITE-6047
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Reporter: Dmitriy Setrakyan
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.2
>
>
> I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
> execute "show" commands, I get an error. 
> We need to support all or most {{SHOW}} commands in H2, as described here:
> http://www.h2database.com/html/grammar.html?highlight=show=show#show
> Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should 
> give a message to use the {{SHOW}} command, if possible, and provide a link 
> to the correct syntax.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6046) Multiple SQL statements in one JDBC command do not work

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124338#comment-16124338
 ] 

Dmitriy Setrakyan commented on IGNITE-6046:
---

Need to test with ODBC as well.

> Multiple SQL statements in one JDBC command do not work
> ---
>
> Key: IGNITE-6046
> URL: https://issues.apache.org/jira/browse/IGNITE-6046
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Reporter: Dmitriy Setrakyan
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.2
>
>
> I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
> execute more than one statement from the SQL Editor, I get an error.
> For example, highlighting and executing these 2 statements gives an error:
> {code:sql}
> INSERT INTO city (id, name) VALUES (2, 'Forest Hill');
> INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3);
> {code}
> Here is the error I get:
> {code}
> [15:25:17,265][SEVERE][sql-connector-#150%null%][JdbcRequestHandler] Failed 
> to execute SQL query [reqId=26, req=JdbcQueryExecuteRequest [schemaName=null, 
> pageSize=1024, maxRows=0, sqlQry=INSERT INTO city (id, name) VALUES (2, 
> 'Forest Hill');
> INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3), args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> Can not set org.h2.command.Prepared field 
> org.h2.command.CommandContainer.prepared to org.h2.command.CommandList
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1863)
> at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:188)
> at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:122)
> at 
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152)
> at 
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at 
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at 
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Can not set 
> org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
> org.h2.command.CommandList
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2316)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860)
> ... 12 more
> Caused by: java.lang.IllegalArgumentException: Can not set 
> org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
> org.h2.command.CommandList
> at 
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
> at 
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
> at 
> sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58)
> at 
> sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)
> at java.lang.reflect.Field.get(Field.java:393)
> at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser$Getter.get(GridSqlQueryParser.java:1600)
> at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.prepared(GridSqlQueryParser.java:443)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1298)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
>

[jira] [Created] (IGNITE-6048) Need to document how to connect to Ignite from external SQL tools

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 
Dmitriy Setrakyan created IGNITE-6048:
-

 Summary: Need to document how to connect to Ignite from external 
SQL tools
 Key: IGNITE-6048
 URL: https://issues.apache.org/jira/browse/IGNITE-6048
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Dmitriy Setrakyan
Assignee: Denis Magda
 Fix For: 2.2


We need to provide all the possible required JDBC and ODBC settings. We should 
also pick any SQL tool and provide screenshots. For example, DBeaver is a good 
candidate.

http://dbeaver.jkiss.org/

D.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6048) Need to document how to connect to Ignite from external SQL tools

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-6048:
--
Labels: docs  (was: )

> Need to document how to connect to Ignite from external SQL tools
> -
>
> Key: IGNITE-6048
> URL: https://issues.apache.org/jira/browse/IGNITE-6048
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: docs
> Fix For: 2.2
>
>
> We need to provide all the possible required JDBC and ODBC settings. We 
> should also pick any SQL tool and provide screenshots. For example, DBeaver 
> is a good candidate.
> http://dbeaver.jkiss.org/
> D.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries

2017-08-11 Thread Nikolay Izhikov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124251#comment-16124251
 ] 

Nikolay Izhikov commented on IGNITE-425:


TC - 
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=pull%2F2372%2Fhead

[~ntikho...@apache.org] Can you please review my changes?

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6031) Web Console: Improve grouping of fields on Cluster Configuration Tab (By importance / alphabetically)

2017-08-11 Thread Denis Magda (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-6031:
---

Assignee: Vica Abramova

> Web Console: Improve grouping of fields on Cluster Configuration Tab (By 
> importance / alphabetically)
> -
>
> Key: IGNITE-6031
> URL: https://issues.apache.org/jira/browse/IGNITE-6031
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6031) Web Console: Improve grouping of fields on Cluster Configuration Tab (By importance / alphabetically)

2017-08-11 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124234#comment-16124234
 ] 

Denis Magda commented on IGNITE-6031:
-

[~vabramova], [~kuaw26], I can not find the new version of the page that lists 
all the configurations. Please enumerate the configurations here.

> Web Console: Improve grouping of fields on Cluster Configuration Tab (By 
> importance / alphabetically)
> -
>
> Key: IGNITE-6031
> URL: https://issues.apache.org/jira/browse/IGNITE-6031
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6047) Need to support "show" SQL commands

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 
Dmitriy Setrakyan created IGNITE-6047:
-

 Summary: Need to support "show" SQL commands
 Key: IGNITE-6047
 URL: https://issues.apache.org/jira/browse/IGNITE-6047
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, sql
Reporter: Dmitriy Setrakyan
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 2.2


I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute "show" commands, I get an error. 

We need to support all or most {{SHOW}} commands in H2, as described here:
http://www.h2database.com/html/grammar.html?highlight=show=show#show

Also, ideally, if a user issues {{DESCRIBE}} or {{DESC}} commands, we should 
give a message to use the {{SHOW}} command, if possible.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5233) JDBC thin Driver: implement metadata support

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Setrakyan updated IGNITE-5233:
--
Priority: Blocker  (was: Major)

> JDBC thin Driver: implement metadata support 
> -
>
> Key: IGNITE-5233
> URL: https://issues.apache.org/jira/browse/IGNITE-5233
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Blocker
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6046) Multiple SQL statements in one command do not work

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 
Dmitriy Setrakyan created IGNITE-6046:
-

 Summary: Multiple SQL statements in one command do not work
 Key: IGNITE-6046
 URL: https://issues.apache.org/jira/browse/IGNITE-6046
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Reporter: Dmitriy Setrakyan
Assignee: Vladimir Ozerov
Priority: Blocker
 Fix For: 2.2


I have connected to Ignite from DBeaver using our thin JDBC driver. When I 
execute more than one statement from the SQL Editor, I get an error.

For example, highlighting and executing these 2 statements gives an error:
{code:sql}
INSERT INTO city (id, name) VALUES (2, 'Forest Hill');
INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3);
{code}
Here is the error I get:
{code}
[15:25:17,265][SEVERE][sql-connector-#150%null%][JdbcRequestHandler] Failed to 
execute SQL query [reqId=26, req=JdbcQueryExecuteRequest [schemaName=null, 
pageSize=1024, maxRows=0, sqlQry=INSERT INTO city (id, name) VALUES (2, 'Forest 
Hill');
INSERT INTO person (id, name, city_id) VALUES (2, 'John Doe', 3), args=[]]]
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Can 
not set org.h2.command.Prepared field org.h2.command.CommandContainer.prepared 
to org.h2.command.CommandList
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1863)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:188)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:122)
at 
org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152)
at 
org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Can not set 
org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
org.h2.command.CommandList
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2316)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860)
... 12 more
Caused by: java.lang.IllegalArgumentException: Can not set 
org.h2.command.Prepared field org.h2.command.CommandContainer.prepared to 
org.h2.command.CommandList
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
at 
sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)
at java.lang.reflect.Field.get(Field.java:393)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser$Getter.get(GridSqlQueryParser.java:1600)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.prepared(GridSqlQueryParser.java:443)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1298)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
... 13 more
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6040) Update Distributed SQL Database page on the website

2017-08-11 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123969#comment-16123969
 ] 

Denis Magda commented on IGNITE-6040:
-

[~pgarg], as a maintainer of this documentation page please find a time to work 
on this task.

> Update Distributed SQL Database page on the website
> ---
>
> Key: IGNITE-6040
> URL: https://issues.apache.org/jira/browse/IGNITE-6040
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: site
>
> # change DDL examples to pure SQL (without Java)
> # change DML examples to pure SQL (without Java)
> # change Query examples to pure SQL (without Java)
> # add Java API section and show 1 Query, 1 DDL, 1 DML example from Java
> # add .NET / C# API section and show 1 Query, 1 DDL, 1 DML example from C#
> # add Other API section and show 1 Query, 1 DDL, 1 DML example from Python, 
> PHP, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6040) Update Distributed SQL Database page on the website

2017-08-11 Thread Denis Magda (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-6040:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Update Distributed SQL Database page on the website
> ---
>
> Key: IGNITE-6040
> URL: https://issues.apache.org/jira/browse/IGNITE-6040
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Prachi Garg
>  Labels: site
>
> # change DDL examples to pure SQL (without Java)
> # change DML examples to pure SQL (without Java)
> # change Query examples to pure SQL (without Java)
> # add Java API section and show 1 Query, 1 DDL, 1 DML example from Java
> # add .NET / C# API section and show 1 Query, 1 DDL, 1 DML example from C#
> # add Other API section and show 1 Query, 1 DDL, 1 DML example from Python, 
> PHP, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6040) Update Distributed SQL Database page on the website

2017-08-11 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123968#comment-16123968
 ] 

Denis Magda commented on IGNITE-6040:
-

[~dsetrakyan], I would propose the following format that is a bit different 
from yours.

# {{Connectivity}} section. Show how to connect from JDBC, ODBC, Java, .NET and 
C++ API
# {{Configuration}} section. Introduce DDL capabilities and show how to create 
a table and indexes using pure SQL, JDBC, ODBC, Java, .NET, C++, Python APIs.
# {{Data Modification}} section. Introduce DML and show how to insert, update 
and delete data with the same APIs as above.
# {{Data Querying}} section. Show how to look up data using SELECTs. It's more 
than enough to show one simple query and one with a distributed join. The APIs 
are the same - pure SQL, JDBC, ODBC, Java, .NET, C++, Python.
# {{Tooling}} section. Refer to the tools supported by Ignite.

The SQL code snippets can be borrowed from the SQL getting started guide:
https://apacheignite.readme.io/v2.1/docs/getting-started-sql

> Update Distributed SQL Database page on the website
> ---
>
> Key: IGNITE-6040
> URL: https://issues.apache.org/jira/browse/IGNITE-6040
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: site
>
> # change DDL examples to pure SQL (without Java)
> # change DML examples to pure SQL (without Java)
> # change Query examples to pure SQL (without Java)
> # add Java API section and show 1 Query, 1 DDL, 1 DML example from Java
> # add .NET / C# API section and show 1 Query, 1 DDL, 1 DML example from C#
> # add Other API section and show 1 Query, 1 DDL, 1 DML example from Python, 
> PHP, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6041) Update Gettting Started documentation page

2017-08-11 Thread Denis Magda (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-6041:
---

Assignee: Akmal Chaudhri  (was: Denis Magda)

> Update Gettting Started documentation page
> --
>
> Key: IGNITE-6041
> URL: https://issues.apache.org/jira/browse/IGNITE-6041
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Akmal Chaudhri
>  Labels: docs
>
> Update Getting Started guide in the documentation [1]:
> # show enable/disable persistence flag
> # add SQL connectivity example (create, insert, select)
> # put data grid example right after SQL
> # add collocated computation example to the data grid example
> # add service grid example
> [1] https://apacheignite.readme.io/docs/getting-started



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6041) Update Gettting Started documentation page

2017-08-11 Thread Denis Magda (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123917#comment-16123917
 ] 

Denis Magda commented on IGNITE-6041:
-

[~abchaudhri], reassigning this task on you as agreed on @dev list.

Let's arrange the section in the following way:
# Node startup section. Explain how to start the node with ignite.sh, 
ignite.bat file from a command line tool or {{IgniteNodeStartup}} from an IDE. 
Spring XML file named {{"examples/config/example-ignite.xml"}} should be used 
as the nodes configuration.
# SQL Section. Show how to create two tables and define indexes using DDL. 
Insert and query data right after that. You can copy-paste a part of the code 
from the SQL getting started. Put a link to the latter for more advanced 
details.
# Key-Value Section. Rework the existing code snippet [1] using the caches 
created in the SQL section above.
# Compute Grid section. Let's rework the existing example [2] and show how to 
broadcast computations to all of the cities we have and how to execute an 
affinity-based computation for a concrete city and people living in it.
# Service Grid. Demonstrate how to deploy and execute a service. The service 
can return a population of a specific city.

[1] 
https://apacheignite.readme.io/docs/getting-started#section-first-ignite-data-grid-application
[2] 
https://apacheignite.readme.io/docs/getting-started#section-first-ignite-compute-application

> Update Gettting Started documentation page
> --
>
> Key: IGNITE-6041
> URL: https://issues.apache.org/jira/browse/IGNITE-6041
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: docs
>
> Update Getting Started guide in the documentation [1]:
> # show enable/disable persistence flag
> # add SQL connectivity example (create, insert, select)
> # put data grid example right after SQL
> # add collocated computation example to the data grid example
> # add service grid example
> [1] https://apacheignite.readme.io/docs/getting-started



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6041) Update Gettting Started documentation page

2017-08-11 Thread Denis Magda (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-6041:

Description: 
Update Getting Started guide in the documentation [1]:
# show enable/disable persistence flag
# add SQL connectivity example (create, insert, select)
# put data grid example right after SQL
# add collocated computation example to the data grid example
# add service grid example

[1] https://apacheignite.readme.io/docs/getting-started

  was:
Update Getting Started guide in documentation:
# show enable/disable persistence flag
# add SQL connectivity example (create, insert, select)
# put data grid example right after SQL
# add collocated computation example to the data grid example
# add service grid example


> Update Gettting Started documentation page
> --
>
> Key: IGNITE-6041
> URL: https://issues.apache.org/jira/browse/IGNITE-6041
> Project: Ignite
>  Issue Type: Task
>  Components: website
>Reporter: Dmitriy Setrakyan
>Assignee: Denis Magda
>  Labels: docs
>
> Update Getting Started guide in the documentation [1]:
> # show enable/disable persistence flag
> # add SQL connectivity example (create, insert, select)
> # put data grid example right after SQL
> # add collocated computation example to the data grid example
> # add service grid example
> [1] https://apacheignite.readme.io/docs/getting-started



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6045) Hibernate dialect for Ignite

2017-08-11 Thread Dmitriy Setrakyan (JIRA) 
Dmitriy Setrakyan created IGNITE-6045:
-

 Summary: Hibernate dialect for Ignite
 Key: IGNITE-6045
 URL: https://issues.apache.org/jira/browse/IGNITE-6045
 Project: Ignite
  Issue Type: Wish
  Components: hibernate, sql
Reporter: Dmitriy Setrakyan


Given that we have a very rich SQL support starting with version 2.1, it makes 
sense to create an Ignite SQL dialect for Hibernate?

https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-configuration.html#configuration-optional-dialects



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

2017-08-11 Thread Alexey Kukushkin (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123660#comment-16123660
 ] 

Alexey Kukushkin commented on IGNITE-6026:
--

Hi Alex,

Please specify "--port 11211" port when running "control.sh --activate". Also, 
add --host IGNITE_NODE if you run control.sh on a host where there are no 
ignite nodes. For example:

./bin/control.sh --host 127.0.0.1 --port 11211 --activate

It looks we have an issue that default Ignite command port is 11211 but 
control.sh uses 11212 by default.

Let me know if it did not help.

Best regards, Alexey


On Friday, August 11, 2017, 10:36:08 AM GMT+3, Alex Negashev (JIRA) 
 wrote:


    [ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122971#comment-16122971
 ] 

Alex Negashev commented on IGNITE-6026:
---

Hello Alexey, we add client to cluster with config:

        
        http://www.springframework.org/schema/beans; 
xmlns:cache="http://www.springframework.org/schema/cache; 
xmlns:context="http://www.springframework.org/schema/context; 
xmlns:mvc="http://www.springframework.org/schema/mvc; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="      
  http://www.springframework.org/schema/beans         
http://www.springframework.org/schema/beans/spring-beans.xsd         
http://www.springframework.org/schema/cache         
http://www.springframework.org/schema/cache/spring-cache-3.1.xsd         
http://www.springframework.org/schema/context         
http://www.springframework.org/schema/context/spring-context.xsd ">
          
              
              
              
              
                
                    
                
              

              
              
                  
              
              
                
                    
                      
                          
                          
                          
                          
                      
                    
                
              
          
        


some logs from instances:
ignite-cache-client-5 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-3 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-2 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]

but if i start script `./bin/control.sh --activate` it output: 
root@36ff2f004f78:/opt/ignite/apache-ignite-fabric-2.1.0-bin# ./bin/control.sh 
--activate
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

WARNING: Failed to initialize topology on client start. Will retry in 
background.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

INFO: Client started [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, protocol=TCP]
Something fail during activation, exception message: Latest topology update 
failed.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 
stop
INFO: Client stopped [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, 
waitCompletion=true]





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


> init cluster for Ignite Persistence by xml 
> ---
>
> Key: IGNITE-6026
> URL: https://issues.apache.org/jira/browse/IGNITE-6026
> Project: Ignite
>  Issue Type: Wish
>  Components: cache, examples, persistence
>Affects Versions: 2.1
> Environment: ignite in docker with zk
>Reporter: Alex Negashev
>Assignee: Alexey Kukushkin
>  Labels: documentation
>
> Hello! We use Ignite 2.1 and would like to use Ignite Persistence, how i can 
> do this without java code? xml only.
> Example attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

2017-08-11 Thread Alexey Kukushkin (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123654#comment-16123654
 ] 

Alexey Kukushkin commented on IGNITE-6026:
--

Hi Alex,

Please specify "--port 11211" port when running "control.sh --activate". Also, 
add --host IGNITE_NODE if you run control.sh on a host where there are no 
ignite nodes. For example:

./bin/control.sh --host 127.0.0.1 --port 11211 --activate

It looks we have an issue that default Ignite command port is 11211 but 
control.sh uses 11212 by default.

Let me know if it did not help.

> init cluster for Ignite Persistence by xml 
> ---
>
> Key: IGNITE-6026
> URL: https://issues.apache.org/jira/browse/IGNITE-6026
> Project: Ignite
>  Issue Type: Wish
>  Components: cache, examples, persistence
>Affects Versions: 2.1
> Environment: ignite in docker with zk
>Reporter: Alex Negashev
>Assignee: Alexey Kukushkin
>  Labels: documentation
>
> Hello! We use Ignite 2.1 and would like to use Ignite Persistence, how i can 
> do this without java code? xml only.
> Example attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away

2017-08-11 Thread Mikhail Cherkasov (JIRA) 
Mikhail Cherkasov created IGNITE-6044:
-

 Summary: SQL insert waits for transaction commit, but it must be 
executed right away
 Key: IGNITE-6044
 URL: https://issues.apache.org/jira/browse/IGNITE-6044
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
 Environment: Doc says:

""Presently, DML supports the atomic mode only meaning that if there is a DML 
query that is executed as a part of an Ignite transaction then it will not be 
enlisted in the transaction's writing queue and will be executed right away.""

https://apacheignite.readme.io/docs/dml#section-transactional-support

However the data will be added to cache only after transaction commit.
Reporter: Mikhail Cherkasov






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log

2017-08-11 Thread Vadim Opolski (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123379#comment-16123379
 ] 

Vadim Opolski commented on IGNITE-4756:
---

[~tledkov-gridgain] [~avinogradov]] Review please - 
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-277

> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expectedPrimary=, 
> exectedBackups=, 
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
> backups=3(75%)].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

2017-08-11 Thread Andrey Kuznetsov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123316#comment-16123316
 ] 

Andrey Kuznetsov commented on IGNITE-6009:
--

Blocking compute jobs leaded to compute threads exhausting, and to deadlock, 
consequently. Fixed by limiting blocking ("consumer") job count by value less 
than total compute thread count.

[~DmitriyGovorukhin], please review my changes.

> CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout
> --
>
> Key: IGNITE-6009
> URL: https://issues.apache.org/jira/browse/IGNITE-6009
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Andrey Kuznetsov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

2017-08-11 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123294#comment-16123294
 ] 

ASF GitHub Bot commented on IGNITE-6009:


GitHub user andrey-kuznetsov opened a pull request:

https://github.com/apache/ignite/pull/2434

IGNITE-6009: Fixed IgniteSemaphore test.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6009

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2434.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2434


commit 0aa7cc63a58ae2699c225d99b5b147ee50c7
Author: Andrey Kuznetsov 
Date:   2017-08-11T12:51:31Z

IGNITE-6009: Fixed IgniteSemaphore test.




> CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout
> --
>
> Key: IGNITE-6009
> URL: https://issues.apache.org/jira/browse/IGNITE-6009
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Andrey Kuznetsov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6026) init cluster for Ignite Persistence by xml

2017-08-11 Thread Alexey Kukushkin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kukushkin reassigned IGNITE-6026:


Assignee: Alexey Kukushkin

> init cluster for Ignite Persistence by xml 
> ---
>
> Key: IGNITE-6026
> URL: https://issues.apache.org/jira/browse/IGNITE-6026
> Project: Ignite
>  Issue Type: Wish
>  Components: cache, examples, persistence
>Affects Versions: 2.1
> Environment: ignite in docker with zk
>Reporter: Alex Negashev
>Assignee: Alexey Kukushkin
>  Labels: documentation
>
> Hello! We use Ignite 2.1 and would like to use Ignite Persistence, how i can 
> do this without java code? xml only.
> Example attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

2017-08-11 Thread Andrey Kuznetsov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Kuznetsov reassigned IGNITE-6009:


Assignee: Andrey Kuznetsov

> CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout
> --
>
> Key: IGNITE-6009
> URL: https://issues.apache.org/jira/browse/IGNITE-6009
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Andrey Kuznetsov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5902) Refactor VisorCacheStopTask to support stopping several caches at once

2017-08-11 Thread Pavel Konstantinov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123142#comment-16123142
 ] 

Pavel Konstantinov commented on IGNITE-5902:


Tested.

> Refactor  VisorCacheStopTask to support stopping several caches at once
> ---
>
> Key: IGNITE-5902
> URL: https://issues.apache.org/jira/browse/IGNITE-5902
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Stopping several caches at once much more faster then one-by-one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-5902) Refactor VisorCacheStopTask to support stopping several caches at once

2017-08-11 Thread Pavel Konstantinov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-5902.
--

> Refactor  VisorCacheStopTask to support stopping several caches at once
> ---
>
> Key: IGNITE-5902
> URL: https://issues.apache.org/jira/browse/IGNITE-5902
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> Stopping several caches at once much more faster then one-by-one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5940) Datastreamer does not propagate OOME

2017-08-11 Thread Mikhail Cherkasov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-5940:
--
Summary:  Datastreamer does not propagate OOME  (was: DataStreamer throws 
exception as it's closed if OOM occurs on server node.)

>  Datastreamer does not propagate OOME
> -
>
> Key: IGNITE-5940
> URL: https://issues.apache.org/jira/browse/IGNITE-5940
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5940) Datastreamer does not propagate OOME

2017-08-11 Thread Mikhail Cherkasov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-5940:
--
Description: DataStreamer throws exception as it's closed if OOM occurs on 
server node.

>  Datastreamer does not propagate OOME
> -
>
> Key: IGNITE-5940
> URL: https://issues.apache.org/jira/browse/IGNITE-5940
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> DataStreamer throws exception as it's closed if OOM occurs on server node.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4784) Web Console: Revise demo mode

2017-08-11 Thread Dmitriy Shabalin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Shabalin reassigned IGNITE-4784:


Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

[~kuaw26] Added changes, pls review it

> Web Console: Revise demo mode
> -
>
> Key: IGNITE-4784
> URL: https://issues.apache.org/jira/browse/IGNITE-4784
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> Let's add animated blue line.
> Demo: https://marvelapp.com/32e928b
> # Link 'Close Demo' should be red onhover.
> # Let's delete btn 'Close Demo' on demo mode
> # We should use affix behaviour (*y)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6026) init cluster for Ignite Persistence by xml

2017-08-11 Thread Alex Negashev (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122971#comment-16122971
 ] 

Alex Negashev commented on IGNITE-6026:
---

Hello Alexey, we add client to cluster with config:


http://www.springframework.org/schema/beans; 
xmlns:cache="http://www.springframework.org/schema/cache; 
xmlns:context="http://www.springframework.org/schema/context; 
xmlns:mvc="http://www.springframework.org/schema/mvc; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="  
   http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans.xsd 
http://www.springframework.org/schema/cache 
http://www.springframework.org/schema/cache/spring-cache-3.1.xsd 
http://www.springframework.org/schema/context 
http://www.springframework.org/schema/context/spring-context.xsd ">
   
  
  
  
  
 

 
  

  
  
  
  
  
 

   
  
  
  
  
   

 
  
   



some logs from instances:
ignite-cache-client-5 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-3 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]
ignite-cache-client-2 | [07:29:53] Topology snapshot [ver=30, servers=5, 
clients=5, CPUs=40, heap=10.0GB]

but if i start script `./bin/control.sh --activate` it output: 
root@36ff2f004f78:/opt/ignite/apache-ignite-fabric-2.1.0-bin# ./bin/control.sh 
--activate
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

WARNING: Failed to initialize topology on client start. Will retry in 
background.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 

INFO: Client started [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, protocol=TCP]
Something fail during activation, exception message: Latest topology update 
failed.
Aug 11, 2017 7:33:59 AM org.apache.ignite.internal.client.impl.GridClientImpl 
stop
INFO: Client stopped [id=6b6279f1-6d5c-46a4-b88a-83d1378d94d2, 
waitCompletion=true]


> init cluster for Ignite Persistence by xml 
> ---
>
> Key: IGNITE-6026
> URL: https://issues.apache.org/jira/browse/IGNITE-6026
> Project: Ignite
>  Issue Type: Wish
>  Components: cache, examples, persistence
>Affects Versions: 2.1
> Environment: ignite in docker with zk
>Reporter: Alex Negashev
>  Labels: documentation
>
> Hello! We use Ignite 2.1 and would like to use Ignite Persistence, how i can 
> do this without java code? xml only.
> Example attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6043) Fix GridCacheSemaphoreImpl methods semantics

2017-08-11 Thread Andrey Kuznetsov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Kuznetsov updated IGNITE-6043:
-
Description: 
Current semaphore implementation, {{GridCacheSemaphoreImpl}}, has inverted 
method semantics: {{acquire()}} releases the permit and {{release()}} acquires 
it. Also, debug-level method {{availablePermits()}} returns permits acquired so 
far. This confusing behaviour should be fixed.

Also, it's worth noting in IgniteSemaphore's javadoc its unbounded nature, as 
opposed to {{java.util.concurrent.Semaphore}}.

  was:
Current semaphore implementation, {{GridCacheSemaphoreImpl}}, has inverted 
method semantics: {{acquire()}} releases the permit and {{release()}} acquires 
it. Also, debug-level method {{availablePermits()}} returns permits acquired so 
far. This confusing behaviour should be fixed.

Also, it's worth noting in IgniteSemaphore's javadoc it's unbounded nature, as 
opposed to {{java.util.concurrent.Semaphore}}.


> Fix GridCacheSemaphoreImpl methods semantics
> 
>
> Key: IGNITE-6043
> URL: https://issues.apache.org/jira/browse/IGNITE-6043
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.1
>Reporter: Andrey Kuznetsov
>Priority: Critical
>
> Current semaphore implementation, {{GridCacheSemaphoreImpl}}, has inverted 
> method semantics: {{acquire()}} releases the permit and {{release()}} 
> acquires it. Also, debug-level method {{availablePermits()}} returns permits 
> acquired so far. This confusing behaviour should be fixed.
> Also, it's worth noting in IgniteSemaphore's javadoc its unbounded nature, as 
> opposed to {{java.util.concurrent.Semaphore}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6043) Fix GridCacheSemaphoreImpl methods semantics

2017-08-11 Thread Andrey Kuznetsov (JIRA) 
Andrey Kuznetsov created IGNITE-6043:


 Summary: Fix GridCacheSemaphoreImpl methods semantics
 Key: IGNITE-6043
 URL: https://issues.apache.org/jira/browse/IGNITE-6043
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Affects Versions: 2.1
Reporter: Andrey Kuznetsov
Priority: Critical


Current semaphore implementation, {{GridCacheSemaphoreImpl}}, has inverted 
method semantics: {{acquire()}} releases the permit and {{release()}} acquires 
it. Also, debug-level method {{availablePermits()}} returns permits acquired so 
far. This confusing behaviour should be fixed.

Also, it's worth noting in IgniteSemaphore's javadoc it's unbounded nature, as 
opposed to {{java.util.concurrent.Semaphore}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)