[jira] [Assigned] (IGNITE-5230) Web Console: SVG icons integration

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5230:


Assignee: Andrey Novikov  (was: Ilya Borisov)

Please review Dmitry's changes. He applied new icons to his pages.

> Web Console: SVG icons integration
> --
>
> Key: IGNITE-5230
> URL: https://issues.apache.org/jira/browse/IGNITE-5230
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Minor
>
> We need a common way to use SVG icons that:
> 1. Does not require extra styles.
> 2. Allows for CSS styling of icons, especially icon color.
> 3. Easy to add new icons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5165) Web Console: Buttons redesign

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-5165.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console:  Buttons redesign 
> ---
>
> Key: IGNITE-5165
> URL: https://issues.apache.org/jira/browse/IGNITE-5165
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: 5165 debug page.diff
>
>
> Create common style to all buttons in project.
> Refactoring current style for buttons in 
> web-console/frontend/public/stylesheets/style.scss
> 1) Button with icon and text
> 2) Button with only icon
> 3) Button with only text
> 4) Button group
> 5) fill and stroke buttons for color Red, Blue, White
> Implement class modificator .btn-ignite to apply this features



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5082) Redesign base template

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-5082.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5250) Unhelpful exception when value of wrong type is passed to H2

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5250:

Attachment: ExampleNodeStartup.java

> Unhelpful exception when value of wrong type is passed to H2
> 
>
> Key: IGNITE-5250
> URL: https://issues.apache.org/jira/browse/IGNITE-5250
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Sergi Vladykin
> Fix For: 2.1
>
> Attachments: ExampleNodeStartup.java
>
>
> For instance, if an SQL schema defined this way:
> {code}
> cfg.setIndexedTypes(AffinityKey.class, Person.class);
> {code}
> and then, by some reason, the users confuses the type of the key passing 
> {{int}} instead of {{AffinityKey}}
> {code}
> SqlFieldsQuery query = new SqlFieldsQuery("INSERT INTO Person (_key, 
> id, name, country ) " +
> "VALUES ( ? , ? , ? , ?)");
> // Setting the key of a wrong type (AffinityKey instance must be used 
> instead).
> query.setArgs(100, 1000, "John", "Canada");
> // Getting not user friendly exception.
> cache.query(query).getAll();
> {code}
> he will get an exception that doesn't point out to the exact root cause:
> {noformat}
> Caused by: class org.apache.ignite.IgniteException: Failed to execute SQL 
> query.
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:365)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:836)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:378)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:173)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:207)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1657)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1701)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1699)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2129)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1706)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:783)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> SQL query.
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1224)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1276)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$1300(IgniteH2Indexing.java:239)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1079)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1067)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:362)
>   ... 18 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number 
> of characters: "100"; SQL statement:
> SELECT
> TABLE._KEY,
> TABLE.ID,
> TABLE.NAME,
> TABLE.COUNTRY
> FROM TABLE(_KEY OTHER=(?1,), ID BIGINT=(?2,), NAME VARCHAR=(?3,), COUNTRY 
> VARCHAR=(?4,)) [90003-195]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
>   at org.h2.message.DbException.get(DbException.java:179)
>   at org.h2.message.DbException.get(DbException.java:155)
>   at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
>   at org.h2.value.Value.convertTo(Value.java:957)
>   at org.h2.table.Column.convert(Column.java:167)
>   at org.h2.expression.TableFunction.getTable(TableFunction.java:118)
>   at org.h2.expression.TableFunction.getValue(TableFunction.java:41)
>   at org.h2.table.FunctionTable.getValueResultSet(FunctionTable.java:218)
>   at org.h2.table.FunctionTable.getResult(FunctionTable.java:189)
>   at 

[jira] [Created] (IGNITE-5250) Unhelpful exception when value of wrong type is passed to H2

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5250:
---

 Summary: Unhelpful exception when value of wrong type is passed to 
H2
 Key: IGNITE-5250
 URL: https://issues.apache.org/jira/browse/IGNITE-5250
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.0
Reporter: Denis Magda
Assignee: Sergi Vladykin
 Fix For: 2.1


For instance, if an SQL schema defined this way:
{code}
cfg.setIndexedTypes(AffinityKey.class, Person.class);
{code}

and then, by some reason, the users confuses the type of the key passing 
{{int}} instead of {{AffinityKey}}

{code}
SqlFieldsQuery query = new SqlFieldsQuery("INSERT INTO Person (_key, 
id, name, country ) " +
"VALUES ( ? , ? , ? , ?)");

// Setting the key of a wrong type (AffinityKey instance must be used 
instead).
query.setArgs(100, 1000, "John", "Canada");

// Getting not user friendly exception.
cache.query(query).getAll();
{code}

he will get an exception that doesn't point out to the exact root cause:
{noformat}
Caused by: class org.apache.ignite.IgniteException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:365)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:836)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:378)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:173)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:207)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1657)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1701)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1699)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2129)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1706)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:783)
... 6 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1224)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1276)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$1300(IgniteH2Indexing.java:239)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1079)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1067)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:362)
... 18 more
Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of 
characters: "100"; SQL statement:
SELECT
TABLE._KEY,
TABLE.ID,
TABLE.NAME,
TABLE.COUNTRY
FROM TABLE(_KEY OTHER=(?1,), ID BIGINT=(?2,), NAME VARCHAR=(?3,), COUNTRY 
VARCHAR=(?4,)) [90003-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
at org.h2.value.Value.convertTo(Value.java:957)
at org.h2.table.Column.convert(Column.java:167)
at org.h2.expression.TableFunction.getTable(TableFunction.java:118)
at org.h2.expression.TableFunction.getValue(TableFunction.java:41)
at org.h2.table.FunctionTable.getValueResultSet(FunctionTable.java:218)
at org.h2.table.FunctionTable.getResult(FunctionTable.java:189)
at org.h2.index.FunctionIndex.find(FunctionIndex.java:50)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at 
org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at 

[jira] [Closed] (IGNITE-5104) Refactor javadocs and annotations to single style

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-5104.
---

> Refactor javadocs and annotations to single style
> -
>
> Key: IGNITE-5104
> URL: https://issues.apache.org/jira/browse/IGNITE-5104
> Project: Ignite
>  Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Trivial
>
> According to Ignite codestyle:
> We should use a shorter version of {@inheritDoc} when it possible.
> Annotations @Nullable and @Override should be placed on one line with declare 
> of method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5104) Refactor javadocs and annotations to single style

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5104:
-

[~NSAmelchev], merged, thanks for the contribution!

> Refactor javadocs and annotations to single style
> -
>
> Key: IGNITE-5104
> URL: https://issues.apache.org/jira/browse/IGNITE-5104
> Project: Ignite
>  Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Trivial
>
> According to Ignite codestyle:
> We should use a shorter version of {@inheritDoc} when it possible.
> Annotations @Nullable and @Override should be placed on one line with declare 
> of method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4887) Support for starting transaction in another thread

[Igor Gorkov (JIRA)]

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

Igor Gorkov commented on IGNITE-4887:
-

Yakov,

I think it will be useful in case of full JTA support.
XA specification says that calling xa_end method upon XA Resource should 
dissociate the thread from a transaction branch whereas xa_start should start 
or resume a transaction branch.

But in current ignite CacheJtaResource implementation of 
javax.transaction.xa.XAResource methods end and start do not work as described 
in the specification (nor in XAResource interface). E.g. flags like TMSUSPEND 
are ignored. (And I think in general XAResource interface is used not as it's 
developers intended it to be used)

It will be cool if we can fully implement XAResource with transaction branches 
switched between threads. I think we could manage some timeout monitors to 
heuristically finish stuck transactions.

Igor

> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another 
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction. 
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be 
> able to introduce futher changes into transaction and commit it in the end.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-5106) Website still contains links to to "incubator-ignite"

[Prachi Garg (JIRA)]

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

Prachi Garg resolved IGNITE-5106.
-
Resolution: Fixed

Removed all occurrences of 'incubator' from the website.

> Website still contains links to to "incubator-ignite" 
> --
>
> Key: IGNITE-5106
> URL: https://issues.apache.org/jira/browse/IGNITE-5106
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Affects Versions: 1.1.4
>Reporter: Konstantin Boudnik
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> At least some of the examples referred by the website pages are pointed to 
> "incubator-ignite" mirror on the github. Which were empty for a long time.
> Let's get this fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5106) Website still contains links to to "incubator-ignite"

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-5106.
---

> Website still contains links to to "incubator-ignite" 
> --
>
> Key: IGNITE-5106
> URL: https://issues.apache.org/jira/browse/IGNITE-5106
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Affects Versions: 1.1.4
>Reporter: Konstantin Boudnik
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> At least some of the examples referred by the website pages are pointed to 
> "incubator-ignite" mirror on the github. Which were empty for a long time.
> Let's get this fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-4575:


Fixed all except p.2 and p.5. 

> Implement in Ignite wrapper for enums based on H2 user value type
> -
>
> Key: IGNITE-4575
> URL: https://issues.apache.org/jira/browse/IGNITE-4575
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5106) Website still contains links to to "incubator-ignite"

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5106:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Website still contains links to to "incubator-ignite" 
> --
>
> Key: IGNITE-5106
> URL: https://issues.apache.org/jira/browse/IGNITE-5106
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Affects Versions: 1.1.4
>Reporter: Konstantin Boudnik
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> At least some of the examples referred by the website pages are pointed to 
> "incubator-ignite" mirror on the github. Which were empty for a long time.
> Let's get this fixed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5017) HTML formatted releases notes

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-5017.
---

> HTML formatted releases notes
> -
>
> Key: IGNITE-5017
> URL: https://issues.apache.org/jira/browse/IGNITE-5017
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.9
>Reporter: Sergey Kozlov
>Assignee: Denis Magda
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5017) HTML formatted releases notes

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5017:
-

Done, here is an example of how the page looks like:
https://ignite.apache.org/releases/2.0.0/release_notes.html

> HTML formatted releases notes
> -
>
> Key: IGNITE-5017
> URL: https://issues.apache.org/jira/browse/IGNITE-5017
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.9
>Reporter: Sergey Kozlov
>Assignee: Denis Magda
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-5017) HTML formatted releases notes

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-5017.
-
Resolution: Fixed

> HTML formatted releases notes
> -
>
> Key: IGNITE-5017
> URL: https://issues.apache.org/jira/browse/IGNITE-5017
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.9
>Reporter: Sergey Kozlov
>Assignee: Denis Magda
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4947) Create AI 2.0 TC suites

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-4947:


Discussion
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-0-TeamCity-Run-configurations-td17751.html

Configs:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview

> Create AI 2.0 TC suites
> ---
>
> Key: IGNITE-4947
> URL: https://issues.apache.org/jira/browse/IGNITE-4947
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Due to OptimizedMarshaller removal from public API per IGNITE-4938, we need 
> all-new post-OptimizedMarshaller set of TC suites that will be used by 
> default after 2.0 is released.
> What has to be done:
> - Remove all OptimizedMarshaller specific suites
> - Make all 'binary' suites 'standard'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5249) The release build procedure

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5249:
-

 Summary: The release build procedure
 Key: IGNITE-5249
 URL: https://issues.apache.org/jira/browse/IGNITE-5249
 Project: Ignite
  Issue Type: Task
  Components: build
Reporter: Sergey Kozlov
 Fix For: 2.1


The release build procedure should be placed on the CI/CD server and available 
to run for the release engineer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5245) MIN function returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-5245:
--
Description: 
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where one entry has the field is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value

  was:
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where that field is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value


> MIN function returns NULL if a numeric column of class has NULL values
> --
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> 1. Use class with the numeric field (e.g. {{Short col_Short_1}})
> 2. Put a few entries where one entry has the field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5245) MIN function returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-5245:
--
Description: 
1. Use class ({{DefaultTable}}) with the numeric field (e.g. {{Short 
col_Short_1}})
2. Put a few entries where one entry has the field is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value

  was:
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where one entry has the field is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value


> MIN function returns NULL if a numeric column of class has NULL values
> --
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> 1. Use class ({{DefaultTable}}) with the numeric field (e.g. {{Short 
> col_Short_1}})
> 2. Put a few entries where one entry has the field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-5248:
-
Labels: newbie  (was: )

> Best effort check to detect a 32-bit JVM trying to allocate too big amount of 
> memory
> 
>
> Key: IGNITE-5248
> URL: https://issues.apache.org/jira/browse/IGNITE-5248
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>  Labels: newbie
> Fix For: 2.1
>
>
> A follow-up on the user list discussion:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
> We can catch the IllegalArgumentException and see if the allocated space 
> exceeds 2Gb. In this case, we should suggest that user check that he is 
> running a 64-bit JVM.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5248) Best effort check to detect a 32-bit JVM trying to allocate too big amount of memory

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5248:


 Summary: Best effort check to detect a 32-bit JVM trying to 
allocate too big amount of memory
 Key: IGNITE-5248
 URL: https://issues.apache.org/jira/browse/IGNITE-5248
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
 Fix For: 2.1


A follow-up on the user list discussion:
http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html

We can catch the IllegalArgumentException and see if the allocated space 
exceeds 2Gb. In this case, we should suggest that user check that he is running 
a 64-bit JVM.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (IGNITE-5168) Make IGFS metrics available for user

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky updated IGNITE-5168:

Comment: was deleted

(was: tests)

> Make IGFS metrics available for user
> 
>
> Key: IGNITE-5168
> URL: https://issues.apache.org/jira/browse/IGNITE-5168
> Project: Ignite
>  Issue Type: New Feature
>  Components: igfs
>Affects Versions: 2.0
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
>
> Now in Ignite the only way to see IGFS metrics is to get them programmically 
> from the code. But customers need them to understand what is cached in IGFS, 
> so to expose the metrics would be useful. 
> There are options to expose the metrics via 
> 1) MBean 
> 2) console Visor .
> 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console 
> )



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5227) StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5227:


GitHub user mcherkasov opened a pull request:

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

IGNITE-5227: StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

StackOverflowError occurs due recursion in methods:
GridCacheMapEntry.checkOwnerChanged -> 
GridDistributedCacheEntry.checkThreadChain -> GridDistributedCacheEntry.recheck 
-> GridCacheMapEntry.checkOwnerChanged

I broke this cycle by introducing "checkCandidateChain" flag in 
GridCacheMapEntry.checkOwnerChanged method, which allow to miss 
GridDistributedCacheEntry.checkThreadChain. 
The check fo the whole candidate chain is moved to 
GridDistributedCacheEntry.checkThreadChain method, as you can see there  
already was cycle for this, I've just removed break(put it in else branch in 
case we don't have any kes for lock candidates).

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

$ git pull https://github.com/mcherkasov/ignite master

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

https://github.com/apache/ignite/pull/1967.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 #1967


commit fbe059e8003b04568a39a3cfb604a248928d1f6f
Author: mcherkasov 
Date:   2017-05-17T17:12:14Z

IGNITE-5227: StackOverflowError in GridCacheMapEntry#checkOwnerChanged()




> StackOverflowError in GridCacheMapEntry#checkOwnerChanged()
> ---
>
> Key: IGNITE-5227
> URL: https://issues.apache.org/jira/browse/IGNITE-5227
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Alexey Goncharuk
>Assignee: Mikhail Cherkasov
>Priority: Critical
> Fix For: 2.1
>
>
> A simple test reproducing this error:
> {code}
> /**
>  * @throws Exception if failed.
>  */
> public void testBatchUnlock() throws Exception {
>startGrid(0);
>grid(0).createCache(new CacheConfiguration Integer>(DEFAULT_CACHE_NAME)
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
> try {
> final CountDownLatch releaseLatch = new CountDownLatch(1);
> IgniteInternalFuture fut = GridTestUtils.runAsync(new 
> Callable() {
> @Override public Object call() throws Exception {
> IgniteCache cache = grid(0).cache(null);
> Lock lock = cache.lock("key");
> try {
> lock.lock();
> releaseLatch.await();
> }
> finally {
> lock.unlock();
> }
> return null;
> }
> });
> Map putMap = new LinkedHashMap<>();
> putMap.put("key", "trigger");
> for (int i = 0; i < 10_000; i++)
> putMap.put("key-" + i, "value");
> IgniteCache asyncCache = 
> grid(0).cache(null).withAsync();
> asyncCache.putAll(putMap);
> IgniteFuture resFut = asyncCache.future();
> Thread.sleep(1000);
> releaseLatch.countDown();
> fut.get();
> resFut.get();
> }
> finally {
> stopAllGrids();
> }
> {code}
> We should replace a recursive call with a simple iteration over the linked 
> list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5168) Make IGFS metrics available for user

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-5168 at 5/17/17 5:23 PM:
--

Pull request https://github.com/apache/ignite/pull/1966 exposes IGFS metrics 
through the MXBeans (makes the metrics observable via JConsole).


was (Author: iveselovskiy):
https://github.com/apache/ignite/pull/1966

> Make IGFS metrics available for user
> 
>
> Key: IGNITE-5168
> URL: https://issues.apache.org/jira/browse/IGNITE-5168
> Project: Ignite
>  Issue Type: New Feature
>  Components: igfs
>Affects Versions: 2.0
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
>
> Now in Ignite the only way to see IGFS metrics is to get them programmically 
> from the code. But customers need them to understand what is cached in IGFS, 
> so to expose the metrics would be useful. 
> There are options to expose the metrics via 
> 1) MBean 
> 2) console Visor .
> 3) web console ( https://apacheignite-tools.readme.io/docs/ignite-web-console 
> )



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5247) TcpCommunicationSpi calls GridNioRecoveryDescriptor with looks unusually large rcvCnt and fail with null.

[Chandra Bose Renganathan (JIRA)]

Chandra Bose Renganathan created IGNITE-5247:


 Summary: TcpCommunicationSpi calls GridNioRecoveryDescriptor with 
looks unusually large rcvCnt and fail with null. 
 Key: IGNITE-5247
 URL: https://issues.apache.org/jira/browse/IGNITE-5247
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Chandra Bose Renganathan
Priority: Critical


TcpCommunicationSpi calls GridNioRecoveryDescriptor with looks unusually large 
rcvCnt and fail with null. 

This happens when new node try to join existing grid of size 2 or 3, 

Environment linux.

rcvCnt=216172782113783808 ???
The configuration following. PopcornJGroupsTcpDiscoveryIpFinder returns 3 
InetSocketAddress including self.

  IgniteConfiguration cfg = new IgniteConfiguration();
  cfg.setGridLogger(new Slf4jLogger(LOG));
  TcpDiscoverySpi spi = new TcpDiscoverySpi();
  spi.setLocalPort(cachePort);
  
spi.setSocketTimeout(popcornCfg.getLongProperty("popcorn.cache.socketTimeout", 
1L));
  
spi.setLocalPortRange(popcornCfg.getIntProperty("popcorn.cache.portRange", 2));
  spi.setIpFinder(new PopcornJGroupsTcpDiscoveryIpFinder(this));
  Ignition.start(cfg);



08:15:00.838-07:00 [grid-nio-worker-tcp-comm-1-#522%demo-cluster.service%] 
ERROR o.a.i.s.c.t.TcpCommunicationSpi -  - Caught unhandled exception in NIO 
worker thread (restart the node)., "exception":"java.lang.AssertionError: 
Missed message [rcvCnt=216172782113783808, acked=3, 
desc=GridNioRecoveryDescriptor [acked=3, resendCnt=0, rcvCnt=3, sentCnt=3, 
reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
[id=acf668c2-188b-4488-bc02-f4a4eca46ab3, addrs=[127.0.0.1, 144.77.76.153], 
sockAddrs=[/127.0.0.1:20103, .com/144.77.76.153:20103], discPort=20103, 
order=2, intOrder=2, lastExchangeTime=1495034080652, loc=false, 
ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], connected=true, 
connectCnt=1, queueLimit=4096, reserveCnt=1, pairedConnections=false]]", 
"stack":[

"o.a.i.i.u.n.GridNioRecoveryDescriptor.ackReceived(GridNioRecoveryDescriptor.java:207)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.s.c.t.TcpCommunicationSpi$2.onMessage(TcpCommunicationSpi.java:647) 
~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.s.c.t.TcpCommunicationSpi$2.onMessage(TcpCommunicationSpi.java:342) 
~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:117) 
~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:88)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3062)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175) 
~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1121)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2031)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1868)
 ~[ignite-core-2.0.0.jar:2.0.0]",

"o.a.i.i.u.n.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1573)
 ~[ignite-core-2.0.0.jar:2.0.0]",
"o.a.i.i.u.w.GridWorker.run(GridWorker.java:110) 
[ignite-core-2.0.0.jar:2.0.0]",
"java.lang.Thread.run(Thread.java:745) [na:1.8.0_112]"]}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4887) Support for starting transaction in another thread

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-4887:
---

Alexey,

It seems that dev list is a better place for discussions like this. Tickets 
should be filed after some consensus is reached.

I don't like the suggestion because we can end up in millions of uncommitted 
transactions. Imagine none picks paused transaction and it is never committed. 
We will have stale locks all over our cache with no understanding about when 
they should be released. This can happen due to some exceptions or due to bugs 
in code.

Why don't  you pass the whole transaction to that async future's listener? So 
transaction gets started and committed in single method.

Thanks!

Yakov

> Support for starting transaction in another thread
> --
>
> Key: IGNITE-4887
> URL: https://issues.apache.org/jira/browse/IGNITE-4887
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Consider the following pseudo-code:
> {code:xml}
> IgniteTransactions transactions = ignite1.transactions();
> Transaction tx = startTransaction(transactions);
> cache.put("key1", 1);
> tx.stop();
> {code}
> And in another thread:
> {code:xml}
> transactions.txStart(tx);
> cache.put("key3", 3);
> cache.remove("key2");
> tx.commit();
> {code}
> The Api should be implemented , that let you continue transaction in another 
> thread.
> method stop() should mark the transaction as unavailable for further commit.
> method txStart() should resume the transaction. 
> reason behind the proposal :
> Consider the next scenario:
> we begin transaction, doing some changes and start async future that will be 
> able to introduce futher changes into transaction and commit it in the end.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4910) Add copyOnRead property for near cache.

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-4910:
---

[~dreamx], I would consider this PR to be the very first step to the actual 
goal of this ticket. The second one is to make Ignite return cached 
deserialized value or deserialize binary object each time according to the 
configuration parameter set by user.

Please see how org.apache.ignite.configuration.CacheConfiguration#isCopyOnRead 
is treated and please add tests for the new property.

Thanks!

Yakov 

> Add copyOnRead property for near cache.
> ---
>
> Key: IGNITE-4910
> URL: https://issues.apache.org/jira/browse/IGNITE-4910
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Maksim Kozlov
>Assignee: Maksim Kozlov
> Fix For: 2.1
>
>
> Add {{setCopyOnRead}} to {{NearCacheConfiguration}} class.
> Continuation of the task from the ticket 
> [https://issues.apache.org/jira/browse/IGNITE-2558].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5212) Allow custom affinity for system caches

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov edited comment on IGNITE-5212 at 5/17/17 3:03 PM:


This is my PR: https://github.com/apache/ignite/pull/1964
[~sboikov], please look at this change.

I have added possibility to set custom affinity function through 
{{AtomicConfiguration#setAffinity}}.


was (Author: v.pyatkov):
This is my PR: https://github.com/apache/ignite/pull/1964
[~sboikov], please look at this change.

I have added available to set custom affinity function through 
{{AtomicConfiguration#setAffinity}}.

> Allow custom affinity for system caches
> ---
>
> Key: IGNITE-5212
> URL: https://issues.apache.org/jira/browse/IGNITE-5212
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Vladislav Pyatkov
>  Labels: newbie
>
> Currently there is no option to specify affinity function atomics system 
> cache, which may be not appropriate in custom data placement scenarios.
> Suggestion: allow setting custom affinity for AtomicConfiguration



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5212) Allow custom affinity for system caches

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov commented on IGNITE-5212:
---

This is my PR: https://github.com/apache/ignite/pull/1964
[~sboikov], please look at this change.

I have added available to set custom affinity function through 
{{AtomicConfiguration#setAffinity}}.

> Allow custom affinity for system caches
> ---
>
> Key: IGNITE-5212
> URL: https://issues.apache.org/jira/browse/IGNITE-5212
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Vladislav Pyatkov
>  Labels: newbie
>
> Currently there is no option to specify affinity function atomics system 
> cache, which may be not appropriate in custom data placement scenarios.
> Suggestion: allow setting custom affinity for AtomicConfiguration



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5218) Decision trees

[Yury Babak (JIRA)]

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

Yury Babak commented on IGNITE-5218:


I think that it's also may include random forest implementation.

> Decision trees
> --
>
> Key: IGNITE-5218
> URL: https://issues.apache.org/jira/browse/IGNITE-5218
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>
> We want to implement Decision trees for Ignite ML because it's really common 
> one for ML.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4648) IgniteInternalTx.prepare() does not wait for async operations to complete

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-4648:
---

Dmitry, can you please add a test that fails before the fix and passes after? 
In Ignite we try to react on a problem reported with a  test that fails. Then 
we fix the test. 

Please look at this test - 
org.apache.ignite.internal.processors.cache.AbstractCacheJtaSelfTest

You can add new test method and do some putAsync() for keys that are currently 
locked by pessimistic transactions in parallel threads. Then you commit JTA 
transaction and then commit cache transaction in parallel thread and then 
assert the results.

Thanks!

Yakov

> IgniteInternalTx.prepare() does not wait for async operations to complete
> -
>
> Key: IGNITE-4648
> URL: https://issues.apache.org/jira/browse/IGNITE-4648
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Fix For: 2.1
>
>
> {{commit}} and {{rollback}} wait for async operations by calling 
> {{tx.txState().awaitLastFut();}} (see {{GridCacheSharedContext}}).
> There is no such thing in {{IgniteInternalTx.prepare()}} implementations.
> Since {{prepare}} is an internal method, this is not an issue mostly, except 
> for two things:
> * JTA. {{CacheJtaResource}} calls {{prepare()}} explicitly. 
> * .NET {{TransactionScope}} API. Same thing as JTA, basically. 
> {{PlatformTransactions}} call {{prepare()}} as well.
> As a result, if user starts an async operation within JTA transaction and 
> then completes the tx, undefined behavior is possible.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5246) Fuzzy c-means (FCM)

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5246:
--

 Summary: Fuzzy c-means (FCM)
 Key: IGNITE-5246
 URL: https://issues.apache.org/jira/browse/IGNITE-5246
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Yury Babak


We want to have implementation of fuzzy clusterization.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (IGNITE-5054) Support SQL schema sharing between different caches

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5054:

Comment: was deleted

(was: GitHub user devozerov opened a pull request:

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

IGNITE-5054



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5054

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

https://github.com/apache/ignite/pull/1923.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 #1923


commit 26229676f70dbc8fadcd449b5745ca644078ac67
Author: devozerov 
Date:   2017-05-10T10:40:02Z

Minor refactoring.

commit bbeedbfa6e2747d1647f80d009ca8331dcabc296
Author: devozerov 
Date:   2017-05-10T10:48:26Z

Minor refactoring (2).

commit ae1578e0b8e7c14c73e8cae901afc5bfa70b3ccf
Author: devozerov 
Date:   2017-05-10T10:56:33Z

Refactoring (3).

commit 116f5a2dc604b3051bda4068d6feb9022dac1dbe
Author: devozerov 
Date:   2017-05-10T11:25:50Z

WIP.

commit 1279f8b4b6fe94a9d3e197a66789804dfc37883f
Author: devozerov 
Date:   2017-05-10T11:53:00Z

WIP.


)

> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5054) Support SQL schema sharing between different caches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5054:


GitHub user devozerov opened a pull request:

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

IGNITE-5054



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5054-splitter

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

https://github.com/apache/ignite/pull/1962.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 #1962






> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (IGNITE-5054) Support SQL schema sharing between different caches

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5054:

Comment: was deleted

(was: Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/1923
)

> Support SQL schema sharing between different caches
> ---
>
> Key: IGNITE-5054
> URL: https://issues.apache.org/jira/browse/IGNITE-5054
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>
> Current every cache "lives" in it's own schema. We need to allow different 
> caches to optionally share the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction

[Ryabov Dmitrii (JIRA)]

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

Ryabov Dmitrii commented on IGNITE-2313:


[~amashenkov], done.

[~yzhdanov], can you make a final review for this ticket?

> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.1
>
>
> Currently atomic operations within a transaction succeed without alarming a 
> user that no transaction really occurs. We should add a mode to fail such 
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following 
> error message: {{Transaction spans operations on atomic cache (consider 
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to 
> true)}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4406) .NET: Control DateTime serialization via attribute

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4406 at 5/17/17 1:17 PM:
-

Another way we can enable control over this are 
{{BinaryConfiguration.ForceTimestamp}} and 
{{BinaryTypeConfiguration.ForceTimestamp}} properties. However, it is the 
{{IBinarySerializer}} implementation responsibility to use {{WriteTimestamp}} 
or not.


was (Author: ptupitsyn):
Another way we can enable control over this are 
{{BinaryConfiguration.ForceTimestamp}} and 
{{BinaryTypeConfiguration.ForceTimestamp}} properties.

> .NET: Control DateTime serialization via attribute
> --
>
> Key: IGNITE-4406
> URL: https://issues.apache.org/jira/browse/IGNITE-4406
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> .NET can write DateTime in internal format (preserves DateTime.Kind) and as 
> Timestamp (does not allow non-UTC values).
> By default we use internal format. To use Timestamp user has to mark field 
> with QuerySqlField (non obvious), or override IBinarizable.
> * Provide a dedicated attribute to enforce timestamp mode.
> * Attribute can be applied to a field, property, or a whole type
> * Provide a property on {{BinaryReflectiveSerializer}} to force Timestamp 
> everywhere - this may be needed when class code can't be modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4406) .NET: Control DateTime serialization via attribute

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4406:
---
Priority: Major  (was: Minor)

> .NET: Control DateTime serialization via attribute
> --
>
> Key: IGNITE-4406
> URL: https://issues.apache.org/jira/browse/IGNITE-4406
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> .NET can write DateTime in internal format (preserves DateTime.Kind) and as 
> Timestamp (does not allow non-UTC values).
> By default we use internal format. To use Timestamp user has to mark field 
> with QuerySqlField (non obvious), or override IBinarizable.
> * Provide a dedicated attribute to enforce timestamp mode.
> * Attribute can be applied to a field, property, or a whole type
> * Provide a property on {{BinaryReflectiveSerializer}} to force Timestamp 
> everywhere - this may be needed when class code can't be modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5203) JDBC driver should support BLOB fields

[Andrey Gura (JIRA)]

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

Andrey Gura reassigned IGNITE-5203:
---

Assignee: Andrey Gura

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5203) JDBC driver should support BLOB fields

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-5203:

Fix Version/s: 2.1

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> JDBD driver doesn't support BLOB fields. Need to implement BLOBs, at least 
> simple byte array based implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5245) MIN function returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-5245:
--
Summary: MIN function returns NULL if a numeric column of class has NULL 
values  (was: MIN returns NULL if a numeric column of class has NULL values)

> MIN function returns NULL if a numeric column of class has NULL values
> --
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> 1. Use class with the numeric field (e.g. {{Short col_Short_1}})
> 2. Put a few entries where that field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5245) MIN returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-5245:
--
Description: 
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where that field is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value

  was:
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where that fields is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value


> MIN returns NULL if a numeric column of class has NULL values
> -
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> 1. Use class with the numeric field (e.g. {{Short col_Short_1}})
> 2. Put a few entries where that field is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-1456) CPP: Implement Cache.Rebalance()

[Wuwei Lin (JIRA)]

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

Wuwei Lin commented on IGNITE-1456:
---

Ready for review.

> CPP: Implement Cache.Rebalance()
> 
>
> Key: IGNITE-1456
> URL: https://issues.apache.org/jira/browse/IGNITE-1456
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Wuwei Lin
>  Labels: cpp
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5245) MIN returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-5245:
--
Description: 
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where that fields is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value

  was:
1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where where that fields is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value


> MIN returns NULL if a numeric column of class has NULL values
> -
>
> Key: IGNITE-5245
> URL: https://issues.apache.org/jira/browse/IGNITE-5245
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> 1. Use class with the numeric field (e.g. {{Short col_Short_1}})
> 2. Put a few entries where that fields is null
> 3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
> 4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5245) MIN returns NULL if a numeric column of class has NULL values

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5245:
-

 Summary: MIN returns NULL if a numeric column of class has NULL 
values
 Key: IGNITE-5245
 URL: https://issues.apache.org/jira/browse/IGNITE-5245
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.0
Reporter: Sergey Kozlov
 Fix For: 2.1


1. Use class with the numeric field (e.g. {{Short col_Short_1}})
2. Put a few entries where where that fields is null
3. Run query {{SELECT MIN(col_Short_1) FROM DefaultTable}}
4. It returns NULL but for same case h2 returns non-null minimal value



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4406) .NET: Control DateTime serialization via attribute

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4406:


Another way we can enable control over this are 
{{BinaryConfiguration.ForceTimestamp}} and 
{{BinaryTypeConfiguration.ForceTimestamp}} properties.

> .NET: Control DateTime serialization via attribute
> --
>
> Key: IGNITE-4406
> URL: https://issues.apache.org/jira/browse/IGNITE-4406
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.1
>
>
> .NET can write DateTime in internal format (preserves DateTime.Kind) and as 
> Timestamp (does not allow non-UTC values).
> By default we use internal format. To use Timestamp user has to mark field 
> with QuerySqlField (non obvious), or override IBinarizable.
> * Provide a dedicated attribute to enforce timestamp mode.
> * Attribute can be applied to a field, property, or a whole type
> * Provide a property on {{BinaryReflectiveSerializer}} to force Timestamp 
> everywhere - this may be needed when class code can't be modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5232) GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, which lead to significant increase of node start time on large clusters with ssl

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-5232:


Assignee: Anton Vinogradov

> GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, 
> which lead to significant increase of node start time on large clusters with 
> ssl
> --
>
> Key: IGNITE-5232
> URL: https://issues.apache.org/jira/browse/IGNITE-5232
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Anton Vinogradov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-5244:
--
Attachment: download.png

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Ilya Borisov
> Attachments: download.png, download.png
>
>
> No direct way to download Ignite Web Agent. Let's add the btn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-5244:
--
Attachment: download.png

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Ilya Borisov
> Attachments: download.png
>
>
> No direct way to download Ignite Web Agent. Let's add the btn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5230) Web Console: SVG icons integration

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-5230:


Assignee: Ilya Borisov  (was: Dmitriy Shabalin)

[~Klaster_1] Looks good. Applied new changes to admin panel.
Pls send to final review [~anovikov] 


> Web Console: SVG icons integration
> --
>
> Key: IGNITE-5230
> URL: https://issues.apache.org/jira/browse/IGNITE-5230
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
>
> We need a common way to use SVG icons that:
> 1. Does not require extra styles.
> 2. Allows for CSS styling of icons, especially icon color.
> 3. Easy to add new icons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5165) Web Console: Buttons redesign

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-5165:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

> Web Console:  Buttons redesign 
> ---
>
> Key: IGNITE-5165
> URL: https://issues.apache.org/jira/browse/IGNITE-5165
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Fix For: 2.1
>
> Attachments: 5165 debug page.diff
>
>
> Create common style to all buttons in project.
> Refactoring current style for buttons in 
> web-console/frontend/public/stylesheets/style.scss
> 1) Button with icon and text
> 2) Button with only icon
> 3) Button with only text
> 4) Button group
> 5) fill and stroke buttons for color Red, Blue, White
> Implement class modificator .btn-ignite to apply this features



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5165) Web Console: Buttons redesign

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin commented on IGNITE-5165:
--

[~Klaster_1] reviewed. looks good
[~anovikov] Pls make finally review

> Web Console:  Buttons redesign 
> ---
>
> Key: IGNITE-5165
> URL: https://issues.apache.org/jira/browse/IGNITE-5165
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
> Attachments: 5165 debug page.diff
>
>
> Create common style to all buttons in project.
> Refactoring current style for buttons in 
> web-console/frontend/public/stylesheets/style.scss
> 1) Button with icon and text
> 2) Button with only icon
> 3) Button with only text
> 4) Button group
> 5) fill and stroke buttons for color Red, Blue, White
> Implement class modificator .btn-ignite to apply this features



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5082) Redesign base template

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-5082:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Vica Abramova (JIRA)]

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

Vica Abramova reassigned IGNITE-5244:
-

Assignee: Ilya Borisov  (was: Vica Abramova)

> Web Console: Add 'Download Web Agent' button
> 
>
> Key: IGNITE-5244
> URL: https://issues.apache.org/jira/browse/IGNITE-5244
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Ilya Borisov
>
> No direct way to download Ignite Web Agent. Let's add the btn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5082) Redesign base template

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin commented on IGNITE-5082:
--

[~Klaster_1] Reviewed. Looks good.
[~anovikov] Pls make finally review.

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5244) Web Console: Add 'Download Web Agent' button

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5244:
-

 Summary: Web Console: Add 'Download Web Agent' button
 Key: IGNITE-5244
 URL: https://issues.apache.org/jira/browse/IGNITE-5244
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Vica Abramova


No direct way to download Ignite Web Agent. Let's add the btn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5186) Support CREATE/DROP SCHEMA commands

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5186:

Fix Version/s: (was: 2.1)
   2.2

> Support CREATE/DROP SCHEMA commands
> ---
>
> Key: IGNITE-5186
> URL: https://issues.apache.org/jira/browse/IGNITE-5186
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5242) Disallow DROP TABLE on statically configured caches

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5242:
---

 Summary: Disallow DROP TABLE on statically configured caches
 Key: IGNITE-5242
 URL: https://issues.apache.org/jira/browse/IGNITE-5242
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


Should we allow {{DROP TABLE}} on statically configured cache, there will be a 
room for weird situations when it is impossible to understand on whether to 
start the cache or not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5243) Disallow CREATE INDEX and DROP INDEX on statically configured caches

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5243:
---

 Summary: Disallow CREATE INDEX and DROP INDEX on statically 
configured caches
 Key: IGNITE-5243
 URL: https://issues.apache.org/jira/browse/IGNITE-5243
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.0
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


Same reasoning as in IGNITE-5242.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5165) Web Console: Buttons redesign

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5165:


Assignee: Dmitriy Shabalin  (was: Ilya Borisov)

[~Dmitriyff] please review. I've fixed an issue was affecting "Start/Stop demo" 
button in IE11, text inside it had incorrect vertical alignment due to how IE11 
handles flex and min-height 
(https://github.com/philipwalton/flexbugs#3-min-height-on-a-flex-container-wont-apply-to-its-flex-items).

> Web Console:  Buttons redesign 
> ---
>
> Key: IGNITE-5165
> URL: https://issues.apache.org/jira/browse/IGNITE-5165
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
> Attachments: 5165 debug page.diff
>
>
> Create common style to all buttons in project.
> Refactoring current style for buttons in 
> web-console/frontend/public/stylesheets/style.scss
> 1) Button with icon and text
> 2) Button with only icon
> 3) Button with only text
> 4) Button group
> 5) fill and stroke buttons for color Red, Blue, White
> Implement class modificator .btn-ignite to apply this features



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5165) Web Console: Buttons redesign

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5165:


Assignee: Ilya Borisov  (was: Alexey Kuznetsov)

> Web Console:  Buttons redesign 
> ---
>
> Key: IGNITE-5165
> URL: https://issues.apache.org/jira/browse/IGNITE-5165
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Fix For: 2.1
>
> Attachments: 5165 debug page.diff
>
>
> Create common style to all buttons in project.
> Refactoring current style for buttons in 
> web-console/frontend/public/stylesheets/style.scss
> 1) Button with icon and text
> 2) Button with only icon
> 3) Button with only text
> 4) Button group
> 5) fill and stroke buttons for color Red, Blue, White
> Implement class modificator .btn-ignite to apply this features



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5208) C++ Segfault on Put

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5208:
-

Merged to master.

> C++ Segfault on Put
> ---
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
>  Labels: c++
> Fix For: 2.1
>
>
> The following segfault happens when:
>   - using multiple caches (suffixed with number as in X_\{number\}),
>   - caches contain same type of object but not the same objects,
>   - doing multithreaded `::Put` operation, only one put is done on each cache 
> concurrently, independent caches (X_1, X_2, ...) can be operated on and 
> called `::Put` on concurrently, but that should not be relevant as cache api 
> is thread safe.
> {code:none}
> C  [test+0xf8116a]  std::less::operator()(int const&, int const&) 
> const+0x14
> C  [test+0x1106305]  std::_Rb_tree  >, std::_Select1st  > >, std::less, std::allocator  > > >::_M_lower_bound(std::_Rb_tree_node  > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C  [test+0x1105a9d]  std::_Rb_tree  >, std::_Select1st  > >, std::less, std::allocator  > > >::find(int const&)+0x45
> C  [test+0x1104e7f]  std::map ignite::common::concurrent::SharedPointer,
>  std::less, std::allocator  > > >::find(int const&)+0x23
> C  [test+0x1104031]  
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string  std::char_traits, std::allocator > const&, int)+0x6f
> C  [test+0xe6de2d]  void 
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject  >(std::shared_ptr const&)+0xbb
> C  [test+0xe6cd48]  
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr 
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C  [test+0x1128cf1]  
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
>  ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C  [test+0x1128f67]  ignite::impl::interop::InteropTarget::OutOp(int, 
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C  [test+0x1125f41]  
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&, 
> ignite::IgniteError&)+0x2d
> C  [test+0xe5539a]  ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr 
> >::Put(std::__cxx11::basic_string std::allocator > const&, std::shared_ptr const&, 
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at 
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4  0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler 
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at 
> src/impl/binary/binary_type_manager.cpp:56
> 56  std::map::iterator it = 
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl 
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5208) C++ Segfault on Put

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5208:


Github user isapego closed the pull request at:

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


> C++ Segfault on Put
> ---
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
>  Labels: c++
> Fix For: 2.1
>
>
> The following segfault happens when:
>   - using multiple caches (suffixed with number as in X_\{number\}),
>   - caches contain same type of object but not the same objects,
>   - doing multithreaded `::Put` operation, only one put is done on each cache 
> concurrently, independent caches (X_1, X_2, ...) can be operated on and 
> called `::Put` on concurrently, but that should not be relevant as cache api 
> is thread safe.
> {code:none}
> C  [test+0xf8116a]  std::less::operator()(int const&, int const&) 
> const+0x14
> C  [test+0x1106305]  std::_Rb_tree  >, std::_Select1st  > >, std::less, std::allocator  > > >::_M_lower_bound(std::_Rb_tree_node  > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C  [test+0x1105a9d]  std::_Rb_tree  >, std::_Select1st  > >, std::less, std::allocator  > > >::find(int const&)+0x45
> C  [test+0x1104e7f]  std::map ignite::common::concurrent::SharedPointer,
>  std::less, std::allocator  > > >::find(int const&)+0x23
> C  [test+0x1104031]  
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string  std::char_traits, std::allocator > const&, int)+0x6f
> C  [test+0xe6de2d]  void 
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject  >(std::shared_ptr const&)+0xbb
> C  [test+0xe6cd48]  
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr 
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C  [test+0x1128cf1]  
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
>  ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C  [test+0x1128f67]  ignite::impl::interop::InteropTarget::OutOp(int, 
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C  [test+0x1125f41]  
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&, 
> ignite::IgniteError&)+0x2d
> C  [test+0xe5539a]  ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr 
> >::Put(std::__cxx11::basic_string std::allocator > const&, std::shared_ptr const&, 
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at 
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4  0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler 
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at 
> src/impl/binary/binary_type_manager.cpp:56
> 56  std::map::iterator it = 
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl 
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5163 at 5/17/17 9:28 AM:
---

[~vozerov],
1-5)  fixed;
6) IGNITE-5234;
7)  IGNITE-5233;
8-10) fixed;
11)  IGNITE-5235;
12)  IGNITE-5236;
13)  IGNITE-5237
14-15) fixed.




was (Author: tledkov-gridgain):
1-5)  fixed;
6) IGNITE-5234;
7)  IGNITE-5233;
8-10) fixed;
11)  IGNITE-5235;
12)  IGNITE-5236;
13)  IGNITE-5237
14-15) fixed.



> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4597) CPP: Add mechanism to reset arguments for sql queries.

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-4597 at 5/17/17 9:24 AM:
--

[~vinx13], Sorry I was not reacting for so long - you probably should have 
added comment to your ticket or write to dev list, so we would know that ticket 
is ready for review. We do not have notification when just status of the ticket 
changes. I'm going to run tests now and merge it to master.

Thanks for your contribution!


was (Author: isapego):
[~vinx13], Sorry I have not reacted for so long - you probably should have 
added comment to your ticket or write to dev list, so we would know that ticket 
is ready for review. We do not have notification when just status of the ticket 
changes. I'm going to run tests now and merge it to master.

Thanks for your contribution!

> CPP: Add mechanism to reset arguments for sql queries.
> --
>
> Key: IGNITE-4597
> URL: https://issues.apache.org/jira/browse/IGNITE-4597
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Wuwei Lin
>  Labels: cpp, newbie
> Fix For: 2.1
>
>
> Currently, there is method {{AddArgument}} for {{SqlQuery}} and 
> {{SqlFieldsQuery}}, but there is no way to reset arguments for query once 
> they are set. This leads to inconvenience when user want to call the same 
> query with different arguments as they need to re-create exactly the same 
> query but set different arguments for it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4597) CPP: Add mechanism to reset arguments for sql queries.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4597:

Fix Version/s: 2.1

> CPP: Add mechanism to reset arguments for sql queries.
> --
>
> Key: IGNITE-4597
> URL: https://issues.apache.org/jira/browse/IGNITE-4597
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Wuwei Lin
>  Labels: cpp, newbie
> Fix For: 2.1
>
>
> Currently, there is method {{AddArgument}} for {{SqlQuery}} and 
> {{SqlFieldsQuery}}, but there is no way to reset arguments for query once 
> they are set. This leads to inconvenience when user want to call the same 
> query with different arguments as they need to re-create exactly the same 
> query but set different arguments for it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4597) CPP: Add mechanism to reset arguments for sql queries.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-4597:
-

[~vinx13], Sorry I have not reacted for so long - you probably should have 
added comment to your ticket or write to dev list, so we would know that ticket 
is ready for review. We do not have notification when just status of the ticket 
changes. I'm going to run tests now and merge it to master.

Thanks for your contribution!

> CPP: Add mechanism to reset arguments for sql queries.
> --
>
> Key: IGNITE-4597
> URL: https://issues.apache.org/jira/browse/IGNITE-4597
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Wuwei Lin
>  Labels: cpp, newbie
>
> Currently, there is method {{AddArgument}} for {{SqlQuery}} and 
> {{SqlFieldsQuery}}, but there is no way to reset arguments for query once 
> they are set. This leads to inconvenience when user want to call the same 
> query with different arguments as they need to re-create exactly the same 
> query but set different arguments for it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5082) Redesign base template

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5082:


Assignee: Dmitriy Shabalin  (was: Ilya Borisov)

[~Dmitriyff] Please review. I've fixed layout issues in IE11, it was completely 
broken before.

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5082) Redesign base template

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-5082:


Assignee: Ilya Borisov  (was: Alexey Kuznetsov)

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5163) JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5163:
--

1-5)  fixed;
6) IGNITE-5234;
7)  IGNITE-5233;
8-10) fixed;
11)  IGNITE-5235;
12)  IGNITE-5236;
13)  IGNITE-5237
14-15) fixed.



> JDBC Driver: implement handshake for thin jdbc driver based on common 
> odbc/jdbc protocol
> 
>
> Key: IGNITE-5163
> URL: https://issues.apache.org/jira/browse/IGNITE-5163
> Project: Ignite
>  Issue Type: Task
>  Components: odbc, sql
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The GridClient must be removed from thin jdbc driver.
> It is the first step to unify JDBC & ODBC protocols.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5231) Web Console: Add support for Ignite 2.0 cluster on Queries screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-5231:
---

Tested. Queries work for Ignite node with version 2.0.

> Web Console: Add support for Ignite 2.0 cluster on Queries screen
> -
>
> Key: IGNITE-5231
> URL: https://issues.apache.org/jira/browse/IGNITE-5231
> Project: Ignite
>  Issue Type: Bug
>  Components: UI, wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5240) Web console: Invalid docker repository name in compose file

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5240:
-

Assignee: Andrey Novikov  (was: Vasiliy Sisko)

> Web console: Invalid docker repository name in compose file
> ---
>
> Key: IGNITE-5240
> URL: https://issues.apache.org/jira/browse/IGNITE-5240
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Andrey Novikov
>
> in docker/compose/docker-compose.yml
> Optimize test dependencies end exclude them in build process.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5240) Web console: Invalid docker repository name in compose file

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-5240:
---

Fixed docker image build scripts. 
Andrey. Please exclude test dependencies from build process.

> Web console: Invalid docker repository name in compose file
> ---
>
> Key: IGNITE-5240
> URL: https://issues.apache.org/jira/browse/IGNITE-5240
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> in docker/compose/docker-compose.yml
> Optimize test dependencies end exclude them in build process.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4960) Apache Ignite 2.0 Documentation

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-4960.
---

> Apache Ignite 2.0 Documentation
> ---
>
> Key: IGNITE-4960
> URL: https://issues.apache.org/jira/browse/IGNITE-4960
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 2.0
>
>
> This is an umbrella ticket for all the documentation that has to be prepared 
> or updated as a part of Apache Ignite 2.0 release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-4960) Apache Ignite 2.0 Documentation

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4960.
-
Resolution: Fixed
  Assignee: (was: Denis Magda)

> Apache Ignite 2.0 Documentation
> ---
>
> Key: IGNITE-4960
> URL: https://issues.apache.org/jira/browse/IGNITE-4960
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 2.0
>
>
> This is an umbrella ticket for all the documentation that has to be prepared 
> or updated as a part of Apache Ignite 2.0 release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4960) Apache Ignite 2.0 Documentation

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4960:
-

Closing as all subtasks are done.

> Apache Ignite 2.0 Documentation
> ---
>
> Key: IGNITE-4960
> URL: https://issues.apache.org/jira/browse/IGNITE-4960
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 2.0
>
>
> This is an umbrella ticket for all the documentation that has to be prepared 
> or updated as a part of Apache Ignite 2.0 release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4361) Documentation: working with Ignite through JCache API

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4361:

Fix Version/s: (was: 2.0)
   2.1

> Documentation: working with Ignite through JCache API
> -
>
> Key: IGNITE-4361
> URL: https://issues.apache.org/jira/browse/IGNITE-4361
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> Regardless of the fact that Ignite supports JCache API there is no any 
> documentation with code snippets that will elaborate on how to work with 
> Ignite purely with JCache API.
> This documentation [1] must contain a section showing all the ways how a 
> JCache Ignite provider can be created and used after that.
> [1] https://apacheignite.readme.io/docs/jcache



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-2511) Missing docs on readme.io for Zookeeper-based cluster discovery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2511:

Fix Version/s: (was: 2.0)
   2.1

> Missing docs on readme.io for Zookeeper-based cluster discovery
> ---
>
> Key: IGNITE-2511
> URL: https://issues.apache.org/jira/browse/IGNITE-2511
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, zookeeper
>Reporter: Roman Shtykh
>  Labels: documentation
> Fix For: 2.1
>
>
> Nothing is said on how to use ZookeeperIpFinder on 
> https://apacheignite.readme.io/docs/cluster-config



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-2421) EventTypes are badly documented

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2421:

Fix Version/s: (was: 2.0)
   2.1

> EventTypes are badly documented
> ---
>
> Key: IGNITE-2421
> URL: https://issues.apache.org/jira/browse/IGNITE-2421
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> We have to go through all the {{EventTypes}} and document them well:
> - in which conditions they are fired;
> - what kind of nodes (primary, backups or both) will receive and update;
> - etc.
> As an example.
> From {{EVT_CACHE_ENTRY_CREATED}} is not clear when it's fired at all. However 
> it's fired when an entry is loaded from a storage, or when it's initially 
> created due to a cache put.
> The same situation is around {{EVT_CACHE_OBJECT_PUT}}. There is no info 
> saying that it's fired on both primary and backup nodes. That it's not fired 
> due to a loading from a cache, etc.
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4707) Add documentation for HA IGFS client

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4707:

Fix Version/s: (was: 2.0)
   2.1

> Add documentation for HA IGFS client
> 
>
> Key: IGNITE-4707
> URL: https://issues.apache.org/jira/browse/IGNITE-4707
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, igfs
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.1
>
>
> We need to document HA feature added in IGNITE-2356.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4707) Add documentation for HA IGFS client

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4707:
---

Assignee: (was: Vladimir Ozerov)

> Add documentation for HA IGFS client
> 
>
> Key: IGNITE-4707
> URL: https://issues.apache.org/jira/browse/IGNITE-4707
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, igfs
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.1
>
>
> We need to document HA feature added in IGNITE-2356.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-2731) Cache and cluster metrics documentation on readme.io

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2731:

Fix Version/s: (was: 2.0)
   2.1

> Cache and cluster metrics documentation on readme.io
> 
>
> Key: IGNITE-2731
> URL: https://issues.apache.org/jira/browse/IGNITE-2731
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Sergej Sidorov
> Fix For: 2.1
>
>
> Cache and cluster metrics related topic is becoming hot on the user list.
> 1) 
> http://apache-ignite-users.70518.x6.nabble.com/Monitoring-Cache-Data-counters-Cache-Data-Size-td3203.html#a3211
> 2) 
> http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html
> 3) 
> http://apache-ignite-users.70518.x6.nabble.com/Metrics-for-backup-caches-td2689.html#a2692
> The time to add the documentation to the readme.io has come.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-4205:
-

That's not true. JDBC store does work with binary objects, at least when there 
are no classes on server nodes.

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Konstantin Dudkov
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-2737) Ignite-Spark documentation is missing some useful informations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2737:

Fix Version/s: (was: 2.0)
   2.1

> Ignite-Spark documentation is missing some useful informations
> --
>
> Key: IGNITE-2737
> URL: https://issues.apache.org/jira/browse/IGNITE-2737
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Luca Rea
>  Labels: community
> Fix For: 2.1
>
>
> Hi,
> in my tests I have experienced some configuration issue running spark in 
> local and yarn-client mode, so I want to share them.
> In order to let Ignite work correctly I had to customize spark-defaults.conf 
> adding to "spark.driver.extraClassPath" and "spark.executor.extraClassPath" 
> the string
> {code}
> "/opt/ignite/libs/*:/opt/ignite/libs/optional/ignite-spark/*:/opt/ignite/libs/optional/ignite-log4j/*:/opt/ignite/libs/optional/ignite-yarn/*:/opt/ignite/libs/ignite-spring/*"
> {code}
> (opt/ignite is my IGNITE_HOME) and other IGNITE_ useful variables like 
> "spark.executorEnv.IGNITE_WORK_DIR" in order to let them be loaded by 
> executors.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4707) Add documentation for HA IGFS client

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4707:

Fix Version/s: (was: 2.0)
   2.1

> Add documentation for HA IGFS client
> 
>
> Key: IGNITE-4707
> URL: https://issues.apache.org/jira/browse/IGNITE-4707
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, igfs
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> We need to document HA feature added in IGNITE-2356.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4707) Add documentation for HA IGFS client

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4707:

Fix Version/s: (was: 2.1)
   2.0

> Add documentation for HA IGFS client
> 
>
> Key: IGNITE-4707
> URL: https://issues.apache.org/jira/browse/IGNITE-4707
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, igfs
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> We need to document HA feature added in IGNITE-2356.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4205:
---

In CacheAbstractJdbcStore it was the thread naming question only - because the 
only child class - CacheJdbcPojoStore - doesn't use binary marshaller. So I can 
test only the fact that new threads are instances of IgniteThread, that is 
obvious.

> CassandraCacheStore should start IgniteThread threads in loadCache() method
> ---
>
> Key: IGNITE-4205
> URL: https://issues.apache.org/jira/browse/IGNITE-4205
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Konstantin Dudkov
>
> {{CassandraCacheStore.loadCache()}} method starts a generic thread pool for 
> parallel data load. Threads in this thread pool can't deserialize Ignite 
> internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior. 
> Here is one of the scenarios:
> * There is column in Cassandra which stores an object as BLOB using 
> {{JavaSerializer}}.
> * {{CacheConfiguration.storeKeepBinary}} is {{true}}.
> * When an object is saved, it's passed to the store as an instance of 
> {{BinaryObject}} which is converted to a byte array and saved in Cassandra.
> * When the same object is loaded in {{loadCache}}, the store takes the byte 
> array and tries to convert it to {{BinaryObject}}. But it can't because this 
> implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
> To fix this we need to provide a thread factory that will create instances of 
> {{IgniteThread}} and use it in the pool that loads the data.
> Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
> And in general, any threads created by Ignite internals should be 
> {{IgniteThread}}-s. This should be revisited.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5082) Redesign base template

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-5082.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-2190) ScanQuery without a filter triggers object's deserialization on the server side

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-2190:
-

Hi.

I investigate this issue.
Here is result;

# Attached ScanQueryBug runs OK on 2.0.0 release. So bug seems not reproducible
# I wrote test to make sure bug is not reproducible - 
https://github.com/nizhikov/ignite/pull/2
# Test succeed with OptimizedMarshaller
# Test fails with BinaryMarshaller.

Should I fix BinaryMarshaller is this issue or open another?

Here is stack trace:

{noformat}
[09:05:43,846][ERROR][main][root] Test failed.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Query execution failed: GridCacheQueryBean [qry=GridCacheQueryAdapter 
[type=SCAN, clsName=null, clause=null, filter=null, transform=null, part=null, 
incMeta=false, metrics=GridCacheQueryMetricsAdapter 
[minTime=9223372036854775807, maxTime=0, sumTime=0, avgTime=0.0, execs=0, 
completed=0, fails=0], pageSize=1024, timeout=0, keepAll=true, 
incBackups=false, dedup=false, prj=null, keepBinary=false, 
subjId=22821e9d-92df-43ce-8b85-3fed3c53f8b9, taskHash=0], rdc=null, trans=null]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1421)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$5.onHasNext(GridCacheDistributedQueryManager.java:635)
at 
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1$1.onHasNext(IgniteCacheProxy.java:571)
at 
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:113)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheEmptyScanQueryTest.runEmptyScanQuery(GridCacheEmptyScanQueryTest.java:68)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheEmptyScanQueryTest.testEmptyScanQueryWithBinaryMarshaller(GridCacheEmptyScanQueryTest.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1935)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:125)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1850)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
clause=null, filter=null, transform=null, part=null, incMeta=false, 
metrics=GridCacheQueryMetricsAdapter [minTime=9223372036854775807, maxTime=0, 
sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], pageSize=1024, 
timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null, 
keepBinary=false, subjId=22821e9d-92df-43ce-8b85-3fed3c53f8b9, taskHash=0], 
rdc=null, trans=null]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:257)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:315)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:161)
... 17 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
clsName=null, clause=null, filter=null, transform=null, part=null, 
incMeta=false, metrics=GridCacheQueryMetricsAdapter 
[minTime=9223372036854775807, maxTime=0, sumTime=0, avgTime=0.0, execs=0, 
completed=0, fails=0], pageSize=1024, timeout=0, keepAll=true, 
incBackups=false, dedup=false, prj=null, keepBinary=false, 
subjId=22821e9d-92df-43ce-8b85-3fed3c53f8b9, taskHash=0], rdc=null, 
trans=null], nodeId=96a2b467-00fc-4fb0-befc-6caa54dbc9d2]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:380)

[jira] [Commented] (IGNITE-5100) Exchange queue is not used properly

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny commented on IGNITE-5100:


tests looks like correct: 
http://ci.ignite.apache.org/viewQueued.html?itemId=611081

failed :
TcpDiscoverySslSelfTest.testFailBeforeNodeAddedSent 
IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery - looks 
like flapped, work properly well on my local.

RandomLruNearEnabledPageEvictionMultinodeTest.testPageEviction
and 
IgniteCacheJoinPartitionedAndReplicatedTest.testReplicatedToPartitionedLeftJoin

probably not mine, due to fail in parent branch too.

> Exchange queue is not used properly
> ---
>
> Key: IGNITE-5100
> URL: https://issues.apache.org/jira/browse/IGNITE-5100
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Fix For: 2.1
>
>
> Currently exchange futures share same queue for pending(incomplete) and 
> completed exchanges.
> The queue has fixed hardcoded size of 1000.
> This leads to a problem when > 1000 nodes try to enter grid.
> In such case oldest exchanges will be removed by ExchangeFutureSet size 
> limit, leading to whole exchange hanging.
> Solution: 
> 1. Use separate queues for pending and completed exchanges.
> 2. Pending exchange queue must be unbounded.
> 3. Add system property to control exchange history.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5100) Exchange queue is not used properly

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny reassigned IGNITE-5100:
--

Assignee: Semen Boikov  (was: Stanilovsky Evgeny)

> Exchange queue is not used properly
> ---
>
> Key: IGNITE-5100
> URL: https://issues.apache.org/jira/browse/IGNITE-5100
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.1
>
>
> Currently exchange futures share same queue for pending(incomplete) and 
> completed exchanges.
> The queue has fixed hardcoded size of 1000.
> This leads to a problem when > 1000 nodes try to enter grid.
> In such case oldest exchanges will be removed by ExchangeFutureSet size 
> limit, leading to whole exchange hanging.
> Solution: 
> 1. Use separate queues for pending and completed exchanges.
> 2. Pending exchange queue must be unbounded.
> 3. Add system property to control exchange history.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)