[jira] [Created] (IGNITE-4243) Add examples of using Redis

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-4243:


 Summary: Add examples of using Redis
 Key: IGNITE-4243
 URL: https://issues.apache.org/jira/browse/IGNITE-4243
 Project: Ignite
  Issue Type: Sub-task
Reporter: Roman Shtykh


Add examples of using Redis with Python/PHP/etc. clients to {{examples/}} 
similarly to memcached and rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4241) Web condole: Failed execute query after node restart.

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-4241.

   Resolution: Fixed
 Assignee: Pavel Konstantinov  (was: Andrey Novikov)
Fix Version/s: 1.8

Fixed. Pavel, please test.

> Web condole: Failed execute query after node restart.
> -
>
> Key: IGNITE-4241
> URL: https://issues.apache.org/jira/browse/IGNITE-4241
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 1.8
>
>
> # Run one node with data,
> # Execute query on SQL page,
> # Restart node,
> # Execute query again.
> Console in results area show message:
> Error: Failed to clear query results. Nodes are not available: [d539449e]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4233) Add documentation for REDIS support

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4233:
--

Java page

To connect to Ignite using a Java client for Redis, you need to have an Ignite 
cluster/node configured, if necessary, as shown in Redis Support page and 
running.

To connect to Ignite running on port 6379 with, for instance, Jedis,

{code}
JedisPoolConfig jedisPoolCfg = new JedisPoolConfig();

// your pool configurations.

JedisPool pool = new JedisPool(jedisPoolCfg, "localhost", 6379, 1);

try (Jedis jedis = pool.getResource()) {
jedis.set("key1", "1");
System.out.println("Value for 'key1': " + jedis.get("key1"));
}

pool.destroy();
{code}


> Add documentation for REDIS support
> ---
>
> Key: IGNITE-4233
> URL: https://issues.apache.org/jira/browse/IGNITE-4233
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4233) Add documentation for REDIS support

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4233:
--

'Redis' category page.

h1. Redis Support
h2. Connect to Ignite using Redis compatible client.

Ignite is partially Redis compliant which enables users to store and retrieve 
distributed data from Ignite cache using any Redis compatible client.

In version 1.8.0 only the following commands are supported.
- ECHO
- PING
- QUIT
- GET
- MGET (limitation: not null values returned for non-existing keys)
- SET (limitation: without key expiration)
- MSET
- INCR
- DECR
- INCRBY
- DECRBY
- APPEND
- STRLEN
- GETSET
- SETRANGE
- GETRANGE
- DEL (limitation: number of submitted keys returned)
- EXISTS
- DBSIZE

Cluster nodes accepts Redis requests listening on a particular socket. By 
default each Ignite node is listening for incoming requests on 
{{\[host\]:11211}}. You can override the host and port using 
ConnectorConfiguration class

{quote}

...







{quote}

+Information note(readme.io):+ In Redis, databases are identified by an integer 
index, not by a database name. Therefore, currently you cannot switch between 
caches by names and only entries from null cache are handled.


> Add documentation for REDIS support
> ---
>
> Key: IGNITE-4233
> URL: https://issues.apache.org/jira/browse/IGNITE-4233
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4233) Add documentation for REDIS support

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-4233:
--

Before posting it on readme.io, I'll put the contents here.

> Add documentation for REDIS support
> ---
>
> Key: IGNITE-4233
> URL: https://issues.apache.org/jira/browse/IGNITE-4233
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Andrey Novikov
>Assignee: Roman Shtykh
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4125:

Assignee: Pavel Tupitsyn  (was: Denis Magda)

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4125:
-

Pavel, looks good to merge. Please address my latest notes I've left in GitHub 
and close the ticket.

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4129) .NET: add documentation and example for near cache

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4129:
-

Pavel, awesome, thanks!

I've added minor notes in the GitHub. Please take them into account and merge 
the changes closing the ticket right after that.

> .NET: add documentation and example for near cache
> --
>
> Key: IGNITE-4129
> URL: https://issues.apache.org/jira/browse/IGNITE-4129
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Presently the documentation and example about the near caching are missing on 
> .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/near-caches
> - This example should be used as a reference
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/NearCacheExample.cs
> However, we have to improve it by showing that the near cache is really used 
> (metrics or event listeners or something else)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4128) .NET: add documentation and example for EntryProcessor

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4128:

Assignee: Prachi Garg  (was: Denis Magda)

> .NET: add documentation and example for EntryProcessor
> --
>
> Key: IGNITE-4128
> URL: https://issues.apache.org/jira/browse/IGNITE-4128
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 1.8
>
>
> Let's add the documentation and example for {{EntryProcessor}} functionality.
> The example should be similar to Java's {{CacheEntryProcessorExample}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4128) .NET: add documentation and example for EntryProcessor

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4128:
-

Pavel, let's put off the documentation for now then. We will add it a bit later 
once it has been added to Java.

As for the example, it looks good to me. The only that is still confuses me is 
the first sentence of the example documentation.

"This example demonstrates co-locating a closure with data, creating and 
modifying cache entries with EntryProcessor."

I would rather say

"This examples demonstrates the affinity collocation of a closure with data by 
showing how cache entries can be created and modified with an EntryProcessor"

[~pgarg], please suggest more grammatically correct variant.

> .NET: add documentation and example for EntryProcessor
> --
>
> Key: IGNITE-4128
> URL: https://issues.apache.org/jira/browse/IGNITE-4128
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Let's add the documentation and example for {{EntryProcessor}} functionality.
> The example should be similar to Java's {{CacheEntryProcessorExample}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4135) .NET: unable to find assembly error

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4135:
-

Looks good, thanks!

> .NET: unable to find assembly error
> ---
>
> Key: IGNITE-4135
> URL: https://issues.apache.org/jira/browse/IGNITE-4135
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> A user can get "unable to find assembly error" at the time when an object is 
> missing in .NET assembly.
> Document explicitly that DDLs has to be added using "-assembly" flag upon a 
> .NET node startup. In addition, add the similar info to the troubleshooting 
> doc
> https://apacheignite-net.readme.io/docs/troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4135) .NET: unable to find assembly error

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-4135.
---

> .NET: unable to find assembly error
> ---
>
> Key: IGNITE-4135
> URL: https://issues.apache.org/jira/browse/IGNITE-4135
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> A user can get "unable to find assembly error" at the time when an object is 
> missing in .NET assembly.
> Document explicitly that DDLs has to be added using "-assembly" flag upon a 
> .NET node startup. In addition, add the similar info to the troubleshooting 
> doc
> https://apacheignite-net.readme.io/docs/troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4136) .NET: document ways on how to manage Ignite Service deployments

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4136:
-

Special for you, just created the Java version of the documentation.
http://apacheignite.gridgain.org/v1.7/docs/service-grid#deployment-management

> .NET: document ways on how to manage Ignite Service deployments
> ---
>
> Key: IGNITE-4136
> URL: https://issues.apache.org/jira/browse/IGNITE-4136
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Provide documentation on how to manage deployments of a specific Ignite 
> Service:
> - node filter
> - cluster group
> - affinity based deployment
> Add code snippets near to the text documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4019) ODBC and DML: Document the usage on Apache Readme.io

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-4019.
---

> ODBC and DML: Document the usage on Apache Readme.io
> 
>
> Key: IGNITE-4019
> URL: https://issues.apache.org/jira/browse/IGNITE-4019
> Project: Ignite
>  Issue Type: Task
>  Components: cache, odbc
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.8
>
>
> Create "a new page" under ODBC section [1] on readme.io naming "DML Support" 
> and put the following content:
> - basic description on DML support by our ODBC driver. There should be a 
> reference to IGNITE-4018 that will contain overall information on DML.
> - list every supported command (INSERT, MERGE, UPDATE, DELETE) providing a 
> small code snippet examples. The examples can be taken from the example that 
> will be enhanced as a part of IGNITE-4016
> [1] https://apacheignite.readme.io/docs/odbc-driver



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-3303:
---

[~avinogradov]

Hi Anton,

Thank you for your feedback.

1. I removed the stop method and added the changes in cancel(). You are correct 
that the stream collection continue to run even when stopped was called. I 
break the loop once the data collection is complete and then validate the 
results.

2. I have added tests for parallelism > 1. 

I have tested that multiple sources are not getting supported although I added 
multiple IgniteSources with different caches the data collection do not proceed 
further. So far single IgniteSource with cache but parallel threads to collect 
data is supported.

3. tests link : http://ci.ignite.apache.org/viewLog.html?buildId=362395

Regards
Saikat

> Apache Flink Integration - Flink source to run a continuous query against one 
> or multiple caches
> 
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
> Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, 
> testFlinkIgniteSourceWithLargeBatch.log, win7.PNG
>
>
> Apache Flink integration 
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion : 
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4196) H2 debug console is always started on artificial port

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-4196:

Fix Version/s: (was: 1.8)
   2.0

> H2 debug console is always started on artificial port
> -
>
> Key: IGNITE-4196
> URL: https://issues.apache.org/jira/browse/IGNITE-4196
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 2.0
>
>
> When H2 debug console is started as described in [1], it always binds to an 
> artificial port. This has at least two issues:
> * Sometimes a client wants to connect through firewall. It's impossible to 
> port all possible ports for the console.
> * If there is no GUI on server node, console can't be opened in a browser, so 
> user has no idea what to do next and how to connect.
> We should:
> * Print out the information about how to connect to the console after it's 
> started.
> * Allow to use a specific port provided as a system property.
> [1] https://apacheignite.readme.io/docs/sql-queries#using-h2-debug-console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4019) ODBC and DML: Document the usage on Apache Readme.io

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-4019:
---

Assignee: Denis Magda  (was: Prachi Garg)

Made minor edits to the document.

> ODBC and DML: Document the usage on Apache Readme.io
> 
>
> Key: IGNITE-4019
> URL: https://issues.apache.org/jira/browse/IGNITE-4019
> Project: Ignite
>  Issue Type: Task
>  Components: cache, odbc
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.8
>
>
> Create "a new page" under ODBC section [1] on readme.io naming "DML Support" 
> and put the following content:
> - basic description on DML support by our ODBC driver. There should be a 
> reference to IGNITE-4018 that will contain overall information on DML.
> - list every supported command (INSERT, MERGE, UPDATE, DELETE) providing a 
> small code snippet examples. The examples can be taken from the example that 
> will be enhanced as a part of IGNITE-4016
> [1] https://apacheignite.readme.io/docs/odbc-driver



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3921) ODBC: Add documentation for the PDO interoperability.

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-3921:
-

Made some minor edits.

> ODBC: Add documentation for the PDO interoperability.
> -
>
> Key: IGNITE-3921
> URL: https://issues.apache.org/jira/browse/IGNITE-3921
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Denis Magda
>  Labels: documentation, odbc
> Fix For: 1.8
>
>
> We have checked our ODBC driver for the compatibility with the PDO. Now we 
> need to document it for our users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4103) IgniteDataStreamer doesn't throw exception if cache is destroyed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4103:


Github user samaitra closed the pull request at:

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


> IgniteDataStreamer doesn't throw exception if cache is destroyed
> 
>
> Key: IGNITE-4103
> URL: https://issues.apache.org/jira/browse/IGNITE-4103
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
> Fix For: 1.8
>
> Attachments: StreamerTest.java
>
>
> Test reproducing the issue is attached.
> When a streamer streams the data and someone concurrently destroys the cache, 
> {{addData}} doesn't throw an exception. Code continues to work and a lot of 
> messages like this appear in the log:
> {noformat}
> [12:20:38,451][ERROR][main][CacheObjectBinaryProcessorImpl] Failed to get 
> partition
> {noformat}
> The problematic code is in {{IgniteCacheObjectProcessorImpl.partition(...)}} 
> method:
> {code}
> try {
> return cctx != null ?
> cctx.affinity().partition(obj, false) :
> ctx.kernalContext().affinity().partition0(ctx.cacheName(), obj, null);
> }
> catch (IgniteCheckedException e) {
> U.error(log, "Failed to get partition");
> return  -1;
> }
> {code}
> There are two issues here:
> # Exception is completely ignored, it's not even printed out in {{U.error}}.
> # The exception should be actually rethrown so that streamer can stop adding 
> data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4103) IgniteDataStreamer doesn't throw exception if cache is destroyed

[Saikat Maitra (JIRA)]

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

Saikat Maitra commented on IGNITE-4103:
---

[~avinogradov]

Thanks Anton. The changes looks good.

Regards,
Saikat

> IgniteDataStreamer doesn't throw exception if cache is destroyed
> 
>
> Key: IGNITE-4103
> URL: https://issues.apache.org/jira/browse/IGNITE-4103
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
> Fix For: 1.8
>
> Attachments: StreamerTest.java
>
>
> Test reproducing the issue is attached.
> When a streamer streams the data and someone concurrently destroys the cache, 
> {{addData}} doesn't throw an exception. Code continues to work and a lot of 
> messages like this appear in the log:
> {noformat}
> [12:20:38,451][ERROR][main][CacheObjectBinaryProcessorImpl] Failed to get 
> partition
> {noformat}
> The problematic code is in {{IgniteCacheObjectProcessorImpl.partition(...)}} 
> method:
> {code}
> try {
> return cctx != null ?
> cctx.affinity().partition(obj, false) :
> ctx.kernalContext().affinity().partition0(ctx.cacheName(), obj, null);
> }
> catch (IgniteCheckedException e) {
> U.error(log, "Failed to get partition");
> return  -1;
> }
> {code}
> There are two issues here:
> # Exception is completely ignored, it's not even printed out in {{U.error}}.
> # The exception should be actually rethrown so that streamer can stop adding 
> data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4017) DML: Add Java Example

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4017:
-

[~al.psc], rather than creating a new example let's update the existing one 
{{CacheQueryExample}}.

In that example you can replace all cache.put operations with INSERTS.
- after querying data update some data using UPDATE and execute a SELECT making 
sure that the data has been updated.
- do the same for DELETE.

Talk to [~isapego] who updated the existing ODBC example in a similar way.

> DML: Add Java Example
> -
>
> Key: IGNITE-4017
> URL: https://issues.apache.org/jira/browse/IGNITE-4017
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 1.8
>
>
> In Apache Ignite 1.8 the community is planning to release DML support.
> To adopt DML usage we need to improve existed or add additional examples.
> We need to add {{CacheDmlExample}} doing the following with DML's *GridGain 
> Java API*:
> - fill up a cache using INSERT commands.
> - execute SELECT statements. There are should be queries with joins.
> - perform cache update using UPDATE and MERGE statements.
> - execute SELECT statements. There are should be queries with joins.
> - remove a part of the data from cache using DELETE command.
> execute SELECTs again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4238:
-

[~avinogradov], thanks for the review. Modified poms according to your comments 
and pushed the changes to the master.

[~amashenkov], please investigate the reason of the issue above. You can run 
the example ({{SpatialQueryExample}}) from the master as is or one of the tests 
created for the example - {{SpatialQueryExampleSelfTest}}, 
{{SpatialQueryExampleMultiNodeSelfTest}}

> Example for spatial queries
> ---
>
> Key: IGNITE-4238
> URL: https://issues.apache.org/jira/browse/IGNITE-4238
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 1.8
>
>
> The geospatial example is missing in Apache examples. It makes sense to add 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4238:

Assignee: Andrew Mashenkov  (was: Sergi Vladykin)

> Example for spatial queries
> ---
>
> Key: IGNITE-4238
> URL: https://issues.apache.org/jira/browse/IGNITE-4238
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 1.8
>
>
> The geospatial example is missing in Apache examples. It makes sense to add 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4242) ExchangeManager should wait for cache rebalancing in async way

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-4242:


 Summary: ExchangeManager should wait for cache rebalancing in 
async way
 Key: IGNITE-4242
 URL: https://issues.apache.org/jira/browse/IGNITE-4242
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov


Current code waits at system pool's thread, that unacceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4136) .NET: document ways on how to manage Ignite Service deployments

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4136:
--

Assignee: Denis Magda  (was: Pavel Tupitsyn)

> .NET: document ways on how to manage Ignite Service deployments
> ---
>
> Key: IGNITE-4136
> URL: https://issues.apache.org/jira/browse/IGNITE-4136
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Provide documentation on how to manage deployments of a specific Ignite 
> Service:
> - node filter
> - cluster group
> - affinity based deployment
> Add code snippets near to the text documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4136) .NET: document ways on how to manage Ignite Service deployments

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4136:


Denis, not sure what do you mean exactly. 
Is there Java documentation on these topics? If no, can you create it first?

> .NET: document ways on how to manage Ignite Service deployments
> ---
>
> Key: IGNITE-4136
> URL: https://issues.apache.org/jira/browse/IGNITE-4136
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Provide documentation on how to manage deployments of a specific Ignite 
> Service:
> - node filter
> - cluster group
> - affinity based deployment
> Add code snippets near to the text documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4135) .NET: unable to find assembly error

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4135 at 11/17/16 2:22 PM:
--

https://apacheignite-net.readme.io/docs/standalone-nodes#loading-user-assemblies
https://apacheignite-net.readme.io/docs/troubleshooting#could-not-load-file-or-assembly-myassembly-or-one-


was (Author: ptupitsyn):
https://apacheignite-net.readme.io/docs/standalone-nodes#loading-user-assemblies

> .NET: unable to find assembly error
> ---
>
> Key: IGNITE-4135
> URL: https://issues.apache.org/jira/browse/IGNITE-4135
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> A user can get "unable to find assembly error" at the time when an object is 
> missing in .NET assembly.
> Document explicitly that DDLs has to be added using "-assembly" flag upon a 
> .NET node startup. In addition, add the similar info to the troubleshooting 
> doc
> https://apacheignite-net.readme.io/docs/troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4135) .NET: unable to find assembly error

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4135:


https://apacheignite-net.readme.io/docs/standalone-nodes#loading-user-assemblies

> .NET: unable to find assembly error
> ---
>
> Key: IGNITE-4135
> URL: https://issues.apache.org/jira/browse/IGNITE-4135
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> A user can get "unable to find assembly error" at the time when an object is 
> missing in .NET assembly.
> Document explicitly that DDLs has to be added using "-assembly" flag upon a 
> .NET node startup. In addition, add the similar info to the troubleshooting 
> doc
> https://apacheignite-net.readme.io/docs/troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4128) .NET: add documentation and example for EntryProcessor

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4128:


Example added.

There is no EntryProcessor documentation for Java. Denis, can you create that, 
and I'll adapt it to .NET then?

> .NET: add documentation and example for EntryProcessor
> --
>
> Key: IGNITE-4128
> URL: https://issues.apache.org/jira/browse/IGNITE-4128
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Let's add the documentation and example for {{EntryProcessor}} functionality.
> The example should be similar to Java's {{CacheEntryProcessorExample}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4128) .NET: add documentation and example for EntryProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4128:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-4128 .NET: Add EntryProcessorExample



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

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

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

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


commit e6a81ae10ea2aba07e0c217c71d23dcce4eba552
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:53:09Z

Adding the processor

commit 98ed204d524bda8d32f35cd9954a154988002003
Author: Pavel Tupitsyn 
Date:   2016-11-17T13:14:47Z

wip

commit c19d48d1506d2648649d31ce7f9a4b0ab2daca4d
Author: Pavel Tupitsyn 
Date:   2016-11-17T13:24:19Z

Example done




> .NET: add documentation and example for EntryProcessor
> --
>
> Key: IGNITE-4128
> URL: https://issues.apache.org/jira/browse/IGNITE-4128
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Let's add the documentation and example for {{EntryProcessor}} functionality.
> The example should be similar to Java's {{CacheEntryProcessorExample}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2294) Implement SQL DML (insert, update, delete) clauses.

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-2294:
-

Made fixes for all comments given by Vlad (here) and Sergi (on github) where 
needed (few points had been agreed on).

Additionally made DML logic more "flat" (after a statement has been analyzed 
and cached for the first time, subsequent runs will perform faster than the 
first one) and got rid of some new code duplication.

Old classes (IgniteH2Indexing, GridSqlQuerySplitter, GridReduceQueryExecutor) 
remain virtually unchanged.

Please advise on the next steps.

> Implement SQL DML (insert, update, delete) clauses.
> ---
>
> Key: IGNITE-2294
> URL: https://issues.apache.org/jira/browse/IGNITE-2294
> Project: Ignite
>  Issue Type: Wish
>Reporter: Sergi Vladykin
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 1.8
>
>
> We need to add parsing for all the listed SQL commands and translate them 
> into respective cache operations (putIfAbstent, put, remove).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4231) Hangs on compute result serialization error

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-4231:

Fix Version/s: (was: 1.8)
   2.0

> Hangs on compute result serialization error
> ---
>
> Key: IGNITE-4231
> URL: https://issues.apache.org/jira/browse/IGNITE-4231
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Dmitry Karachentsev
>Assignee: Semen Boikov
> Fix For: 2.0
>
>
> Compute task may hang if was thrown exception on result serialization. This 
> should be properly handled and responded to client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (IGNITE-4100) Some typos and missing references in cpp platform instructions

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova reopened IGNITE-4100:
-

Please, change odbc/README.txt to $IGNITE_HOME/platforms/cpp/odbc/README.txt in 
DEVNOTES as well

> Some typos and missing references in cpp platform instructions
> --
>
> Key: IGNITE-4100
> URL: https://issues.apache.org/jira/browse/IGNITE-4100
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> 1) Fix typo in $IGNITE_HOME/platforms/cpp/DEVNOTES.txt, line 40:
> {{heasders}} -> {{headers}}
> 2)  Fix typo in  $IGNITE_HOME/platforms/cpp/README.txt, line 5:
> {{you can execute perform}} -> {{you can perform}} or {{you can execute}}
> 3) Fix typo in  $IGNITE_HOME/platforms/cpp/README.txt, line 52:
> {{odbc.dll}} -> {{ignite.odbc.dll}}
> 4) $IGNITE_HOME/platforms/cpp/DEVNOTES.txt: 
> add some note (to both linux and windows sections or to common section) that 
> user should refer to $IGNITE_HOME/platforms/cpp/odbc/README.txt  to install 
> odbc driver
> 5) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 10 {{Apache Ignite 
> C++ must be built according to instructions for your platform}}:
> add a reference to the instruction $IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 6) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 29 {{Apache Ignite 
> ODBC driver must be built and installed according to instructions for your 
> platform.}}:
> suggest you moving this to {{Common requirements}} (since it's actual for 
> both Linux and Win) and adding a reference to the instruction 
> $IGNITE_HOME/platforms/cpp/odbc/README.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[Fred (JIRA)]

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

Fred commented on IGNITE-3429:
--

That hurts pushing it to 2.0, I havent found a solid way of getting Hibernate 
L2 cache working:
http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities
http://stackoverflow.com/questions/40140645/apache-ignite-hibernate-sessionfactory-serialization-issue
https://issues.apache.org/jira/browse/IGNITE-1794
http://apacheignite.gridgain.org/docs/binary-marshaller

> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries 
> in the Hibernate L2 cache. This class contains {{type}} field and custom 
> {{equals}} logic where the type is used as a helper and does not participate 
> in comparison. Instances of the same type are producing different hash codes 
> in different JVMs, which actually breaks comparison when binary format is 
> used, where byte arrays are compared.
> The issue is described in more detail here: 
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4129) .NET: add documentation and example for near cache

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4129:


Docs added: https://apacheignite-net.readme.io/docs/near-caches

> .NET: add documentation and example for near cache
> --
>
> Key: IGNITE-4129
> URL: https://issues.apache.org/jira/browse/IGNITE-4129
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the near caching are missing on 
> .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/near-caches
> - This example should be used as a reference
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/NearCacheExample.cs
> However, we have to improve it by showing that the near cache is really used 
> (metrics or event listeners or something else)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4129) .NET: add documentation and example for near cache

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4129:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-4129 .NET: Add NearCacheExample



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

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

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

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


commit 4b23bf3ccc1489d91f64bc29d4eb649dec037941
Author: Pavel Tupitsyn 
Date:   2016-11-17T11:53:18Z

IGNITE-4129 .NET: add documentation and example for near cache

commit fb099c195167efc53aee1c75e588e176feb66470
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:06:40Z

Merge branch 'master' into ignite-4129

commit 11ec72a03194bb361a04401505b0bc950d51f53c
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:14:07Z

wip

commit f7b67d284340259ad3aa858b645c136320ddf6c5
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:21:50Z

wip

commit fd7e1f60802eb0dba37a49abe4cd740551e0db2e
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:24:23Z

Example done

commit 9a97d11a7f6c1fc0ea31c423b629117f1d8a48a6
Author: Pavel Tupitsyn 
Date:   2016-11-17T12:26:44Z

wip




> .NET: add documentation and example for near cache
> --
>
> Key: IGNITE-4129
> URL: https://issues.apache.org/jira/browse/IGNITE-4129
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the near caching are missing on 
> .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/near-caches
> - This example should be used as a reference
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/NearCacheExample.cs
> However, we have to improve it by showing that the near cache is really used 
> (metrics or event listeners or something else)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-3705) Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova closed IGNITE-3705.
---
Assignee: Ksenia Rybakova  (was: Igor Sapego)

> Warnings when build ignite and ignite-example cpp projects with Visual Studio 
> 2015 (v140) toolset
> -
>
> Key: IGNITE-3705
> URL: https://issues.apache.org/jira/browse/IGNITE-3705
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
> Environment: Windows 2010, Visual Studio 2015
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>Priority: Minor
>  Labels: cpp
> Fix For: 1.8
>
>
> The following warnings apper when build ignite and ignite-example cpp 
> projects with Visual Studio 2015 (v140) toolset:
> {noformat}
> platforms\cpp\common\include\ignite/ignite_error.h(90): warning C4275: non 
> dll-interface class 'std::exception' used as base for dll-interface class 
> 'ignite::IgniteError'
> C:\Program Files (x86)\Microsoft Visual Studio 
> 14.0\VC\include\vcruntime_exception.h(43): note: see declaration of 
> 'std::exception'
> platforms\cpp\common\include\ignite/ignite_error.h(89): note: see declaration 
> of 'ignite::IgniteError'
> cl : Command line warning D9025: overriding '/sdl-' with '/GS-'
> {noformat}
> Steps to reproduce:
> - Install VS 2015 and SDK 8.1
> - Open %IGNITE_HOME%\platforms\cpp\project\vs\ignite.sln and 
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln solutions 
> in VS
> - Set "Visual Studio 2015 (v140)" as Platform Toolset and "8.1" as Target 
> Platform Version  in projects properties
> - Build solutions
> Expected: 
> - no errors and warnings



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4095) .NET: Deprecated CompiledQuery is used in examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4095.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .NET: Deprecated CompiledQuery is used in examples
> --
>
> Key: IGNITE-4095
> URL: https://issues.apache.org/jira/browse/IGNITE-4095
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Replace deprecated API calls in examples (including LINQ)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-3456) Make sure EntryProcessor is always running on a OWNING partition

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-3456:


Assignee: Anton Vinogradov

> Make sure EntryProcessor is always running on a OWNING partition
> 
>
> Key: IGNITE-3456
> URL: https://issues.apache.org/jira/browse/IGNITE-3456
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Anton Vinogradov
>
> Let's say I need to maintain some sort of an aggregate function over a 
> partition. This aggregate is maintained using an entry processor, and before 
> an update this entry processor queries this local aggregate.
> If an entry processor is applied on a partition with a MOVING state, the 
> state of the local aggregate is not valid because not all data has been 
> preloaded. If entry processor is applied on an OWNING partition, the result 
> is guaranteed to be correct.
> Given that we have implemented late affinity assignment when a new node is 
> assigned primary only when rebalancing is finished, this should be already 
> maintained. We just need to add tests verifying the partition state in 
> EntryProcessor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4112) Client is stopped if communication to servers is lost during (re)connect routine.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-4112:


Assignee: Anton Vinogradov

> Client is stopped if communication to servers is lost during (re)connect 
> routine.
> -
>
> Key: IGNITE-4112
> URL: https://issues.apache.org/jira/browse/IGNITE-4112
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Anton Vinogradov
> Fix For: 2.0
>
>
> Consider the following situation for the client which is currently 
> disconnected:
> 1) Link to servers is restored;
> 2) Clients connects successfully;
> 3) Link is broken again after some time.
> Result: client is disconnected.
> But!
> 1) Link to servers is restored;
> 2) Clients is re-connecting;
> 3) Link is broken again before reconnect is finished.
> Result: client might be stopped (for new client it will exit from 
> {{Ignition.start}} routine with exception).
> Apparently, we need to make (re)connect routine "atomic" with respect to 
> concurrent network events. That is, we either reconnect all components 
> successfully, or client is forcefully moved to disconnected state again. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4125:


Example done, output:
{code}
>>> Cache entries layout: [Total=1, Java heap=1, Off-Heap=0, Swap=0]
>>> Cache entries created: 11

>>> Cache entries layout: [Total=11, Java heap=10, Off-Heap=1, Swap=0]
>>> Cache entries created: 21

>>> Cache entries layout: [Total=21, Java heap=10, Off-Heap=9, Swap=2]
>>> Cache entries created: 31

>>> Cache entries layout: [Total=31, Java heap=10, Off-Heap=9, Swap=12]
>>> Cache entries created: 41

>>> Cache entries layout: [Total=41, Java heap=10, Off-Heap=9, Swap=22]
>>> Cache entries created: 51

>>> Cache entries layout: [Total=51, Java heap=10, Off-Heap=9, Swap=32]
>>> Cache entries created: 61

>>> Cache entries layout: [Total=61, Java heap=10, Off-Heap=9, Swap=42]
>>> Cache entries created: 71

>>> Cache entries layout: [Total=71, Java heap=10, Off-Heap=9, Swap=52]
>>> Cache entries created: 81

>>> Cache entries layout: [Total=81, Java heap=10, Off-Heap=9, Swap=62]
>>> Cache entries created: 91

>>> Cache entries layout: [Total=91, Java heap=10, Off-Heap=9, Swap=72]
>>> Waiting for metrics final update...

>>> Cache entries layout: [Total=100, Java heap=10, Off-Heap=9, Swap=81]
{code}

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4201) CPP: fix versioning of C++ libs

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4201:

Description: 
Currently  versions are not set properly in Ignite C++ core libraries names if 
we build this libraries on Linux according to 
$IGNITE_HOME/platforms/cpp/DEVNOTES.txt.

For instance, for version 1.7 names are libignite*-1.6.0.8653 instead of 
libignite*-1.7.0

  was:
Currently  versions are not set properly in Ignite C++ core libraries names if 
we build this libraries on Linux according to 
$IGNITE_HOME/platforms/cpp/DEVNOTES.txt.

For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of 
libignite*-1.7.3


> CPP: fix versioning of C++ libs
> ---
>
> Key: IGNITE-4201
> URL: https://issues.apache.org/jira/browse/IGNITE-4201
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
> Fix For: 1.8
>
>
> Currently  versions are not set properly in Ignite C++ core libraries names 
> if we build this libraries on Linux according to 
> $IGNITE_HOME/platforms/cpp/DEVNOTES.txt.
> For instance, for version 1.7 names are libignite*-1.6.0.8653 instead of 
> libignite*-1.7.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (IGNITE-2693) withKeepBinary and non-binary marshallers

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2693:

Comment: was deleted

(was: 
http://172.25.1.150:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F1244%2Fhead)

> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
>  Labels: newbie
> Fix For: 1.8
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used 
> marshaller. But it obviously causes ClassCastException for non-binary 
> marshallers and should be available only for binary marshaller.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2693:
-

http://172.25.1.150:8111/project.html?projectId=IgniteTests_IgniteTests=pull%2F1244%2Fhead

> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
>  Labels: newbie
> Fix For: 1.8
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used 
> marshaller. But it obviously causes ClassCastException for non-binary 
> marshallers and should be available only for binary marshaller.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2693:
-

Need to re-run tests one more time.

> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
>  Labels: newbie
> Fix For: 1.8
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used 
> marshaller. But it obviously causes ClassCastException for non-binary 
> marshallers and should be available only for binary marshaller.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2693:


GitHub user devozerov opened a pull request:

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

IGNITE-2693



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

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

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

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


commit cfd924ba0ee18debefe9b70475b09c94b0eae087
Author: Oddo Da 
Date:   2016-03-01T03:00:39Z

IGNITE-2693: Fix withKeepBinary() to only return new cache if binary 
marshaller is used

commit 83d87d4720c227cb787f00b45f50f244284dcd5c
Author: Oddo Da 
Date:   2016-03-05T23:55:42Z

IGNITE-2693: fix withKeepBinary() to throw an exception if no binary 
marshaller is used in the cache

commit a8f11c95ec6c81d53a7b906d17936a2a31000133
Author: Oddo Da 
Date:   2016-03-06T01:36:18Z

Fix to allow compile by jdk 1.7

commit 9c18bbee4086f9e76e2d5811c80b20b4402d6fde
Author: Oddo Da 
Date:   2016-03-06T14:27:05Z

Streamline withKeepBinary() tests

commit 2910470de2a5c76a7255662679fa08915b36464a
Author: Oddo Da 
Date:   2016-03-09T16:16:00Z

Fix test to pass after change to withKeepBinary()

commit 150600af176017b93c23ea5bf05e10b6fd1581c2
Author: Oddo Da 
Date:   2016-03-09T18:22:54Z

Fix test to pass after change to withKeepBinary() - add test cache name

commit 31c2dc07554977e7001fa0809df6df66b3980195
Author: Oddo Da 
Date:   2016-03-09T21:28:42Z

Fix tests to match new withKeepBinary() interface

commit 419683708630d0406030332d1c12cd5ed402387a
Author: vozerov-gridgain 
Date:   2016-05-24T09:17:54Z

Merge branch 'IGNITE-2693' of https://github.com/oddodaoddo/ignite into 
ignite-2693

commit b915b850d8f15807efe1e7e0fc416a97c6d4e408
Author: vozerov-gridgain 
Date:   2016-05-24T11:00:27Z

Minors.

commit 7fd543c340bcfc495a108dc4b11278644767070f
Author: vozerov-gridgain 
Date:   2016-05-24T11:12:13Z

Minors.

commit c5390868f57d96e5217f004ae6ac5016f185175d
Author: devozerov 
Date:   2016-11-17T10:50:11Z

Merge branch 'master' into ignite-2693

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheProxy.java




> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
>  Labels: newbie
> Fix For: 1.8
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used 
> marshaller. But it obviously causes ClassCastException for non-binary 
> marshallers and should be available only for binary marshaller.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4116) .NET: documentation and example for client reconnect feature

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4116:


Merged to master. Prachi, please review readme.io docs.

> .NET: documentation and example for client reconnect feature
> 
>
> Key: IGNITE-4116
> URL: https://issues.apache.org/jira/browse/IGNITE-4116
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 1.8
>
> Attachments: Screen Shot 2016-10-31 at 8.53.01 AM.png
>
>
> Presently the documentation and example about the client reconnect feature is 
> missing on .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> (https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnect)
> - The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4116) .NET: documentation and example for client reconnect feature

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4116:


Github user asfgit closed the pull request at:

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


> .NET: documentation and example for client reconnect feature
> 
>
> Key: IGNITE-4116
> URL: https://issues.apache.org/jira/browse/IGNITE-4116
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 1.8
>
> Attachments: Screen Shot 2016-10-31 at 8.53.01 AM.png
>
>
> Presently the documentation and example about the client reconnect feature is 
> missing on .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> (https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnect)
> - The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4116) .NET: documentation and example for client reconnect feature

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4116:


Fixed in code.

> .NET: documentation and example for client reconnect feature
> 
>
> Key: IGNITE-4116
> URL: https://issues.apache.org/jira/browse/IGNITE-4116
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 1.8
>
> Attachments: Screen Shot 2016-10-31 at 8.53.01 AM.png
>
>
> Presently the documentation and example about the client reconnect feature is 
> missing on .NET side. Let's fill this gap.
> - Documentation can be taken from Java side 
> (https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnect)
> - The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3588) Cassandra store should use batching in writeAll and deleteAll methods

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3588:

Fix Version/s: (was: 1.8)
   2.0

> Cassandra store should use batching in writeAll and deleteAll methods
> -
>
> Key: IGNITE-3588
> URL: https://issues.apache.org/jira/browse/IGNITE-3588
> Project: Ignite
>  Issue Type: Improvement
>  Components: ignite-cassandra
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Igor Rudyak
> Fix For: 2.0
>
>
> In current implementation Cassandra store executes all updates one by one 
> when {{writeAll}} or {{deleteAll}} method is called.
> We should add an option to use {{BatchStatement}} instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2909) Checking cache object type in runtime

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2909:

Fix Version/s: (was: 1.8)
   2.0

> Checking cache object type in runtime
> -
>
> Key: IGNITE-2909
> URL: https://issues.apache.org/jira/browse/IGNITE-2909
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladislav Pyatkov
>  Labels: community, important
> Fix For: 2.0
>
>
> In some cases there is necessity to control a type of object that is being
> inserted into a cache.
> Presently this kind of check is accomplished at compile time only relying
> on Java Generics. However it doesn't prevent us from connecting to a
> cluster using a non-generic instance of a cache and put any kind of data in
> it. This may be not a harmful intention but rather a silly developer mistake.
> It's preferable to rely on the cache interceptor based solution:
> - user will create a generic interceptor that will accept "typeName" in its 
> constructor;
> - class of this interceptor will be placed in the classpath of all the nodes;
> - when a new cache is started statically (Spring cfg) or dynamically this 
> interceptor can be set with a particular allowed "typeName";
> - when interceptor is invoked allowed typeId (taken from allowed "typeName") 
> will be compared with a typeID of a key/value being inserted;
> - exception has to be thrown if allowed typeId is not equal to a key/value 
> typeId being inserted.
> We need to allow to throw exceptions from interceptor and provide an example 
> on how perform type validation using interceptors based approach.
> Refer to the discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Controlling-type-of-object-inserted-in-IgniteCache-td8128.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3467) jdbc getTables() returns catalog as null

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3467:

Fix Version/s: (was: 1.8)
   2.0

> jdbc getTables() returns catalog as null
> 
>
> Key: IGNITE-3467
> URL: https://issues.apache.org/jira/browse/IGNITE-3467
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc-driver, SQL
>Affects Versions: 1.6
>Reporter: Alexandre Boudnik
>Assignee: Alexandre Boudnik
>Priority: Critical
> Fix For: 2.0
>
>
> Then some jdbc query tool uses null values as catalog name. An H2 database 
> returns word "DATABASE" in CATALOG column, and then correctly resolves a 
> fully-qualified name. I would recommend to do the same for these metadata.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3468) Missing Primary Key flag in getColumns()

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3468:

Fix Version/s: (was: 1.8)
   2.0

> Missing Primary Key flag in getColumns()
> 
>
> Key: IGNITE-3468
> URL: https://issues.apache.org/jira/browse/IGNITE-3468
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, jdbc-driver, SQL
>Affects Versions: 1.6
>Reporter: Alexandre Boudnik
>Assignee: Alexandre Boudnik
> Fix For: 2.0
>
>
> When implemented it allows BI tools to build more optimal queries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2092) Ignite does not recognize the right number of CPU cores when running under Docker

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2092:

Fix Version/s: (was: 1.8)
   2.0

> Ignite does not recognize the right number of CPU cores when running under 
> Docker
> -
>
> Key: IGNITE-2092
> URL: https://issues.apache.org/jira/browse/IGNITE-2092
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Eduard Yuzlikeev
>  Labels: newbie
> Fix For: 2.0
>
>
> Run Ignite under a Docker container.
> Limit Ignite from using all CPUs by way of Docker settings (which internally 
> uses Linux CGROUPS). 
> Ignite will still report that all available CPUs are used ignoring Docker 
> settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2231:

Fix Version/s: (was: 1.8)
   2.0

> 'Put' cache event treats entry created at lock acquisition time as old value
> 
>
> Key: IGNITE-2231
> URL: https://issues.apache.org/jira/browse/IGNITE-2231
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: wmz7year
>  Labels: important
> Fix For: 2.0
>
> Attachments: EventsProcessingTest.java
>
>
> Subscribe for EVT_CACHE_OBJECT_PUT event on one node and perform 'put' 
> operations from the other to an empty transnational cache.
> The subscriber will receive a notification saying that there was an old value 
> for a key at the time the new was being inserted. In fact the was no an old 
> value, the entry with a {{null}} as a value was generated as a part of 
> implicit lock acquisition.
> This snippet of the code in {{GridCacheMapEntry}} generates a wrong event 
> (innerSet function)
> {noformat}
> if (evt && newVer != null && 
> cctx.events().isRecordable(EVT_CACHE_OBJECT_PUT)) {
> CacheObject evtOld = cctx.unwrapTemporary(old);
> cctx.events().addEvent(partition(),
> key,
> evtNodeId,
> tx == null ? null : tx.xid(),
> newVer,
> EVT_CACHE_OBJECT_PUT,
> val,
> val != null,
> evtOld,
> evtOld != null || hasValueUnlocked(),
> subjId, null, taskName,
> keepBinary);
> }
> {noformat}
> Attached the test that lets reproduce the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1238:

Fix Version/s: (was: 1.8)
   2.0

> Joining node should be discarded in case discovery exchange data can't be 
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: 2.0
>
>
> Currently a node will join even if unmarshalling fails (see 
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected 
> behaviour. For example, a continuous query listener is not deployed on some 
> nodes in topology. Everything works, but some updates are lost. We should 
> discard the node in this case and give a good error message to user with 
> information on how to fix it properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4128) .NET: add documentation and example for EntryProcessor

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4128:

Assignee: Pavel Tupitsyn

> .NET: add documentation and example for EntryProcessor
> --
>
> Key: IGNITE-4128
> URL: https://issues.apache.org/jira/browse/IGNITE-4128
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Let's add the documentation and example for {{EntryProcessor}} functionality.
> The example should be similar to Java's {{CacheEntryProcessorExample}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4136) .NET: document ways on how to manage Ignite Service deployments

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4136:

Assignee: Pavel Tupitsyn

> .NET: document ways on how to manage Ignite Service deployments
> ---
>
> Key: IGNITE-4136
> URL: https://issues.apache.org/jira/browse/IGNITE-4136
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Provide documentation on how to manage deployments of a specific Ignite 
> Service:
> - node filter
> - cluster group
> - affinity based deployment
> Add code snippets near to the text documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4095) .NET: Deprecated CompiledQuery is used in examples

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4095:

Assignee: Pavel Tupitsyn

> .NET: Deprecated CompiledQuery is used in examples
> --
>
> Key: IGNITE-4095
> URL: https://issues.apache.org/jira/browse/IGNITE-4095
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Replace deprecated API calls in examples (including LINQ)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4135) .NET: unable to find assembly error

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4135:

Assignee: Pavel Tupitsyn

> .NET: unable to find assembly error
> ---
>
> Key: IGNITE-4135
> URL: https://issues.apache.org/jira/browse/IGNITE-4135
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> A user can get "unable to find assembly error" at the time when an object is 
> missing in .NET assembly.
> Document explicitly that DDLs has to be added using "-assembly" flag upon a 
> .NET node startup. In addition, add the similar info to the troubleshooting 
> doc
> https://apacheignite-net.readme.io/docs/troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3997) .NET: Readme.io documentation update for 1.8

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3997:

Assignee: Pavel Tupitsyn

> .NET: Readme.io documentation update for 1.8
> 
>
> Key: IGNITE-3997
> URL: https://issues.apache.org/jira/browse/IGNITE-3997
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Update documentation for new features:
> * Logging
> * ASP.NET Session State
> * Entity Framework caching
> etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4173:

Fix Version/s: (was: 1.8)
   2.0

> IgniteSemaphore with failoverSafe enabled doesn't release permits in case 
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in 
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3997) .NET: Readme.io documentation update for 1.8

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3997:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Readme.io documentation update for 1.8
> 
>
> Key: IGNITE-3997
> URL: https://issues.apache.org/jira/browse/IGNITE-3997
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Update documentation for new features:
> * Logging
> * ASP.NET Session State
> * Entity Framework caching
> etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4165) ignite-spark module scaladocs isn't included in Scala API docs

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4165:

Fix Version/s: (was: 1.8)
   2.0

> ignite-spark module scaladocs isn't included in Scala API docs
> --
>
> Key: IGNITE-4165
> URL: https://issues.apache.org/jira/browse/IGNITE-4165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
> Fix For: 2.0
>
>
> Ignie Scala API docs contains only Scalar scaladoc but not ignite-spark 
> scaladoc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3997) .NET: Readme.io documentation update for 1.8

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3997:

Fix Version/s: (was: 2.0)
   1.8

> .NET: Readme.io documentation update for 1.8
> 
>
> Key: IGNITE-3997
> URL: https://issues.apache.org/jira/browse/IGNITE-3997
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Update documentation for new features:
> * Logging
> * ASP.NET Session State
> * Entity Framework caching
> etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4241) Web condole: Failed execute query after node restart.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-4241:
-

 Summary: Web condole: Failed execute query after node restart.
 Key: IGNITE-4241
 URL: https://issues.apache.org/jira/browse/IGNITE-4241
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 1.8
Reporter: Vasiliy Sisko
Assignee: Andrey Novikov


# Run one node with data,
# Execute query on SQL page,
# Restart node,
# Execute query again.

Console in results area show message:
Error: Failed to clear query results. Nodes are not available: [d539449e]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3347) CacheEvictableEntryImpl does not take CopyOnRead mode into account

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3347:

Fix Version/s: (was: 1.8)
   2.0

> CacheEvictableEntryImpl does not take CopyOnRead mode into account
> --
>
> Key: IGNITE-3347
> URL: https://issues.apache.org/jira/browse/IGNITE-3347
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> CacheConfiguration.setCopyOnRead(false) causes CacheObjectImpl to hold both 
> val and valBytes, increasing memory usage.
> CacheEvictableEntryImpl.size method does not take this into account.
> As a result, memory-based eviction policies work incorrectly when 
> copyOnRead=false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3608) QuerySqlFunction methods with Object type var args do not work

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3608:

Fix Version/s: (was: 1.8)
   2.0

> QuerySqlFunction methods with Object type var args do not work
> --
>
> Key: IGNITE-3608
> URL: https://issues.apache.org/jira/browse/IGNITE-3608
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: 1.5.0.final, 1.6
>Reporter: Edward Kaganovich
>  Labels: SQL, UDF
> Fix For: 2.0
>
>
> We often use interactive sql consoles to query caches.  Several field values 
> as well as _key in caches are stored as objects.  To support queries by these 
> fields we have registered a generic UDF that should let us instantiate 
> certain types:
> {code}  @QuerySqlFunction 
> public static Object t(String clz, Object... ctorArgs) throws
> Exception {
> Class c = Class.forName(keyClz); 
> Class[] argTypes = new Class[ctorArgs.length]; 
> for (int i=0; i < ctorArgs.length; i++) { 
> argTypes[i] = ctorArgs[i].getClass(); 
> } 
> Constructor ctor = c.getConstructor(argTypes); 
> return ctor.newInstance(ctorArgs); 
> }
> {code}
> Unfortunately Ignite fails to find and execute this function for the 
> following SQL:
> {color:blue}select t('java.lang.String', 'key20'){color}{color:red} <- 
> Fails{color}
> However, there is no problems with this function:
> {code}   @QuerySqlFunction 
> public static Object t1(String clz, String... ctorArgs) throws Exception 
> { 
> return t(clz, ctorArgs);
> }
> {code}
> {color:blue}select t1('java.lang.String', 'key20'){color}{color:green} <- 
> Works as expected{color}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3053) Document cache store per-node behavior

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3053:

Fix Version/s: (was: 1.8)
   2.0

> Document cache store per-node behavior
> --
>
> Key: IGNITE-3053
> URL: https://issues.apache.org/jira/browse/IGNITE-3053
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> Frequent user question is "which node does write-through/write-behind".
> For example: 
> http://apache-ignite-users.70518.x6.nabble.com/Persistent-CacheStore-and-backups-td1368.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3690) Log Message Glossary

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3690:

Fix Version/s: (was: 1.8)
   2.0

> Log Message Glossary
> 
>
> Key: IGNITE-3690
> URL: https://issues.apache.org/jira/browse/IGNITE-3690
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 1.4
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> It's time for Ignite to create a page which lists ALL the log messages, their 
> common causes and potential solutions.
> Probably it makes sense to assign an unique ID for the most well-know errors 
> so that a user is able to look up an error in the glossary quicker.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3679) ClassNotFoundException

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3679:

Fix Version/s: (was: 1.8)
   2.0

> ClassNotFoundException
> --
>
> Key: IGNITE-3679
> URL: https://issues.apache.org/jira/browse/IGNITE-3679
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: SonixLegend
> Fix For: 2.0
>
>
> cache.savePairs(rdd, false) is work, but if change to "true", the program is 
> failure.
> case class Test(@(QuerySqlField @field)(index = true) id: Long, 
> @(QuerySqlField @field)(index = true) test: String)
> val cache: IgniteRDD[Long, Test] = igniteContext.fromCache("spark")
> val rdd: RDD[(Long, Test)] = sparkContext.parallelize(1 to 1, 10).map(i 
> => (i, Test(i, "Test")))
> cache.savePairs(rdd, true)
> println(cache.count)
>   
>   
>   
>class="org.apache.ignite.configuration.CacheConfiguration">
>   
>value="PARTITIONED" />
>   
>value="false" />
>value="ONHEAP_TIERED" />
>value="#{10 * 1024L * 1024L * 1024L}" />
>   
>class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>name="maxSize" value="100" />
>   
>   
>value="TRANSACTIONAL" />
>value="1" />
>   
>  
> class="org.apache.ignite.cache.store.jdbc.CacheJdbcBlobStoreFactory">
>name="connectionUrl"
>   
> value="jdbc:h2:tcp://localhost:9092//mnt/data/data/ignite/spark;AUTO_RECONNECT=TRUE"
>  />
>value="sa" />
>   
>   
>value="true" />
>value="true" />
>value="true" />
>   
>   
>   
> Caused by: java.lang.ClassNotFoundException: com.newtouch.sample.Test
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8350)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:662)
>   ... 75 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3885) .NET: Describe development process on Wiki

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3885:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Describe development process on Wiki
> --
>
> Key: IGNITE-3885
> URL: https://issues.apache.org/jira/browse/IGNITE-3885
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.0
>
>
> Ignite wiki: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home
> Add .NET development process page:
> * Coding guidelines (naming conventions, etc)
> * Project structure
> * Code inspections, how to run locally and on TC
> * Test coverage
> * How to build (AnyCPU nuances, NuGet, embedded CPP part, Java, etc)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3458) poor performance on the function “primaryEntrySet()”

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3458:

Fix Version/s: (was: 1.8)
   2.0

> poor performance on the function “primaryEntrySet()”
> 
>
> Key: IGNITE-3458
> URL: https://issues.apache.org/jira/browse/IGNITE-3458
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.6
>Reporter: bluehu
>Priority: Minor
>  Labels: primaryEntrySet
> Fix For: 2.0
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> the implement of primaryEntrySet() in ignite 1.6 is this:
> {code:title=GridCacheAdapter.java|borderStyle=solid}
> /**
>  * @return Primary entry set.
>  */
> public Set> primaryEntrySet() {
> return new 
> EntrySet(map.entrySet(CU.cachePrimary(ctx.grid().affinity(ctx.name()), 
> ctx.localNode(;
> }
> {code}
> this function may scan all the partitions including backup partitions on 
> local node, then filter each entry with this CacheEntryPredicate:
> {code:title=GridCacheUtils.java|borderStyle=solid}
> /**
>  * @param aff Affinity.
>  * @param n Node.
>  * @return Predicate that evaluates to {@code true} if entry is primary 
> for node.
>  */
> public static CacheEntryPredicate cachePrimary(
> final Affinity aff,
> final ClusterNode n
> ) {
> return new CacheEntryPredicateAdapter() {
> @Override public boolean apply(GridCacheEntryEx e) {
> return aff.isPrimary(n, e.key());
> }
> };
> }
> {code}
> I think it has poor performance. 
> Since we can get the primary partitions id of localnode from 
> GridAffinityAssignment:
> {code:title=GridAffinityAssignment.java|borderStyle=solid}
> /**
>  * Get primary partitions for specified node ID.
>  *
>  * @param nodeId Node ID to get primary partitions for.
>  * @return Primary partitions for specified node ID.
>  */
> public Set primaryPartitions(UUID nodeId) {
> Set set = primary.get(nodeId);
> return set == null ? Collections.emptySet() : set;
> }
> {code}
> why not get primary partitions directly(not including backup partitions) and 
> then return all the entry of primary partitions(no need use 
> CacheEntryPredicate to judge each entry)?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3222) IgniteCache.invokeAll for all cache entries

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3222:

Fix Version/s: (was: 1.8)
   2.0

> IgniteCache.invokeAll for all cache entries
> ---
>
> Key: IGNITE-3222
> URL: https://issues.apache.org/jira/browse/IGNITE-3222
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> Implement an invokeAll overload that processes all cache keys (not some 
> specific set).
> Proposed signature:
> {code}
> public void invokeAll(CacheEntryProcessor entryProcessor, Object... 
> args);
> public  Map invokeAll(CacheEntryProcessor V, T> entryProcessor, boolean returnAffectedOnly, Object... args);
> {code}
> This will apply the specified processor to all cache entries.
> First method does not return anything.
> Second method either returns all results for all entries, or only for entries 
> that have been changed by the processor in any way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2895) OS info in console is incorrect when using x86 JRE on x64 Windows

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2895:

Fix Version/s: (was: 1.8)
   2.0

> OS info in console is incorrect when using x86 JRE on x64 Windows
> -
>
> Key: IGNITE-2895
> URL: https://issues.apache.org/jira/browse/IGNITE-2895
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Trivial
> Fix For: 2.0
>
>
> Steps:
> * Use any x64 Windows (*nix might work too)
> * Use x86 JRE (by setting JAVA_HOME accordingly)
> * Run any test or example, see console log:
> {code} OS: Windows 8 6.2 x86{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2907) GridServiceNotFoundException is not descriptive

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2907:

Fix Version/s: (was: 1.8)
   2.0

> GridServiceNotFoundException is not descriptive
> ---
>
> Key: IGNITE-2907
> URL: https://issues.apache.org/jira/browse/IGNITE-2907
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Minor
> Fix For: 2.0
>
>
> "Service node found" message does not make sense.
> * Message should be fixed
> * More details should be added (why is this situation possible, how to fix it)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3271) Can't start a node with default config when no pause (-np) parameter is set

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3271:

Fix Version/s: (was: 1.8)
   2.0

> Can't start a node with default config when no pause (-np) parameter is set
> ---
>
> Key: IGNITE-3271
> URL: https://issues.apache.org/jira/browse/IGNITE-3271
> Project: Ignite
>  Issue Type: Bug
>  Components: community
>Affects Versions: 1.6
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> If to start an Ignite instance with "-np" argument then the node is not able 
> to start with the exception below.
> {code}
> ./ignite.sh -np
> Invalid arguments: -np
> Usage:
>./ignite.sh [?]|[path {-v}{-np}]|[-i]
>Where:
>?, /help, -help, - show this message.
>-v   - verbose mode (quiet by default).
>-np  - no pause on exit (pause by default)
>-nojmx   - disable JMX monitoring (enabled by default)
>-i  - interactive mode (choose configuration file from
> list).
>path- path to Spring XML configuration file.
>  Path can be absolute or relative to IGNITE_HOME.
> Spring file should contain one bean definition of Java type
> 'org.apache.ignite.configuration.IgniteConfiguration'. Note that bean will
> be
> fetched by the type and its ID is not used./
> {code}
> However if to set a configuration file parameter then everything will work 
> fine
> {code}
> ./ignite.sh -np ../examples/config/example-ignite.xml 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2955) Exception in CacheStore.sessionEnd breaks the cache

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2955:

Fix Version/s: (was: 1.8)
   2.0

> Exception in CacheStore.sessionEnd breaks the cache
> ---
>
> Key: IGNITE-2955
> URL: https://issues.apache.org/jira/browse/IGNITE-2955
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.0
>
>
> If there is an exception in user implementation of CacheStore.sessionEnd, 
> cache becomes unusable: TransactionRollbackException is thrown on any 
> consequent cache.put().
> Configuration:
> * 1 node
> * Local transactional write-through cache with a store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3244) Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3244:

Fix Version/s: (was: 1.8)
   2.0

> Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
> ---
>
> Key: IGNITE-3244
> URL: https://issues.apache.org/jira/browse/IGNITE-3244
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Minor
> Fix For: 2.0
>
>
> If to put a custom object array into a cache like this one
> {code}
> TestObject[] arr = new TestObject[] {new TestObject(i)};
> cache.put(0, arr);
> {code}
> then it will be serialized as Object[] array in 
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} method.
> This leads to the situation when object's array type is lost and on cache.get 
> the code below produces {{ClassCastException}}
> {code}
> TestObject[] obj = cache.get(i);
> {code}
> The full test is already added into 
> {{GridCacheBinaryObjectsAbstractSelfTest.testCustomArrays}}.
> To fix the issue we have to revisit logic of 
> {{CacheObjectBinaryProcessorImpl.marshallToBinary}} and 
> {{CacheObjectContext.unwrapBinary}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3137) IgniteDataStreamer silently hangs if exception happens on a remote side

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3137:

Fix Version/s: (was: 1.8)
   2.0

> IgniteDataStreamer silently hangs if exception happens on a remote side
> ---
>
> Key: IGNITE-3137
> URL: https://issues.apache.org/jira/browse/IGNITE-3137
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
> Fix For: 2.0
>
> Attachments: CacheDataStreamerExample.java, ExampleNodeStartup.java
>
>
> If an exception happens on a remote side during the streaming 
> IgniteDataStreamer can either not receive an ack for a sent batch or not 
> process an error response properly on a streaming side. 
> This will lead to the situation that the side that does streaming will hang 
> indefinitely.
> Attaching a simple code that reproduces the issue. Please note that exception 
> can be of other kind.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2839) Working paths are hard-coded in bin/ scripts and log4j xml

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2839:

Fix Version/s: (was: 1.8)
   2.0

> Working paths are hard-coded in bin/ scripts and log4j xml
> --
>
> Key: IGNITE-2839
> URL: https://issues.apache.org/jira/browse/IGNITE-2839
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: knivit
>Priority: Minor
>  Labels: community
> Fix For: 2.0
>
>
> Some working paths are hard-coded, for example
> # bin/ignite.sh:
> {code}
> RESTART_SUCCESS_FILE="${IGNITE_HOME}/work/ignite_success_${RANDOM_NUMBER}"
> {code}
> # config/ignite-log4j.xml, config/ignite-log4j2.xml
> {code}
> 
> {code}
> Usually an installation (i.e. $IGNITE_HOME) folder is read-only for non-root 
> users so Ignite won't start.
> Need to introduce IGNITE_WORK_DIR, IGNITE_LOG_DIR variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3081) NearCacheConfiguration incorrectly extends MutableConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3081:

Fix Version/s: (was: 1.8)
   2.0

> NearCacheConfiguration incorrectly extends MutableConfiguration
> ---
>
> Key: IGNITE-3081
> URL: https://issues.apache.org/jira/browse/IGNITE-3081
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, community
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.0
>
>
> NearCacheConfiguration extends MutableConfiguration, but does not use 
> anything inherited.
> This confuses both developers and users (there were questions in Gitter).
> Two solutions:
> * Remove this base class
> * Or, if compatibility is needed, override all members and throw exceptions 
> from them; update documentation to make this clear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2511:

Fix Version/s: (was: 1.8)
   2.0

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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2421:

Fix Version/s: (was: 1.8)
   2.0

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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2768) Public API for data structures should be guarded from being invoked after node is stopped

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2768:

Fix Version/s: (was: 1.8)
   2.0

> Public API for data structures should be guarded from being invoked after 
> node is stopped
> -
>
> Key: IGNITE-2768
> URL: https://issues.apache.org/jira/browse/IGNITE-2768
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.6
>Reporter: Vladisav Jelisavcic
>Priority: Minor
> Fix For: 2.0
>
>
> For such functionality we have GridKernalGateway, which guards all public API 
> calls from being invoked after node is stopped. Public method implementations 
> should be surrounded with ctx.gateway().readLock() and 
> ctx.gateway().readUnlock(). As an example see GridExecutorService.
> This ticket is based on conversation: 
> [https://issues.apache.org/jira/browse/IGNITE-2735?focusedCommentId=15181493=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15181493]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2436) GridCacheWriteBehindStore flushes a single value when the queue size is reached

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2436:

Fix Version/s: (was: 1.8)
   2.0

> GridCacheWriteBehindStore flushes a single value when the queue size is 
> reached
> ---
>
> Key: IGNITE-2436
> URL: https://issues.apache.org/jira/browse/IGNITE-2436
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> When the queue size is reached we have to flush a batch as well rather than a 
> single value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2422) Prevent serialization of BinaryObjectBuilder

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2422:

Fix Version/s: (was: 1.8)
   2.0

> Prevent serialization of BinaryObjectBuilder
> 
>
> Key: IGNITE-2422
> URL: https://issues.apache.org/jira/browse/IGNITE-2422
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>  Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> Presently it's possible to serialize {{BinaryObjectBuilder}} but it will lead 
> to the errors at deserialization stage.
> We have to prevent serialization of the builder throwing a meaningful 
> exception.
> Run an example from attach and you will see an exception that is caused by 
> the serialization/deserialization of the builder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2452) .NET: Custom discovery SPI

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2452:

Fix Version/s: (was: 1.8)
   2.0

> .NET: Custom discovery SPI
> --
>
> Key: IGNITE-2452
> URL: https://issues.apache.org/jira/browse/IGNITE-2452
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-1906 introduced predefined discovery configuration in C# code. Need to 
> allow custom SPI similar to Java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2399) Add asynchronous acquire to IgniteSemaphore

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2399:

Fix Version/s: (was: 1.8)
   2.0

> Add asynchronous acquire to IgniteSemaphore
> ---
>
> Key: IGNITE-2399
> URL: https://issues.apache.org/jira/browse/IGNITE-2399
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Reporter: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> Usually a permit acquisition is followed by an action, followed by a release 
> of the permit. A simple enhancement to the existing Semaphore API can be made 
> that enables asynchronous acquire:
>  IgniteFuture acquireAndExecute(Callable action, int numPermits);
> The method would immediately return a future to be later completed by the 
> action's result. Permits are to be released after the future is completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2425) BinaryObject.readField() called for an object Java array field reads objects class

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2425:

Fix Version/s: (was: 1.8)
   2.0

> BinaryObject.readField() called for an object Java array field reads objects 
> class 
> ---
>
> Key: IGNITE-2425
> URL: https://issues.apache.org/jira/browse/IGNITE-2425
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>  Labels: important
> Fix For: 2.0
>
> Attachments: ExampleNodeStartup.java
>
>
> If there is a {{BinaryObject}} that has a field that refers to an array of 
> some custom user objects then during the time {{BinaryObject.field()}} is 
> called the class of this custom will be read. This can lead to 
> {{ClassNotFoundException}} on a server side or another ones related.
> In the attach example the following issue is demonstrated using 
> {{BinaryObjectBuilder}} which class is not listed in classnames.properties.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2569) Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2569:

Fix Version/s: (was: 1.8)
   2.0

> Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE
> -
>
> Key: IGNITE-2569
> URL: https://issues.apache.org/jira/browse/IGNITE-2569
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Priority: Minor
> Fix For: 2.0
>
>
> IgniteKernal could stop GridComponents during start without calling 
> stopKernal before it. Showcase: 
> {noformat}
> 19:09:58,301][ERROR][async-runner-1][IgniteClientReconnectCacheTest3] Failed 
> to pre-stop processor: GridProcessorAdapter []
> java.lang.AssertionError
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:109)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:884)
>  at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1814)
>  at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1760)
>  at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:932)
>  at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1687)
>  at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1546)
>  at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1002)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:533)
>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:514)
>  at org.apache.ignite.Ignition.start(Ignition.java:322)
>  at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest$8.call(IgniteClientReconnectCacheTest.java:700)
>  at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest$8.call(IgniteClientReconnectCacheTest.java:697)
>  at 
> org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:758)
>  at 
> org.apache.ignite.testframework.GridTestUtils$8.call(GridTestUtils.java:1054)
>  at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
> This can cause different NPE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2002) Data streamer does not work with peerClassLoadingEnabled

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2002:

Fix Version/s: (was: 2,0)
   2.0

> Data streamer does not work with peerClassLoadingEnabled
> 
>
> Key: IGNITE-2002
> URL: https://issues.apache.org/jira/browse/IGNITE-2002
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, streaming
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.0
>
>
> Add  to spring config, 
> run streamer tests or examples, there are exceptions in Java and flush hangs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2027) Need to add README.txt to "memcached" and "rest" folders under "examples"

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2027:

Fix Version/s: (was: 1.8)
   2.0

> Need to add README.txt to "memcached" and "rest" folders under "examples"
> -
>
> Key: IGNITE-2027
> URL: https://issues.apache.org/jira/browse/IGNITE-2027
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Setrakyan
> Fix For: 2.0
>
>
> Every folder under "examples" should have a {{README.txt}} file. We should 
> add this file to:
> - {{examples/memcached}}
> - {{examples/rest}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2337) SSL & TLS use distinguished name of the certificate (DN)

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2337:

Fix Version/s: (was: 1.8)
   2.0

> SSL & TLS use distinguished name of the certificate (DN)
> 
>
> Key: IGNITE-2337
> URL: https://issues.apache.org/jira/browse/IGNITE-2337
> Project: Ignite
>  Issue Type: New Feature
>  Components: 1.4
>Reporter: Andrey Kartashov
>  Labels: community, newbie
> Fix For: 2.0
>
>
> Can you add the use of SSLPEERNAME for SslContextFactory parameter to check 
> distinguished name of the certificate. It is necessary to use certificates 
> signed by the certification authority. To get rid of certificate exchange.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2339) Distributed collections unwrap Binary objects

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2339:

Fix Version/s: (was: 1.8)
   2.0

> Distributed collections unwrap Binary objects
> -
>
> Key: IGNITE-2339
> URL: https://issues.apache.org/jira/browse/IGNITE-2339
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
>  Labels: community
> Fix For: 2.0
>
>
> Ignite distributed Queue and Set can held binary objects as values.
> This can lead to {{ClassNotFoundException}} in cases when a binary value is 
> unintentionally deserialized on a server node that doesn't have a class 
> definition in its class path.
> As an example the following exception can arise when {{Queue.poll}} method is 
> executed on a server node
> {noformat}
> [11:27:38,159][SEVERE][pub-#7%null%][GridDhtAtomicCache]  
> Unexpected exception during cache update
> class org.apache.ignite.binary.BinaryInvalidTypeException: ignitetest.Task
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:492)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
>   at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
>   at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
>   at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:145)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheReturn.initValue(GridCacheReturn.java:193)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheReturn.(GridCacheReturn.java:110)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2040)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1319)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1194)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:457)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1400(GridNearAtomicUpdateFuture.java:72)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:417)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$19.apply(GridDhtAtomicCache.java:994)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$19.apply(GridDhtAtomicCache.java:992)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:700)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.removeAllAsync0(GridDhtAtomicCache.java:992)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAndRemoveAsync(GridDhtAtomicCache.java:600)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAndRemove(GridDhtAtomicCache.java:592)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl.poll(GridAtomicCacheQueueImpl.java:83)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueProxy.poll(GridCacheQueueProxy.java:416)
>   at ignitetest.Test.lambda$0(Test.java:36)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
>   at 
> 

[jira] [Updated] (IGNITE-2307) IgniteCache.removeAll method doesn't notify eviction policy in case of atomic cache.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2307:

Fix Version/s: (was: 1.8)
   2.0

> IgniteCache.removeAll method doesn't notify eviction policy in case of atomic 
> cache.
> 
>
> Key: IGNITE-2307
> URL: https://issues.apache.org/jira/browse/IGNITE-2307
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4, 1.5.0.final
>Reporter: Andrey Gura
> Fix For: 2.0
>
>
> {{IgniteCache.removeAll}} method doesn't notify configured eviction policy in 
> case of {{CacheAtomicityMode}} is {{ATOMIC}}.
> Bug can be reproduced using test case in the following PR: 
> https://github.com/apache/ignite/pull/387



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2002) Data streamer does not work with peerClassLoadingEnabled

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2002:

Fix Version/s: (was: 1.8)
   2,0

> Data streamer does not work with peerClassLoadingEnabled
> 
>
> Key: IGNITE-2002
> URL: https://issues.apache.org/jira/browse/IGNITE-2002
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, streaming
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.0
>
>
> Add  to spring config, 
> run streamer tests or examples, there are exceptions in Java and flush hangs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1971) Refactor various streamers implementations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1971:

Fix Version/s: (was: 1.8)
   2.0

> Refactor various streamers implementations
> --
>
> Key: IGNITE-1971
> URL: https://issues.apache.org/jira/browse/IGNITE-1971
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> Re-visit streamers implementations and should address at least the following 
> points below.
> 1) {{start}} method in streamers implementations throws 
> {{IllegalArgumentException}}.
> According to the contract of IllegalArgumentException this exception is 
> thrown only when an invalid argument is passed into the function. However no 
> argument is passed to the method at all and we shouldn't throw this exception 
> from this point of execution.
> My suggestion is to use org.apache.ignite.IgniteIllegalStateException if we 
> don't find better alternative. See how it's used in Ignite.ignite() method 
> description.
> 2) Streamers perform the same basics checks in their implementation of 
> {{start}} method.
> It makes sense to add {{start}} method to StreamAdapter and perform there 
> basic checks that are the same for every streamer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1948:

Fix Version/s: (was: 1.8)
   2.0

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1719) [Test] GridUpdateNotifierSelfTest.testNotifier fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1719:

Fix Version/s: (was: 1.8)
   2.0

> [Test] GridUpdateNotifierSelfTest.testNotifier fails
> -
>
> Key: IGNITE-1719
> URL: https://issues.apache.org/jira/browse/IGNITE-1719
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> The test fails with timeout: 
> {code}
> java.util.concurrent.TimeoutException: Test has been timed out 
> [test=testNotifier, timeout=3]
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1630)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)