[jira] [Commented] (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:comment-tabpanel=16028634#comment-16028634
 ] 

Andrey Gura commented on IGNITE-5203:
-

Merged.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>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] [Commented] (IGNITE-5030) Support Spring @Cacheable(sync=true) annotation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5030:


GitHub user mcherkasov opened a pull request:

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

IGNITE-5030 Support Spring @Cacheable(sync=true) annotation



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

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

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

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


commit 37ae9bf51aa68a17a41199df6c41897fda1c7cd3
Author: mcherkasov 
Date:   2017-05-29T17:29:28Z

Added support for sync option in @Cacheable annotation




> Support Spring @Cacheable(sync=true) annotation
> ---
>
> Key: IGNITE-5030
> URL: https://issues.apache.org/jira/browse/IGNITE-5030
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Mikhail Cherkasov
>
> @Cacheable(sync=true) guarantee that only one thread (across the cluster) 
> will fetch value for a key on get, even in case of some simultaneous gets.
> So, 
> org.apache.ignite.cache.spring.SpringCache#get(java.lang.Object, 
> java.util.concurrent.Callable) 
> should be implemented to provide such guarantee.



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

[jira] [Assigned] (IGNITE-5301) JVM crashes on H2TreeIndex destroy

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-5301:
-

Assignee: Alexey Goncharuk  (was: Eduard Shangareev)

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

Please, take a look!

> JVM crashes on H2TreeIndex destroy
> --
>
> Key: IGNITE-5301
> URL: https://issues.apache.org/jira/browse/IGNITE-5301
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Igor Seliverstov
>Assignee: Alexey Goncharuk
> Attachments: hs_err_pid9664.log
>
>
> There is a bug in destroy method because of which 
> {noformat}cctx.offheap().dropRootPageForIndex(idxName){noformat} method 
> actually does nothing. It happens because idx names on create RootPage and 
> destroy it are different (unlike creation a root page, a segment suffix isn't 
> added to tree name on destroy, so that it can't delete the page from 
> metastore by different key).
> After fixing this behavior I faced JVM crash. 
> I'm quite not familiar with the code, but I suppose something is wrong in 
> MetaStoreInnerIO logic.
> Crash report is attached.
> How to reproduce:
> just create and destroy a cache with indexed types and enabled PDS feature 
> after the fix I provided above is applied.



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

[jira] [Commented] (IGNITE-5301) JVM crashes on H2TreeIndex destroy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5301:


GitHub user EdShangGG opened a pull request:

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

IGNITE-5301 JVM crashes on H2TreeIndex destroy



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

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

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

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


commit ef01e7558bec7f5e12d8f75694bb40e8f84998cf
Author: EdShangGG 
Date:   2017-05-29T19:49:41Z

IGNITE-5301 JVM crashes on H2TreeIndex destroy




> JVM crashes on H2TreeIndex destroy
> --
>
> Key: IGNITE-5301
> URL: https://issues.apache.org/jira/browse/IGNITE-5301
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Igor Seliverstov
>Assignee: Eduard Shangareev
> Attachments: hs_err_pid9664.log
>
>
> There is a bug in destroy method because of which 
> {noformat}cctx.offheap().dropRootPageForIndex(idxName){noformat} method 
> actually does nothing. It happens because idx names on create RootPage and 
> destroy it are different (unlike creation a root page, a segment suffix isn't 
> added to tree name on destroy, so that it can't delete the page from 
> metastore by different key).
> After fixing this behavior I faced JVM crash. 
> I'm quite not familiar with the code, but I suppose something is wrong in 
> MetaStoreInnerIO logic.
> Crash report is attached.
> How to reproduce:
> just create and destroy a cache with indexed types and enabled PDS feature 
> after the fix I provided above is applied.



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5097:


Ok, I'll rollback incompatible changes shortly.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Updated] (IGNITE-5170) .NET: Compute peer deployment example

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5170:
---
Description: 
* Add example for IGNITE-2492.
* Enable peer loading in LINQPad compute example so it works with a standalone 
node (update docs there), explain how to run Apache.Ignite.exe from NuGet

  was:
* Add example for IGNITE-2492.
* Enable peer loading in LINQPad compute example so it works with a standalone 
node (update docs there)


> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there), explain how to run Apache.Ignite.exe 
> from NuGet



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

[jira] [Commented] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5333:


* {{Apache.Ignite.exe}} and {{Apache.Ignite.exe.config}} files added to package
* NuGet test added to make sure it runs and resolves home dir properly

Waiting for TC: http://ci.ignite.apache.org/viewQueued.html?itemId=635894

> .NET: Include Apache.Ignite.exe in the main NuGet package
> -
>
> Key: IGNITE-5333
> URL: https://issues.apache.org/jira/browse/IGNITE-5333
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, NuGet
> Fix For: 2.1
>
>
> Include {{Apache.Ignite.exe}} in the NuGet package.
> This will allow nuget-based standalone node deployment via simple command: 
> {{nuget install Apache.Ignite}}.
> After all, everything else is available via NuGet, except this exe file.



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

[jira] [Commented] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5333:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5333 .NET: Include Apache.Ignite.exe in the main NuGet package



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

$ git pull https://github.com/ptupitsyn/ignite ignite-5333

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

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


commit 85c95d0a6d531b6e122ab8913ebc93880d674ac5
Author: Pavel Tupitsyn 
Date:   2017-05-29T15:48:30Z

IGNITE-5333 .NET: Include Apache.Ignite.exe in the main NuGet package

commit 7901752b5b827272acac0d04281ea598b8b76f27
Author: Pavel Tupitsyn 
Date:   2017-05-29T15:52:03Z

Update app.config to use default section

commit 84b14050010e7c44a014a3813374f3ab7a4f523d
Author: Pavel Tupitsyn 
Date:   2017-05-29T16:04:04Z

Fix NuGet home detection

commit faa89bd94f78cc6a2dd29c59e03401f9c192c8b6
Author: Pavel Tupitsyn 
Date:   2017-05-29T16:06:29Z

wip

commit ff687b8eca2aa623e343f496344e12960bb629ec
Author: Pavel Tupitsyn 
Date:   2017-05-29T16:43:15Z

Add ApacheIgniteExe test to NuGet tests




> .NET: Include Apache.Ignite.exe in the main NuGet package
> -
>
> Key: IGNITE-5333
> URL: https://issues.apache.org/jira/browse/IGNITE-5333
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, NuGet
> Fix For: 2.1
>
>
> Include {{Apache.Ignite.exe}} in the NuGet package.
> This will allow nuget-based standalone node deployment via simple command: 
> {{nuget install Apache.Ignite}}.
> After all, everything else is available via NuGet, except this exe file.



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

[jira] [Updated] (IGNITE-5335) Wrong value read by SQL query for field containing negative decimal

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov updated IGNITE-5335:
---
Attachment: BinaryObjectFieldDecimalTest.java

> Wrong value read by SQL query for field containing negative decimal
> ---
>
> Key: IGNITE-5335
> URL: https://issues.apache.org/jira/browse/IGNITE-5335
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, sql
>Affects Versions: 2.0
>Reporter: Sergey Kalashnikov
> Attachments: BinaryObjectFieldDecimalTest.java
>
>
> Steps to reproduce:
> 1) Create a cache with value type having some decimal field.
> 2) Instantiate a value, intialize decimal field with a negative value and put 
> it to the cache.
> 3) Perform an sql query on the decimal field.
> 4) Check the selected value.



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

[jira] [Commented] (IGNITE-5335) Wrong value read by SQL query for field containing negative decimal

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-5335:


Attached the reproducer

> Wrong value read by SQL query for field containing negative decimal
> ---
>
> Key: IGNITE-5335
> URL: https://issues.apache.org/jira/browse/IGNITE-5335
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, sql
>Affects Versions: 2.0
>Reporter: Sergey Kalashnikov
> Attachments: BinaryObjectFieldDecimalTest.java
>
>
> Steps to reproduce:
> 1) Create a cache with value type having some decimal field.
> 2) Instantiate a value, intialize decimal field with a negative value and put 
> it to the cache.
> 3) Perform an sql query on the decimal field.
> 4) Check the selected value.



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

[jira] [Created] (IGNITE-5335) Wrong value read by SQL query for field containing negative decimal

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-5335:
--

 Summary: Wrong value read by SQL query for field containing 
negative decimal
 Key: IGNITE-5335
 URL: https://issues.apache.org/jira/browse/IGNITE-5335
 Project: Ignite
  Issue Type: Bug
  Components: binary, sql
Affects Versions: 2.0
Reporter: Sergey Kalashnikov


Steps to reproduce:
1) Create a cache with value type having some decimal field.
2) Instantiate a value, intialize decimal field with a negative value and put 
it to the cache.
3) Perform an sql query on the decimal field.
4) Check the selected value.




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

[jira] [Updated] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5333:
---
Description: 
Include {{Apache.Ignite.exe}} in the NuGet package.
This will allow nuget-based standalone node deployment via simple command: 
{{nuget install Apache.Ignite}}.

After all, everything else is available via NuGet, except this exe file.

  was:
Include {{Apache.Ignite.exe}} in the NuGet package. This will allow nuget-based 
standalone node deployment via simple command: {{nuget install Apache.Ignite}}.

After all, everything else is available via NuGet, except this exe file.


> .NET: Include Apache.Ignite.exe in the main NuGet package
> -
>
> Key: IGNITE-5333
> URL: https://issues.apache.org/jira/browse/IGNITE-5333
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, NuGet
> Fix For: 2.1
>
>
> Include {{Apache.Ignite.exe}} in the NuGet package.
> This will allow nuget-based standalone node deployment via simple command: 
> {{nuget install Apache.Ignite}}.
> After all, everything else is available via NuGet, except this exe file.



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

[jira] [Updated] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5333:
---
Description: 
Include {{Apache.Ignite.exe}} in the NuGet package. This will allow nuget-based 
standalone node deployment via simple command: {{nuget install Apache.Ignite}}.

After all, everything else is available via NuGet, except this exe file.

  was:Include {{Apache.Ignite.exe}} in the NuGet package. This will allow 
nuget-based standalone node deployment. After all, everything else is available 
via NuGet, except this exe file.


> .NET: Include Apache.Ignite.exe in the main NuGet package
> -
>
> Key: IGNITE-5333
> URL: https://issues.apache.org/jira/browse/IGNITE-5333
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, NuGet
> Fix For: 2.1
>
>
> Include {{Apache.Ignite.exe}} in the NuGet package. This will allow 
> nuget-based standalone node deployment via simple command: {{nuget install 
> Apache.Ignite}}.
> After all, everything else is available via NuGet, except this exe file.



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

[jira] [Commented] (IGNITE-4188) Savepoints support inside of Ignite Transactions

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4188:
--

[~SomeFire]
Please fix found on review 
(http://reviews.ignite.apache.org/ignite/review/IGNT-CR-186)

> Savepoints support inside of Ignite Transactions
> 
>
> Key: IGNITE-4188
> URL: https://issues.apache.org/jira/browse/IGNITE-4188
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Ryabov Dmitrii
> Fix For: 2.1
>
>
> A savepoint is a special mark inside a transaction that allows all commands 
> that are executed after it was established to be rolled back, restoring the 
> transaction state to what it was at the time of the savepoint.
> Here is a reference to the similar functionality implemented by some of RDBMs 
> vendors.
> https://www.postgresql.org/docs/8.1/static/sql-savepoint.html
> https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_10001.htm
> http://dev.mysql.com/doc/refman/5.7/en/savepoint.html
> Consider the following example.
> {code}
> BEGIN;
> INSERT INTO table1 VALUES (1); 
> SAVEPOINT my_savepoint; 
> INSERT INTO table1 VALUES (2); 
> ROLLBACK TO SAVEPOINT my_savepoint; 
> INSERT INTO table1 VALUES (3); 
> COMMIT;
> {code}
> The execution result must guarantee that only values 1 and 3 are inserted 
> into table1.
> In Ignite, it should be supported this way (preserving the same behavior as 
> above).
> {code}
> Ignite ignite = ;
> IgniteCache c = ;
> try (Transaction tx = ignite.transactions().txStart()) {
> c.put(1, 1);
> 
> tx.savepoint("mysavepoint");
> 
> c.put(2, 2);
> 
> tx.rollbackToSavepoint("mysavepoint");
> 
> c.put(3, 3);
> 
> tx.commit();
> }
> {code}
> As a summary the following has to be supported on Ignite side:
> - The {{savepoint}} method which will set a named transaction savepoint with 
> a name of an identifier.
> - Multiple savepoints defined within a transaction. The names of the 
> savepoints have to differ from each other. If the current transaction has a 
> savepoint with the same name, the old savepoint is deleted and a new one is 
> set.
> - The {{rollbackToSavepoint}} method that will roll back all the changes done 
> after a specific checkpoint establishment.
> - The {{releaseCheckpoint}} method that will destroy a savepoint, keeping the 
> effects of commands executed after it was established.
> - Full support of the behavior listed above at the level of ODBC and JDBC 
> drivers and DML (will be handled under separate tickets).
> - The behavior has to be support for all transactional modes.
> Original proposal on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/TX-savepoints-td12041.html



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

[jira] [Commented] (IGNITE-5334) Return old schema escape behavior

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5334:


GitHub user devozerov opened a pull request:

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

IGNITE-5334



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

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

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

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


commit 71c7b7846ed2b531fc5a6bc2ac45fccde35774e2
Author: devozerov 
Date:   2017-05-29T15:40:50Z

IGNITE-5334




> Return old schema escape behavior
> -
>
> Key: IGNITE-5334
> URL: https://issues.apache.org/jira/browse/IGNITE-5334
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Make sure that schema escape semantics matches what is described in JavaDocs 
> to {{CacheConfiguration.sqlSchema}}.



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5097:
-

Well, OK, it's all ready for C++ already then. Waiting for Java part.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Created] (IGNITE-5334) Return old schema escape behavior

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5334:
---

 Summary: Return old schema escape behavior
 Key: IGNITE-5334
 URL: https://issues.apache.org/jira/browse/IGNITE-5334
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.1


Make sure that schema escape semantics matches what is described in JavaDocs to 
{{CacheConfiguration.sqlSchema}}.



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

[jira] [Updated] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5333:
---
Description: Include {{Apache.Ignite.exe}} in the NuGet package. This will 
allow nuget-based standalone node deployment. After all, everything else is 
available via NuGet, except this exe file.  (was: Include {{Apache.Ignite.exe}} 
in the NuGet package. This will allow nuget-based standalone node deployment. 
After all, everything else is available via NuGet, except this exe file.

Or should we produce a separate package?)

> .NET: Include Apache.Ignite.exe in the main NuGet package
> -
>
> Key: IGNITE-5333
> URL: https://issues.apache.org/jira/browse/IGNITE-5333
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, NuGet
> Fix For: 2.1
>
>
> Include {{Apache.Ignite.exe}} in the NuGet package. This will allow 
> nuget-based standalone node deployment. After all, everything else is 
> available via NuGet, except this exe file.



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

[jira] [Created] (IGNITE-5333) .NET: Include Apache.Ignite.exe in the main NuGet package

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5333:
--

 Summary: .NET: Include Apache.Ignite.exe in the main NuGet package
 Key: IGNITE-5333
 URL: https://issues.apache.org/jira/browse/IGNITE-5333
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


Include {{Apache.Ignite.exe}} in the NuGet package. This will allow nuget-based 
standalone node deployment. After all, everything else is available via NuGet, 
except this exe file.

Or should we produce a separate package?



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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5176:


Github user tledkov-gridgain closed the pull request at:

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


> JDBC Driver: implement query execution for thin jdbc driver based on common 
> odbc/jdbc protocol
> --
>
> Key: IGNITE-5176
> URL: https://issues.apache.org/jira/browse/IGNITE-5176
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Implementation query execution & fetch results for thin JDBC driver over ODBC 
> protocol.



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5097:
-

[~isapego], yes, it makes sense for strings as well.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Commented] (IGNITE-5278) BLAS implementation

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5278:
--

We have some problems here: the natural approach for this task is to delegate 
BLAS calls to any of existing BLAS libs. All BLAS libraries which I met during 
implementing this task (jBlas, netlib-java) require storing internal data for 
matrices flattened (i.e [row1, row2...rown] instead of [[row1], [row2], ... 
[rowN]]), therefore it seems that we have two options here:

1. Redesign storing;
2. keep storing, but do flatten array -> do blas call -> unflatten underlying 
arrays. 

If we take second approach, we do not get any boost (rather, we'll get 
slowdowns) in BLAS levels 1 and 2 for array based matrix impls. We still can 
get boost in BLAS level 3 calls. 

For first approach to be taken, separate research task need to be done.

> BLAS implementation
> ---
>
> Key: IGNITE-5278
> URL: https://issues.apache.org/jira/browse/IGNITE-5278
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Artem Malykh
> Fix For: 2.1
>
>
> We need BLAS implementation for local computations.



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

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

[Vadim Opolski (JIRA)]

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

Vadim Opolski reassigned IGNITE-4756:
-

Assignee: Vadim Opolski

> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.1
>
>
> Print information about affinity assignment to log.
> e.g.: 
> {noformat}
> : primary, [, , 
> ], ...,  [, , 
> ]
> : backup_0, [, , 
> ], ...,  [, , 
> ]
> ...
> : backup_N, [, , 
> ], ...,  [, , 
> ]
> {noformat}



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

[jira] [Updated] (IGNITE-4618) CPP: Do not start JVM if it is already started

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4618:

Labels: cpp  (was: )

> CPP: Do not start JVM if it is already started
> --
>
> Key: IGNITE-4618
> URL: https://issues.apache.org/jira/browse/IGNITE-4618
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: cpp
> Fix For: 2.1
>
>
> *Problem*
> Consider the following scenario:
> 1) User's app started JVM in the process somehow.
> 2) User tries to start the node. 
> 3) Result: exception.
> *Solution*
> We need to check if JVM is already started. If yes - then try re-using. Note 
> that we are likely to fail at this point because user might forgot to pass 
> proper Ignite classpath. In this case we must throw extremely sensible 
> exception, so that user understand how to fix the problem right away. 
> E.g.: "Failed to start Ignite node with already started JVM due to invalid 
> classpath; please add the following JARs to the classpath: [PATH TO 
> IGNITE_HOME JARS]".



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

[jira] [Updated] (IGNITE-5309) CPP: Add "schema" property to SqlQuery and SqlFieldsQuery

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5309:

Labels: cpp  (was: )

> CPP: Add "schema" property to SqlQuery and SqlFieldsQuery
> -
>
> Key: IGNITE-5309
> URL: https://issues.apache.org/jira/browse/IGNITE-5309
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Propagate new properties from IGNITE-5307.



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

[jira] [Updated] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5161:

Labels: cpp  (was: )

> CPP: Provide basic Ignite Compute Grid Examples
> ---
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several 
> examples to demonstrate basic capabilities.



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

[jira] [Updated] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5161:

Summary: CPP: Provide basic Ignite Compute Grid Examples  (was: Provide 
basic Ignite Compute Grid Examples)

> CPP: Provide basic Ignite Compute Grid Examples
> ---
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several 
> examples to demonstrate basic capabilities.



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

[jira] [Updated] (IGNITE-5161) CPP: Provide basic Ignite Compute Grid Examples

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5161:

Affects Version/s: 2.0

> CPP: Provide basic Ignite Compute Grid Examples
> ---
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several 
> examples to demonstrate basic capabilities.



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

[jira] [Commented] (IGNITE-3355) CPP: Implement Compute::Call() for Ignite C++.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3355:


Github user isapego closed the pull request at:

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


> CPP: Implement Compute::Call() for Ignite C++.
> --
>
> Key: IGNITE-3355
> URL: https://issues.apache.org/jira/browse/IGNITE-3355
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement {{Compute}} class with {{Compute::Call}} method.



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

[jira] [Resolved] (IGNITE-5321) DiscoverySpi#setDataExchange returns concrete implementation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov resolved IGNITE-5321.
-
Resolution: Fixed

Fixed by following commit - 
https://github.com/apache/ignite/commit/0f8af137caa6d2ab5bd00ea33a34d4a969adff2b

> DiscoverySpi#setDataExchange returns concrete implementation
> 
>
> Key: IGNITE-5321
> URL: https://issues.apache.org/jira/browse/IGNITE-5321
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Trivial
> Fix For: 2.1
>
>
> Two method of DiscoverySpi interface returns concrete implementation instead 
> of interface.
> {code:java}
> public interface DiscoverySpi extends IgniteSpi {
> 
> TcpDiscoverySpi setDataExchange(DiscoverySpiDataExchange var1);
> TcpDiscoverySpi setMetricsProvider(DiscoveryMetricsProvider var1);
> ...
> }
> {code}



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

[jira] [Comment Edited] (IGNITE-5321) DiscoverySpi#setDataExchange returns concrete implementation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-5321 at 5/29/17 2:30 PM:
--

Fixed by commit - 
https://github.com/apache/ignite/commit/0f8af137caa6d2ab5bd00ea33a34d4a969adff2b


was (Author: nizhikov):
Fixed by following commit - 
https://github.com/apache/ignite/commit/0f8af137caa6d2ab5bd00ea33a34d4a969adff2b

> DiscoverySpi#setDataExchange returns concrete implementation
> 
>
> Key: IGNITE-5321
> URL: https://issues.apache.org/jira/browse/IGNITE-5321
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Trivial
> Fix For: 2.1
>
>
> Two method of DiscoverySpi interface returns concrete implementation instead 
> of interface.
> {code:java}
> public interface DiscoverySpi extends IgniteSpi {
> 
> TcpDiscoverySpi setDataExchange(DiscoverySpiDataExchange var1);
> TcpDiscoverySpi setMetricsProvider(DiscoveryMetricsProvider var1);
> ...
> }
> {code}



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

[jira] [Updated] (IGNITE-5332) Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's inheritors

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-5332:

Labels: newbie  (was: )

> Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's 
> inheritors
> ---
>
> Key: IGNITE-5332
> URL: https://issues.apache.org/jira/browse/IGNITE-5332
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Dmitry Karachentsev
>  Labels: newbie
> Fix For: 1.9
>
>
> GridNearAtomicAbstractSingleUpdateRequest and all his inheritors should 
> implement toString() method.



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

[jira] [Created] (IGNITE-5332) Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's inheritors

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5332:
---

 Summary: Add toString() to 
GridNearAtomicAbstractSingleUpdateRequest and it's inheritors
 Key: IGNITE-5332
 URL: https://issues.apache.org/jira/browse/IGNITE-5332
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Dmitry Karachentsev
 Fix For: 1.9


GridNearAtomicAbstractSingleUpdateRequest and all his inheritors should 
implement toString() method.



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

[jira] [Updated] (IGNITE-5170) .NET: Compute peer deployment example

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5170:
---
Description: 
* Add example for IGNITE-2492.
* Enable peer loading in LINQPad compute example so it works with a standalone 
node (update docs there)

  was:Add example for IGNITE-2492.


> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * Add example for IGNITE-2492.
> * Enable peer loading in LINQPad compute example so it works with a 
> standalone node (update docs there)



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

[jira] [Commented] (IGNITE-1894) .NET: Delegate support in the API via extension methods

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-1894:


Postponing until IGNITE-5329 is done in 2.2

> .NET: Delegate support in the API via extension methods
> ---
>
> Key: IGNITE-1894
> URL: https://issues.apache.org/jira/browse/IGNITE-1894
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.1
>
>
> In many places we require a single-method interface implementation from the 
> user:
> {code:title=ICompute}
> TRes Call(IComputeFunc clo);
> {code}
> All of these can be extended to accept a delegate:
> {code:title=ICompute}
> TRes Call(Func clo);
> {code}
> We can't replace interfaces with delegates completely (which is desirable), 
> because it will take away serialization control from the user. So the 
> interface approach has to stay as a primary.
> Delegate support can be added via extension methods, which wrap provided 
> delegates into a class that implements corresponding interface.



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

[jira] [Commented] (IGNITE-5170) .NET: Compute peer deployment example

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5170:


Peer deployment only works for Compute. Let's add a dedicated example for now 
and keep all other examples as is.

> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> Add example for IGNITE-2492.



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

[jira] [Updated] (IGNITE-5170) .NET: Compute peer deployment example

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5170:
---
Description: Add example for IGNITE-2492.  (was: Once IGNITE-2492 is 
finished, we should simplify examples:
* Remove the requirement to start Apache.Ignite.exe with {{-assembly}} parameter
* Remove ExamplesDll project, put all classes into one project to avoid 
confusion)

> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> Add example for IGNITE-2492.



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

[jira] [Updated] (IGNITE-5170) .NET: Compute peer deployment example

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5170:
---
Summary: .NET: Compute peer deployment example  (was: .NET: Use peer 
deployment in examples)

> .NET: Compute peer deployment example
> -
>
> Key: IGNITE-5170
> URL: https://issues.apache.org/jira/browse/IGNITE-5170
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> Once IGNITE-2492 is finished, we should simplify examples:
> * Remove the requirement to start Apache.Ignite.exe with {{-assembly}} 
> parameter
> * Remove ExamplesDll project, put all classes into one project to avoid 
> confusion



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

[jira] [Commented] (IGNITE-5299) Don't set IgniteLock as broken if lock is failoverSafe

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5299:


GitHub user ezhuravl opened a pull request:

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

IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe



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

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

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

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


commit 02ebe624a37379055345ae1409918ba96da1d3fc
Author: Evgenii Zhuravlev 
Date:   2017-05-29T13:46:11Z

IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe




> Don't set IgniteLock as broken if lock is failoverSafe
> --
>
> Key: IGNITE-5299
> URL: https://issues.apache.org/jira/browse/IGNITE-5299
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>
> It's unnecessary to set isBroken flag to IgniteLock when failoverSafe=true, 
> because it's only used in case when failoverSafe=false



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

[jira] [Created] (IGNITE-5331) Investigate performance implications of SQL schema refactoring

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5331:
---

 Summary: Investigate performance implications of SQL schema 
refactoring
 Key: IGNITE-5331
 URL: https://issues.apache.org/jira/browse/IGNITE-5331
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
 Fix For: 2.1


SQL is now decoupled from concrete cache. It means tha:
1) Special cache-agnostic implementation {{CacheQueryObjectValueContext}} is 
passed to binary objects, with {{copyOnGet}} always returning true.
2) {{GridH2ValueCacheObject.getObject(boolean)}} is now called with {{true}} 
argument more oftner (see usages and Git history).

All in all it means that more object copying could occur than before. We need 
to understand whether performance is affected. 

One important thing to consider is immutability of binary object. That is, once 
created, {{BinaryObject}} never changes. It means that is {{BinaryMarshaller}} 
is enabled, we can always avoid copying safely.



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

[jira] [Assigned] (IGNITE-5300) .NET: LINQ RemoveAll examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5300:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: LINQ RemoveAll examples
> -
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.2
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} LINQ bulk 
> delete (IGNITE-4904).



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

[jira] [Comment Edited] (IGNITE-5300) .NET: LINQ RemoveAll examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5300 at 5/29/17 2:00 PM:
-

I think we should wait for {{UpdateAll}} (IGNITE-5298) before adding these to 
the examples.


was (Author: ptupitsyn):
I think we should wait for {{UpdateAll}} before adding these to the examples.

> .NET: LINQ RemoveAll examples
> -
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.2
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} LINQ bulk 
> delete (IGNITE-4904).



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

[jira] [Updated] (IGNITE-5300) .NET: LINQ RemoveAll examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5300:
---
Fix Version/s: (was: 2.1)
   2.2

> .NET: LINQ RemoveAll examples
> -
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.2
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} LINQ bulk 
> delete (IGNITE-4904).



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

[jira] [Commented] (IGNITE-5300) .NET: LINQ RemoveAll examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5300:


I think we should wait for {{UpdateAll}} before adding these to the examples.

> .NET: LINQ RemoveAll examples
> -
>
> Key: IGNITE-5300
> URL: https://issues.apache.org/jira/browse/IGNITE-5300
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, LINQ
> Fix For: 2.2
>
>
> Update examples (normal and LinqPad) to demonstrate {{RemoveAll}} LINQ bulk 
> delete (IGNITE-4904).



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

[jira] [Updated] (IGNITE-1442) CPP: Implement asynchronous cache operations.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-1442:

Fix Version/s: (was: 2.1)
   2.2

> CPP: Implement asynchronous cache operations.
> -
>
> Key: IGNITE-1442
> URL: https://issues.apache.org/jira/browse/IGNITE-1442
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: cpp
> Fix For: 2.2
>
>




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

[jira] [Updated] (IGNITE-3025) CPP: C++ client node can not access the cache for which PlatformDotNetCacheStoreFactory is used.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-3025:

Fix Version/s: (was: 2.1)
   2.2

> CPP: C++ client node can not access the cache for which 
> PlatformDotNetCacheStoreFactory is used.
> 
>
> Key: IGNITE-3025
> URL: https://issues.apache.org/jira/browse/IGNITE-3025
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Igor Sapego
>  Labels: cpp
> Fix For: 2.2
>
>
> If there is .NET node with {{PlatformDotNetCacheStoreFactory}} configured for 
> some cache then this cache can not be accessed by the C++ client node.
> Following error observed on the attempt to access the cache:
> {noformat}
> [GridDhtPartitionsExchangeFuture] Failed to reinitialize local partitions 
> (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], nodeId=2bf10735, evt=DISCOVERY_CUSTOM_EVT]
> PlatformNoCallbackException []
> at 
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.cacheStoreCreate(Native
>  Method)
> at 
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.cacheStoreCreate(PlatformCallbackGateway.java:63)
> at 
> org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetCacheStore.initialize(PlatformDotNetCacheStore.java:338)
> at 
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore0(PlatformProcessorImpl.java:347)
> at 
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore(PlatformProcessorImpl.java:317)
> at 
> org.apache.ignite.internal.processors.cache.store.CacheOsStoreManager.start0(CacheOsStoreManager.java:60)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1051)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1648)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1563)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:956)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:523)
> {noformat}



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

[jira] [Resolved] (IGNITE-3574) CPP: Implement compute API

[Igor Sapego (JIRA)]

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

Igor Sapego resolved IGNITE-3574.
-
Resolution: Won't Fix

Going to split up in several tickets and implement one by one in several steps.

> CPP: Implement compute API
> --
>
> Key: IGNITE-3574
> URL: https://issues.apache.org/jira/browse/IGNITE-3574
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp, important
> Fix For: 2.1
>
>
> Umbrella ticket to host all compute API tickets.



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

[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2492:


Github user asfgit closed the pull request at:

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


> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2492:


Merged to master: {{69876116dd851d7bfbf0d82e6850654cc57d3d0b}}

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Resolved] (IGNITE-2492) .NET: Peer assembly loading

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-2492.

Resolution: Fixed

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Updated] (IGNITE-5074) Split up asynchronous and synchronous calls in PlatformCompute

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5074:

Fix Version/s: (was: 2.1)
   2.2

> Split up asynchronous and synchronous calls in PlatformCompute
> --
>
> Key: IGNITE-5074
> URL: https://issues.apache.org/jira/browse/IGNITE-5074
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: .net, cpp
> Fix For: 2.2
>
>
> Currently, there is only asynchronous version of calls in 
> {{PlatformCompute}}, which means we create temporary objects (like futures 
> and listeners) which we do not need during synchronous calls.
> Add synchronous version of API calls which generate less garbage.



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

[jira] [Assigned] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-5176:


Assignee: Taras Ledkov  (was: Igor Sapego)

> JDBC Driver: implement query execution for thin jdbc driver based on common 
> odbc/jdbc protocol
> --
>
> Key: IGNITE-5176
> URL: https://issues.apache.org/jira/browse/IGNITE-5176
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> Implementation query execution & fetch results for thin JDBC driver over ODBC 
> protocol.



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

[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2492:


1) I think {{CurrentAppDomain}} reflects the mechanics better: users will right 
away get a hint about underlying mechanics. {{Shared}} does not tell much, on 
the other hand.
2) Docs in code updated, readme.io ticket created: IGNITE-5330

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Assigned] (IGNITE-5299) Don't set IgniteLock as broken if lock is failoverSafe

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev reassigned IGNITE-5299:
-

Assignee: Evgenii Zhuravlev

> Don't set IgniteLock as broken if lock is failoverSafe
> --
>
> Key: IGNITE-5299
> URL: https://issues.apache.org/jira/browse/IGNITE-5299
> Project: Ignite
>  Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>
> It's unnecessary to set isBroken flag to IgniteLock when failoverSafe=true, 
> because it's only used in case when failoverSafe=false



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

[jira] [Created] (IGNITE-5330) .NET: Peer assembly loading documentation

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5330:
--

 Summary: .NET: Peer assembly loading documentation
 Key: IGNITE-5330
 URL: https://issues.apache.org/jira/browse/IGNITE-5330
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
 Fix For: 2.1


Document peer assembly loading on https://apacheignite-net.readme.io/



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

[jira] [Commented] (IGNITE-5317) Remove strict dependency on concrete cache from SQL execute methods

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5317:


GitHub user devozerov opened a pull request:

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

IGNITE-5317



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

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

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

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


commit 0f205c7b6e1ef4928f713b8551792049b2b4b815
Author: devozerov 
Date:   2017-05-28T11:24:43Z

WIP.

commit faf0df3292ac798489c730c67c5e8bd228d5aa84
Author: devozerov 
Date:   2017-05-28T14:46:13Z

WIP.

commit 55f18339e354a9b4e2e13d4db4b4199a697d99f9
Author: devozerov 
Date:   2017-05-29T08:04:55Z

WIP.

commit 55256730e0bdff09b24f3ca234e8f849997440a0
Author: devozerov 
Date:   2017-05-29T08:17:02Z

WIP.

commit 4f0d6a45241d44b5f77aa3f94dd426e96d7d27ea
Author: devozerov 
Date:   2017-05-29T08:19:20Z

WIP.

commit 9991c7e57799e938fa75fa014c9d58f23ff6fb81
Author: devozerov 
Date:   2017-05-29T08:20:29Z

WIP.

commit d60591eca93f3d6c98a73759e3552953a47446cc
Author: devozerov 
Date:   2017-05-29T08:25:52Z

WIP.

commit 3837146dc9a045599030b45a3d8a58733715c3ee
Author: devozerov 
Date:   2017-05-29T12:18:16Z

Merge branch 'master' into ignite-5317

commit 2692e639085111e188d1821fb771a34c0f9620f5
Author: devozerov 
Date:   2017-05-29T12:21:41Z

WIP.

commit 4064fadf55495488ff08a6517e8ea912ade4cc70
Author: devozerov 
Date:   2017-05-29T12:26:03Z

WIP.

commit 645de3c2f32738f8dcb47c52899439cb12606b64
Author: devozerov 
Date:   2017-05-29T12:51:20Z

Minors.

commit 30eaab2d9fc2d4692f525ab1af56f161fafb9a28
Author: devozerov 
Date:   2017-05-29T12:52:51Z

WIP (queryLocalText).




> Remove strict dependency on concrete cache from SQL execute methods
> ---
>
> Key: IGNITE-5317
> URL: https://issues.apache.org/jira/browse/IGNITE-5317
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> All query execute methods in {{GridQueryProcessor}} and {{IgniteH2Indexing}} 
> should accept cache name or cache context as optional parameters, and should 
> be able to work without them at all. With all recent refactorings in place it 
> should be fairly easy to do so.



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

[jira] [Updated] (IGNITE-5161) Provide basic Ignite Compute Grid Examples

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5161:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3574)

> Provide basic Ignite Compute Grid Examples
> --
>
> Key: IGNITE-5161
> URL: https://issues.apache.org/jira/browse/IGNITE-5161
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> As a part of Ignite Compute release for C++ we need to provide several 
> examples to demonstrate basic capabilities.



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

[jira] [Updated] (IGNITE-3355) CPP: Implement Compute::Call() for Ignite C++.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-3355:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3574)

> CPP: Implement Compute::Call() for Ignite C++.
> --
>
> Key: IGNITE-3355
> URL: https://issues.apache.org/jira/browse/IGNITE-3355
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement {{Compute}} class with {{Compute::Call}} method.



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

[jira] [Created] (IGNITE-5329) .NET: Enable peer assembly loading in all APIs

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5329:
--

 Summary: .NET: Enable peer assembly loading in all APIs
 Key: IGNITE-5329
 URL: https://issues.apache.org/jira/browse/IGNITE-5329
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
 Fix For: 2.2


IGNITE-2492 implemented peer assembly loading mechanism and enabled it for 
Compute. Now we can enable it for all other APIs where remote code execution is 
used (services, events, messaging, cache filters, etc).



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

[jira] [Assigned] (IGNITE-5290) Events might be missed during concurrent CQ registration and cache operations

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov reassigned IGNITE-5290:


Assignee: Nikolay Tikhonov

> Events might be missed during concurrent CQ registration and cache operations
> -
>
> Key: IGNITE-5290
> URL: https://issues.apache.org/jira/browse/IGNITE-5290
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nikolay Tikhonov
>Assignee: Nikolay Tikhonov
> Attachments: test.patch
>
>
> Events might be missed during concurrent CQ registration and cache 
> operations. See attached test.



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

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5315:


Github user asfgit closed the pull request at:

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


> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Resolved] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5315.

Resolution: Fixed

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5315:


* {{TableName}} and {{Aliases}} changing their values on 
{{cache.GetConfiguration}} is not a bug. Tests fixed.
* LINQ provider fixed to respect {{SqlEscapeAll}} and quote identifiers when 
needed, tests added. {{_KEY}} and {{_VAL}} are always uppercase now.
* Hanging nodes on incorrect config: IGNITE-1094
* Index field names (SQL and Full-Text) fixed (use dot notation with full 
nesting)

TC is fine, merged to master: {{}}

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Assigned] (IGNITE-5324) Move volatile data structures into a separate cache

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-5324:


Assignee: Ilya Lantukh

> Move volatile data structures into a separate cache
> ---
>
> Key: IGNITE-5324
> URL: https://issues.apache.org/jira/browse/IGNITE-5324
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Ilya Lantukh
> Fix For: 2.1
>
>
> With new persistence mechanism, we should move volatile data structures (such 
> as Locks) into a separate cache for which persistence should be disabled.



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

[jira] [Commented] (IGNITE-2492) .NET: Peer assembly loading

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2492:
-

[~ptupitsyn], looks good to me, except of two things:
1) I would rather name the mode {{Shared}} instead of {{CurrentAppDomain}}. 
2) We need to have detailed description on how this mode works. I'e' user 
should clearly understand that loaded assembly will never be unloaded. Also, we 
should explain that potentially all nodes will have this assembly loaded to 
their address space, and explain users how to deal with different versions of 
the same assembly.

> .NET: Peer assembly loading
> ---
>
> Key: IGNITE-2492
> URL: https://issues.apache.org/jira/browse/IGNITE-2492
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, important
> Fix For: 2.1
>
>
> Similar to peer class loading in Java, we can provide a possibility to load 
> assemblies on already started nodes, so that a node can execute jobs that are 
> not present on other nodes.
> Considerations:
> * Can we unload assemblies after use to free memory? This requires a separate 
> AppDomain, can we work with that?



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

[jira] [Created] (IGNITE-5328) Support cache atomicity mode for CREATE TABLE

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5328:
---

 Summary: Support cache atomicity mode for CREATE TABLE
 Key: IGNITE-5328
 URL: https://issues.apache.org/jira/browse/IGNITE-5328
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


Users should be able to set atomicity mode through "WITH" synthax.

Property name: {{atomicityMode}}
Allowed values (case insensitive): {{atomic}}, {{transactional}}



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

[jira] [Created] (IGNITE-5327) Create predefined cache templates for CREATE TABLE command

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5327:
---

 Summary: Create predefined cache templates for CREATE TABLE command
 Key: IGNITE-5327
 URL: https://issues.apache.org/jira/browse/IGNITE-5327
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


We need to add predefined templates which will always be available on the node. 
Let's avoid adding them to node configuration to avoid cache data sharing on 
node startup. Instead, let's just create them on-fly when certain template name 
is found.

Proposed templates:
1) "PARTITIONED" => {{new CacheConfiguration().setCacheMode(PARTITIONED)}}
2) "REPLICATED" => {{new CacheConfiguration().setCacheMode(REPLICATED)}}



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

[jira] [Created] (IGNITE-5326) Support "backups" property for CREATE TABLE property

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5326:
---

 Summary: Support "backups" property for CREATE TABLE property
 Key: IGNITE-5326
 URL: https://issues.apache.org/jira/browse/IGNITE-5326
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


We need to support {{backups}} property through {{WITH}} keyword.



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

[jira] [Created] (IGNITE-5325) CREATE TABLE should support "cacheGroup" property

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5325:
---

 Summary: CREATE TABLE should support "cacheGroup" property
 Key: IGNITE-5325
 URL: https://issues.apache.org/jira/browse/IGNITE-5325
 Project: Ignite
  Issue Type: Bug
  Components: cache, sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1


When cache groups are ready (IGNITE-5075), we should be able to configure group 
name through {{WITH}} keyword in the same way as we configure template name for 
now.



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

[jira] [Updated] (IGNITE-5325) CREATE TABLE should support "cacheGroup" property

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5325:

Issue Type: Task  (was: Bug)

> CREATE TABLE should support "cacheGroup" property
> -
>
> Key: IGNITE-5325
> URL: https://issues.apache.org/jira/browse/IGNITE-5325
> Project: Ignite
>  Issue Type: Task
>  Components: cache, sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> When cache groups are ready (IGNITE-5075), we should be able to configure 
> group name through {{WITH}} keyword in the same way as we configure template 
> name for now.



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

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5315:


{{Field not found}} error is caused by changed behavior for indexes (SQL and 
Full-Text), they now require dot notation for nested fields. This breaks many 
examples.

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Created] (IGNITE-5324) Move volatile data structures into a separate cache

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5324:


 Summary: Move volatile data structures into a separate cache
 Key: IGNITE-5324
 URL: https://issues.apache.org/jira/browse/IGNITE-5324
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.1


With new persistence mechanism, we should move volatile data structures (such 
as Locks) into a separate cache for which persistence should be disabled.



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

[jira] [Created] (IGNITE-5323) Move record serializer version from file name to file header

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5323:


 Summary: Move record serializer version from file name to file 
header
 Key: IGNITE-5323
 URL: https://issues.apache.org/jira/browse/IGNITE-5323
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
Assignee: Konstantin Dudkov
 Fix For: 2.1


Keeping records serializer version in the WAL segment file name makes it hard 
to implement forward serializer version update because we need to rename files 
on recovery.
Instead, we should write serializer version in the file header and use it when 
reading records.
We should also add some boilerplate code in order to make it easier to add new 
serializer versions in the future.



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

[jira] [Assigned] (IGNITE-5322) Improve WAL record/iterator structure

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-5322:


Assignee: Dmitriy Govorukhin

> Improve WAL record/iterator structure
> -
>
> Key: IGNITE-5322
> URL: https://issues.apache.org/jira/browse/IGNITE-5322
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Govorukhin
> Fix For: 2.1
>
>
> Currently, we rely on the WAL files layout and zero-ing to make a decision 
> when to stop the iteration.
> Instead, we should write a WAL Pointer to each record with it's position in 
> the file. This will allow us to verify that we are reading a consistent 
> records sequence and should also remove a requirement for zero-clean WAL 
> segment.
> When iterating over the WAL, we should calculate expected next WAL pointer 
> and check that read pointer is equal to the read. If we found a difference, 
> this means that we encountered a stale segment and can stop the iteration.



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5097:
-

[~vozerov], what about strings?

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Created] (IGNITE-5322) Improve WAL record/iterator structure

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5322:


 Summary: Improve WAL record/iterator structure
 Key: IGNITE-5322
 URL: https://issues.apache.org/jira/browse/IGNITE-5322
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.1


Currently, we rely on the WAL files layout and zero-ing to make a decision when 
to stop the iteration.
Instead, we should write a WAL Pointer to each record with it's position in the 
file. This will allow us to verify that we are reading a consistent records 
sequence and should also remove a requirement for zero-clean WAL segment.
When iterating over the WAL, we should calculate expected next WAL pointer and 
check that read pointer is equal to the read. If we found a difference, this 
means that we encountered a stale segment and can stop the iteration.



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5097:
-

I would only do that for arrays. Applying varlens to enums and decimals would 
make them hard to analyze and parse and hence may cause slowdown in SQL and 
sereliazation and deserialization.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5097:


I agree.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5097:


[~isapego], [~ptupitsyn], [~vozerov]

Let's describe discussion result:
We can use varint encoding to following cases (in the all platforms):
1) size of all arrays 
2) BigDecimal: scale and mag
3) Strings: chars array length
4) Enum ordinals

Do you agree?

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.1
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Comment Edited] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5315 at 5/29/17 10:54 AM:
--

Another probable bug: Ignite hangs on correct configuration with nested field.

Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], nodeId=eaa7f2f1, 
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=false, hash=516389979], init=false, 
lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
skipPreload=false, clientOnlyExchange=false, initTs=1496054631061, 
centralizedAff=false, changeGlobalStateE=null, 
exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[], 
srvNodes=[TcpDiscoveryNode [id=eaa7f2f1-8630-4ccf-9252-483688fab579, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1496054630311, loc=true, 
ver=2.1.0#19700101-sha1:, isClient=false]], super=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=class o.a.i.IgniteCheckedException: 
Field not found: Zip, hash=1647581106]]

class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:407)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:691)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:828)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1173)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1850)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1736)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:399)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:660)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:509)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1784)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}


was (Author: ptupitsyn):
Another probable bug: Ignite hangs on correct configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 

[jira] [Comment Edited] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5315 at 5/29/17 10:53 AM:
--

Another probable bug: Ignite hangs on correct configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], nodeId=eaa7f2f1, 
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=false, hash=516389979], init=false, 
lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
skipPreload=false, clientOnlyExchange=false, initTs=1496054631061, 
centralizedAff=false, changeGlobalStateE=null, 
exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[], 
srvNodes=[TcpDiscoveryNode [id=eaa7f2f1-8630-4ccf-9252-483688fab579, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1496054630311, loc=true, 
ver=2.1.0#19700101-sha1:, isClient=false]], super=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=class o.a.i.IgniteCheckedException: 
Field not found: Zip, hash=1647581106]]

class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:407)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:691)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:828)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1173)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1850)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1736)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:399)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:660)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:509)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1784)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}


was (Author: ptupitsyn):
Another probable bug: Ignite hangs on incorrect configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5315:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5315 .NET: Fix LINQ and cache configuration broken by IGNITE-5287 
(sqlEscapeAll)



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

$ git pull https://github.com/ptupitsyn/ignite ignite-5315

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

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


commit 8ccd4d950723cacc304e5991e7f5d02f735f7362
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:00:00Z

Adding SqlEscapeAll to LINQ tests

commit 1bf215407e49f95282e930b27173995ae6c6b502
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:00:54Z

Add CacheLinqTestSqlEscapeAll

commit d63fd89355ebe797d94dc0a3f63f6ca4ffa2cd8c
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:09:32Z

Improve table name inference

commit 2f60dc38a2646db044f7c294f6748d86c0ecf028
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:14:26Z

Fixing SqlEscapeAll behavior

commit eda94f2e8edbf9e9f2587c15c657fcf7e27287b4
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:17:50Z

wip escapeAll

commit 5b43111c8b7887aaf56ee37e28e0254cd36715be
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:18:50Z

wip

commit 73cca2e321d4594e489ef473d2f3e7305868bf61
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:31:48Z

Fix _key, _val handling

commit 51631ec425a58e8659eea377dddc647993988cc6
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:39:15Z

wip key valu

commit ece993b9aec715ce4919f8fa7a98f521cd610951
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:45:28Z

wip

commit 28faa89e36e390ab20e1d9d7a6a8913d8ce384b7
Author: Pavel Tupitsyn 
Date:   2017-05-29T09:52:40Z

wip tests

commit 0e39b7e2f4f81cd97ac3f8f30eae5fa91b1d1a89
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:04:16Z

TestIntrospection fixed

commit 0f86000bd5c851816cd84427be6241801aa84abb
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:06:50Z

wip

commit 9a45cd95d76849825ba5ea9616a78c100ca32462
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:11:13Z

wip

commit 80ed376b41103ad320901daa5e609eec99fa5825
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:24:37Z

wip

commit 6fdebb27156efac07c797b8a8c790b1e177ba14a
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:32:52Z

Add QueryEntity.GetAlias

commit 61fe2cdad27d75b3e3bcd3a0b60c035ad12594a3
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:34:22Z

Fix alias lookup efficiency

commit 3e5b6300a3152becf3537b3fcc2a85b886bc64d2
Author: Pavel Tupitsyn 
Date:   2017-05-29T10:40:18Z

LINQ tests are green




> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Comment Edited] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5315 at 5/29/17 10:45 AM:
--

Another probable bug: Ignite hangs on incorrect configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], nodeId=eaa7f2f1, 
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=false, hash=516389979], init=false, 
lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
skipPreload=false, clientOnlyExchange=false, initTs=1496054631061, 
centralizedAff=false, changeGlobalStateE=null, 
exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[], 
srvNodes=[TcpDiscoveryNode [id=eaa7f2f1-8630-4ccf-9252-483688fab579, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1496054630311, loc=true, 
ver=2.1.0#19700101-sha1:, isClient=false]], super=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=class o.a.i.IgniteCheckedException: 
Field not found: Zip, hash=1647581106]]

class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:407)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:691)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:828)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1173)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1850)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1736)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:399)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:660)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:509)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1784)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}


was (Author: ptupitsyn):
Another probable bug: Ignite hangs on incorrect configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 

[jira] [Comment Edited] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5315 at 5/29/17 10:45 AM:
--

Another probable bug: Ignite hangs on incorrect configuration.

{code}
Failed to wait for completion of partition map exchange (preloading will not 
start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, 
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=1, nodeId8=eaa7f2f1, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1496054631061]], crd=TcpDiscoveryNode 
[id=eaa7f2f1-8630-4ccf-9252-483688fab579, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1496054630311, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], nodeId=eaa7f2f1, 
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=false, hash=516389979], init=false, 
lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
skipPreload=false, clientOnlyExchange=false, initTs=1496054631061, 
centralizedAff=false, changeGlobalStateE=null, 
exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[], 
srvNodes=[TcpDiscoveryNode [id=eaa7f2f1-8630-4ccf-9252-483688fab579, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1496054630311, loc=true, 
ver=2.1.0#19700101-sha1:, isClient=false]], super=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=class o.a.i.IgniteCheckedException: 
Field not found: Zip, hash=1647581106]]
class org.apache.ignite.IgniteCheckedException: Field not found: Zip
class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:407)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:691)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:828)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1173)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1850)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1736)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:399)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:660)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:509)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1784)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}


was (Author: ptupitsyn):
Another probable bug: Ignite hangs on incorrect configuration.

{code}
class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5315:


Another probable bug: Ignite hangs on incorrect configuration.

{code}
class org.apache.ignite.IgniteCheckedException: Field not found: Zip
at 
org.apache.ignite.internal.processors.query.QueryIndexDescriptorImpl.addField(QueryIndexDescriptorImpl.java:124)
at 
org.apache.ignite.internal.processors.query.QueryUtils.createIndexDescriptor(QueryUtils.java:579)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndex(QueryUtils.java:596)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processIndexes(QueryUtils.java:532)
at 
org.apache.ignite.internal.processors.query.QueryUtils.processBinaryMeta(QueryUtils.java:493)
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:407)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:691)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:828)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1173)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1850)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1736)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:399)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:660)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:509)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1784)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{code}

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

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

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-5203:
-

Looks good now.

> JDBC driver should support BLOB fields
> --
>
> Key: IGNITE-5203
> URL: https://issues.apache.org/jira/browse/IGNITE-5203
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>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] [Commented] (IGNITE-5290) Events might be missed during concurrent CQ registration and cache operations

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-5290:
--

[~sboikov]
Thank you for your idea!  I've already implemeted it. Could you please look at 
PR? 
https://github.com/apache/ignite/pull/2010

> Events might be missed during concurrent CQ registration and cache operations
> -
>
> Key: IGNITE-5290
> URL: https://issues.apache.org/jira/browse/IGNITE-5290
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Nikolay Tikhonov
> Attachments: test.patch
>
>
> Events might be missed during concurrent CQ registration and cache 
> operations. See attached test.



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

[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5053:
---

Assignee: Alexander Paschenko

> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute. 
> Final name is yet to be defined. May be we should have several synonyms 
> resembling other databases to make migration to Ignite easier.



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

[jira] [Updated] (IGNITE-4509) SQL: query with condition on affinity columns and without joins and subqueries should go to affinity node only

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4509:

Summary: SQL: query with condition on affinity columns and without joins 
and subqueries should go to affinity node only  (was: SQL: query with condition 
on affinity columns and without joins and subqueries can be replaced with GET)

> SQL: query with condition on affinity columns and without joins and 
> subqueries should go to affinity node only
> --
>
> Key: IGNITE-4509
> URL: https://issues.apache.org/jira/browse/IGNITE-4509
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
>  Labels: important, performance, sql
> Fix For: 2.1
>
>
> Simple SQL queries usually demonstrate negative scalability when more nodes 
> are added. 
> Consider the following query:
> {code}
> SELECT * FROM Person p
> WHERE p.id = ?
> {code}
> If {{Person.id}} is affinity field, then query can be replaced with plain 
> {{IgniteCache.get}} or some specialized version of GET, which will return 
> only desired fields. This optimization will guarantee smooth scale with any 
> number of nodes.



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

[jira] [Assigned] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5273:
---

Assignee: Pavel Tupitsyn

> .NET: MemoryMetrics API improvements to be ported to .NET
> -
>
> Key: IGNITE-5273
> URL: https://issues.apache.org/jira/browse/IGNITE-5273
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Reporter: Sergey Chugunov
>Assignee: Pavel Tupitsyn
>  Labels: important
> Fix For: 2.1
>
>
> Improvements already made for linked ticket need to be ported on .NET side.



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

[jira] [Updated] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5273:

Component/s: platforms

> .NET: MemoryMetrics API improvements to be ported to .NET
> -
>
> Key: IGNITE-5273
> URL: https://issues.apache.org/jira/browse/IGNITE-5273
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Reporter: Sergey Chugunov
>  Labels: important
> Fix For: 2.1
>
>
> Improvements already made for linked ticket need to be ported on .NET side.



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

[jira] [Updated] (IGNITE-4724) AVG function always returns double type instead of the argument type

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4724:

Labels: important  (was: )

> AVG function always returns double type instead of the argument type
> 
>
> Key: IGNITE-4724
> URL: https://issues.apache.org/jira/browse/IGNITE-4724
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.9
>Reporter: Sergey Kozlov
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.1
>
>
> For H2:
> SELECT AVG(intCol) FROM cache_part_2 AS part_2 WHERE (10*shortCol/100) > 
> longCol
> -[472]
> For Ignite:
> SELECT AVG(intCol) FROM AllTypes AS part_2 WHERE (10*shortCol/100) > longCol
> +[472.2307692307692]



--
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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5250:

Labels:   (was: important)

> 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
>  Components: sql
>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)
>  

[jira] [Comment Edited] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-5315 at 5/29/17 9:06 AM:
-

1) {{CacheConfigurationTest}} is broken because even though user has not 
specified `QueryEntity.TableName`, some value is returned always (inferred from 
type name). I think this is not a correct behavior.

2) {{LinqTest}} is broken due to the same thing: table name is not expected.

We should also take {{CacheConfiguration.SqlEscapeAll}} into account in LINQ 
engine (add tests).


was (Author: ptupitsyn):
1) {{CacheConfigurationTest}} is broken because even though user has not 
specified `QueryEntity.TableName`, some value is returned always (inferred from 
type name). I think this is not a correct behavior.

2) {{LinqTest}} is broken due to table name uppercasing. We should take 
{{CacheConfiguration.SqlEscapeAll}} into account in LINQ engine.

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

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

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5176:
-

[~tledkov-gridgain], I've finished with the C++ part. Tests also pass.

> JDBC Driver: implement query execution for thin jdbc driver based on common 
> odbc/jdbc protocol
> --
>
> Key: IGNITE-5176
> URL: https://issues.apache.org/jira/browse/IGNITE-5176
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> Implementation query execution & fetch results for thin JDBC driver over ODBC 
> protocol.



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

[jira] [Commented] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5315:


1) {{CacheConfigurationTest}} is broken because even though user has not 
specified `QueryEntity.TableName`, some value is returned always (inferred from 
type name). I think this is not a correct behavior.

2) {{LinqTest}} is broken due to table name uppercasing. We should take 
{{CacheConfiguration.SqlEscapeAll}} into account in LINQ engine.

> .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
> ---
>
> Key: IGNITE-5315
> URL: https://issues.apache.org/jira/browse/IGNITE-5315
> Project: Ignite
>  Issue Type: Task
>  Components: platforms, sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.1
>
>
> Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. 
> Need to investigate why and fix.



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

[jira] [Updated] (IGNITE-5205) Optimize SQL messaging

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5205:

Component/s: general

> Optimize SQL messaging
> --
>
> Key: IGNITE-5205
> URL: https://issues.apache.org/jira/browse/IGNITE-5205
> Project: Ignite
>  Issue Type: Bug
>  Components: general, sql
>Affects Versions: 2.0
>Reporter: Sergi Vladykin
>Assignee: Sergi Vladykin
>  Labels: important
> Fix For: 2.1
>
>
> Currently we create Message object for each H2 Value being sent or received 
> over the wire. Lets write and read them directly without intermediate 
> conversions.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4575:
---

Assignee: Sergey Kalashnikov  (was: Vladimir Ozerov)

> 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-4575) Implement in Ignite wrapper for enums based on H2 user value type

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4575:
---

Assignee: Vladimir Ozerov  (was: Sergey Kalashnikov)

> 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: Vladimir Ozerov
>  Labels: important
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-4501) Improvement of connection in a cluster of new node

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4501:

Labels:   (was: important)

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.1
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



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