[jira] [Commented] (IGNITE-1886) NPE in H2 when running query with subselects
[
https://issues.apache.org/jira/browse/IGNITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011397#comment-15011397
]
Sergi Vladykin commented on IGNITE-1886:
This is fixed in newer H2 version.
> 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] [Updated] (IGNITE-1510) Weird format() and remove() semantics.
[ https://issues.apache.org/jira/browse/IGNITE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky updated IGNITE-1510: Description: Currently we have two methods to remove something from IGFS: 1) remove - performs soft delete for PRIMARY mode and hard delete for others 2) format - delete of all IGFS data without touching seocndary file system, which can be either soft or hard depending on some very coutner-intuitive conditions. I think we should do the following: 1) remove operation stays as is. 2) format method is deprecated and just falls-back to a new method "clear(ROOT)". 3) "clear" operation is semantically identical to cache clear: remove in-memory data, do not touch persistence layer. Essentially it just moves a tree into the trash just like remove does. But also this operation will offer sync and async modes. In sync mode operation exits when all in-memory data is really removed even from trash. was: Currently we have two methods to remove something from IGFS: 1) remove - performs soft delete for PRIMARY mode and hard delete for others 2) format - delete of all IGFS data without touching seocndary file system, which can be either soft or hard depending on some very coutner-intuitive conditions. I think we should do the following: 1) remove operation stays as is. 2) format method is deprecated and just falls-back to a new method "clear(ROOT)". 3) "clear" operation is semantically identical to cache clear: remove in-memory data, do not touch persistence layer. Essentially it just moves a tree into the trash just like remove does. But also this operation will offer sync and async modes. In sync mode operation exits when all data in-memory data is really removed even from trash. > Weird format() and remove() semantics. > -- > > Key: IGNITE-1510 > URL: https://issues.apache.org/jira/browse/IGNITE-1510 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Ivan Veselovsky >Priority: Critical > Fix For: 1.5 > > > Currently we have two methods to remove something from IGFS: > 1) remove - performs soft delete for PRIMARY mode and hard delete for others > 2) format - delete of all IGFS data without touching seocndary file system, > which can be either soft or hard depending on some very coutner-intuitive > conditions. > I think we should do the following: > 1) remove operation stays as is. > 2) format method is deprecated and just falls-back to a new method > "clear(ROOT)". > 3) "clear" operation is semantically identical to cache clear: remove > in-memory data, do not touch persistence layer. Essentially it just moves a > tree into the trash just like remove does. But also this operation will offer > sync and async modes. In sync mode operation exits when all in-memory data is > really removed even from trash. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
[
https://issues.apache.org/jira/browse/IGNITE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk closed IGNITE-1377.
Assignee: Alexey Goncharuk (was: Semen Boikov)
> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
> Issue Type: Sub-task
> Components: general, interop
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.5
>
>
> I removed metadata update on for objects not defined in configuration (this
> is not an introduced bug, it existed before) because it causes portable
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute
> {{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1909) .Net: Discovery configuration
[ https://issues.apache.org/jira/browse/IGNITE-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1909: Description: Configure discovery in code: * support TcpDiscoverySpi only * provide a way to set TcpDiscoverySpi properties in code was:Configure discovery in code > .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 >Assignee: Pavel Tupitsyn > Fix For: 1.6 > > > Configure discovery in code: > * support TcpDiscoverySpi only > * provide a way to set TcpDiscoverySpi properties in code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
[
https://issues.apache.org/jira/browse/IGNITE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-1377.
--
Resolution: Fixed
> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
> Issue Type: Sub-task
> Components: general, interop
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.5
>
>
> I removed metadata update on for objects not defined in configuration (this
> is not an introduced bug, it existed before) because it causes portable
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute
> {{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
[
https://issues.apache.org/jira/browse/IGNITE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011178#comment-15011178
]
Alexey Goncharuk commented on IGNITE-1377:
--
Merged proposed changes to ignite-1282
> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
> Issue Type: Sub-task
> Components: general, interop
>Reporter: Alexey Goncharuk
>Assignee: Semen Boikov
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.5
>
>
> I removed metadata update on for objects not defined in configuration (this
> is not an introduced bug, it existed before) because it causes portable
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute
> {{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1931) .Net: Store configuration
[ https://issues.apache.org/jira/browse/IGNITE-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-1931. - Resolution: Fixed > .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 >Assignee: Pavel Tupitsyn > Fix For: 1.6 > > > Configure store in .NET code: add ICacheStoreFactory property to the > CacheConfiguration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1944) .Net: IgniteConfiguration properties
Pavel Tupitsyn created IGNITE-1944: --- Summary: .Net: IgniteConfiguration properties Key: IGNITE-1944 URL: https://issues.apache.org/jira/browse/IGNITE-1944 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Fix For: 1.6 Configure basic IgniteConfiguration properties in C# code: * clientMode * timeouts * log frequency * etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1945) Get rid of keepDeserialized flag in configuration
Alexey Goncharuk created IGNITE-1945: Summary: Get rid of keepDeserialized flag in configuration Key: IGNITE-1945 URL: https://issues.apache.org/jira/browse/IGNITE-1945 Project: Ignite Issue Type: Sub-task Reporter: Alexey Goncharuk Assignee: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1790) Implement an Apache Camel Data Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011582#comment-15011582 ] Raúl Kripalani commented on IGNITE-1790: Documentation pending. > Implement an Apache Camel Data Streamer > --- > > Key: IGNITE-1790 > URL: https://issues.apache.org/jira/browse/IGNITE-1790 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > An Apache Camel data streamer would make it possible for a user to use any of > Camel's [150+ adapters/components|http://camel.apache.org/components.html] to > consume data from the outside world and feed it into an Ignite cache. > SOAP, REST, HTTP, WebSockets, FTP, File, XMPP, SMPP, POP3, IMAP, TCP, etc. > This data streamer will instantiate a Camel consumer endpoint, it'll apply > the user-specified StreamTransformer to the incoming Exchange and it'll add > the result to the data streamer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-801) [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010440#comment-15010440
]
Denis Magda commented on IGNITE-801:
Did final improvements. All the tests works fine in different modes. The only
issue is with IgniteAtomicSequence and IgniteQueue which tests fail from time
to time due to some hard to debug issues in the implementation.
I would commit the current changes that fix the failover tests in general and
let us to unmute ~ 60 muted tests. After that I'll create dedicated tests for a
couple of failing tests and they will be investigated separately.
> [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
>
>
> Key: IGNITE-801
> URL: https://issues.apache.org/jira/browse/IGNITE-801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Labels: Muted_test
> Fix For: 1.5
>
> Attachments: ignite-801.patch, ignite-801.patch
>
>
> See GG-5306
> http://94.72.60.102/viewLog.html?buildId=113217=bt6=buildResultsDiv
> {noformat}
> 2013-05-31 10:39:07
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x03a94800 nid=0x648 waiting on
> condition [0x]
>java.lang.Thread.State: RUNNABLE
> "tcp-disco-sock-reader-#2408%a940475f-1965-484a-8a43-0a1fcc3bf292" prio=10
> tid=0x7f06f8b1a000 nid=0x42d runnable [0x7f0702d84000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerInputStreamWrapper.read(GridJdkMarshallerInputStreamWrapper.java:47)
> at
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
> at java.io.ObjectInputStream.init(ObjectInputStream.java:299)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerObjectInputStream.init(GridJdkMarshallerObjectInputStream.java:30)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshaller.unmarshal(GridJdkMarshaller.java:115)
> at
> org.gridgain.grid.spi.discovery.tcp.GridTcpDiscoverySpi$SocketReader.body(GridTcpDiscoverySpi.java:3985)
> at org.gridgain.grid.spi.GridSpiThread.run(GridSpiThread.java:56)
> "Thread-1905" prio=10 tid=0x7f06f8268000 nid=0x428 waiting on condition
> [0x7f06e1f29000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x00078a53c600 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a473b60 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "Thread-1911" prio=10 tid=0x026b1000 nid=0x420 waiting on condition
> [0x7f06e6af4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x000789b76068 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a4738f8 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "SIGTERM handler" daemon prio=10 tid=0x01ec2800 nid=0x41e in
> Object.wait() [0x7f06e8316000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> -
[jira] [Commented] (IGNITE-1835) .Net: Use thread-local pool to store schemas in PortableWriter
[ https://issues.apache.org/jira/browse/IGNITE-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010597#comment-15010597 ] ASF GitHub Bot commented on IGNITE-1835: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/196 > .Net: Use thread-local pool to store schemas in PortableWriter > -- > > Key: IGNITE-1835 > URL: https://issues.apache.org/jira/browse/IGNITE-1835 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Avoid array allocations in PortableWriter by keeping a single ThreadLocal > array to store schema fields. > See SchemaHolder in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1886) NPE in H2 when running query with subselects
[
https://issues.apache.org/jira/browse/IGNITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010711#comment-15010711
]
Denis Magda commented on IGNITE-1886:
-
Serg, please share you investigations result in the following thread
http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html
> 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
>
[jira] [Commented] (IGNITE-462) Revise the logic of IGFS communication start
[ https://issues.apache.org/jira/browse/IGNITE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010951#comment-15010951 ] Ivan Veselovsky commented on IGNITE-462: Item "2)" (Second handshake is performed upon filesystem closing) is not valid any more after some recent changes -- now only one connection is performed per one successful operation. > Revise the logic of IGFS communication start > > > Key: IGNITE-462 > URL: https://issues.apache.org/jira/browse/IGNITE-462 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: sprint-2 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky >Priority: Minor > Fix For: 1.5 > > > See IGNITE-419. > Issues to be addressed: > 1) Is that okay that the client tries several communication protocols in turn > each time it initiates IGFS communication? (There is no way to specify > communication protocol on the client side). > 2) Second handshake is performed upon filesystem closing because the instance > is not cached, so each client FS command involves 2 handshakes. May be this > is just a bug -- need to investigate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-1282) Move GridGain platforms code to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-1282: --- Comment: was deleted (was: At this moment there is error in the ignite-1282 sources: in the /examples/config/ config example-default.xml is renamed into example-ignite.xml. And conversely: example-ignite.xml is renamed into example-default.xml. Please, fix it before merge. Оtherwise many of examples will be failed with "new" example-ignite.xml) > Move GridGain platforms code to Ignite. > --- > > Key: IGNITE-1282 > URL: https://issues.apache.org/jira/browse/IGNITE-1282 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1816) Portables: optionally do not write field IDs to object footer.
[ https://issues.apache.org/jira/browse/IGNITE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1816. --- > 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] [Assigned] (IGNITE-1510) Weird format() and remove() semantics.
[ https://issues.apache.org/jira/browse/IGNITE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Veselovsky reassigned IGNITE-1510: --- Assignee: Ivan Veselovsky > Weird format() and remove() semantics. > -- > > Key: IGNITE-1510 > URL: https://issues.apache.org/jira/browse/IGNITE-1510 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Ivan Veselovsky >Priority: Critical > Fix For: 1.5 > > > Currently we have two methods to remove something from IGFS: > 1) remove - performs soft delete for PRIMARY mode and hard delete for others > 2) format - delete of all IGFS data without touching seocndary file system, > which can be either soft or hard depending on some very coutner-intuitive > conditions. > I think we should do the following: > 1) remove operation stays as is. > 2) format method is deprecated and just falls-back to a new method > "clear(ROOT)". > 3) "clear" operation is semantically identical to cache clear: remove > in-memory data, do not touch persistence layer. Essentially it just moves a > tree into the trash just like remove does. But also this operation will offer > sync and async modes. In sync mode operation exits when all data in-memory > data is really removed even from trash. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1941) BinaryObject: review field() and hasField() methods.
Vladimir Ozerov created IGNITE-1941: --- Summary: BinaryObject: review field() and hasField() methods. Key: IGNITE-1941 URL: https://issues.apache.org/jira/browse/IGNITE-1941 Project: Ignite Issue Type: Task Components: general, interop Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: 1.5 There are TODOs suggesting removal of these methods. I think we should keep these methods because they are convenient shortcuts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1942) Binary format: minimize map lookups during read.
Vladimir Ozerov created IGNITE-1942: --- Summary: Binary format: minimize map lookups during read. Key: IGNITE-1942 URL: https://issues.apache.org/jira/browse/IGNITE-1942 Project: Ignite Issue Type: Task Components: general, interop Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: 1.5 Currently we have to perform at least 3 hash map lookups from BinaryReader to PortableContext: - ID mapper - Schema registry - Class descriptor. We must refactor PortableContext to allow for only single lookup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1940) Wrong file names in the ignite-1282 branch
Vasilisa Sidorova created IGNITE-1940: -- Summary: Wrong file names in the ignite-1282 branch Key: IGNITE-1940 URL: https://issues.apache.org/jira/browse/IGNITE-1940 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.5 Reporter: Vasilisa Sidorova Assignee: Vladimir Ozerov Priority: Critical Fix For: 1.5 At this moment there is error in the ignite-1282 sources: in the /examples/config/ config example-default.xml is renamed into example-ignite.xml. And conversely: example-ignite.xml is renamed into example-default.xml. Please, fix it before merge. Оtherwise many of examples will be failed with "new" example-ignite.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1816) Portables: optionally do not write field IDs to object footer.
[ https://issues.apache.org/jira/browse/IGNITE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-1816. - Resolution: Fixed > 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] [Updated] (IGNITE-1940) Wrong file names in the ignite-1282 branch
[ https://issues.apache.org/jira/browse/IGNITE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1940: Component/s: interop > Wrong file names in the ignite-1282 branch > -- > > Key: IGNITE-1940 > URL: https://issues.apache.org/jira/browse/IGNITE-1940 > Project: Ignite > Issue Type: Bug > Components: general, interop >Affects Versions: 1.5 >Reporter: Vasilisa Sidorova >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > At this moment there is error in the ignite-1282 sources: in the > /examples/config/ config example-default.xml is renamed into > example-ignite.xml. And conversely: example-ignite.xml is renamed into > example-default.xml. Please, fix it before merge. Оtherwise many of examples > will be failed with "new" example-ignite.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1938) NullPointerException/IllegalMonitorStateException under IBM SDK 8
[
https://issues.apache.org/jira/browse/IGNITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura closed IGNITE-1938.
---
> 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 with message
> {{#JITSTATE: t= 2533 VM changed state to NOT_STARTUP}} in JIT log.
> {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
>
[jira] [Resolved] (IGNITE-1938) NullPointerException/IllegalMonitorStateException under IBM SDK 8
[
https://issues.apache.org/jira/browse/IGNITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura resolved IGNITE-1938.
-
Resolution: Won't Fix
> 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 with message
> {{#JITSTATE: t= 2533 VM changed state to NOT_STARTUP}} in JIT log.
> {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)
>
[jira] [Commented] (IGNITE-1910) .Net: Possible handle leak in ScanQuery
[ https://issues.apache.org/jira/browse/IGNITE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010629#comment-15010629 ] ASF GitHub Bot commented on IGNITE-1910: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/232 > .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-1880) .Net: Intermittent "Invalid global JNI handle passed to DeleteGlobalRef"
[
https://issues.apache.org/jira/browse/IGNITE-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010620#comment-15010620
]
ASF GitHub Bot commented on IGNITE-1880:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/213
> .Net: Intermittent "Invalid global JNI handle passed to DeleteGlobalRef"
>
>
> Key: IGNITE-1880
> URL: https://issues.apache.org/jira/browse/IGNITE-1880
> Project: Ignite
> Issue Type: Bug
> Components: interop
>Affects Versions: 1.5
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Example of a failure: http://94.72.60.102/viewLog.html?buildId=565513
> {code}
> [18:07:47] : [Step 10/11] FATAL ERROR in native method: Invalid global JNI
> handle passed to DeleteGlobalRef
> [18:07:47] : [Step 10/11] FATAL ERROR in native method: Bad global or local
> ref passed to JNI
> {code}
> UnmanagedTarget class releases JNI handles in finalizer.
> Finalizers run at non-deterministic time. Due to some irrelevant changes
> there may be failures sometimes. Need to ensure that we do not release the
> same handle twice, and that we pass correct handles from unmanaged code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1884) .Net: JNI local ref can't be accessed from another thread
[
https://issues.apache.org/jira/browse/IGNITE-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010622#comment-15010622
]
ASF GitHub Bot commented on IGNITE-1884:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/215
> .Net: JNI local ref can't be accessed from another thread
> -
>
> Key: IGNITE-1884
> URL: https://issues.apache.org/jira/browse/IGNITE-1884
> Project: Ignite
> Issue Type: Bug
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Documentation:
> https://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/design.html
> {code}
> Local references are only valid in the thread in which they are created. The
> native code must not pass local references from one thread to another.
> {code}
> We have two places where we DO pass local JNI reference to another thread:
> * CacheParallelLoadStoreAdapter
> * CacheTestStore.LoadCache
> And, potentially (due to user code):
> * UnmanagedCallbacks.DataStreamerStreamReceiverInvoke
> For some reason it has worked for us before.
> But renamings in IGNITE-1881 have caused test execution order to change, and
> these store tests cause process crash.
> To reproduce, BinaryBuilderSelfTest (former PortableApiSelfTest) has to be
> executed before store tests. All other tests can be excluded. 100% repro
> rate: "FATAL ERROR in native method: Bad global or local ref passed to JNI".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1935) Add sanity tests for GridCacheContext.deferredDelete method
[
https://issues.apache.org/jira/browse/IGNITE-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura closed IGNITE-1935.
---
> 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] [Commented] (IGNITE-1282) Move GridGain platforms code to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010697#comment-15010697 ] Vasilisa Sidorova commented on IGNITE-1282: At this moment there is error in the ignite-1282 sources: in the /examples/config/ config example-default.xml is renamed into example-ignite.xml. And conversely: example-ignite.xml is renamed into example-default.xml. Please, fix it. Оtherwise many of examples will be failed with "new" example-ignite.xml > Move GridGain platforms code to Ignite. > --- > > Key: IGNITE-1282 > URL: https://issues.apache.org/jira/browse/IGNITE-1282 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1662) .Net: Improve docs for IEvents and IMessaging.
[ https://issues.apache.org/jira/browse/IGNITE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010570#comment-15010570 ] ASF GitHub Bot commented on IGNITE-1662: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/148 > .Net: Improve docs for IEvents and IMessaging. > -- > > Key: IGNITE-1662 > URL: https://issues.apache.org/jira/browse/IGNITE-1662 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Looks like our documentation in these classes is insufficient. User must have > very clear undestanding on what will happen in case returning true or false > in various use cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1367) Platforms .Net: Move grid executable to Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010566#comment-15010566 ] ASF GitHub Bot commented on IGNITE-1367: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/70 > Platforms .Net: Move grid executable to Ignite > -- > > Key: IGNITE-1367 > URL: https://issues.apache.org/jira/browse/IGNITE-1367 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > * Create Apache.Ignite.exe > * Unignore forked tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1693) .Net: Rename IMessage.Send(IEnumerable, object) method.
[
https://issues.apache.org/jira/browse/IGNITE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010615#comment-15010615
]
ASF GitHub Bot commented on IGNITE-1693:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/160
> .Net: Rename IMessage.Send(IEnumerable, object) method.
> ---
>
> Key: IGNITE-1693
> URL: https://issues.apache.org/jira/browse/IGNITE-1693
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> As some of integral .Net types implement "IEnumerable", we should rename the
> method
> {code}
> IMessage.Send(IEnumerable, object);
> {code}
> to
> {code}
> IMessage.SendAll(IEnumerable, object);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1696) .Net: Ignite does not start with IBM JDK
[ https://issues.apache.org/jira/browse/IGNITE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010613#comment-15010613 ] ASF GitHub Bot commented on IGNITE-1696: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/161 > .Net: Ignite does not start with IBM JDK > > > Key: IGNITE-1696 > URL: https://issues.apache.org/jira/browse/IGNITE-1696 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > ERROR: Failed to load jvm.dll ([option=JAVA_HOME, > path=C:\Java\ibm_sdk71\jre\bin\server\jvm.dll, errorCode=126]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1646) .Net: IgniteGuid must be serializable and portable.
[ https://issues.apache.org/jira/browse/IGNITE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010614#comment-15010614 ] ASF GitHub Bot commented on IGNITE-1646: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/164 > .Net: IgniteGuid must be serializable and portable. > --- > > Key: IGNITE-1646 > URL: https://issues.apache.org/jira/browse/IGNITE-1646 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > 1) User must be able to pass IgniteGuid over a wire using serializable > semantics when serialized manually by user. > 2) On the other hand, it must be portable for correct passing between Java > and .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1682) .Net: Remove RemoteListen from Events API
[ https://issues.apache.org/jira/browse/IGNITE-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010618#comment-15010618 ] ASF GitHub Bot commented on IGNITE-1682: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/158 > .Net: Remove RemoteListen from Events API > - > > Key: IGNITE-1682 > URL: https://issues.apache.org/jira/browse/IGNITE-1682 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Remote listen API in Java is broken. Let's remove it from .Net (since it has > not been released yet) and bring it back as soon as it is fixed, to avoid > releasing broken API. > * remove RemoteListen/StopRemoteListen from public API > * rename IEventFilter to IEventListener > * remove Guid from filter and listener (for now there is no use for it) -- 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.
[ https://issues.apache.org/jira/browse/IGNITE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010445#comment-15010445 ] Vladimir Ozerov commented on IGNITE-1816: - Merged. > 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] [Commented] (IGNITE-1289) Platforms .Net: Move portable marshaller to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010559#comment-15010559 ] ASF GitHub Bot commented on IGNITE-1289: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/46 > Platforms .Net: Move portable marshaller to Ignite. > --- > > Key: IGNITE-1289 > URL: https://issues.apache.org/jira/browse/IGNITE-1289 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: 1.5 > > > We need to move portable serialziation logic to Ignite. It is important that > initially we _must_not_ move pre-configured classes to Ignite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010591#comment-15010591 ] ASF GitHub Bot commented on IGNITE-1496: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/96 > Platform .Net: Add .Net examples > > > Key: IGNITE-1496 > URL: https://issues.apache.org/jira/browse/IGNITE-1496 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > * Create separate Examples solution (with 2 projects - main and dll) > * Add these projects to main Ignite solution > * Include example tests into Apache.Ignite.Core.Tests > * Fix config files and documentation, make sure GridGain in not mentioned > anywhere -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1565) Platform .Net: Fix examples
[ https://issues.apache.org/jira/browse/IGNITE-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010587#comment-15010587 ] ASF GitHub Bot commented on IGNITE-1565: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/112 > Platform .Net: Fix examples > --- > > Key: IGNITE-1565 > URL: https://issues.apache.org/jira/browse/IGNITE-1565 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Paths have changed in ignite-1282 branch: > * config paths should be fixed in examples > * example files paths should be fixed in example tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1492) Platform .Net: Set up FxCop project, fix/suppress warnings
[ https://issues.apache.org/jira/browse/IGNITE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010590#comment-15010590 ] ASF GitHub Bot commented on IGNITE-1492: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/95 > Platform .Net: Set up FxCop project, fix/suppress warnings > -- > > Key: IGNITE-1492 > URL: https://issues.apache.org/jira/browse/IGNITE-1492 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1570) Move .Net local benchmarks project to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010588#comment-15010588 ] ASF GitHub Bot commented on IGNITE-1570: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/113 > Move .Net local benchmarks project to Ignite. > - > > Key: IGNITE-1570 > URL: https://issues.apache.org/jira/browse/IGNITE-1570 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails
[ https://issues.apache.org/jira/browse/IGNITE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010586#comment-15010586 ] ASF GitHub Bot commented on IGNITE-1589: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/119 > Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails > --- > > Key: IGNITE-1589 > URL: https://issues.apache.org/jira/browse/IGNITE-1589 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1416) .Net: Implement AtomicLong data structure
[ https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010585#comment-15010585 ] ASF GitHub Bot commented on IGNITE-1416: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/111 > .Net: Implement AtomicLong data structure > - > > Key: IGNITE-1416 > URL: https://issues.apache.org/jira/browse/IGNITE-1416 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1619) Platform .Net: Generic type is lost during array/collection serialization
[ https://issues.apache.org/jira/browse/IGNITE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010609#comment-15010609 ] ASF GitHub Bot commented on IGNITE-1619: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/136 > Platform .Net: Generic type is lost during array/collection serialization > - > > Key: IGNITE-1619 > URL: https://issues.apache.org/jira/browse/IGNITE-1619 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: ignite-1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > We do not serialize collection/array element type, so on deserialization we > can not recreate original collection. So generic arrays/collections can't be > used in job arguments, service arguments, etc. > * We should keep current format for non-generic collections, arrays of > primitives, and arrays of objects > * Generic collections and arrays should be written with new TypeIds (not > compatible with other platforms) and include type information -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1480) Platform .Net: IClusterNode.IsClient
[ https://issues.apache.org/jira/browse/IGNITE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010612#comment-15010612 ] ASF GitHub Bot commented on IGNITE-1480: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/90 > Platform .Net: IClusterNode.IsClient > > > Key: IGNITE-1480 > URL: https://issues.apache.org/jira/browse/IGNITE-1480 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Ignite in Java has ClusterNode.isClient, need to implement in .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1934) .Net: Store tests broken after keepPortableInStore renaming
[ https://issues.apache.org/jira/browse/IGNITE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010619#comment-15010619 ] ASF GitHub Bot commented on IGNITE-1934: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/243 > .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)
[jira] [Commented] (IGNITE-1845) .Net: Adopt portable API changes.
[ https://issues.apache.org/jira/browse/IGNITE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010621#comment-15010621 ] ASF GitHub Bot commented on IGNITE-1845: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/212 > .Net: Adopt portable API changes. > - > > Key: IGNITE-1845 > URL: https://issues.apache.org/jira/browse/IGNITE-1845 > Project: Ignite > Issue Type: Task > Components: general, interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Important API changes will be introduced as a part of IGNITE-950. > Once these changes are in place, we need to port them to .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1665) .Net: Cache field IDs when deserializing objects.
[ https://issues.apache.org/jira/browse/IGNITE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010610#comment-15010610 ] ASF GitHub Bot commented on IGNITE-1665: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/167 > .Net: Cache field IDs when deserializing objects. > - > > Key: IGNITE-1665 > URL: https://issues.apache.org/jira/browse/IGNITE-1665 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Profiliing deserialization of test "Address" object shows that we spend > considerable amount of time (10-20%) inside field ID calculation. > We already optimized this for writes using serialization "paths" concept > where field hashing is replaced with strings reference equality checks. The > same thing should be done for reads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1652) .Net: Rework async APIs (remove WithAsync/GetFuture)
[
https://issues.apache.org/jira/browse/IGNITE-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010606#comment-15010606
]
ASF GitHub Bot commented on IGNITE-1652:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/175
> .Net: Rework async APIs (remove WithAsync/GetFuture)
>
>
> Key: IGNITE-1652
> URL: https://issues.apache.org/jira/browse/IGNITE-1652
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.5
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> {code}
> cache.WithAsync().Get();
> IFuture future = cache.GetFuture();
> {code}
> should become
> {code}
> Task task = cache.GetAsync();
> {code}
> Guidelines: https://msdn.microsoft.com/en-us/library/hh873175(v=vs.110).aspx
> First step is .Net-only (remove GetFuture from public API, call it inside
> *Async methods). This requires 2 JNI calls.
> Later we should look into making it a single JNI call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1927) Show generated pom file on summary page
[ https://issues.apache.org/jira/browse/IGNITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-1927. --- Resolution: Fixed Assignee: Pavel Konstantinov (was: Vasiliy Sisko) Implemented showing of pom file on summary page > Show generated pom file on summary page > --- > > Key: IGNITE-1927 > URL: https://issues.apache.org/jira/browse/IGNITE-1927 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.5 > > > Show pom file as option of chosen presentation on Java tab. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1625) .Net: Remove Types serialization from Continuous Queries
[ https://issues.apache.org/jira/browse/IGNITE-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010579#comment-15010579 ] ASF GitHub Bot commented on IGNITE-1625: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/139 > .Net: Remove Types serialization from Continuous Queries > > > Key: IGNITE-1625 > URL: https://issues.apache.org/jira/browse/IGNITE-1625 > Project: Ignite > Issue Type: Improvement > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > See ContinuousQueryFilterHolder class: it serializes KeyType and ValueType, > but this is redundant, since user filter already carries type information. > * Remove type serialization > * Leverage DelegateTypeDescriptor to get rid of reflection in > UnmanagedCallbacks.ContinuousQueryFilterCreate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
[ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010578#comment-15010578 ] ASF GitHub Bot commented on IGNITE-1571: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/124 > .Net: Improve Guid and DateTime reader/writer interface. > > > Key: IGNITE-1571 > URL: https://issues.apache.org/jira/browse/IGNITE-1571 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Currently we force user to write Guid and DateTime as nullables. We do this > to be more compatible with Java. > But user is more likely to operate on plain types: Guid, Guid[], DateTime, > DateTime[]. > We need to add these methods to API, and rename existing ones to > "ReadNullableDateTime", etc.. > Note that while trivial to on writer side, it will be harder to implement for > readers. Currently we lookup by type ID, which will be equal for the type and > it's nullable counterpart. For this reason we probably must lookup by type ID > + type or simply by type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1664) .Net: Review generic type arguments in the API
[
https://issues.apache.org/jira/browse/IGNITE-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010574#comment-15010574
]
ASF GitHub Bot commented on IGNITE-1664:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/154
> .Net: Review generic type arguments in the API
> --
>
> Key: IGNITE-1664
> URL: https://issues.apache.org/jira/browse/IGNITE-1664
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.5
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> * Make sure that order is correct (in -> out)
> * Fix naming to be meaningful ("T, TR1, TR2" does not help with understanding)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1902) NET: Adopt new marshalling flags.
[
https://issues.apache.org/jira/browse/IGNITE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010626#comment-15010626
]
ASF GitHub Bot commented on IGNITE-1902:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/229
> 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-1845) .Net: Adopt portable API changes.
[ https://issues.apache.org/jira/browse/IGNITE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010594#comment-15010594 ] ASF GitHub Bot commented on IGNITE-1845: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/207 > .Net: Adopt portable API changes. > - > > Key: IGNITE-1845 > URL: https://issues.apache.org/jira/browse/IGNITE-1845 > Project: Ignite > Issue Type: Task > Components: general, interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Important API changes will be introduced as a part of IGNITE-950. > Once these changes are in place, we need to port them to .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1845) .Net: Adopt portable API changes.
[ https://issues.apache.org/jira/browse/IGNITE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010595#comment-15010595 ] ASF GitHub Bot commented on IGNITE-1845: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/210 > .Net: Adopt portable API changes. > - > > Key: IGNITE-1845 > URL: https://issues.apache.org/jira/browse/IGNITE-1845 > Project: Ignite > Issue Type: Task > Components: general, interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Important API changes will be introduced as a part of IGNITE-950. > Once these changes are in place, we need to port them to .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1627) .Net: Consistent product naming.
[ https://issues.apache.org/jira/browse/IGNITE-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010581#comment-15010581 ] ASF GitHub Bot commented on IGNITE-1627: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/144 > .Net: Consistent product naming. > > > Key: IGNITE-1627 > URL: https://issues.apache.org/jira/browse/IGNITE-1627 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > We need to look through all docs and READMEs and ensure that our product is > named consistently: "Apache Ignite.NET". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1562) .Net: Remove "Generic" word from "WriteGenericCollection" and "WriteGenericDictionary".
[ https://issues.apache.org/jira/browse/IGNITE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010583#comment-15010583 ] ASF GitHub Bot commented on IGNITE-1562: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/125 > .Net: Remove "Generic" word from "WriteGenericCollection" and > "WriteGenericDictionary". > --- > > Key: IGNITE-1562 > URL: https://issues.apache.org/jira/browse/IGNITE-1562 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: 1.5 > > > Normally users will use these methods instead of non-generic. Lets make their > names as simple as possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1509) .Net: User must operate on IEnumerable in events API rather than on arrays.
[ https://issues.apache.org/jira/browse/IGNITE-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010582#comment-15010582 ] ASF GitHub Bot commented on IGNITE-1509: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/140 > .Net: User must operate on IEnumerable in events API rather than on arrays. > --- > > Key: IGNITE-1509 > URL: https://issues.apache.org/jira/browse/IGNITE-1509 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Currently we expose arrays for event groups. As they are mutable, we have to > copy them every time user use them. > To avoid this we should switch to IEnumerables and leave shortcut methods > with "params[]" for convenience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1613) Platform .Net: Investigate Guid/DateTime/String interoperability with Java
[ https://issues.apache.org/jira/browse/IGNITE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010584#comment-15010584 ] ASF GitHub Bot commented on IGNITE-1613: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/132 > Platform .Net: Investigate Guid/DateTime/String interoperability with Java > -- > > Key: IGNITE-1613 > URL: https://issues.apache.org/jira/browse/IGNITE-1613 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Currently in .Net we: > * write Guid and DateTime in Java format > * calculate string hash code for field names with Java algorithm on each call > Need to investigate if the following makes sense: > 1) In .Net always write Guid and DateTime in native .Net format as fast as > possible; Make Java understand that format. (Not every Guid written in .Net > will be read in Java, so we can win time). > 2) Cache string hashcodes somehow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-10: - Assignee: Vladimir Ershov (was: Anton Vinogradov) > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Vladimir Ershov > Labels: Muted_test > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.
[ https://issues.apache.org/jira/browse/IGNITE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010569#comment-15010569 ] ASF GitHub Bot commented on IGNITE-1572: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/122 > .Net: Check if we can get rid of "WritePortableOrSerializable" method. > -- > > Key: IGNITE-1572 > URL: https://issues.apache.org/jira/browse/IGNITE-1572 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > We have lots of places where "WritePortableOrSerializable" routine is > invoked. It is not clear why do we need it provided that we already handle > [Serializable] classes properly. > Looks like we are able to get rid of it safely, aren't we? Need to > double-check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1677) .Net: Sign assemblies and store SNK file in git
[ https://issues.apache.org/jira/browse/IGNITE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010604#comment-15010604 ] ASF GitHub Bot commented on IGNITE-1677: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/159 > .Net: Sign assemblies and store SNK file in git > --- > > Key: IGNITE-1677 > URL: https://issues.apache.org/jira/browse/IGNITE-1677 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Currently there is no strong name signing, so anyone who wants to reference > Ignite.NET in their signed assembly will have to modify our sources and build > them. > Providing snk file as part of the open source project is a standard practice > (see log4net > https://svn.apache.org/repos/asf/logging/log4net/trunk/log4net.snk.readme). > Public strong name, of course, does not provide any means of authenticity > checking, but makes development easier. > Authenticity can be ensured by downloading Apache Ignite release from > official download page and verifying check sums. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1834) .Net: Remove MetadataEnabled property
[ https://issues.apache.org/jira/browse/IGNITE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010599#comment-15010599 ] ASF GitHub Bot commented on IGNITE-1834: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/194 > .Net: Remove MetadataEnabled property > - > > Key: IGNITE-1834 > URL: https://issues.apache.org/jira/browse/IGNITE-1834 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > MetadataEnabled is going to be removed from Ignite, need to reflect this in > .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1943) visorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Description:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistic
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
+---+
{noformat}
"mclear" should get effect only for "mget @nX" command (with result "Missing
variable with name: '@nX'") and @ variables should get new values after "node"
(or "tasks") command execution. Like in case for all others @ variables (@cX,
@tX, @aX, @eX)
was:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistic
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 %
[jira] [Updated] (IGNITE-1943) ignitevisorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Description:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistics
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the started cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
+---+
{noformat}
"mclear" should get effect only for "mget @nX" command (with result "Missing
variable with name: '@nX'") and @nX variables should get new values after
"node" (or "tasks") command execution. Like in case for all others @ variables
(@cX, @tX, @aX, @eX)
was:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistics
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the started cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % |
[jira] [Updated] (IGNITE-1943) ignitevisorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Summary: ignitevisorcmd: wrong behavior for "mclear" command (was:
visorcmd: wrong behavior for "mclear" command)
> ignitevisorcmd: wrong behavior for "mclear" command
> ---
>
> Key: IGNITE-1943
> URL: https://issues.apache.org/jira/browse/IGNITE-1943
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 1.5
>Reporter: Vasilisa Sidorova
> Fix For: 1.6
>
>
> -
> DESCRIPTION
> -
> "mclear" should clears all Visor console variables before they will be
> updated during next run of the corresponding command. It OK for all type of
> shortcut (@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After
> "mclear" @nX are disappear from any statistics
> -
> STEPS FOR REPRODUCE
> -
> # Start cluster
> # Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
> # Connect to the started cluster (visor> open)
> # Execute any tasks in it (for example, run any example from EventsExample,
> DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
> ComputeTaskSplitExample)
> # Create several alerts (visor> alert)
> # Run visor "mclear" command
> # Run visor "node" command
> -
> ACTUAL RESULT
> -
> There isn't @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +==+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +==+
> | 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
> | 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
> | 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
> +--+
> {noformat}
> -
> EXPECTED RESULT
> -
> There is @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +===+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +===+
> | 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
> | 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
> | 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
> +---+
> {noformat}
> "mclear" should get effect only for "mget @nX" command (with result "Missing
> variable with name: '@nX'") and @ variables should get new values after
> "node" (or "tasks") command execution. Like in case for all others @
> variables (@cX, @tX, @aX, @eX)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1943) visorcmd: wrong behavior for "mclear" command
Vasilisa Sidorova created IGNITE-1943:
--
Summary: visorcmd: wrong behavior for "mclear" command
Key: IGNITE-1943
URL: https://issues.apache.org/jira/browse/IGNITE-1943
Project: Ignite
Issue Type: Bug
Components: wizards
Affects Versions: 1.5
Reporter: Vasilisa Sidorova
Fix For: 1.6
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistic
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
+---+
{noformat}
"mclear" should get effect only for "mget @nX" command (with result "Missing
variable with name: '@nX'") and @ variables should get new values after "node"
(or "tasks") command.Like in case for all others @ variables (@cX, @tX, @aX,
@eX)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1943) ignitevisorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Component/s: (was: wizards)
general
> ignitevisorcmd: wrong behavior for "mclear" command
> ---
>
> Key: IGNITE-1943
> URL: https://issues.apache.org/jira/browse/IGNITE-1943
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5
>Reporter: Vasilisa Sidorova
> Fix For: 1.6
>
>
> -
> DESCRIPTION
> -
> "mclear" should clears all Visor console variables before they will be
> updated during next run of the corresponding command. It OK for all type of
> shortcut (@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After
> "mclear" @nX are disappear from any statistics
> -
> STEPS FOR REPRODUCE
> -
> # Start cluster
> # Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
> # Connect to the started cluster (visor> open)
> # Execute any tasks in it (for example, run any example from EventsExample,
> DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
> ComputeTaskSplitExample)
> # Create several alerts (visor> alert)
> # Run visor "mclear" command
> # Run visor "node" command
> -
> ACTUAL RESULT
> -
> There isn't @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +==+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +==+
> | 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
> | 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
> | 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
> +--+
> {noformat}
> -
> EXPECTED RESULT
> -
> There is @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +===+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +===+
> | 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
> | 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
> | 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
> +---+
> {noformat}
> "mclear" should get effect only for "mget @nX" command (with result "Missing
> variable with name: '@nX'") and @nX variables should get new values after
> "node" (or "tasks") command execution. Like in case for all others @
> variables (@cX, @tX, @aX, @eX)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1943) visorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Description:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistics
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the started cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
+---+
{noformat}
"mclear" should get effect only for "mget @nX" command (with result "Missing
variable with name: '@nX'") and @ variables should get new values after "node"
(or "tasks") command execution. Like in case for all others @ variables (@cX,
@tX, @aX, @eX)
was:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistics
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00
[jira] [Updated] (IGNITE-1943) visorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1943:
---
Description:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistics
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
+---+
{noformat}
"mclear" should get effect only for "mget @nX" command (with result "Missing
variable with name: '@nX'") and @ variables should get new values after "node"
(or "tasks") command execution. Like in case for all others @ variables (@cX,
@tX, @aX, @eX)
was:
-
DESCRIPTION
-
"mclear" should clears all Visor console variables before they will be updated
during next run of the corresponding command. It OK for all type of shortcut
(@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After "mclear" @nX
are disappear from any statistic
-
STEPS FOR REPRODUCE
-
# Start cluster
# Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
# Connect to the ctarted cluster (visor> open)
# Execute any tasks in it (for example, run any example from EventsExample,
DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
ComputeTaskSplitExample)
# Create several alerts (visor> alert)
# Run visor "mclear" command
# Run visor "node" command
-
ACTUAL RESULT
-
There isn't @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+==+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+==+
| 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
| 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
| 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
+--+
{noformat}
-
EXPECTED RESULT
-
There is @nX values in the first table's column:
{noformat}
visor> node
Select node from:
+===+
| # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
+===+
| 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
| 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
| 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 %
[jira] [Commented] (IGNITE-1907) .Net: Cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010954#comment-15010954 ] ASF GitHub Bot commented on IGNITE-1907: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/241 > .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.6 > > > Configure cache in code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1931) .Net: Store configuration
[ https://issues.apache.org/jira/browse/IGNITE-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1931: --- Assignee: Pavel Tupitsyn > .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 >Assignee: Pavel Tupitsyn > Fix For: 1.6 > > > Configure store in .NET code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1933) .Net: GetOrCreateCache overloads with CacheConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-1933. --- > .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] [Resolved] (IGNITE-1933) .Net: GetOrCreateCache overloads with CacheConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-1933. - Resolution: Done > .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-1907) .Net: Cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-1907. --- > .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.6 > > > Configure cache in code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1907) .Net: Cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-1907. - Resolution: Done > .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.6 > > > Configure cache in code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1906) .Net: Ignite configuration without Spring
[ https://issues.apache.org/jira/browse/IGNITE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010953#comment-15010953 ] Pavel Tupitsyn commented on IGNITE-1906: - Final patch to be created when all subtasks are done. > .Net: Ignite configuration without Spring > - > > Key: IGNITE-1906 > URL: https://issues.apache.org/jira/browse/IGNITE-1906 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.6 > > > * Spring is alien for .NET developers > * In-code configuration is often preferrable -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1935) Add sanity tests for GridCacheContext.deferredDelete method
[
https://issues.apache.org/jira/browse/IGNITE-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011134#comment-15011134
]
Andrey Gura commented on IGNITE-1935:
-
Merged into master branch.
> 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-1946) Rework Schema Import Utility to generate code with new API
Alexey Kuznetsov created IGNITE-1946: Summary: Rework Schema Import Utility to generate code with new API Key: IGNITE-1946 URL: https://issues.apache.org/jira/browse/IGNITE-1946 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.5 Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 1.5 Schema Import Utility Should generate XML and Java code for new Queries and Pojo store API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15013025#comment-15013025 ] Igor Rudyak commented on IGNITE-1371: - Added javadocs for all methods > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexandre Boudnik >Assignee: Igor Rudyak > Attachments: master_02b59e4_ignite-1371.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-801) [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15013077#comment-15013077
]
Semen Boikov commented on IGNITE-801:
-
Hi, I have few comments:
- logic handling CachePartialUpdateCheckedException not neede in
GridAtomicCacheQueueImpl since cache update API will do retries internally
- in 'retryTopologySafe' add handling for
ClusterTopologyServerNotFoundException and add test with client using some data
structure where all server nodes leave
> [Test] GridCacheReplicatedDataStructuresFailoverSelfTest hangs on TC
>
>
> Key: IGNITE-801
> URL: https://issues.apache.org/jira/browse/IGNITE-801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Labels: Muted_test
> Fix For: 1.5
>
> Attachments: ignite-801.patch, ignite-801.patch
>
>
> See GG-5306
> http://94.72.60.102/viewLog.html?buildId=113217=bt6=buildResultsDiv
> {noformat}
> 2013-05-31 10:39:07
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode):
> "Attach Listener" daemon prio=10 tid=0x03a94800 nid=0x648 waiting on
> condition [0x]
>java.lang.Thread.State: RUNNABLE
> "tcp-disco-sock-reader-#2408%a940475f-1965-484a-8a43-0a1fcc3bf292" prio=10
> tid=0x7f06f8b1a000 nid=0x42d runnable [0x7f0702d84000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerInputStreamWrapper.read(GridJdkMarshallerInputStreamWrapper.java:47)
> at
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
> at java.io.ObjectInputStream.init(ObjectInputStream.java:299)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshallerObjectInputStream.init(GridJdkMarshallerObjectInputStream.java:30)
> at
> org.gridgain.grid.marshaller.jdk.GridJdkMarshaller.unmarshal(GridJdkMarshaller.java:115)
> at
> org.gridgain.grid.spi.discovery.tcp.GridTcpDiscoverySpi$SocketReader.body(GridTcpDiscoverySpi.java:3985)
> at org.gridgain.grid.spi.GridSpiThread.run(GridSpiThread.java:56)
> "Thread-1905" prio=10 tid=0x7f06f8268000 nid=0x428 waiting on condition
> [0x7f06e1f29000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x00078a53c600 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a473b60 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "Thread-1911" prio=10 tid=0x026b1000 nid=0x420 waiting on condition
> [0x7f06e6af4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.gridgain.grid.kernal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:89)
> at org.gridgain.grid.kernal.GridKernal.stop0(GridKernal.java:1629)
> - locked 0x000789b76068 (a
> org.gridgain.grid.util.GridBreaker)
> at org.gridgain.grid.kernal.GridKernal.stop(GridKernal.java:1605)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop0(GridFactory.java:2295)
> - locked 0x00078a4738f8 (a
> org.gridgain.grid.GridFactory$GridNamedInstance)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance.stop(GridFactory.java:2256)
> at
> org.gridgain.grid.GridFactory$GridNamedInstance$2.run(GridFactory.java:2223)
> "SIGTERM handler" daemon prio=10 tid=0x01ec2800 nid=0x41e in
> Object.wait() [0x7f06e8316000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> - locked 0x00078a473948 (a
> org.gridgain.grid.GridFactory$GridNamedInstance$2)
> at
