[jira] [Commented] (IGNITE-3345) Implement support for optional key type in REST HTTP get command

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-3345:
---

I think we should do the same for all operations that modify the cache.

> Implement support for optional key type in REST HTTP get command
> 
>
> Key: IGNITE-3345
> URL: https://issues.apache.org/jira/browse/IGNITE-3345
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
> Fix For: 1.7
>
>
> It seems that in current implementation 
> (https://apacheignite.readme.io/docs/rest-api#get)
> GET command could work only with String keys.
> We can add optional parameter "keyType" and implement support for common 
> built-in types such as Integer, Long, UUID,... and user classes that a valid 
> JavaBeans.
> Sample: http://host:port/ignite?cmd=get=1=myCache=Long



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

[jira] [Assigned] (IGNITE-945) HTTP REST prepend/append commands failed

[Saikat Maitra (JIRA)]

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

Saikat Maitra reassigned IGNITE-945:


Assignee: Saikat Maitra  (was: Marko Jevtic)

> HTTP REST prepend/append commands failed
> 
>
> Key: IGNITE-945
> URL: https://issues.apache.org/jira/browse/IGNITE-945
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>  Labels: newbie
>
> Requests 
> http://localhost:8080/ignite?cacheName=partitioned_cache=1=prepend=p
> http://localhost:8080/ignite?cacheName=partitioned_cache=1=append=a
> returns same error:
> {noformat}
> {"error":"Failed to start transaction on non-transactional cache: 
> partitioned_cache","response":null,"sessionToken":"","successStatus":1}
> {noformat}
> Node output is following:
> {noformat}
> [14:01:32,555][SEVERE][ignite-#12%pub-null%][GridRestProcessor] Failed to 
> handle request: CACHE_PREPEND
> class org.apache.ignite.IgniteCheckedException: Failed to start transaction 
> on non-transactional cache: partitioned_cache
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6732)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:901)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to start 
> transaction on non-transactional cache: partitioned_cache
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.checkTransactional(IgniteTransactionsImpl.java:193)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.txStartEx(IgniteTransactionsImpl.java:121)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.txStartEx(GridCacheAdapter.java:3239)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.txStartEx(GridCacheProxyImpl.java:808)
>   at 
> org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler$1.call(GridCacheCommandHandler.java:405)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6124)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:893)
>   ... 4 more
> {noformat}
> Is there a limitation for use non-transactional caches for prepend/append 
> commands?



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

[jira] [Closed] (IGNITE-3252) Web console: add validator to Package field in Import metadata dialog

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko closed IGNITE-3252.
-
Assignee: (was: Vasiliy Sisko)

Tested.

> Web console: add validator to Package field in Import metadata dialog
> -
>
> Key: IGNITE-3252
> URL: https://issues.apache.org/jira/browse/IGNITE-3252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.7
>
>
> Currently this field shows error message in case of invalid value, but the 
> field has no red frame and triangle.



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

[jira] [Created] (IGNITE-3345) Implement support for optional key type in REST HTTP get command

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3345:


 Summary: Implement support for optional key type in REST HTTP get 
command
 Key: IGNITE-3345
 URL: https://issues.apache.org/jira/browse/IGNITE-3345
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
 Fix For: 1.7


It seems that in current implementation 
(https://apacheignite.readme.io/docs/rest-api#get)
GET command could work only with String keys.

We can add optional parameter "keyType" and implement support for common 
built-in types such as Integer, Long, UUID,... and user classes that a valid 
JavaBeans.

Sample: http://host:port/ignite?cmd=get=1=myCache=Long



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

[jira] [Commented] (IGNITE-3330) CPP: Implement Cache::Invoke method.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3330:


GitHub user isapego opened a pull request:

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

IGNITE-3330: Cache::Invoke method implemented.



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

$ git pull https://github.com/isapego/ignite ignite-1680

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

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


commit 2ccbad0ca93cdb0987bd4fabe9f0ea3f78bc5aff
Author: isapego 
Date:   2015-10-26T14:16:26Z

First approach for the IGNITE-1680

commit e65abb09199c39cb337ec16c06985e4b3171ec99
Author: isapego 
Date:   2016-06-15T12:33:54Z

Merge branch 'master' into ignite-1680

commit d2b2db67ba2e7a25e3e7b787b6b10ff77ffba72e
Author: isapego 
Date:   2016-06-15T15:56:07Z

IGNITE-1680: Merge-related fixes.

commit c7bddfe9b407a153a0b82607a53ddd47414e1532
Author: isapego 
Date:   2016-06-16T18:17:54Z

IGNITE-1680: Fix for reading of the NULL values.

commit a3b6b5c4d384526d8375a30b7910d3fe34e57a76
Author: isapego 
Date:   2016-06-17T17:36:50Z

IGNITE-1680: Invoke implemented.

commit 52d02e4fa67b55f5f0fd3b0a3831d6914110f761
Author: isapego 
Date:   2016-06-20T15:00:04Z

IGNITE-1680: Documentation fixed.

commit 1e4fb50839d759d68d3e7b4c3991f9e5127cb51f
Author: isapego 
Date:   2016-06-20T15:19:58Z

IGNITE-1680: Refactoring.

commit 4d9717e699c4a8c888224e1802f909628204d75a
Author: isapego 
Date:   2016-06-20T15:55:42Z

IGNITE-1680: Documentation improvements.

commit 2f1c8b9ed60d5bbab0184aefb313500c4805fb4e
Author: isapego 
Date:   2016-06-20T17:57:38Z

IGNTIE-1680: Added rethrowing exceptions to Java at the top level of
callbacks.

commit 730dc68afeb7133dd6426dad46362c26ca854b45
Author: isapego 
Date:   2016-06-20T18:44:07Z

IGNITE-1680: Added some more tests.

commit d66b134cb77e82183410a22a13c490afee149c44
Author: isapego 
Date:   2016-06-20T18:47:57Z

IGNITE-1680: Minor fix.




> CPP: Implement Cache::Invoke method.
> 
>
> Key: IGNITE-3330
> URL: https://issues.apache.org/jira/browse/IGNITE-3330
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> Implement {{Cache::Invoke}} method for the Ignite C++.



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

[jira] [Commented] (IGNITE-3184) Hadoop: HADOOP_HOME should not be required if all other environment variables are set.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-3184:
-

Implemented approach of pure-java classpath composition : 
https://github.com/apache/ignite/pull/818 .

> Hadoop: HADOOP_HOME should not be required if all other environment variables 
> are set.
> --
>
> Key: IGNITE-3184
> URL: https://issues.apache.org/jira/browse/IGNITE-3184
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.7
>
>
> *Problem*
> Ignite internals require three pieces to create correct Hadoop classpath:
> 1) Path to common JARs;
> 2) Path to HDFS JARs;
> 3) Path map-reduce JARs.
> These three paths could be set with environment variables HADOOP_COMMON_HOME, 
> HADOOP_HDFS_HOME and HADOOP_MAPRED_HOME respectively. 
> When all of them are set, HADOOP_HOME is no longer needed, but we will throw 
> an exception in this case. We should not do that.
> *Solution*
> Throw exception only in case we cannot resolve any of these paths.



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

[jira] [Resolved] (IGNITE-3252) Web console: add validator to Package field in Import metadata dialog

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-3252.
--
Resolution: Fixed
  Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Fixed on staging

> Web console: add validator to Package field in Import metadata dialog
> -
>
> Key: IGNITE-3252
> URL: https://issues.apache.org/jira/browse/IGNITE-3252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.7
>
>
> Currently this field shows error message in case of invalid value, but the 
> field has no red frame and triangle.



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

[jira] [Commented] (IGNITE-3227) IgniteCache: add method to calculate size per partition

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-3227:
--

Hi Saikat,

Please also correct the test. I see that you test new methods for LOCAL cache, 
but LOCAL cache has only one partition. You can calculate how many keys should 
go into each partition using IgniteAffinity methods and use calculated values 
to verify new methods.

> IgniteCache: add method to calculate size per partition
> ---
>
> Key: IGNITE-3227
> URL: https://issues.apache.org/jira/browse/IGNITE-3227
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Saikat Maitra
>  Labels: community, important
>
> It makes sense to add size calculation per partition. Actually the following 
> methods should be added to the {{IgniteCache}} API.
> {code}
> public int size(int partition, CachePeekMode... peekModes) throws 
> CacheException;
> public int localSize(int partition, CachePeekMode... peekModes);
> {code}



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

[jira] [Updated] (IGNITE-3344) Couldn't import Ignite Image to Google Compute

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-3344:
---
Description: 
-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing 
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction 
https://apacheignite.readme.io/docs/docker-deployment run command 
{noformat}
 gcloud compute images  create   --source-uri 
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}

-
ACTUAL RESULT
-
The result is " - The resource 
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz' 
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions

  was:
-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing 
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction 
https://apacheignite.readme.io/docs/docker-deployment run command 
{noformat}
 gcloud compute images  create   --source-uri 
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}
-
ACTUAL RESULT
-
The result is " - The resource 
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz' 
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions


> Couldn't import Ignite Image to Google Compute
> --
>
> Key: IGNITE-3344
> URL: https://issues.apache.org/jira/browse/IGNITE-3344
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Vasilisa  Sidorova
>
> -
> DESCRIPTION
> -
> Couldn't run Ignite docker container on the Google Compute due to missing 
> ignite-google-image-1.0.0.tar.gz file
> -
> STEPS FOR REPRODUCE
> -
> # In accordance with the instruction 
> https://apacheignite.readme.io/docs/docker-deployment run command 
> {noformat}
>  gcloud compute images  create   --source-uri 
> gs://ignite-media/ignite-google-image-1.0.0.tar.gz
> {noformat}
> -
> ACTUAL RESULT
> -
> The result is " - The resource 
> 'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz' 
> of type 'Google Cloud Storage object' was not found."
> -
> EXPECTED RESULT
> -
> The image should be created without any exceptions



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

[jira] [Created] (IGNITE-3344) Couldn't import Ignite Image to Google Compute

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-3344:
--

 Summary: Couldn't import Ignite Image to Google Compute
 Key: IGNITE-3344
 URL: https://issues.apache.org/jira/browse/IGNITE-3344
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
Reporter: Vasilisa  Sidorova


-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing 
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction 
https://apacheignite.readme.io/docs/docker-deployment run command 
{noformat}
 gcloud compute images  create   --source-uri 
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}
-
ACTUAL RESULT
-
The result is " - The resource 
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz' 
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions



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

[jira] [Commented] (IGNITE-3152) Client node's addresses are registered in IP finder

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-3152:
--

Semantic of {{ClusterNode.isClient()}} is:
{{Tests whether or not this node is connected to cluster as a client.}}
and it's properly used to detect is another node joined to server topology or 
not. 

{{TcpDiscoveryIpFinderAdapter.discoveryClientMode()}}
Used at joining node. Similar check used at 
{{org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#spiStart}}

So, basicly, {{TcpDiscoveryIpFinderAdapter.discoveryClientMode()}} is a cause 
and {{ClusterNode.isClient()}} is an effect.
Seems both method is reqired, and both works correct.

> Client node's addresses are registered in IP finder
> ---
>
> Key: IGNITE-3152
> URL: https://issues.apache.org/jira/browse/IGNITE-3152
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>  Labels: important
> Fix For: 1.7
>
> Attachments: Test.java
>
>
> Currently client node register its addresses in IP finder and never 
> deregisters them. Also looks like coordinator address is also not removed.
> The simple test that shows this behavior is attached.



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

[jira] [Commented] (IGNITE-3227) IgniteCache: add method to calculate size per partition

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-3227:
--

Hi [~saikatr],

I don't think that implementation of GridCacheAdapter#localSizeLong(int 
partition, CachePeekMode[] peekModes) is correct. Currently it will count all 
local entries, even from other partitions.
To obtain partition size, you should use GridDhtLocalPartition#publicSize() 
method. It also has methods to check whether partition is primary or backup for 
a given topology version. An instance of GridDhtLocalPartition can be accessed 
from GridCacheAdapter by calling {code}ctx.topology().localPartition(int p, 
AffinityTopologyVersion topVer, boolean create){code}.
To count entries in swap and offheap, methods 
GridCacheSwapManager#swapEntriesCount(int partId) and 
GridCacheSwapManager#offheapEntriesCount(int partId) should be used, 
respectively.

> IgniteCache: add method to calculate size per partition
> ---
>
> Key: IGNITE-3227
> URL: https://issues.apache.org/jira/browse/IGNITE-3227
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Saikat Maitra
>  Labels: community, important
>
> It makes sense to add size calculation per partition. Actually the following 
> methods should be added to the {{IgniteCache}} API.
> {code}
> public int size(int partition, CachePeekMode... peekModes) throws 
> CacheException;
> public int localSize(int partition, CachePeekMode... peekModes);
> {code}



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

[jira] [Created] (IGNITE-3343) IGFS: Do not query secondary file system properties during create/append/mkdirs.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3343:
---

 Summary: IGFS: Do not query secondary file system properties 
during create/append/mkdirs.
 Key: IGNITE-3343
 URL: https://issues.apache.org/jira/browse/IGNITE-3343
 Project: Ignite
  Issue Type: Improvement
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.7


Currently when we create something in a secondary file system, we perform 
additional calls to the secondary file system to get file/directory info. This 
significantly slows down structural operations, while usually it is not really 
needed in most cases.

We should do the following:
1) Do not write modification time, access time and properties for DUAL entries. 
Instead, we should propagate "info" and "listFiles" calls to secondary file 
system right away.
2) For {{create()}} we do not need length, as the file is either created from 
scratch, or truncated.
3) For {{append()}} we need to know current length, so the second file system 
call appears to be inevitable.



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

[jira] [Updated] (IGNITE-2398) .NET: Change default mapper behavior.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2398:

Labels: .net important  (was: .net)

> .NET: Change default mapper behavior.
> -
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net, important
> Fix For: 1.7
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



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

[jira] [Created] (IGNITE-3341) Hadoop: add ability to link native libraries to HadoopClassLoader if they were loaded by parent classloader.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3341:
---

 Summary: Hadoop: add ability to link native libraries to 
HadoopClassLoader if they were loaded by parent classloader.
 Key: IGNITE-3341
 URL: https://issues.apache.org/jira/browse/IGNITE-3341
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.7






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

[jira] [Updated] (IGNITE-3328) .NET: Support user-defined AffinityFunction

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3328:
---
Labels: .net  (was: )

> .NET: Support user-defined AffinityFunction
> ---
>
> Key: IGNITE-3328
> URL: https://issues.apache.org/jira/browse/IGNITE-3328
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .net
> Fix For: 1.7
>
>
> Allow custom AffinityFunction implementation in .NET
> Make sure it can be set in XML config.



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

[jira] [Updated] (IGNITE-2827) .NET: Write XmlSerializer types as binary

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2827:
---
Labels: .net  (was: )

> .NET: Write XmlSerializer types as binary
> -
>
> Key: IGNITE-2827
> URL: https://issues.apache.org/jira/browse/IGNITE-2827
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Types intended to be serialized with XmlSerializer can be identified by 
> [XmlRoot] attribute, or one of the [XmlElement], [XmlAttribute], etc 
> attributes on type members.
> We should write such types using Ignite binary format, and respect attributes 
> where applicable.



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

[jira] [Updated] (IGNITE-3111) .NET: Configure SSL without Spring

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3111:
---
Labels: .net  (was: )

> .NET: Configure SSL without Spring
> --
>
> Key: IGNITE-3111
> URL: https://issues.apache.org/jira/browse/IGNITE-3111
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> User should be able to configure SLL in .NET terms without Spring and Java 
> KeyStore.
> See https://apacheignite.readme.io/docs/ssltls.



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

[jira] [Updated] (IGNITE-1914) .Net: Get rid of boxing in DoOutInOpNullable

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1914:
---
Labels: .net  (was: )

> .Net: Get rid of boxing in DoOutInOpNullable
> 
>
> Key: IGNITE-1914
> URL: https://issues.apache.org/jira/browse/IGNITE-1914
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
> Fix For: 1.7
>
>
> See CacheImpl.DoOutInOpNullable overloads.
> We read result as object and then check for null. Nulls are quite frequent in 
> these scenarios.
> To get rid of boxing we need to introduce TryUnmarshal method which allows 
> reading value types with null semantics.



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

[jira] [Updated] (IGNITE-2491) .NET: Async examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2491:
---
Labels: .net  (was: )

> .NET: Async examples
> 
>
> Key: IGNITE-2491
> URL: https://issues.apache.org/jira/browse/IGNITE-2491
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Our examples do not use *Async methods, probably we should demonstrate 
> asynchronous computations as well.
> Also, consider creating C#5 examples with async/await, similar to separate 
> java8 examples in Java.



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

[jira] [Updated] (IGNITE-3289) .NET: Add logging messages

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3289:
---
Labels: .net  (was: )

> .NET: Add logging messages
> --
>
> Key: IGNITE-3289
> URL: https://issues.apache.org/jira/browse/IGNITE-3289
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Add various logging where it might be useful:
> * Startup (starting JVM, loading DLLs, resolving IGNITE_HOME and classpath, 
> initializing store, etc)
> * Unmanaged callbacks
> * Anything else?



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

[jira] [Updated] (IGNITE-3291) .NET: IClusterGroup.ForDaemons

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3291:
---
Labels: .net  (was: )

> .NET: IClusterGroup.ForDaemons
> --
>
> Key: IGNITE-3291
> URL: https://issues.apache.org/jira/browse/IGNITE-3291
> Project: Ignite
>  Issue Type: Improvement
>  Components: newbie, platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .net
> Fix For: 1.7
>
>
> Java side is finally fixed (IGNITE-2911), we can enable this in .NET



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

[jira] [Updated] (IGNITE-2102) .NET: Simplify query examples

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2102:
---
Labels: .net  (was: )

> .NET: Simplify query examples
> -
>
> Key: IGNITE-2102
> URL: https://issues.apache.org/jira/browse/IGNITE-2102
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.7
>
>
> Simply move IGNITE-2097 to .NET once it is ready.



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

[jira] [Updated] (IGNITE-1424) .Net: Add tests for BIG_ENDIANs.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1424:
---
Labels: .net  (was: )

> .Net: Add tests for BIG_ENDIANs.
> 
>
> Key: IGNITE-1424
> URL: https://issues.apache.org/jira/browse/IGNITE-1424
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>  Labels: .net
>
> As all our hardware uses LITTLE_ENDIAN byte order, BIG_ENDIAN was never 
> tested properly. We do not know, whether it works. We do not know it's 
> performance characteristics. 
> Need to add ability to override endian final flags in both .Net and Java 
> (e.g. through a system property or through "Ex" configuration) and then run 
> unit tests with it.



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

[jira] [Updated] (IGNITE-2940) .NET: Plugin system

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2940:
---
Labels: .net  (was: )

> .NET: Plugin system
> ---
>
> Key: IGNITE-2940
> URL: https://issues.apache.org/jira/browse/IGNITE-2940
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Implement a plugin system to allow extending Ignite functionality by third 
> parties.



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

[jira] [Updated] (IGNITE-2578) .NET: Native object comparison

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2578:
---
Labels: .net  (was: )

> .NET: Native object comparison
> --
>
> Key: IGNITE-2578
> URL: https://issues.apache.org/jira/browse/IGNITE-2578
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are 
> performed in binary form on Java side. This may not work as intended when 
> user has overridden Equals/GetHashCode. Need to investigate whether we can or 
> should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



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

[jira] [Updated] (IGNITE-3324) .NET: LINQPad Data Context Driver

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3324:
---
Labels: .net  (was: )

> .NET: LINQPad Data Context Driver
> -
>
> Key: IGNITE-3324
> URL: https://issues.apache.org/jira/browse/IGNITE-3324
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
>
> LINQPad can be extended with a custom Data Context Driver: 
> http://www.linqpad.net/Extensibility.aspx
> With SQL databases, this displays a tree view (top left) of databases, 
> tables, columns, and allows easy strongly-typed queries, as well as raw SQL 
> queries in some cases.
> In our case, I imagine the following:
> * User connects to the grid with our Ignite LINQPad Driver
> * List of queryable entities is displayed (one per QueryEntity) - for SQL and 
> LINQ queries
> * Separate list of all caches is displayed (regardless of query 
> configuration) - for LINQ-to-objects and other raw cache operations (in 
> binary mode only)
> This is a low priority integration, but nice and fun one. Something like 
> Visor for .NET world with LINQ.



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

[jira] [Updated] (IGNITE-1432) .Net: Fix InteropCacheEntryProcessor performance on remote nodes

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1432:
---
Labels: .net  (was: )

> .Net: Fix InteropCacheEntryProcessor performance on remote nodes
> 
>
> Key: IGNITE-1432
> URL: https://issues.apache.org/jira/browse/IGNITE-1432
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> Considerations:
> 1) Invoke with single key is expected to be called only once, so no changes 
> is needed here - deploy and execute in a single JNI call.
> 2) If there are several keys, there is a high chance (but still not 100% due 
> to partitioning) that processor will be called multiple times.
> Proposed solution:
> 1) Check amout of keys.
> 2) If cnt == 1, no changes to current logic.
> 3) If cnt > 1, first deploy (JNI call), then execute (JNI call). Processor 
> entry must be put into weak-map located somewhere inside the interop 
> processor. Interop processor must constantly listen for corresponding 
> reference queue and release .Net entries as soon as processor is weakly 
> reacheable.



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

[jira] [Updated] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1433:
---
Labels: .net  (was: )

> .Net: Add IgniteException.JavaStackTrace
> 
>
> Key: IGNITE-1433
> URL: https://issues.apache.org/jira/browse/IGNITE-1433
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.7
>
>
> Propagate java stack trace as a string in ExceptionUtils.GetException and 
> write it to a new field in IgniteException class.
> This will simplify debugging for us both locally and when getting error 
> reports from clients.



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

[jira] [Updated] (IGNITE-3267) Java and .NET nodes with default configs can not join

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3267:
---
Labels: .net  (was: )

> Java and .NET nodes with default configs can not join
> -
>
> Key: IGNITE-3267
> URL: https://issues.apache.org/jira/browse/IGNITE-3267
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Priority: Critical
>  Labels: .net
> Fix For: 1.7
>
>
> .NET sets BinaryConfiguration explicitly, while Java has 'null'. Need to find 
> a way to fix this.



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

[jira] [Updated] (IGNITE-3102) .NET: Call user-defined constructor for IBinarizable objects

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3102:
---
Labels: .net  (was: )

> .NET: Call user-defined constructor for IBinarizable objects
> 
>
> Key: IGNITE-3102
> URL: https://issues.apache.org/jira/browse/IGNITE-3102
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Currently we create user objects with 
> FormatterServices.GetUninitializedObject and then call user-defined 
> IBinarizable.ReadBinary method.
> This is not convenient both for us and the user:
> * FormatterServices.GetUninitializedObject is not a clean way of constructing 
> objects
> * User-defined constructor does not get called
> * User types can't have readonly fields
> For example, ISerializable mechanism does not have Read method; it calls 
> user-defined constructor instead. We should provide similar mechanism.
> To maintain compatibility, we may have to introduce a new interface with a 
> single Write method, and call user-defined ctor on read.



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

[jira] [Updated] (IGNITE-2398) .NET: Change default mapper behavior.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2398:
---
Labels: .net  (was: important)

> .NET: Change default mapper behavior.
> -
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
> Fix For: 1.7
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



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

[jira] [Updated] (IGNITE-1969) .NET: Optimize PlatformCache "loadCache" and "readScanQuery" methods.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1969:
---
Labels: .net  (was: )

> .NET: Optimize PlatformCache "loadCache" and "readScanQuery" methods.
> -
>
> Key: IGNITE-1969
> URL: https://issues.apache.org/jira/browse/IGNITE-1969
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
>
> Earlier we have an optimization when we passed pointer to .Net object along 
> with its serialized form to avoid deserialization for node-local scenarios. 
> But then we revealed leaks in implementation and disabled this opto.
> As as result we always pass 0 to corresponding native methods (see loadCache0 
> and readScanQuery). 
> We need either re-apply this opto correctly, or refactor native methods and 
> forget about.



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

[jira] [Updated] (IGNITE-3181) .NET: Speed up TypeCaster with reflection.emit

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3181:
---
Labels: .net  (was: )

> .NET: Speed up TypeCaster with reflection.emit
> --
>
> Key: IGNITE-3181
> URL: https://issues.apache.org/jira/browse/IGNITE-3181
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Investigate whether emitted IL can be more efficient than compiled expression 
> tree due to less checks.



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

[jira] [Updated] (IGNITE-2746) .NET: Improve ReflectiveSerializer control with attributes

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2746:
---
Labels: .net  (was: )

> .NET: Improve ReflectiveSerializer control with attributes
> --
>
> Key: IGNITE-2746
> URL: https://issues.apache.org/jira/browse/IGNITE-2746
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
> Fix For: 1.7
>
>
> Allow custom field names and ordering (similar to DataMemberAttribute, for 
> example: 
> https://msdn.microsoft.com/en-us/library/system.runtime.serialization.datamemberattribute(v=vs.110).aspx)



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

[jira] [Updated] (IGNITE-3206) .NET: Automatic persistence

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3206:
---
Labels: .net  (was: )

> .NET: Automatic persistence
> ---
>
> Key: IGNITE-3206
> URL: https://issues.apache.org/jira/browse/IGNITE-3206
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> See how Automatic Persistence works in Java: 
> http://apacheignite.gridgain.org/docs/automatic-persistence
> Think of a way to do the same in .NET with raw SqlClient and/or with 
> EntityFramework/NHibernate.



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

[jira] [Updated] (IGNITE-3280) .NET: Log4net integration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3280:
---
Labels: .net  (was: )

> .NET: Log4net integration
> -
>
> Key: IGNITE-3280
> URL: https://issues.apache.org/jira/browse/IGNITE-3280
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Provide Log4net implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.



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

[jira] [Updated] (IGNITE-1429) .Net: Optimize stream receiver so that it is created only once on remote node.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1429:
---
Labels: .net  (was: )

> .Net: Optimize stream receiver so that it is created only once on remote node.
> --
>
> Key: IGNITE-1429
> URL: https://issues.apache.org/jira/browse/IGNITE-1429
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> Looks like we can employ PhantomReference in Java for this.



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

[jira] [Updated] (IGNITE-1418) .Net: Implement distributed count-down latch (event).

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1418:
---
Labels: .net  (was: )

> .Net: Implement distributed count-down latch (event).
> -
>
> Key: IGNITE-1418
> URL: https://issues.apache.org/jira/browse/IGNITE-1418
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>




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

[jira] [Updated] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3199:
---
Labels: .net  (was: )

> .NET: ASP.NET Session-State Store Provider
> --
>
> Key: IGNITE-3199
> URL: https://issues.apache.org/jira/browse/IGNITE-3199
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Priority: Critical
>  Labels: .net
> Fix For: 1.7
>
>
> See https://msdn.microsoft.com/en-us/library/ms178587.aspx
> Code should be put to Apache.Ignite.AspNet assembly (see IGNITE-2379)



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

[jira] [Updated] (IGNITE-2687) Call .NET services from Java

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2687:
---
Labels: .net  (was: )

> Call .NET services from Java
> 
>
> Key: IGNITE-2687
> URL: https://issues.apache.org/jira/browse/IGNITE-2687
> Project: Ignite
>  Issue Type: New Feature
>  Components: managed services, platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> .NET services can be called via PlatformDotNetService interface, providing 
> method name and arguments. 



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2492:
---
Labels: .net  (was: )

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



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

[jira] [Updated] (IGNITE-3169) .NET: Provide better error messages when user assembly loading has failed

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3169:
---
Labels: .net  (was: )

> .NET: Provide better error messages when user assembly loading has failed
> -
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>




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

[jira] [Updated] (IGNITE-1628) .Net: Ensure that .Net works on Mono platform.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1628:
---
Labels: .net  (was: )

> .Net: Ensure that .Net works on Mono platform.
> --
>
> Key: IGNITE-1628
> URL: https://issues.apache.org/jira/browse/IGNITE-1628
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> *NOTE*: Targeted for 1.6, but could be moved even further in case of tight 
> release schedule.
> *Goal*
> As Microsoft is moving .Net towards open standards, Mono receives more an 
> more attention. 
> We need to ensure that our product works fine on this platform. This includes 
> both Windows, Linux and (possibly) Mac environments.
> *Tasks*
> - Ensure that Ignite works with Mono on Windows. This is the easiest task 
> because we only need to re-compile .Net part.
> - Ensure that Ignite works with Mono on Linux. This will require alternate 
> build procedure because CPP recompilation will be required as well.
> - Create relevant TC builds.



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

[jira] [Updated] (IGNITE-1975) .NET: Ignite Entity Framework Data Provider

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1975:
---
Labels: .net  (was: )

> .NET: Ignite Entity Framework Data Provider
> ---
>
> Key: IGNITE-1975
> URL: https://issues.apache.org/jira/browse/IGNITE-1975
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Implement Entity Framework Data Provider for Ignite:
> https://msdn.microsoft.com/en-us/library/ee789835(v=vs.100).aspx



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

[jira] [Updated] (IGNITE-3278) .NET: Allow PlatformCallbackGateway usage during shutdown

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3278:
---
Labels: .net  (was: )

> .NET: Allow PlatformCallbackGateway usage during shutdown
> -
>
> Key: IGNITE-3278
> URL: https://issues.apache.org/jira/browse/IGNITE-3278
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Currently we block PlatformCallbackGateway calls during node stop. This 
> causes issues with things like store and event logging, which need to 
> function  during stop.



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

[jira] [Updated] (IGNITE-2825) .NET: Write Serializable as binary

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2825:
---
Labels: .net  (was: )

> .NET: Write Serializable as binary
> --
>
> Key: IGNITE-2825
> URL: https://issues.apache.org/jira/browse/IGNITE-2825
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Write [Serializable] classes in Ignite binary format. Employ the same logic 
> as .NET does with NonSerializedAttribute and ISerializable interface.



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

[jira] [Updated] (IGNITE-2657) .NET: SqlDependency for cache items

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2657:
---
Labels: .net  (was: )

> .NET: SqlDependency for cache items
> ---
>
> Key: IGNITE-2657
> URL: https://issues.apache.org/jira/browse/IGNITE-2657
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Update cache when SQL Server data changes
> * https://msdn.microsoft.com/en-us/library/62xk7953(v=vs.110).aspx
> * http://www.alachisoft.com/ncache/database-synchronization.html



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

[jira] [Updated] (IGNITE-1654) .Net: Ensure consistent "keepPortable" behavior.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1654:
---
Labels: .net  (was: )

> .Net: Ensure consistent "keepPortable" behavior.
> 
>
> Key: IGNITE-1654
> URL: https://issues.apache.org/jira/browse/IGNITE-1654
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> We need to ensure that "keep portable" concept is
> a) Consistent;
> b) Exists for all logical units where it is necessary.
> Lets split "keep portable" behavior in two scenarios:
> 1) Client mode. This is when client (caller) operates on portable objects. 
> Example: ICache.Get(...);
> 2) Server mode. This is when some server side object (caller) operates on 
> portable objects. Example: a remote service which should not deserialize 
> passed arguments and operate on portables instead.
> Looks like both cases can be handled using the same "keep portable" flag on 
> related logical unit.
> Logical units affected:
> 1) Compute - at the very least closures can be executed in this mode;
> 2) Cache;
> 3) Data streamer;
> 4) Data structures: atomic stamped, atmoc reference;
> 5) Cache events;
> 6) Messages;
> 7) Services.
> Probably we should introduce a kind of "IKeepPortableEnabled" (or so) 
> interface, which will have a method "T WithKeepPortable()". This way users 
> will be able to easily understand that "keep portable" semantics is 
> applicable.
> Lets split it into several children tickets if necessary.



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

[jira] [Updated] (IGNITE-3170) .NET: Add user-friendly ToString overrides for public types

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3170:
---
Labels: .net  (was: )

> .NET: Add user-friendly ToString overrides for public types
> ---
>
> Key: IGNITE-3170
> URL: https://issues.apache.org/jira/browse/IGNITE-3170
> Project: Ignite
>  Issue Type: Improvement
>  Components: newbie, platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Events, cache entry events, mutable cache entries, etc, should have ToString 
> overridden. See CacheEntry for example.



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

[jira] [Updated] (IGNITE-1415) .Net: Optimize handle registry.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1415:
---
Labels: .net  (was: )

> .Net: Optimize handle registry.
> ---
>
> Key: IGNITE-1415
> URL: https://issues.apache.org/jira/browse/IGNITE-1415
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> The main problem with handle registry is CAS on a single shared variable. 
> This could result in a very bad performance under contention. 
> Several techniques can be applied here:
> 1) Stripes. Assign some ID to a thread and then use it to pick correct stripe 
> for the thread. Be careful with false-sharing effects as stripes can be 
> located very close to each other.
> 2) Cleanup with relaxed membars. When we are to remove the handle, no need 
> for full HB semantics. We are ok if subsequent calls to the same handle will 
> see not-killed object for a while.



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

[jira] [Updated] (IGNITE-2890) .NET: Add CacheConfiguration.NodeFilter

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2890:
---
Labels: .net  (was: )

> .NET: Add CacheConfiguration.NodeFilter
> ---
>
> Key: IGNITE-2890
> URL: https://issues.apache.org/jira/browse/IGNITE-2890
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> See ServiceConfiguration.NodeFilter
> * Caches start earlier than platform => need to pass pointer for static 
> CacheConfigurations
> * For dynamic cache start, no need for pointers



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

[jira] [Updated] (IGNITE-1410) .Net: Implement IEvents.RecordLocal.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1410:
---
Labels: .net  (was: )

> .Net: Implement IEvents.RecordLocal.
> 
>
> Key: IGNITE-1410
> URL: https://issues.apache.org/jira/browse/IGNITE-1410
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
>




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

[jira] [Updated] (IGNITE-1427) .Net: Services - add support for non-deserializable AffinityKey.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1427:
---
Labels: .net  (was: )

> .Net: Services - add support for non-deserializable AffinityKey.
> 
>
> Key: IGNITE-1427
> URL: https://issues.apache.org/jira/browse/IGNITE-1427
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
>
> Currently if affinity key cannot be marshalled for some reason, it will break 
> not only affected service descriptor, but all services API.
> We should catch marshalling exceptions and pass it to .Net in a wrapped form. 
> These exception must be thrown only if user is trying to access problematic 
> key explicitly.



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

[jira] [Updated] (IGNITE-2581) .NET: AtomicReference binary mode

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2581:
---
Labels: .net  (was: )

> .NET: AtomicReference binary mode
> -
>
> Key: IGNITE-2581
> URL: https://issues.apache.org/jira/browse/IGNITE-2581
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Work with AtomicReference in binary mode, see comments in IGNITE-1563



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

[jira] [Updated] (IGNITE-3006) .NET: ContinuousQuery.FilterFactory

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3006:
---
Labels: .net  (was: )

> .NET: ContinuousQuery.FilterFactory
> ---
>
> Key: IGNITE-3006
> URL: https://issues.apache.org/jira/browse/IGNITE-3006
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> To conform to Java APIs:
> * Add ContinuousQuery.FilterFactory
> * Deprecate  ContinuousQuery.Filter
> Make sure that resource injection works.



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

[jira] [Updated] (IGNITE-1412) .Net: Pass local entry processor pointer to Java.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1412:
---
Labels: .net  (was: )

> .Net: Pass local entry processor pointer to Java.
> -
>
> Key: IGNITE-1412
> URL: https://issues.apache.org/jira/browse/IGNITE-1412
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
>
> Currently we always serialize .Net entry processor and pass only serialized 
> bytes to Java. 
> If processor is to be executed locally, then we pass the same bytes back and 
> deserialize them again. 
> Instead, we can do the following:
> 1) Serialize entry processor.
> 2) Allocate handle for it.
> 3) Pass bytes and handle to Java.
> 4) In case of local execution, just return back the handle.
> 5) Once execution is finished, handle can be safely released in "finally" 
> block.
> This can be easily implemented only for synchronous entry processing. 
> For async mode there is no try/finally. We could release the handle during 
> feature completion, but the problem is that there is no guarantee tha user 
> will ever request this feature.



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

[jira] [Updated] (IGNITE-2826) .NET: Write DataContract types as binary

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2826:
---
Labels: .net  (was: )

> .NET: Write DataContract types as binary
> 
>
> Key: IGNITE-2826
> URL: https://issues.apache.org/jira/browse/IGNITE-2826
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Types marked with [DataContract] attribute should be written in binary 
> format, respecting [DataMember] and other related attributes, so that 
> existing user types can be used in Ignite without any changes.



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

[jira] [Updated] (IGNITE-3095) .NET: Reference NUnit via NuGet instead of predefined folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3095:
---
Labels: .net  (was: )

> .NET: Reference NUnit via NuGet instead of predefined folder
> 
>
> Key: IGNITE-3095
> URL: https://issues.apache.org/jira/browse/IGNITE-3095
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Currently test projects require NUnit binaries in 
> modules\platforms\dotnet\libs folder. This requires extra steps from 
> developers.
> Using NuGet reference is more developer friendly.



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

[jira] [Updated] (IGNITE-2292) Add ability to build .NET platform from Maven.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2292:
---
Labels: .net  (was: )

> Add ability to build .NET platform from Maven.
> --
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
> Fix For: 1.7
>
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can 
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true 
> -Dignite.net.build =true -Dignite.net.build.x86=true 
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}



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

[jira] [Updated] (IGNITE-1431) .Net: Ensure strings are written correctly in BIG/LITTLE endian modes.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1431:
---
Labels: .net  (was: )

> .Net: Ensure strings are written correctly in BIG/LITTLE endian modes.
> --
>
> Key: IGNITE-1431
> URL: https://issues.apache.org/jira/browse/IGNITE-1431
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>  Labels: .net
>




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

[jira] [Updated] (IGNITE-1785) .Net: Improve PlatformMemory/PortableStream performance and memory usage

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1785:
---
Labels: .net  (was: )

> .Net: Improve PlatformMemory/PortableStream performance and memory usage
> 
>
> Key: IGNITE-1785
> URL: https://issues.apache.org/jira/browse/IGNITE-1785
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> * PlatformMemory is just a single "long _memPtr" and can be easily converted 
> to a struct to reduce allocations (it is allocated a lot)
> * PlatformMemoryStream works with PlatformMemory.Length and Capacity 
> indirectly. By employing a struct approach from 
> https://issues.apache.org/jira/browse/IGNITE-1428 we can work with Length and 
> Capacity directly, which may be faster, and will eliminate the need for 
> SyncronizeInput/Output calls.
> * PlatformMemoryStream is allocated even more often than PlatformMemory, need 
> to investigate whether it can also be a struct. See how List<>.GetEnumerator 
> works, which is a struct.



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

[jira] [Updated] (IGNITE-3088) .NET: Support POCO proxy serialization

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3088:
---
Labels: .net  (was: )

> .NET: Support POCO proxy serialization
> --
>
> Key: IGNITE-3088
> URL: https://issues.apache.org/jira/browse/IGNITE-3088
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> WCF provides a way to serialize POCO proxies: 
> https://msdn.microsoft.com/en-us/library/ee705457(v=vs.100).aspx
> We should come up with a way to do this.
> To reproduce: 
> * Create a database with 2 tables and a foreign key; populate some rows
> * Create a new EF6 project from that database
> * Retrieve one of the entities
> * Attempt to put it into cache



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

[jira] [Updated] (IGNITE-2122) .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2122:
---
Labels: .net  (was: )

> .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.
> 
>
> Key: IGNITE-2122
> URL: https://issues.apache.org/jira/browse/IGNITE-2122
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>




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

[jira] [Updated] (IGNITE-2295) .Net: Provide performance counters

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2295:
---
Labels: .net  (was: )

> .Net: Provide performance counters
> --
>
> Key: IGNITE-2295
> URL: https://issues.apache.org/jira/browse/IGNITE-2295
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Ignite.NET should be instrumented with Performance Monitor (perfmon) counters 
> for diagnostic purposes. We can use existing metrics (cluster, cache, etc) to 
> provide custom counters.



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

[jira] [Updated] (IGNITE-1422) .Net: Marshalling can be optimized for fixed-length objects.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1422:
---
Labels: .net  (was: )

> .Net: Marshalling can be optimized for fixed-length objects.
> 
>
> Key: IGNITE-1422
> URL: https://issues.apache.org/jira/browse/IGNITE-1422
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
>
> Sometimes we can guess user object length in advance:
> 1) Strict rule: it is "reflective" and contains only fixed-length fields.
> 2) Speculative rule: It is "marshal aware", contains only fixed-length fields 
> and there is only one metadata "path".
> In these cases we can do the following:
> 1) No tracking of length and raw offset.
> 2) Header can be written as one memcpy() rather than as multiple 
> int/byte/bool writes.
> We need to have a fallback strategy for a cases when new metadata path 
> appears or user write raw data. It is very easy: if expected and actual 
> lengths differ at the end, set proper values.



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

[jira] [Updated] (IGNITE-3255) .NET: Script execution

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3255:
---
Labels: .net  (was: )

> .NET: Script execution
> --
>
> Key: IGNITE-3255
> URL: https://issues.apache.org/jira/browse/IGNITE-3255
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Introduce an ability to execute C# scripts on remote nodes.
> This may be useful for:
> * Diagnostics and debugging on live cluster
> * Quick try-out for computations
> * Demo purposes
> This is a light-weight alternative to IGNITE-2492: we don't have to deal with 
> automatically detecting whether assembly needs to be loaded remotely, with 
> it's dependencies and AppDomain lifecycle. 
> Instead, we send a string, compile it remotely, execute in a separate 
> AppDomain and unload it.



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

[jira] [Updated] (IGNITE-3279) .NET: NLog integration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3279:
---
Labels: .net  (was: )

> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.



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

[jira] [Updated] (IGNITE-2658) .NET: NHibernate Second Level Cache

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2658:
---
Labels: .net  (was: )

> .NET: NHibernate Second Level Cache
> ---
>
> Key: IGNITE-2658
> URL: https://issues.apache.org/jira/browse/IGNITE-2658
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> http://nhibernate.info/blog/2009/02/09/quickly-setting-up-and-using-nhibernate-s-second-level-cache.html



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

[jira] [Updated] (IGNITE-3275) .NET: Enable REST HTTP in .NET nodes

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3275:
---
Labels: .net  (was: )

> .NET: Enable REST HTTP in .NET nodes
> 
>
> Key: IGNITE-3275
> URL: https://issues.apache.org/jira/browse/IGNITE-3275
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net
>
> * Include REST HTTP jars in NuGet (either in core, or in a separate package). 
> Keep in mind NuGet size limitation
> * Add required options to IgniteConfiguration to enable/disable REST



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

[jira] [Updated] (IGNITE-2662) .NET Core support

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2662:
---
Labels: .net  (was: )

> .NET Core support
> -
>
> Key: IGNITE-2662
> URL: https://issues.apache.org/jira/browse/IGNITE-2662
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> .NET core is next gen open-source cross-platform implementation of .NET: 
> https://github.com/dotnet/core
> Since Ignite mostly does not use any platform-specific .NET features, it may 
> be possible to add Core support.
> Benefits:
> * ASP.NET Core (ver 5) https://www.asp.net/vnext
> * OSX & Linux
> Possible difficulties:
> * JNI interop. Core has dllImport and it works on linux, and our C++ client 
> works on linux, so it should be possible
> * Reflection. We use it a lot, and API has changed.



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

[jira] [Updated] (IGNITE-1683) .Net: IEvents.RemoteListen

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1683:
---
Labels: .net  (was: )

> .Net: IEvents.RemoteListen
> --
>
> Key: IGNITE-1683
> URL: https://issues.apache.org/jira/browse/IGNITE-1683
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Bring back IEvents.RemoteListen as soon as it is fixed in Java.
> Currently rmtFilter is not actually a filter and semantics are unclear.



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

[jira] [Updated] (IGNITE-1417) .Net: Implement distributed queue.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-1417:
---
Labels: .net  (was: )

> .Net: Implement distributed queue.
> --
>
> Key: IGNITE-1417
> URL: https://issues.apache.org/jira/browse/IGNITE-1417
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>




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

[jira] [Created] (IGNITE-3340) .NET: Cache store is not destroyed on DestroyCache

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3340:
--

 Summary: .NET: Cache store is not destroyed on DestroyCache
 Key: IGNITE-3340
 URL: https://issues.apache.org/jira/browse/IGNITE-3340
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Priority: Critical
 Fix For: 1.7


cacheStoreDestroy platform callback should be called whenever owner cache is 
destroyed.



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

[jira] [Updated] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-3339:

Description: 
On OFFHEAP_TIERED TRANSACTIONAL cache:
1. Put entry.
2. Cache size equals 1 and iterator returns one entry.
3. Open PESSIMISTIC READ_COMMITED transaction.
4. get() that value.
5. Commit transaction.
6. Cache size now equals 2 and iterator returns two identical entries.

By fast investigation was found that after put() operation value goes to 
offheap. After get() operation in explicit transaction the same value appears 
in onheap and offheap iterators. As a result user sees two the same entries.


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

  was:
Configure cache as OFFHEAP_TIERED .

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


> get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies 
> data from offheap to onheap.
> 
>
> Key: IGNITE-3339
> URL: https://issues.apache.org/jira/browse/IGNITE-3339
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Dmitry Karachentsev
> Fix For: 1.7
>
>
> On OFFHEAP_TIERED TRANSACTIONAL cache:
> 1. Put entry.
> 2. Cache size equals 1 and iterator returns one entry.
> 3. Open PESSIMISTIC READ_COMMITED transaction.
> 4. get() that value.
> 5. Commit transaction.
> 6. Cache size now equals 2 and iterator returns two identical entries.
> By fast investigation was found that after put() operation value goes to 
> offheap. After get() operation in explicit transaction the same value appears 
> in onheap and offheap iterators. As a result user sees two the same entries.
> https://github.com/apache/ignite/pull/817



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

[jira] [Updated] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-3339:

Description: 
On OFFHEAP_TIERED TRANSACTIONAL cache:
1. Put entry.
2. Cache size equals 1 and iterator returns one entry.
3. Open PESSIMISTIC READ_COMMITED transaction.
4. get() that value.
5. Commit transaction.
6. Cache size now equals 2 and iterator returns two identical entries.

By fast investigation was found that after put() operation value goes to 
offheap. After get() operation in explicit transaction the same value appears 
in onheap and offheap iterators. As a result user sees two the same entries.

Pull request with test that reproduces the bug:
https://github.com/apache/ignite/pull/817

  was:
On OFFHEAP_TIERED TRANSACTIONAL cache:
1. Put entry.
2. Cache size equals 1 and iterator returns one entry.
3. Open PESSIMISTIC READ_COMMITED transaction.
4. get() that value.
5. Commit transaction.
6. Cache size now equals 2 and iterator returns two identical entries.

By fast investigation was found that after put() operation value goes to 
offheap. After get() operation in explicit transaction the same value appears 
in onheap and offheap iterators. As a result user sees two the same entries.


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


> get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies 
> data from offheap to onheap.
> 
>
> Key: IGNITE-3339
> URL: https://issues.apache.org/jira/browse/IGNITE-3339
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Dmitry Karachentsev
> Fix For: 1.7
>
>
> On OFFHEAP_TIERED TRANSACTIONAL cache:
> 1. Put entry.
> 2. Cache size equals 1 and iterator returns one entry.
> 3. Open PESSIMISTIC READ_COMMITED transaction.
> 4. get() that value.
> 5. Commit transaction.
> 6. Cache size now equals 2 and iterator returns two identical entries.
> By fast investigation was found that after put() operation value goes to 
> offheap. After get() operation in explicit transaction the same value appears 
> in onheap and offheap iterators. As a result user sees two the same entries.
> Pull request with test that reproduces the bug:
> https://github.com/apache/ignite/pull/817



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

[jira] [Updated] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-3339:

Description: 
Configure cache as OFFHEAP_TIERED .

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

  was:https://github.com/apache/ignite/pull/817


> get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies 
> data from offheap to onheap.
> 
>
> Key: IGNITE-3339
> URL: https://issues.apache.org/jira/browse/IGNITE-3339
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Dmitry Karachentsev
> Fix For: 1.7
>
>
> Configure cache as OFFHEAP_TIERED .
> https://github.com/apache/ignite/pull/817



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

[jira] [Reopened] (IGNITE-3252) Web console: add validator to Package field in Import metadata dialog

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reopened IGNITE-3252:
---
  Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: add validator to Package field in Import metadata dialog
> -
>
> Key: IGNITE-3252
> URL: https://issues.apache.org/jira/browse/IGNITE-3252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.7
>
>
> Currently this field shows error message in case of invalid value, but the 
> field has no red frame and triangle.



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

[jira] [Commented] (IGNITE-3252) Web console: add validator to Package field in Import metadata dialog

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-3252:
---

Invalid tooltip when package is empty.

> Web console: add validator to Package field in Import metadata dialog
> -
>
> Key: IGNITE-3252
> URL: https://issues.apache.org/jira/browse/IGNITE-3252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.7
>
>
> Currently this field shows error message in case of invalid value, but the 
> field has no red frame and triangle.



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

[jira] [Resolved] (IGNITE-3266) Web console: error in docker file

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-3266.

   Resolution: Won't Fix
 Assignee: Pavel Konstantinov  (was: Andrey Novikov)
Fix Version/s: 1.7

This is correct command format. 

> Web console: error in docker file
> -
>
> Key: IGNITE-3266
> URL: https://issues.apache.org/jira/browse/IGNITE-3266
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.7
>
>
> I've noticed error in docker file: 'cp {} '
> {code}
> # Copy project jars to node classpath.
> RUN mkdir $IGNITE_HOME/libs/1 && \
>find 1/target -name "*.jar" -type f -exec cp {} $IGNITE_HOME/libs/1 \; && \
>cp -r 1/config/* $IGNITE_HOME/config
> {code}
> I suppose this should be 'jdbc-drivers/*' folder. But in case when project 
> doesn't contain any jdbs drivers  an incorrect text is generated.



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

[jira] [Assigned] (IGNITE-3266) Web console: error in docker file

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-3266:
--

Assignee: Andrey Novikov  (was: Maxim Afanasiev)

> Web console: error in docker file
> -
>
> Key: IGNITE-3266
> URL: https://issues.apache.org/jira/browse/IGNITE-3266
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>
> I've noticed error in docker file: 'cp {} '
> {code}
> # Copy project jars to node classpath.
> RUN mkdir $IGNITE_HOME/libs/1 && \
>find 1/target -name "*.jar" -type f -exec cp {} $IGNITE_HOME/libs/1 \; && \
>cp -r 1/config/* $IGNITE_HOME/config
> {code}
> I suppose this should be 'jdbc-drivers/*' folder. But in case when project 
> doesn't contain any jdbs drivers  an incorrect text is generated.



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

[jira] [Commented] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3339:


GitHub user dkarachentsev opened a pull request:

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

IGNITE-3339 - get() in explicit READ_COMMITTED transaction on OFFHEAP…

…_TIERED cache copies data from offheap to onheap.

Test.

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

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

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

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


commit 4a620790f4c5c2e2f6dcb93fdc9bca9f7faf1f90
Author: dkarachentsev 
Date:   2016-06-20T10:33:50Z

IGNITE-3339 - get() in explicit READ_COMMITTED transaction on 
OFFHEAP_TIERED cache copies data from offheap to onheap.

Test.




> get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies 
> data from offheap to onheap.
> 
>
> Key: IGNITE-3339
> URL: https://issues.apache.org/jira/browse/IGNITE-3339
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Dmitry Karachentsev
> Fix For: 1.7
>
>




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

[jira] [Updated] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-3339:

Description: https://github.com/apache/ignite/pull/817

> get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies 
> data from offheap to onheap.
> 
>
> Key: IGNITE-3339
> URL: https://issues.apache.org/jira/browse/IGNITE-3339
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Dmitry Karachentsev
> Fix For: 1.7
>
>
> https://github.com/apache/ignite/pull/817



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

[jira] [Created] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-3339:
---

 Summary: get() in explicit READ_COMMITTED transaction on 
OFFHEAP_TIERED cache copies data from offheap to onheap.
 Key: IGNITE-3339
 URL: https://issues.apache.org/jira/browse/IGNITE-3339
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Dmitry Karachentsev
 Fix For: 1.7






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

[jira] [Updated] (IGNITE-3338) BinaryObjectException: Failed to get field because type ID of passed object differs from type ID this BinaryField belongs to - during load test with eviction configured

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-3338:

Description: 
The following exceptions occur during load test with eviction configured:

{noformat}
ERROR: The benchmark of random operation failed.
Type '--help' for usage.
Finishing main test [ts=1466178657166, date=Fri Jun 17 08:50:57 PDT 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
(retry update if possible).: [26, 1872066, 1945790, 2405741, 3845651, 
4830233, 7284502, 8555643]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1467)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1972)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.removeAll(IgniteCacheProxy.java:1416)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doRemoveAll(IgniteCacheRandomOperationBenchmark.java:809)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:551)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:509)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:156)
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
at java.lang.Thread.run(Thread.java:745)
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [26, 1872066, 1945790, 
2405741, 3845651, 4830233, 7284502, 8555643]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:311)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2958)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:129)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:266)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:264)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
... 1 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:369)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1711)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1482)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:2937)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:129)
at 

[jira] [Assigned] (IGNITE-2638) "Connection to Ignite Web Agent is not established" form not in focus

[Maxim Afanasiev (JIRA)]

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

Maxim Afanasiev reassigned IGNITE-2638:
---

Assignee: Maxim Afanasiev

> "Connection to Ignite Web Agent is not established" form not in focus
> -
>
> Key: IGNITE-2638
> URL: https://issues.apache.org/jira/browse/IGNITE-2638
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.6
> Environment: OS X 10.10.5
> Safari 9.0.2 (10601.3.9)
>Reporter: Ilya Suntsov
>Assignee: Maxim Afanasiev
>Priority: Minor
> Attachments: after.png, before.png
>
>
> Steps for reproduce:
> 1. Stop  ignite-web-agent 
> 2. Go to https://console.gridgain.com/sql/demo
> 3. Click on 'Show security token'
> Result:
> Text in form became blurry. Please look in attachment.



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

[jira] [Resolved] (IGNITE-3252) Web console: add validator to Package field in Import metadata dialog

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-3252.
--
   Resolution: Fixed
 Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)
Fix Version/s: 1.7

Added validator. Please test on staging.

> Web console: add validator to Package field in Import metadata dialog
> -
>
> Key: IGNITE-3252
> URL: https://issues.apache.org/jira/browse/IGNITE-3252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.7
>
>
> Currently this field shows error message in case of invalid value, but the 
> field has no red frame and triangle.



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

[jira] [Updated] (IGNITE-3338) BinaryObjectException: Failed to get field because type ID of passed object differs from type ID this BinaryField belongs to - during load test with eviction configured

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-3338:

Summary: BinaryObjectException: Failed to get field because type ID of 
passed object differs from type ID this BinaryField belongs to -  during load 
test with eviction configured  (was: CachePartialUpdateCheckedException: Failed 
to update keys during load test with eviction configured)

> BinaryObjectException: Failed to get field because type ID of passed object 
> differs from type ID this BinaryField belongs to -  during load test with 
> eviction configured
> -
>
> Key: IGNITE-3338
> URL: https://issues.apache.org/jira/browse/IGNITE-3338
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Ksenia Rybakova
> Fix For: 1.7
>
>
> The following exceptions occur during load test with eviction configured:
> {noformat}
> ERROR: The benchmark of random operation failed.
> Type '--help' for usage.
> Finishing main test [ts=1466178657166, date=Fri Jun 17 08:50:57 PDT 2016]
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [26, 1872066, 1945790, 2405741, 3845651, 
> 4830233, 7284502, 8555643]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1467)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1972)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.removeAll(IgniteCacheProxy.java:1416)
> at 
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doRemoveAll(IgniteCacheRandomOperationBenchmark.java:809)
> at 
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:551)
> at 
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:509)
> at 
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:156)
> at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [26, 1872066, 
> 1945790, 2405741, 3845651, 4830233, 7284502, 8555643]
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:311)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2958)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:129)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:266)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:264)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ... 1 

[jira] [Reopened] (IGNITE-3298) Action "Export all" does not work on SQL page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reopened IGNITE-3298:
---
  Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

In description added steps to reproduce.

> Action "Export all" does not work on SQL page
> -
>
> Key: IGNITE-3298
> URL: https://issues.apache.org/jira/browse/IGNITE-3298
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 1.7
>
>
> To reproduce: 
> # Start 2 node with cache "bank_Condition" and fill by data with type 
> "Condition"
> # Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
> # Try to "Export all" results.
> Export is not work. Browser log is empty. In clicked link area browser show 
> "javascript:void(0)"
> Export all work for other caches and types.



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

[jira] [Updated] (IGNITE-3298) Action "Export all" does not work on SQL page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-3298:
--
Description: 
To reproduce: 
# Start 2 node with cache "bank_Condition" and fill by data with type 
"Condition"
# Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
# Try to "Export all" results.
Export is not work. Browser log is empty. In clicked link area browser show 
"javascript:void(0)"
Export all work for other caches and types.

  was:
To reproduce: 
# Start node with cache "bank_Condition" and fill by data with type "Condition"
# Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
# Try to "Export all" results.
Export is not work. Browser log is empty. In clicked link area browser show 
"javascript:void(0)"


> Action "Export all" does not work on SQL page
> -
>
> Key: IGNITE-3298
> URL: https://issues.apache.org/jira/browse/IGNITE-3298
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
>
> To reproduce: 
> # Start 2 node with cache "bank_Condition" and fill by data with type 
> "Condition"
> # Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
> # Try to "Export all" results.
> Export is not work. Browser log is empty. In clicked link area browser show 
> "javascript:void(0)"
> Export all work for other caches and types.



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

[jira] [Updated] (IGNITE-3298) Action "Export all" does not work on SQL page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-3298:
--
Description: 
To reproduce: 
# Start node with cache "bank_Condition" and fill by data with type "Condition"
# Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
# Try to "Export all" results.
Export is not work. Browser log is empty. In clicked link area browser show 
"javascript:void(0)"

  was:Log is empty.


> Action "Export all" does not work on SQL page
> -
>
> Key: IGNITE-3298
> URL: https://issues.apache.org/jira/browse/IGNITE-3298
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
>
> To reproduce: 
> # Start node with cache "bank_Condition" and fill by data with type 
> "Condition"
> # Execute query: Select 0 as a, 1 as b from "bank_Condition".Condition
> # Try to "Export all" results.
> Export is not work. Browser log is empty. In clicked link area browser show 
> "javascript:void(0)"



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

[jira] [Closed] (IGNITE-1860) SQL: Do not export system columns if they are OFF (invisible)

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko closed IGNITE-1860.
-

Tested. The system columns is not exported when they are disabled in result.

> SQL: Do not export system columns if they are OFF (invisible)
> -
>
> Key: IGNITE-1860
> URL: https://issues.apache.org/jira/browse/IGNITE-1860
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
>
> Export only visible columns



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

[jira] [Resolved] (IGNITE-1860) SQL: Do not export system columns if they are OFF (invisible)

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-1860.

   Resolution: Fixed
 Assignee: Vasiliy Sisko
Fix Version/s: 1.7

Fixed. Vasiliy please test.

> SQL: Do not export system columns if they are OFF (invisible)
> -
>
> Key: IGNITE-1860
> URL: https://issues.apache.org/jira/browse/IGNITE-1860
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
>
> Export only visible columns



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

[jira] [Commented] (IGNITE-1223) Use Gson instead of net.sf.json-lib:json-lib:2.4

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-1223:


Used jackson v2 instead of Gson because it serializes only fields.

> Use Gson instead of net.sf.json-lib:json-lib:2.4
> 
>
> Key: IGNITE-1223
> URL: https://issues.apache.org/jira/browse/IGNITE-1223
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergey Evdokimov
> Fix For: 1.7
>
> Attachments: master_ae11e9b_ignite-1223.patch
>
>
> Gson faster then "net.sf.json-lib:json-lib:2.4" 4 times. (Serialization of 
> GridRestCommand#NODE responce 2 times take 1,45 seconds with Gson and 5,8 
> seconds with json-lib. Also json-lib cannot work with gridgain-style getters 
> and setters.



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

[jira] [Created] (IGNITE-3338) CachePartialUpdateCheckedException: Failed to update keys during load test with eviction configured

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-3338:
---

 Summary: CachePartialUpdateCheckedException: Failed to update keys 
during load test with eviction configured
 Key: IGNITE-3338
 URL: https://issues.apache.org/jira/browse/IGNITE-3338
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Ksenia Rybakova
 Fix For: 1.7


The following exceptions occur during load test with eviction configured:

{noformat}
ERROR: The benchmark of random operation failed.
Type '--help' for usage.
Finishing main test [ts=1466178657166, date=Fri Jun 17 08:50:57 PDT 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
(retry update if possible).: [26, 1872066, 1945790, 2405741, 3845651, 
4830233, 7284502, 8555643]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1467)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1972)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.removeAll(IgniteCacheProxy.java:1416)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doRemoveAll(IgniteCacheRandomOperationBenchmark.java:809)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:551)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:509)
at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:156)
at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
at java.lang.Thread.run(Thread.java:745)
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [26, 1872066, 1945790, 
2405741, 3845651, 4830233, 7284502, 8555643]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:311)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2958)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:129)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:266)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:264)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
... 1 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:369)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1711)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1482)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:2937)
at 

[jira] [Assigned] (IGNITE-3277) Migrate rest-http from outdated json-lib to Jackson

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-3277:


Assignee: Alexey Kuznetsov  (was: Semen Boikov)

Reviewed, looks good.

> Migrate rest-http from outdated json-lib to Jackson
> ---
>
> Key: IGNITE-3277
> URL: https://issues.apache.org/jira/browse/IGNITE-3277
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.7
>
>
> ignite-rest-http module uses json-lib 2.4 [1] for java to JSON 
> transformations and this library last release was on 2010-12-14.
> This is very old library and after some investigations I found that it 
> produce a lot of garbage during java to JSON transformation.
> I'm planing to replace json-lib 2.4 with Jackson 2.x [2]
> 1. https://sourceforge.net/projects/json-lib
> 2. https://github.com/FasterXML/jackson



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

[jira] [Resolved] (IGNITE-3298) Action "Export all" does not work on SQL page

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-3298.
--
Resolution: Cannot Reproduce
  Assignee: Vasiliy Sisko

Failed to reproduce.

> Action "Export all" does not work on SQL page
> -
>
> Key: IGNITE-3298
> URL: https://issues.apache.org/jira/browse/IGNITE-3298
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
>
> Log is empty.



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