[jira] [Commented] (IGNITE-1923) [Test failed] IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed fails with portable marshaller

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-1923:
--

Thank for your contribution! Looks good.

> [Test failed] 
> IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed
>  fails with portable marshaller
> --
>
> Key: IGNITE-1923
> URL: https://issues.apache.org/jira/browse/IGNITE-1923
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Priority: Trivial
> Fix For: 1.5
>
>
> {{IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed}}
>  fails with portable marshaller. Test is incorrect.



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

[jira] [Closed] (IGNITE-1912) .Net: Continuous query does not work for value types

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1912.
---

> .Net: Continuous query does not work for value types
> 
>
> Key: IGNITE-1912
> URL: https://issues.apache.org/jira/browse/IGNITE-1912
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> OldValue comes as Null from java, but we try to deserialize it as TK, which 
> fails for value types.
> Need to employ the same approach as in cache with CacheResult.



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

[jira] [Closed] (IGNITE-1923) [Test failed] IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed fails with portable marshaller

[Andrey Gura (JIRA)]

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

Andrey Gura closed IGNITE-1923.
---

> [Test failed] 
> IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed
>  fails with portable marshaller
> --
>
> Key: IGNITE-1923
> URL: https://issues.apache.org/jira/browse/IGNITE-1923
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Priority: Trivial
> Fix For: 1.5
>
>
> {{IgniteCacheP2pUnmarshallingQueryErrorTest.testResponseMessageOnRequestUnmarshallingFailed}}
>  fails with portable marshaller. Test is incorrect.



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

[jira] [Commented] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-803:


Modified the tests in way that there is always a primary or backup that holds 
an atomic value or distributed data structure. 
Performed additional improvements in failover processing.

Presently almost all tests pass except multy-failover tests for 
{{IgniteAtomicSequence}} and {{IgniteQueue}} that fail from time to time. The 
reason of the failure caused by some issues in the implementation of this 
classes and hard to debug. I prefer to merge the current changes and create 
dedicated JIRA issues for the rest of failing tests cause there is no reason to 
have 60 muted tests until we haven't fixed two more.

Checking all the changes with TC. The patch was attached to IGNITE-801. 

> [Test] DataStructures failover tests fail with partitioned cache
> 
>
> Key: IGNITE-803
> URL: https://issues.apache.org/jira/browse/IGNITE-803
> Project: Ignite
>  Issue Type: Sub-task
> Environment: See GG-2699
>Reporter: Artem Shutak
>Assignee: Denis Magda
>  Labels: Muted_test
> Fix For: 1.5
>
>
> See GG-2699



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

[jira] [Updated] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-803:
---
Fix Version/s: 1.5

> [Test] DataStructures failover tests fail with partitioned cache
> 
>
> Key: IGNITE-803
> URL: https://issues.apache.org/jira/browse/IGNITE-803
> Project: Ignite
>  Issue Type: Sub-task
> Environment: See GG-2699
>Reporter: Artem Shutak
>Assignee: Denis Magda
>  Labels: Muted_test
> Fix For: 1.5
>
>
> See GG-2699



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

[jira] [Updated] (IGNITE-1933) .Net: GetOrCreateCache overloads with CacheConfiguration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1933:

Assignee: (was: Pavel  Tupitsyn)

> .Net: GetOrCreateCache overloads with CacheConfiguration
> 
>
> Key: IGNITE-1933
> URL: https://issues.apache.org/jira/browse/IGNITE-1933
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Add GetOrCreateCache overloads that accept CacheConfiguration, similar to 
> Ignite in Java.



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

[jira] [Created] (IGNITE-1933) .Net: GetOrCreateCache overloads with CacheConfiguration

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1933:
---

 Summary: .Net: GetOrCreateCache overloads with CacheConfiguration
 Key: IGNITE-1933
 URL: https://issues.apache.org/jira/browse/IGNITE-1933
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: 1.6


Add GetOrCreateCache overloads that accept CacheConfiguration, similar to 
Ignite in Java.



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

[jira] [Closed] (IGNITE-1921) .Net: Handle leak during ComputeJobHolder serialization

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1921.
---

> .Net: Handle leak during ComputeJobHolder serialization
> ---
>
> Key: IGNITE-1921
> URL: https://issues.apache.org/jira/browse/IGNITE-1921
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> See where ComputeJobHolder is constructed and serialized. In case of 
> non-serializable user job there is a handle leak.



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

[jira] [Updated] (IGNITE-1907) .Net: Cache configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1907:

Description: Configure cache in code  (was: * Configure cache in code
* Add GetOrCreateCache overloads)

> .Net: Cache configuration
> -
>
> Key: IGNITE-1907
> URL: https://issues.apache.org/jira/browse/IGNITE-1907
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> Configure cache in code



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

[jira] [Updated] (IGNITE-1931) .Net: Store configuration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1931:

Fix Version/s: (was: 1.5)
   1.6

> .Net: Store configuration
> -
>
> Key: IGNITE-1931
> URL: https://issues.apache.org/jira/browse/IGNITE-1931
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Configure store in .NET code



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

[jira] [Updated] (IGNITE-1909) .Net: Discovery configuration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1909:

Fix Version/s: (was: 1.5)
   1.6

> .Net: Discovery configuration
> -
>
> Key: IGNITE-1909
> URL: https://issues.apache.org/jira/browse/IGNITE-1909
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Configure discovery in code



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

[jira] [Created] (IGNITE-1936) implement spa abilities to web-console

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-1936:
-

 Summary: implement spa abilities to web-console
 Key: IGNITE-1936
 URL: https://issues.apache.org/jira/browse/IGNITE-1936
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.6
Reporter: Dmitriyff
Assignee: Dmitriyff
 Fix For: 1.6






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

[jira] [Closed] (IGNITE-1865) Need to add tests on SpringResource annotation

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-1865.
---

> Need to add tests on SpringResource annotation
> --
>
> Key: IGNITE-1865
> URL: https://issues.apache.org/jira/browse/IGNITE-1865
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Roman Shtykh
>  Labels: newbie
>
> Ignite has SpringResource annotation, but there's no unit-tests for it.
> Need to add unit-tests.



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

[jira] [Commented] (IGNITE-1865) Need to add tests on SpringResource annotation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1865:
-

Reviewed, checked, merged to ignite-1.5.

Roman, thanks for the contribution! In addition, please, trigger TeamCity tests 
for changes validation manually. I've updated related section recently:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request


> Need to add tests on SpringResource annotation
> --
>
> Key: IGNITE-1865
> URL: https://issues.apache.org/jira/browse/IGNITE-1865
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Roman Shtykh
>  Labels: newbie
>
> Ignite has SpringResource annotation, but there's no unit-tests for it.
> Need to add unit-tests.



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

[jira] [Commented] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-1926:
-

Can we use {code} IgniteHadoopIgfsSecondaryFileSystem("file:///", null, null); 
file system?
Please see post 
http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-tp1882p1987.html
 .

> Implement IgfsSecondaryFileSystem using java.io.File API
> 
>
> Key: IGNITE-1926
> URL: https://issues.apache.org/jira/browse/IGNITE-1926
> Project: Ignite
>  Issue Type: Improvement
>  Components: IGFS, newbie
>Reporter: Valentin Kulichenko
>Assignee: Ivan Veselovsky
>  Labels: newbie
>
> This will allow to persist IGFS data on the local disk. Currently we have 
> only Hadoop-based implementation.
> Corresponding user thread: 
> http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html



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

[jira] [Assigned] (IGNITE-1933) .Net: GetOrCreateCache overloads with CacheConfiguration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-1933:
---

Assignee: Pavel  Tupitsyn

> .Net: GetOrCreateCache overloads with CacheConfiguration
> 
>
> Key: IGNITE-1933
> URL: https://issues.apache.org/jira/browse/IGNITE-1933
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Add GetOrCreateCache overloads that accept CacheConfiguration, similar to 
> Ignite in Java.



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

[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-529:
-

Roman, 

Thanks for contribution,
Code was successfully merged to Ignite 
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=9a5fc056786494e748c982e0c766fa9842ba523e
and willl be released as a part of 1.5.

P.s. Waiting for Wiki page content.

> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from 
> Apache Flume and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Updated] (IGNITE-1930) Configured class loader is ignored in many places in the code

[Romain Gilles (JIRA)]

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

Romain Gilles updated IGNITE-1930:
--
Assignee: (was: Romain Gilles)

> Configured class loader is ignored in many places in the code
> -
>
> Key: IGNITE-1930
> URL: https://issues.apache.org/jira/browse/IGNITE-1930
> Project: Ignite
>  Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>
> Currently the user-set ClassLoader
> (IgniteConfiguration#setClassLoader) is ignored in many places where iit 
> should be preferred, e.g.:
> * Optimized Marshaller
> * U.gridClassLoader() and its many usages.
> * etc.
> Looks like Ignite should use the user-preferred classloader for everything, 
> and only fallback to getClass().getClassLoader() and other methods as a 
> default.
> Currently the user's ClassLoader is only used from these spots:
> * GridDeploymentManager
> * GridDeploymentPerVersionStore
> * CacheObjectImpl
> * GridCacheDeploymentManager



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

[jira] [Assigned] (IGNITE-1930) Configured class loader is ignored in many places in the code

[Romain Gilles (JIRA)]

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

Romain Gilles reassigned IGNITE-1930:
-

Assignee: Romain Gilles

> Configured class loader is ignored in many places in the code
> -
>
> Key: IGNITE-1930
> URL: https://issues.apache.org/jira/browse/IGNITE-1930
> Project: Ignite
>  Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Romain Gilles
>
> Currently the user-set ClassLoader
> (IgniteConfiguration#setClassLoader) is ignored in many places where iit 
> should be preferred, e.g.:
> * Optimized Marshaller
> * U.gridClassLoader() and its many usages.
> * etc.
> Looks like Ignite should use the user-preferred classloader for everything, 
> and only fallback to getClass().getClassLoader() and other methods as a 
> default.
> Currently the user's ClassLoader is only used from these spots:
> * GridDeploymentManager
> * GridDeploymentPerVersionStore
> * CacheObjectImpl
> * GridCacheDeploymentManager



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

[jira] [Comment Edited] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-1926 at 11/17/15 3:50 PM:
---

Can we use {code} IgniteHadoopIgfsSecondaryFileSystem("file:///", null, 
null);{code} file system?
Please see post 
http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-tp1882p1987.html
 .


was (Author: iveselovskiy):
Can we use {code} IgniteHadoopIgfsSecondaryFileSystem("file:///", null, null); 
file system?
Please see post 
http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-tp1882p1987.html
 .

> Implement IgfsSecondaryFileSystem using java.io.File API
> 
>
> Key: IGNITE-1926
> URL: https://issues.apache.org/jira/browse/IGNITE-1926
> Project: Ignite
>  Issue Type: Improvement
>  Components: IGFS, newbie
>Reporter: Valentin Kulichenko
>Assignee: Ivan Veselovsky
>  Labels: newbie
>
> This will allow to persist IGFS data on the local disk. Currently we have 
> only Hadoop-based implementation.
> Corresponding user thread: 
> http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html



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

[jira] [Commented] (IGNITE-1908) .Net: Query configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1908:
-

Stopping this because new query API (QueryEntity) is not yet finalized.

> .Net: Query configuration
> -
>
> Key: IGNITE-1908
> URL: https://issues.apache.org/jira/browse/IGNITE-1908
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Configure queries in code.
> This includes attribute-based configuration (similar to QuerySqlField in 
> Java).



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

[jira] [Created] (IGNITE-1935) Add sanity tests for GridCacheContext.deferredDelete method

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-1935:
---

 Summary: Add sanity tests for GridCacheContext.deferredDelete 
method
 Key: IGNITE-1935
 URL: https://issues.apache.org/jira/browse/IGNITE-1935
 Project: Ignite
  Issue Type: Test
Reporter: Andrey Gura
Assignee: Andrey Gura
Priority: Minor
 Fix For: 1.5


Need to add sanity tests for {{GridCacheContext.deferredDelete}} method.



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

[jira] [Created] (IGNITE-1934) .Net: Store tests broken after keepPortableInStore renaming

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1934:
---

 Summary: .Net: Store tests broken after keepPortableInStore 
renaming
 Key: IGNITE-1934
 URL: https://issues.apache.org/jira/browse/IGNITE-1934
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
Priority: Blocker
 Fix For: 1.5


Need to fix .net test configs



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

[jira] [Commented] (IGNITE-1934) .Net: Store tests broken after keepPortableInStore renaming

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1934:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1934 .Net: Store tests broken after keepPortableInStore renaming



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

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

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

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


commit ac30f30433aad0a843a67c3d429e55e38de98884
Author: Pavel Tupitsyn 
Date:   2015-11-17T14:42:53Z

IGNITE-1934 .Net: Store tests broken after keepPortableInStore renaming




> .Net: Store tests broken after keepPortableInStore renaming
> ---
>
> Key: IGNITE-1934
> URL: https://issues.apache.org/jira/browse/IGNITE-1934
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> Need to fix .net test configs



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

[jira] [Updated] (IGNITE-1907) .Net: Cache configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1907:

Description: 
* Configure cache in code
* Add GetOrCreateCache overloads

  was:Configure cache in code


> .Net: Cache configuration
> -
>
> Key: IGNITE-1907
> URL: https://issues.apache.org/jira/browse/IGNITE-1907
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> * Configure cache in code
> * Add GetOrCreateCache overloads



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

[jira] [Assigned] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky reassigned IGNITE-1926:
---

Assignee: Ivan Veselovsky

> Implement IgfsSecondaryFileSystem using java.io.File API
> 
>
> Key: IGNITE-1926
> URL: https://issues.apache.org/jira/browse/IGNITE-1926
> Project: Ignite
>  Issue Type: Improvement
>  Components: IGFS, newbie
>Reporter: Valentin Kulichenko
>Assignee: Ivan Veselovsky
>  Labels: newbie
>
> This will allow to persist IGFS data on the local disk. Currently we have 
> only Hadoop-based implementation.
> Corresponding user thread: 
> http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html



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

[jira] [Updated] (IGNITE-1626) .Net: Create NuGet package.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1626:

Fix Version/s: (was: 1.5)
   1.6

> .Net: Create NuGet package.
> ---
>
> Key: IGNITE-1626
> URL: https://issues.apache.org/jira/browse/IGNITE-1626
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.6
>
>
> *Overview*
> To boost usage of the product we need to distribute it using NuGet, which is 
> tightly integrated with Visual Studio.
> To achieve this several technical, infrastructure and marketing tasks must be 
> completed.
> *Technical tasks*
> - Apache Ignite.NET heavily depends on relative positions of compiled Java 
> classes. We must be able to apply different classpath search strategies 
> depending on packaging. This includes normal search in exploded build 
> directory, search in NuGet package, search in local Maven repo.
> - We need a way to select classpath search strategy. E.g. we can add special 
> marker resource to NuGet package so that DLL understands that it is 
> NuGet-based. More investigation here is reuqired.
> - Minimal set of required JARs should be defined. Currently we have over 
> >100Mb of Java libraries shipped with Ignite build. NuGet have limitation of 
> 30Mb per package. Only vital subset of JARs should be shipped.
> *Infrastructure tasks*
> - INFRA team must be asked about a place where NuGet package could be stored. 
> - Separate build plan should be created, producing NuGet artifacts.
> *Marketing tasks*
> - We need to produce clean, selling and intriguing header and description for 
> our package and attach logo.



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

[jira] [Updated] (IGNITE-1896) .Net: Improve query API

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1896:

Fix Version/s: (was: 1.5)
   1.6

> .Net: Improve query API
> ---
>
> Key: IGNITE-1896
> URL: https://issues.apache.org/jira/browse/IGNITE-1896
> Project: Ignite
>  Issue Type: Improvement
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Current API is very clumsy.
> Cache is generic, however we require the user to specify query type 
> explicitly.
> There are cases when query type is a string and/or is different from current 
> cache generic type, so the current API has to be kept.
> However, we should provide simple methods with generic inference:
> {code}
> IQueryCursor> ScanQuery(ICacheEntryFilter 
> filter);
> IQueryCursor> SqlQuery(string sql, params 
> object[] args);
> IQueryCursor> SqlQuery(string sql, bool local, 
> params object[] args);
> IQueryCursor> TextQuery(string text);
> IQueryCursor> TextQuery(string text, bool local);
> {code}



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

[jira] [Closed] (IGNITE-1910) .Net: Possible handle leak in ScanQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1910.
---

> .Net: Possible handle leak in ScanQuery
> ---
>
> Key: IGNITE-1910
> URL: https://issues.apache.org/jira/browse/IGNITE-1910
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> * See ScanQuery.cs, "writer.WriteObject(holder);" line. If it fails due to 
> user filter being non-serializable, we leak a handle.
> * Same thing in Cache.LoadCache
> * Another leak is in Java. If the GridCloseableIteratorAdapter fails in ctor, 
> it does not close keyValFilter.



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

[jira] [Commented] (IGNITE-1900) Ignite JMX problem with Spring Boot

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1900:
-

Reviewed, checked, merged to ignite-1.5.

Thanks for the contribution! In addition, please, trigger TeamCity tests for 
changes validation manually. I've updated related section recently:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request

> Ignite JMX problem with Spring Boot
> ---
>
> Key: IGNITE-1900
> URL: https://issues.apache.org/jira/browse/IGNITE-1900
> Project: Ignite
>  Issue Type: Bug
>  Components: 1.4
>Affects Versions: ignite-1.4
>Reporter: wmz7year
>Assignee: wmz7year
>  Labels: patch
> Fix For: 1.5
>
>
> I use Ignite with Spring Boot.
> When start application,Spring Boot will register JMX info.
> In IgniteMXBean interface,There is two method getUserAttributesFormatted and 
> getLifecycleBeansFormatted return Collection
> But In JMX DefaultMXBeanMappingFactory.makeParameterizedTypeMapping method 
> will get method return type.
> {noformat}
>  final Type rawType = objType.getRawType();
> if (rawType instanceof Class) {
> Class c = (Class) rawType;
> if (c == List.class || c == Set.class || c == SortedSet.class) {
> Type[] actuals = objType.getActualTypeArguments();
> assert(actuals.length == 1);
> if (c == SortedSet.class)
> mustBeComparable(c, actuals[0]);
> return makeArrayOrCollectionMapping(objType, actuals[0], 
> factory);
> } else {
> boolean sortedMap = (c == SortedMap.class);
> if (c == Map.class || sortedMap) {
> Type[] actuals = objType.getActualTypeArguments();
> assert(actuals.length == 2);
> if (sortedMap)
> mustBeComparable(c, actuals[0]);
> return makeTabularMapping(objType, sortedMap,
> actuals[0], actuals[1], factory);
> }
> }
> }
> {noformat}
> The Collection will not match any type for this although IgniteKernal 
> return type is Set or List.
> I think IgniteMXBean interface should change Collection to Set and List



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

[jira] [Closed] (IGNITE-1900) Ignite JMX problem with Spring Boot

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-1900.
---

> Ignite JMX problem with Spring Boot
> ---
>
> Key: IGNITE-1900
> URL: https://issues.apache.org/jira/browse/IGNITE-1900
> Project: Ignite
>  Issue Type: Bug
>  Components: 1.4
>Affects Versions: ignite-1.4
>Reporter: wmz7year
>Assignee: wmz7year
>  Labels: patch
> Fix For: 1.5
>
>
> I use Ignite with Spring Boot.
> When start application,Spring Boot will register JMX info.
> In IgniteMXBean interface,There is two method getUserAttributesFormatted and 
> getLifecycleBeansFormatted return Collection
> But In JMX DefaultMXBeanMappingFactory.makeParameterizedTypeMapping method 
> will get method return type.
> {noformat}
>  final Type rawType = objType.getRawType();
> if (rawType instanceof Class) {
> Class c = (Class) rawType;
> if (c == List.class || c == Set.class || c == SortedSet.class) {
> Type[] actuals = objType.getActualTypeArguments();
> assert(actuals.length == 1);
> if (c == SortedSet.class)
> mustBeComparable(c, actuals[0]);
> return makeArrayOrCollectionMapping(objType, actuals[0], 
> factory);
> } else {
> boolean sortedMap = (c == SortedMap.class);
> if (c == Map.class || sortedMap) {
> Type[] actuals = objType.getActualTypeArguments();
> assert(actuals.length == 2);
> if (sortedMap)
> mustBeComparable(c, actuals[0]);
> return makeTabularMapping(objType, sortedMap,
> actuals[0], actuals[1], factory);
> }
> }
> }
> {noformat}
> The Collection will not match any type for this although IgniteKernal 
> return type is Set or List.
> I think IgniteMXBean interface should change Collection to Set and List



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

[jira] [Created] (IGNITE-1937) ignite-flume module

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-1937:
-

 Summary: ignite-flume module
 Key: IGNITE-1937
 URL: https://issues.apache.org/jira/browse/IGNITE-1937
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
 Fix For: 1.5


Ignite flume should have following:
 - added as an optional module for binary fabric package
 - uploaded on maven repository
 - README.TXT 



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

[jira] [Commented] (IGNITE-1938) NullPointerException/IllegalMonitorStateException under IBM SDK 8

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-1938:
-

The problem in JIT of IBM J9 8.0-1.10. If JIT is switched off the problem 
doesn't reproduce. Unfortunatelly I can't file ticket in IBM bugtracker. The 
work around is disabling of compilation {{GridDhtAtomicCache.unlockEntries}} 
and {{GridDhtAtomicCache.lockEntries}} by JIT using the following JVM option:

{noformat}
-Xjit:exclude={org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affinity/AffinityTopologyVersion;)V|org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.lockEntries(Ljava/util/List;Lorg/apache/ignite/internal/processors/affinity/AffinityTopologyVersion;)Ljava/util/List;}
{noformat}

Similar way can be used in case of problems with other methods.

> NullPointerException/IllegalMonitorStateException under IBM SDK 8
> -
>
> Key: IGNITE-1938
> URL: https://issues.apache.org/jira/browse/IGNITE-1938
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>
> {{CachePutGetExample}} fails under IBM J9 8.0-1.10. Also similar problem was 
> reported on user-list: 
> https://mail-archives.apache.org/mod_mbox/ignite-user/201511.mbox/%3c1446577964016-1830.p...@n6.nabble.com%3E
> Usually Ignite throws {{NullPointerException}} or 
> {{IllegalMonitorStateException}} or both (see below) from 
> {{GridDhtAtomicCache.lockEntries}} and {{GridDhtAtomicCache.unlockEntries}}. 
> Sometimes JVM crashes with {{SIGSEGV}} and {{vmState=0x}} code in 
> {{ibj9jit28.so}} module. In rare cases system just hangs.
> {noformat}
> [22:16:11,241][ERROR][main][GridDhtAtomicCache]  
> Unexpected exception during cache update
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lockEntries(GridDhtAtomicCache.java:2161)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1100)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1060)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:291)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:841)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:839)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:645)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:839)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAsync0(GridDhtAtomicCache.java:378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2218)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put(GridDhtAtomicCache.java:354)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:1924)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1017)
>   at 
> org.apache.ignite.examples.datagrid.CachePutGetExample.putGet(CachePutGetExample.java:72)
>   at 
> org.apache.ignite.examples.datagrid.CachePutGetExample.main(CachePutGetExample.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>   at 

[jira] [Created] (IGNITE-1938) NullPointerException/IllegalMonitorStateException under IBM SDK 8

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-1938:
---

 Summary: NullPointerException/IllegalMonitorStateException under 
IBM SDK 8
 Key: IGNITE-1938
 URL: https://issues.apache.org/jira/browse/IGNITE-1938
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura
Assignee: Andrey Gura


{noformat}
[22:16:11,241][ERROR][main][GridDhtAtomicCache]  Unexpected 
exception during cache update
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lockEntries(GridDhtAtomicCache.java:2161)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1100)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1060)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:462)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(GridNearAtomicUpdateFuture.java:73)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:891)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:291)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:841)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:839)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:645)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:839)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAsync0(GridDhtAtomicCache.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2218)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put(GridDhtAtomicCache.java:354)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:1924)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1017)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.putGet(CachePutGetExample.java:72)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.main(CachePutGetExample.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{noformat}

{noformat}
Exception in thread "main" org.apache.ignite.cache.CachePartialUpdateException: 
Failed to update keys (retry update if possible).: [5372]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1615)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1750)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1024)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.putGet(CachePutGetExample.java:72)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.main(CachePutGetExample.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [5372]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1186)
at 

[jira] [Resolved] (IGNITE-1686) Autoscrolling to the newly created query

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-1686.

Assignee: Pavel Konstantinov  (was: Andrey Novikov)

> Autoscrolling to the newly created query
> 
>
> Key: IGNITE-1686
> URL: https://issues.apache.org/jira/browse/IGNITE-1686
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1686.png
>
>
> Currently user must scroll the page manually.



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

[jira] [Closed] (IGNITE-1867) Fix java class names and package declaration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-1867.
--
Assignee: (was: Pavel Konstantinov)

Tested.

> Fix java class names and package declaration
> 
>
> Key: IGNITE-1867
> URL: https://issues.apache.org/jira/browse/IGNITE-1867
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Prachi Garg
> Fix For: 1.5
>
>
> I noticed a few issues when I imported my project, created using the web 
> console, in IDEA -
> 1. ServerConfigurationFactory class name is create in the file called 
> “ConfigurationFactory.java”. Class name and file name should be the same.
> 2. The package declaration for ClientConfigurationFactory and 
> SeverConfigurationFactory classes is missing.
> 3. There should be simple 'nodeStartup' class for starting a node, in the 
> IDE, using the XML configuration file.
> 4. Missing near configuration for client in java code.



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

[jira] [Closed] (IGNITE-1806) Rework UI and code generation to new query configuration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-1806.
--
Assignee: (was: Pavel Konstantinov)

Tested.

> Rework UI and code generation to new query configuration
> 
>
> Key: IGNITE-1806
> URL: https://issues.apache.org/jira/browse/IGNITE-1806
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
> Fix For: 1.5
>
>
> New query configuration is being implemented in ignite-950-new branch.
> Web Console should correspond to new implementation.



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

[jira] [Closed] (IGNITE-1686) Autoscrolling to the newly created query

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-1686.
--
Assignee: (was: Pavel Konstantinov)

Tested.

> Autoscrolling to the newly created query
> 
>
> Key: IGNITE-1686
> URL: https://issues.apache.org/jira/browse/IGNITE-1686
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1686.png
>
>
> Currently user must scroll the page manually.



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

[jira] [Updated] (IGNITE-1886) NPE in H2 when running query with subselects

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1886:

Attachment: QueryTest.java

Test is attached.

> NPE in H2 when running query with subselects
> 
>
> Key: IGNITE-1886
> URL: https://issues.apache.org/jira/browse/IGNITE-1886
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: 1.5
>
> Attachments: QueryTest.java
>
>
> Test reproducing the issue is attached. NPE is thrown as a result (see below).
> Corresponding user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:636)
>   at 
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
> SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:641)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:627)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> query: SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END 
> id FROM "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT 
> CASE WHEN og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1510)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:634)
>   ... 7 more
> Caused by: javax.cache.CacheException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:938)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:636)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:634)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   ... 8 more
> Caused by: org.h2.jdbc.JdbcSQLException: General error: 
> "java.lang.NullPointerException" [5-175]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
>   at org.h2.message.DbException.get(DbException.java:161)
>   at org.h2.message.DbException.convert(DbException.java:284)
>   at org.h2.message.DbException.toSQLException(DbException.java:257)
>   at org.h2.message.TraceObject.logAndConvert(TraceObject.java:368)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:270)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:935)
>   ... 12 more
> Caused by: java.lang.NullPointerException
>   at 

[jira] [Commented] (IGNITE-1686) Autoscrolling to the newly created query

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-1686:


Added expand to panel.

> Autoscrolling to the newly created query
> 
>
> Key: IGNITE-1686
> URL: https://issues.apache.org/jira/browse/IGNITE-1686
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
> Attachments: ig-1686.png
>
>
> Currently user must scroll the page manually.



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

[jira] [Assigned] (IGNITE-1908) .Net: Query configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-1908:
---

Assignee: Pavel  Tupitsyn

> .Net: Query configuration
> -
>
> Key: IGNITE-1908
> URL: https://issues.apache.org/jira/browse/IGNITE-1908
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> Configure queries in code.
> This includes attribute-based configuration (similar to QuerySqlField in 
> Java).



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

[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-529:
-

Roman, 

Seems page is private due to 1.5 is not releaset yet. 
I think that I can create initial markup with text you'll provide and after 
release you'll sugest final changes. Thats our first documentation from 
contributor, so minor issues is the norm ;) 
I'll check pull request today and push it in case everythyng is ok.


> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from 
> Apache Flume and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Created] (IGNITE-1930) Configured class loader is ignored in many places in the code

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-1930:


 Summary: Configured class loader is ignored in many places in the 
code
 Key: IGNITE-1930
 URL: https://issues.apache.org/jira/browse/IGNITE-1930
 Project: Ignite
  Issue Type: Task
Affects Versions: ignite-1.4
Reporter: Alexey Goncharuk


Currently the user-set ClassLoader
(IgniteConfiguration#setClassLoader) is ignored in many places where iit should 
be preferred, e.g.:

* Optimized Marshaller
* U.gridClassLoader() and its many usages.
* etc.

Looks like Ignite should use the user-preferred classloader for everything, and 
only fallback to getClass().getClassLoader() and other methods as a default.

Currently the user's ClassLoader is only used from these spots:

* GridDeploymentManager
* GridDeploymentPerVersionStore
* CacheObjectImpl
* GridCacheDeploymentManager



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

[jira] [Commented] (IGNITE-1907) .Net: Cache configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1907:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1907 .Net: Cache configuration



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

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

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

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


commit 39a8bc65a3d8f20145153c614ca4e9746ce331d6
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:40:03Z

IGNITE-1907 .Net: Cache configuration

commit c73d82dfe0e47d16fbfbb0a270d822bd9c8246db
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:47:22Z

IGNITE-1907 .Net: Cache configuration

commit 5e94417d8946d1b92541e83869f14cb8fdc38da9
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:54:51Z

wip

commit 5fce7a1247c4bc34789b8733b921ecfcb4cbdf64
Author: Pavel Tupitsyn 
Date:   2015-11-16T14:17:43Z

wip

commit a4e9c1da1c50dc1081dc97b3aa8eafdecf52fec2
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:23:00Z

wip

commit ad0ff6eb90246c71bd7e7687f3855820e2a9621d
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:29:28Z

wip

commit 1ceca1200fbb98b96c10c173c24d30d80712b94b
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:35:59Z

unit test skeleton

commit 11ed6a55c9d6f1d6a6a77b9f9ecbece135402796
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:41:51Z

wip GetConfiguration

commit 033c5e35d2304976cddd428ccf92e76e2eb039c1
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:50:34Z

wip

commit 45938e6ff0cf0a51726bf82886f53d3f20bc8a9b
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:52:02Z

wip test

commit 8bbb57919397f36697ea6d885418d0de92c02b02
Author: Pavel Tupitsyn 
Date:   2015-11-16T16:36:10Z

wip

commit 3fc284307f15e63c8d12e6a1a13c61f2a3b01ebc
Author: Pavel Tupitsyn 
Date:   2015-11-16T16:49:02Z

wip CacheConfiguration

commit 8a702577910b6d263c99b39c0bccbdd34a09aaf1
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:08:52Z

wip

commit 3bde86ddc3f81b767c8718673b6f8e0c7a89ddcb
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:12:38Z

wip

commit 3960e0aee4c36b6f47181bf79fbd7eb962ae7344
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:16:50Z

wip enums

commit c80dfc80379c3c2640ec2dcf36494112d4bdcd94
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:20:08Z

wip enums

commit 17fb91293a5569f4d0bc924008f7fabbfff2eb73
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:28:34Z

wip enums

commit b74e4c705843d3e9822fcbf2415ae0666b9a8ec5
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:32:58Z

enums done

commit 58f0611a519fd2c82d0af8329145089726deea51
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:59:41Z

wip default values

commit 6d4c3deb39d18ad5a01a74da37acc464fb2889fc
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:09:56Z

Default values done

commit c23078a52683d998e2f5265fa511600418de8dfa
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:13:37Z

cleanup wip

commit 27f12b17c6e00eb1125b1b7ce0fb2025e096b337
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:22:29Z

wip docs

commit 88f52a6ff309f03934bdb4f5da558d9eb8155965
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:32:20Z

Docs done

commit e8ad49508b93ce50dde1f4bfcfe1c19890588c82
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:38:22Z

Timespans instead of milliseconds

commit b2a2382c2fed12ca0ee3e456d4b8f46a4766963c
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:45:19Z

Read from stream

commit 6fbe92cf73a13b856d89dce44bd5bbb5d7283f67
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:51:46Z

write to stream

commit 929477791e9acac41e3ac3d040d082ea8c1f88a9
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:55:32Z

wip

commit e8fbf65080d06726681e753a1b7a446dcd861295
Author: Pavel Tupitsyn 
Date:   2015-11-17T09:02:39Z

wip

commit c89d43c0cd9e50f22ad69f4eb17c9e069f39bb92
Author: Pavel Tupitsyn 
Date:   2015-11-17T09:14:35Z

wip tests

commit 

[jira] [Created] (IGNITE-1931) .Net: Store configuration

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1931:
---

 Summary: .Net: Store configuration
 Key: IGNITE-1931
 URL: https://issues.apache.org/jira/browse/IGNITE-1931
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
 Fix For: 1.5


Configure store in .NET code



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

[jira] [Commented] (IGNITE-1937) ignite-flume module

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-1937:
--

Sergey,

I checked latest 1.5 prerelease build and it has ignite-flume as an optional 
module for binary fabric (lgpl & nolgpl) package.
Latest 1.5 prerelease maven staging also contains ingnite flume jars.

So, the only one issue is missing of README.TXT. Shoul we replace README.md 
with same README.TXT?

> ignite-flume module
> ---
>
> Key: IGNITE-1937
> URL: https://issues.apache.org/jira/browse/IGNITE-1937
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Ignite flume should have following:
>  - added as an optional module for binary fabric package
>  - uploaded on maven repository
>  - README.TXT 



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

[jira] [Commented] (IGNITE-1816) Portables: optionally do not write field IDs to object footer.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-1816:
-

Merged all subtasks. What is left:
1) Merge 1282;
2) Add cross-node valudation;
3) Add cross-node validation tests.

> Portables: optionally do not write field IDs to object footer.
> --
>
> Key: IGNITE-1816
> URL: https://issues.apache.org/jira/browse/IGNITE-1816
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> 1) Implement compact schema write mode - instead of writting it in object 
> footer, we can store field IDs in REPLICATED metadata cache.
> When object is written in compact format, 0x10h flag must be set.
> 2) Add optional global switch on configuration to choose between compact 
> (default) and non-compact modes.



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

[jira] [Created] (IGNITE-1939) Create proper FIX for angular-strap dropdown SelectAll/DeselectAll or even use another component instead

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-1939:


 Summary: Create proper FIX for angular-strap dropdown 
SelectAll/DeselectAll or even use another component instead
 Key: IGNITE-1939
 URL: https://issues.apache.org/jira/browse/IGNITE-1939
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Assignee: Andrey Novikov


In case of drop-down with more than 100 items SelectAll/DeselectAll take too 
much time.

Dirty hack is here 
[https://github.com/akuznetsov-gridgain/angular-strap/tree/fix-1852-2.3.6], but 
this will never be merged.

We need to create clean solution or may be use angular-UI dropdown instead.



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

[jira] [Closed] (IGNITE-1847) Portables: add "field" method to PortableMetadata.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1847.
---

> Portables: add "field" method to PortableMetadata.
> --
>
> Key: IGNITE-1847
> URL: https://issues.apache.org/jira/browse/IGNITE-1847
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> 1) Add "PortableField field()" method to PortableMetadata. Currently it is 
> located on "PortableObject", which is wrong.
> 2) PortableObject "field" and "hasField" methods must go through cached 
> PortableFields.



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

[jira] [Closed] (IGNITE-1902) NET: Adopt new marshalling flags.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1902.
---

> NET: Adopt new marshalling flags.
> -
>
> Key: IGNITE-1902
> URL: https://issues.apache.org/jira/browse/IGNITE-1902
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> As a part of IGNITE-1816 I had to revisit our flags. Here are how they look 
> now:
> {code}
> /** Flag: user type. */
> public static final short FLAG_USR_TYP = 0x0001;
> /** Flag: schema exists. */
> public static final short FLAG_HAS_SCHEMA = 0x0002;
> /** Flag indicating that object has raw data. */
> public static final short FLAG_HAS_RAW = 0x0004;
> /** Flag: offsets take 1 byte. */
> public static final short FLAG_OFFSET_ONE_BYTE = 0x0008;
> /** Flag: offsets take 2 bytes. */
> public static final short FLAG_OFFSET_TWO_BYTES = 0x0010;
> /** Flag: compact footer, no field IDs. */
> public static final short FLAG_COMPACT_FOOTER = 0x0020;
> {code}
> The following changes must be made to NET:
> 1) When schema exists (i.e. at least on non-raw fieid was written), HAS_ 
> SCHEMA flag is set to true. This is the inversed version of what previously 
> was "RAW_ONLY".
> 2) When raw data exists, HAS_RAW flag is set to true. This flag should be 
> used to determine location of raw data. 
> *DO NOT USE % for this anymore!*
> 3) For now COMPACT_FOOTER should always be 0. If you receive an object with 
> this flag set to 1, an exception must be thrown.



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

[jira] [Commented] (IGNITE-1937) ignite-flume module

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-1937:
--

If this is about IGNITE-529 implementation, it has already README. Please check 
README.md
And Anton and I are preparing a page at readme.io

> ignite-flume module
> ---
>
> Key: IGNITE-1937
> URL: https://issues.apache.org/jira/browse/IGNITE-1937
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.5
>
>
> Ignite flume should have following:
>  - added as an optional module for binary fabric package
>  - uploaded on maven repository
>  - README.TXT 



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

[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-529:
-

Anton,

Thank you. I am a bit busy this week but I hope I can provide contents by the 
beginning of the next week at the latest.

> Implement IgniteFlumeStreamer to stream data from Apache Flume
> --
>
> Key: IGNITE-529
> URL: https://issues.apache.org/jira/browse/IGNITE-529
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Roman Shtykh
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Flume|http://flume.apache.org/] for more information.
> We should create {{IgniteFlumeStreamer}} which will consume messages from 
> Apache Flume and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> * Convert Flume data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Updated] (IGNITE-1938) NullPointerException/IllegalMonitorStateException under IBM SDK 8

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-1938:

Description: 
{{CachePutGetExample}} fails under IBM J9 8.0-1.10. Also similar problem was 
reported on user-list: 
https://mail-archives.apache.org/mod_mbox/ignite-user/201511.mbox/%3c1446577964016-1830.p...@n6.nabble.com%3E

Usually Ignite throws {{NullPointerException}} or 
{{IllegalMonitorStateException}} or both (see below) from 
{{GridDhtAtomicCache.lockEntries}} and {{GridDhtAtomicCache.unlockEntries}}. 
Sometimes JVM crashes with {{SIGSEGV}} and {{vmState=0x}} code in 
{{ibj9jit28.so}} module. In rare cases system just hangs.

{noformat}
[22:16:11,241][ERROR][main][GridDhtAtomicCache]  Unexpected 
exception during cache update
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lockEntries(GridDhtAtomicCache.java:2161)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1100)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1060)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:462)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(GridNearAtomicUpdateFuture.java:73)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:891)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:291)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:841)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply(GridDhtAtomicCache.java:839)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:645)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:839)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAsync0(GridDhtAtomicCache.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2218)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put(GridDhtAtomicCache.java:354)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:1924)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1017)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.putGet(CachePutGetExample.java:72)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.main(CachePutGetExample.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{noformat}

{noformat}
Exception in thread "main" org.apache.ignite.cache.CachePartialUpdateException: 
Failed to update keys (retry update if possible).: [5372]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1615)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1750)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1024)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.putGet(CachePutGetExample.java:72)
at 
org.apache.ignite.examples.datagrid.CachePutGetExample.main(CachePutGetExample.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: class 

[jira] [Closed] (IGNITE-1934) .Net: Store tests broken after keepPortableInStore renaming

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1934.
---

> .Net: Store tests broken after keepPortableInStore renaming
> ---
>
> Key: IGNITE-1934
> URL: https://issues.apache.org/jira/browse/IGNITE-1934
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Need to fix .net test configs



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