[jira] [Updated] (IGNITE-4189) JDBC Driver: support transactional savepoints
[ https://issues.apache.org/jira/browse/IGNITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4189: Fix Version/s: (was: 2.3) > JDBC Driver: support transactional savepoints > - > > Key: IGNITE-4189 > URL: https://issues.apache.org/jira/browse/IGNITE-4189 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Once the savepoints are supported at Java API level they should be supported > at the level of our JDBC driver. JDBC specification defines savepoints > related statements. > https://docs.oracle.com/javase/tutorial/jdbc/basics/transactions.html#set_roll_back_savepoints -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4193) ODBC: transactional support for DML and SELECT statements
[ https://issues.apache.org/jira/browse/IGNITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4193: Fix Version/s: (was: 2.3) > ODBC: transactional support for DML and SELECT statements > - > > Key: IGNITE-4193 > URL: https://issues.apache.org/jira/browse/IGNITE-4193 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Denis Magda > > To support execution of DML and SELECT statements inside of a transaction > started from ODBC driver side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4190) ODBC Driver: support transactional savepoints
[ https://issues.apache.org/jira/browse/IGNITE-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4190: Component/s: odbc > ODBC Driver: support transactional savepoints > - > > Key: IGNITE-4190 > URL: https://issues.apache.org/jira/browse/IGNITE-4190 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Denis Magda > > Once the savepoints are supported at Java API level they should be supported > at the level of our ODBC driver. > It looks like there is no support for the savepoints at the level of ODBC > API. However, ODBC > drivers which implement it just detect "SAVEPOINT" keyword in a query and > process it right away. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4190) ODBC Driver: support transactional savepoints
[ https://issues.apache.org/jira/browse/IGNITE-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4190: Fix Version/s: (was: 2.3) > ODBC Driver: support transactional savepoints > - > > Key: IGNITE-4190 > URL: https://issues.apache.org/jira/browse/IGNITE-4190 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Denis Magda > > Once the savepoints are supported at Java API level they should be supported > at the level of our ODBC driver. > It looks like there is no support for the savepoints at the level of ODBC > API. However, ODBC > drivers which implement it just detect "SAVEPOINT" keyword in a query and > process it right away. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4189) JDBC Driver: support transactional savepoints
[ https://issues.apache.org/jira/browse/IGNITE-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4189: Component/s: jdbc > JDBC Driver: support transactional savepoints > - > > Key: IGNITE-4189 > URL: https://issues.apache.org/jira/browse/IGNITE-4189 > Project: Ignite > Issue Type: Sub-task > Components: jdbc >Reporter: Denis Magda > > Once the savepoints are supported at Java API level they should be supported > at the level of our JDBC driver. JDBC specification defines savepoints > related statements. > https://docs.oracle.com/javase/tutorial/jdbc/basics/transactions.html#set_roll_back_savepoints -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4193) ODBC: transactional support for DML and SELECT statements
[ https://issues.apache.org/jira/browse/IGNITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4193: Component/s: odbc > ODBC: transactional support for DML and SELECT statements > - > > Key: IGNITE-4193 > URL: https://issues.apache.org/jira/browse/IGNITE-4193 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Denis Magda > > To support execution of DML and SELECT statements inside of a transaction > started from ODBC driver side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4192) JDBC: transactional support for DML and SELECT statements
[ https://issues.apache.org/jira/browse/IGNITE-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4192: Fix Version/s: (was: 2.3) > JDBC: transactional support for DML and SELECT statements > - > > Key: IGNITE-4192 > URL: https://issues.apache.org/jira/browse/IGNITE-4192 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Denis Magda > > To support execution of DML and SELECT statements inside of a transaction > started from JDBC driver side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4192) JDBC: transactional support for DML and SELECT statements
[ https://issues.apache.org/jira/browse/IGNITE-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4192: Component/s: sql > JDBC: transactional support for DML and SELECT statements > - > > Key: IGNITE-4192 > URL: https://issues.apache.org/jira/browse/IGNITE-4192 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Denis Magda > > To support execution of DML and SELECT statements inside of a transaction > started from JDBC driver side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4194) DML: transactional support for DML statements
[ https://issues.apache.org/jira/browse/IGNITE-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4194: Component/s: sql > DML: transactional support for DML statements > - > > Key: IGNITE-4194 > URL: https://issues.apache.org/jira/browse/IGNITE-4194 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Denis Magda > > To support execution of DML and statements inside of a transaction started > from DML API side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4194) DML: transactional support for DML statements
[ https://issues.apache.org/jira/browse/IGNITE-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4194: Fix Version/s: (was: 2.3) > DML: transactional support for DML statements > - > > Key: IGNITE-4194 > URL: https://issues.apache.org/jira/browse/IGNITE-4194 > Project: Ignite > Issue Type: Sub-task > Components: sql >Reporter: Denis Magda > > To support execution of DML and statements inside of a transaction started > from DML API side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4618) CPP: Do not start JVM if it is already started
[ https://issues.apache.org/jira/browse/IGNITE-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4618: Fix Version/s: (was: 2.3) > CPP: Do not start JVM if it is already started > -- > > Key: IGNITE-4618 > URL: https://issues.apache.org/jira/browse/IGNITE-4618 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.8 >Reporter: Vladimir Ozerov > Labels: cpp > > *Problem* > Consider the following scenario: > 1) User's app started JVM in the process somehow. > 2) User tries to start the node. > 3) Result: exception. > *Solution* > We need to check if JVM is already started. If yes - then try re-using. Note > that we are likely to fail at this point because user might forgot to pass > proper Ignite classpath. In this case we must throw extremely sensible > exception, so that user understand how to fix the problem right away. > E.g.: "Failed to start Ignite node with already started JVM due to invalid > classpath; please add the following JARs to the classpath: [PATH TO > IGNITE_HOME JARS]". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4689) .NET: Support java.sql.Time
[ https://issues.apache.org/jira/browse/IGNITE-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4689: Component/s: sql > .NET: Support java.sql.Time > --- > > Key: IGNITE-4689 > URL: https://issues.apache.org/jira/browse/IGNITE-4689 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5253) .NET: Fields query cursor metadata
[ https://issues.apache.org/jira/browse/IGNITE-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5253: Component/s: sql > .NET: Fields query cursor metadata > -- > > Key: IGNITE-5253 > URL: https://issues.apache.org/jira/browse/IGNITE-5253 > Project: Ignite > Issue Type: Improvement > Components: platforms, sql >Reporter: Pavel Tupitsyn >Priority: Minor > Labels: .NET > Fix For: 2.3 > > > Same as IGNITE-5252 for .NET: > Provide a way to get fields information from the query cursor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4689) .NET: Support java.sql.Time
[ https://issues.apache.org/jira/browse/IGNITE-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4689: Fix Version/s: (was: 2.3) > .NET: Support java.sql.Time > --- > > Key: IGNITE-4689 > URL: https://issues.apache.org/jira/browse/IGNITE-4689 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6262) TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky.
Vitaliy Biryukov created IGNITE-6262: Summary: TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky. Key: IGNITE-6262 URL: https://issues.apache.org/jira/browse/IGNITE-6262 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov The problem is the same with IGNITE-5865. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4956) Stabilize the test on partition reservation during affinity call
[
https://issues.apache.org/jira/browse/IGNITE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4956:
Fix Version/s: (was: 2.3)
> Stabilize the test on partition reservation during affinity call
>
>
> Key: IGNITE-4956
> URL: https://issues.apache.org/jira/browse/IGNITE-4956
> Project: Ignite
> Issue Type: Test
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>
> Stabilize the test
> *IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp*
> The test periodically failed with the message:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed partition reservation.
> Partition is not primary on the node. [partition=12, cacheName=Person,
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion
> [topVer=9, minorTopVer=0]] at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7172) at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:95)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:271)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:259)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:389)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:343)
> at
> org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:858)
> at
> org.apache.ignite.testframework.GridTestUtils$8.call(GridTestUtils.java:1149)
> at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.IgniteException: Failed partition reservation.
> Partition is not primary on the node. [partition=12, cacheName=Person,
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion
> [topVer=9, minorTopVer=0]] at
> org.apache.ignite.internal.processors.job.GridJobProcessor$PartitionsReservation.reserve(GridJobProcessor.java:1572)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:504)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1228)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:856)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:111)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:798)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745) --- Stdout: ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6262) TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky.
[ https://issues.apache.org/jira/browse/IGNITE-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Biryukov reassigned IGNITE-6262: Assignee: Vitaliy Biryukov > TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and > TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky. > - > > Key: IGNITE-6262 > URL: https://issues.apache.org/jira/browse/IGNITE-6262 > Project: Ignite > Issue Type: Bug >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov > > The problem is the same with IGNITE-5865. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-3558) Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts
[
https://issues.apache.org/jira/browse/IGNITE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153182#comment-16153182
]
Vladimir Ozerov commented on IGNITE-3558:
-
[~tledkov-gridgain], [~sboikov], any more comments here? Are we going implement
anything as a part of this ticket?
> Affinity task hangs when Collision SPI produces a lot of job rejections &
> Failover SPI produces many attempts
> -
>
> Key: IGNITE-3558
> URL: https://issues.apache.org/jira/browse/IGNITE-3558
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> The test to reproduce:
> {{IgniteCacheLockPartitionOnAffinityRunWithCollisionSpiTest.testJobFinishing}}
> *Root cause*
> {{GridJobExecuteResponse}} isn't set from target node because there is a
> confusion with {{GridJobWorker}} instances in the {{CollisionContext}}.
> *Suggestion*
> The method {{GridJobProcessor.CollisionJobContext.cancel()}}
> use {{passiveJobs.remove(jobWorker.getJobId(), jobWorker)}}.
> *passiveJobs* is a ConcurrentHashMap and {{GridJobWorker.equals()}}
> implements as a equation of jobId.
> So, when two thread try to cancel the two workers with *the same jobIds* we
> have the case:
> - thread0 remove jobWorker0 & cancel jobWorker0.
> - thread0 put jobWorker1 (because jobWorker0 already removed);
> - thread1: (has a copy of jobWorker0) and try to cancel it.
> - thread1: remove jobWorker1 instead of jobWorker0 (because jobId is used to
> identify);
> - thread1: doesn't send ExecuteResponse because jobWorker0 has been canceled.
> *Proposal*
> Try to use system default equals for the GridJobWorker
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-4956) Stabilize the test on partition reservation during affinity call
[
https://issues.apache.org/jira/browse/IGNITE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4956:
---
Assignee: (was: Taras Ledkov)
> Stabilize the test on partition reservation during affinity call
>
>
> Key: IGNITE-4956
> URL: https://issues.apache.org/jira/browse/IGNITE-4956
> Project: Ignite
> Issue Type: Test
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>
> Stabilize the test
> *IgniteCacheLockPartitionOnAffinityRunAtomicCacheOpTest.testNotReservedTxCacheOp*
> The test periodically failed with the message:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed partition reservation.
> Partition is not primary on the node. [partition=12, cacheName=Person,
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion
> [topVer=9, minorTopVer=0]] at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7172) at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:95)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:271)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:259)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:389)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:343)
> at
> org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:858)
> at
> org.apache.ignite.testframework.GridTestUtils$8.call(GridTestUtils.java:1149)
> at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.IgniteException: Failed partition reservation.
> Partition is not primary on the node. [partition=12, cacheName=Person,
> nodeId=bf014a48-7032-4b72-9d00-d8a76551, topology=AffinityTopologyVersion
> [topVer=9, minorTopVer=0]] at
> org.apache.ignite.internal.processors.job.GridJobProcessor$PartitionsReservation.reserve(GridJobProcessor.java:1572)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:504)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1228)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:856)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:111)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:798)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745) --- Stdout: ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-1453) CPP: Big endian support in streams.
[ https://issues.apache.org/jira/browse/IGNITE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1453: Fix Version/s: (was: 2.3) > CPP: Big endian support in streams. > --- > > Key: IGNITE-1453 > URL: https://issues.apache.org/jira/browse/IGNITE-1453 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego > Labels: cpp > > Currently we write data with assumption that all parties has little endian. > While true in most cases, we still not to count for big endian machines. > Implementation notes: > 1) Define cross-platform method to determine endian. This can be as easy as > Bits.java:byteOrder() routine. > 2) Add big endian support for all read/write operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-1453) CPP: Big endian support in streams.
[ https://issues.apache.org/jira/browse/IGNITE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-1453: --- Assignee: (was: Igor Sapego) > CPP: Big endian support in streams. > --- > > Key: IGNITE-1453 > URL: https://issues.apache.org/jira/browse/IGNITE-1453 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov > Labels: cpp > > Currently we write data with assumption that all parties has little endian. > While true in most cases, we still not to count for big endian machines. > Implementation notes: > 1) Define cross-platform method to determine endian. This can be as easy as > Bits.java:byteOrder() routine. > 2) Add big endian support for all read/write operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3879) Next generation of Ignite's REST API
[ https://issues.apache.org/jira/browse/IGNITE-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3879: Fix Version/s: (was: 2.3) > Next generation of Ignite's REST API > > > Key: IGNITE-3879 > URL: https://issues.apache.org/jira/browse/IGNITE-3879 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Denis Magda > > This is an umbrella ticket that will contain basic design and paradigm for > the next generation of Ignite's REST API. > Current version of API is extremely limited that prevents from adopting > Ignite across variety of languages and platforms. > The main goal is that it should be possible to use this API from/with such > platforms and languages like: > - NodeJS; > - Objective-C; > - Android; > - Windows Phone. > - embedded systems (Internet of Things). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6255) .NET: Fix TestAffinityCall to take late affinity assignment into account
[
https://issues.apache.org/jira/browse/IGNITE-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153228#comment-16153228
]
ASF GitHub Bot commented on IGNITE-6255:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2589
> .NET: Fix TestAffinityCall to take late affinity assignment into account
>
>
> Key: IGNITE-6255
> URL: https://issues.apache.org/jira/browse/IGNITE-6255
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> {{ComputeApiTest.TestAffinityCall}} fails because affinity assignment changes
> during test execution. Find a way to handle this (either retry the test, or
> wait for some cache event).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-6255) .NET: Fix TestAffinityCall to take late affinity assignment into account
[
https://issues.apache.org/jira/browse/IGNITE-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-6255.
Resolution: Fixed
> .NET: Fix TestAffinityCall to take late affinity assignment into account
>
>
> Key: IGNITE-6255
> URL: https://issues.apache.org/jira/browse/IGNITE-6255
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> {{ComputeApiTest.TestAffinityCall}} fails because affinity assignment changes
> during test execution. Find a way to handle this (either retry the test, or
> wait for some cache event).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6255) .NET: Fix TestAffinityCall to take late affinity assignment into account
[
https://issues.apache.org/jira/browse/IGNITE-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153230#comment-16153230
]
Pavel Tupitsyn commented on IGNITE-6255:
Merged to master: {{ce2a98cdb553e9b4d052d2ab891e4ba7c0fab289}}
> .NET: Fix TestAffinityCall to take late affinity assignment into account
>
>
> Key: IGNITE-6255
> URL: https://issues.apache.org/jira/browse/IGNITE-6255
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> {{ComputeApiTest.TestAffinityCall}} fails because affinity assignment changes
> during test execution. Find a way to handle this (either retry the test, or
> wait for some cache event).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6253) .NET: Replace Doxygen with DocFX for API documentation generation
[
https://issues.apache.org/jira/browse/IGNITE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153254#comment-16153254
]
Pavel Tupitsyn edited comment on IGNITE-6253 at 9/5/17 8:18 AM:
{{Impl}} namespaces excluded, dev list discussion started:
http://apache-ignite-developers.2346864.n4.nabble.com/New-API-docs-look-for-Ignite-NET-td21703.html
was (Author: ptupitsyn):
{{Impl}} namespaces excluded.
> .NET: Replace Doxygen with DocFX for API documentation generation
> -
>
> Key: IGNITE-6253
> URL: https://issues.apache.org/jira/browse/IGNITE-6253
> Project: Ignite
> Issue Type: Improvement
> Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Labels: .NET
> Fix For: 2.3
>
>
> Doxygen has recently became very slow on our code base (can take up to 30
> minutes), and there seems to be no solution to this problem. There are other
> issues: documentation is a bit ugly, customization possibilities are limited,
> C# is not a first-class citizen there.
> [DocFX|https://dotnet.github.io/docfx/] looks like an obvious replacement:
> * It is a go-to documentation generator for .NET (included in .NET Foundation)
> * Documentation looks nice (MSDN-like) out of the box
> * Migration seems to be easy enough
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6253) .NET: Replace Doxygen with DocFX for API documentation generation
[
https://issues.apache.org/jira/browse/IGNITE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153254#comment-16153254
]
Pavel Tupitsyn commented on IGNITE-6253:
{{Impl}} namespaces excluded.
> .NET: Replace Doxygen with DocFX for API documentation generation
> -
>
> Key: IGNITE-6253
> URL: https://issues.apache.org/jira/browse/IGNITE-6253
> Project: Ignite
> Issue Type: Improvement
> Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Labels: .NET
> Fix For: 2.3
>
>
> Doxygen has recently became very slow on our code base (can take up to 30
> minutes), and there seems to be no solution to this problem. There are other
> issues: documentation is a bit ugly, customization possibilities are limited,
> C# is not a first-class citizen there.
> [DocFX|https://dotnet.github.io/docfx/] looks like an obvious replacement:
> * It is a go-to documentation generator for .NET (included in .NET Foundation)
> * Documentation looks nice (MSDN-like) out of the box
> * Migration seems to be easy enough
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5708) CPP: Implement Cluster API
[ https://issues.apache.org/jira/browse/IGNITE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5708: --- Assignee: (was: Igor Sapego) > CPP: Implement Cluster API > -- > > Key: IGNITE-5708 > URL: https://issues.apache.org/jira/browse/IGNITE-5708 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.0 >Reporter: Igor Sapego > Labels: cpp > > Cluster API needed to be implemented for C++. It is needed for example for > decent Compute API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5498) Failures in GridNioSslSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5498:
Fix Version/s: (was: 2.3)
> Failures in GridNioSslSelfTest
> --
>
> Key: IGNITE-5498
> URL: https://issues.apache.org/jira/browse/IGNITE-5498
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Vladimir Ozerov
> Labels: MakeTeamcityGreenAgain, test-fail
>
> Affected tests:
> {{GridNioSslSelfTest.testConcurrentConnects}}
> {{GridNioSslSelfTest.testSimpleMessages}}
> {code}
> junit.framework.AssertionFailedError: Unexpected exception occurred while
> handling connection: class
> org.apache.ignite.internal.util.nio.GridNioException: An established
> connection was aborted by the software in your host machine
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.util.nio.GridNioSelfTest$EchoListener.onDisconnected(GridNioSelfTest.java:1361)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onExceptionCaught(GridNioFilterChain.java:261)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onExceptionCaught(GridNioCodecFilter.java:80)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onExceptionCaught(GridNioSslFilter.java:241)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onExceptionCaught(GridNioServer.java:3188)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onExceptionCaught(GridNioFilterChain.java:160)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2437)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5708) CPP: Implement Cluster API
[ https://issues.apache.org/jira/browse/IGNITE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5708: Fix Version/s: (was: 2.3) > CPP: Implement Cluster API > -- > > Key: IGNITE-5708 > URL: https://issues.apache.org/jira/browse/IGNITE-5708 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.0 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: cpp > > Cluster API needed to be implemented for C++. It is needed for example for > decent Compute API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5016) SQL: Support LEFT JOIN from replicated table to a partitioned.
[ https://issues.apache.org/jira/browse/IGNITE-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5016: Component/s: sql > SQL: Support LEFT JOIN from replicated table to a partitioned. > -- > > Key: IGNITE-5016 > URL: https://issues.apache.org/jira/browse/IGNITE-5016 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin > > Now we return duplicates: > IgniteCacheJoinPartitionedAndReplicatedTest.testReplicatedToPartitionedLeftJoin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5564) Race between read-through and topology version update
[
https://issues.apache.org/jira/browse/IGNITE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev reassigned IGNITE-5564:
---
Assignee: Dmitry Karachentsev
> Race between read-through and topology version update
> -
>
> Key: IGNITE-5564
> URL: https://issues.apache.org/jira/browse/IGNITE-5564
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Dmitry Karachentsev
> Fix For: 2.3
>
> Attachments: GridCachePartitionEvictionDuringReadThroughSelfTest.java
>
>
> I occasionally observe the following assertions when working with ATOMIC
> cache with cache store on changing topology:
> {code}
> java.lang.AssertionError: Invalid version for inner update [isNew=false,
> entry=GridDhtAtomicCacheEntry [super=GridDhtCacheEntry [rdrs=[],
> locPart=GridDhtLocalPartition [id=157,
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurrentMapImpl@7a99d0af,
> rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0], cntr=8,
> shouldBeRenting=false, state=OWNING, reservations=0, empty=false,
> createTime=06/21/2017 09:59:03], super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=1181,
> hasValBytes=true], val=CacheObjectImpl [val=1181, hasValBytes=true],
> startVer=1498028394357, ver=GridCacheVersion [topVer=109508344,
> time=1498028344708, order=1498028394358, nodeOrder=1], hash=1181,
> extras=GridCacheTtlEntryExtras [ttl=6, expireTime=1498028404707],
> flags=0, newVer=GridCacheVersion [topVer=109508343, time=1498028344709,
> order=1498028394369, nodeOrder=1]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2485)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1887)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1727)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.mapSingle(GridNearAtomicAbstractUpdateFuture.java:264)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:494)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:436)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1242)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:675)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2294)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearAtomicCache.put(GridNearAtomicCache.java:437)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2271)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1379)
> {code}
> The assertion happens because there is a race between these events:
> 1) An update is mapped on topology version N
> 2) Topology version changes and discovery updates the version to N+1, but the
> event is not yet processed by the exchange future
> 3) A read-through request comes in and performs the read. Inside
> {{versionedValue()}} call a new entry version is generated. Since the
> discovery version is already updated, the new entry version is based on
> topVer=N+1
> 4) Update request proceeds and read-locks the topology. Since the exchange
> future is not yet initialized, the request does not attempt to remap and
> proceeds with version N
> 5) The next entry version is generated using request topology version = N
> 6) Inside the entry update method, we assert that new version is greater than
> old version, but it's not the case in this scenario, and assertion fails
> Attached is a test reproducing the issue (see
> testConcurrentReadThroughUpdate())
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-2662) .NET Standard support
[ https://issues.apache.org/jira/browse/IGNITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2662: Fix Version/s: (was: 2.3) > .NET Standard support > - > > Key: IGNITE-2662 > URL: https://issues.apache.org/jira/browse/IGNITE-2662 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Labels: .net > > Ignite.NET should target .NET Standard so it is available on maximum number > of platforms, see > https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ > https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again > https://github.com/dotnet/core/blob/master/roadmap.md > This will allow us to run on Windows, OSX, and Linux, and target .NET Core in > additional to good old regular .NET. > Possible difficulties: > * JNI interop. Core has dllImport and it works on linux, and our C++ client > works on linux, so it should be possible > * Reflection. We use it a lot, and API has changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5105) Simplify binary read/write routines
[ https://issues.apache.org/jira/browse/IGNITE-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5105: Fix Version/s: (was: 2.3) > Simplify binary read/write routines > --- > > Key: IGNITE-5105 > URL: https://issues.apache.org/jira/browse/IGNITE-5105 > Project: Ignite > Issue Type: Task > Components: binary >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Minor > > Currently binary read/write routines are excessively complex. There are code > duplicates and unnecessary null checks in several places. > We need to refactor them to common form. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-2657) .NET: SqlDependency for cache items
[ https://issues.apache.org/jira/browse/IGNITE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2657: Fix Version/s: (was: 2.3) > .NET: SqlDependency for cache items > --- > > Key: IGNITE-2657 > URL: https://issues.apache.org/jira/browse/IGNITE-2657 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Labels: .net > > Update cache when SQL Server data changes > * https://msdn.microsoft.com/en-us/library/62xk7953(v=vs.110).aspx > * http://www.alachisoft.com/ncache/database-synchronization.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5016) SQL: Support LEFT JOIN from replicated table to a partitioned.
[ https://issues.apache.org/jira/browse/IGNITE-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5016: --- Assignee: (was: Sergi Vladykin) > SQL: Support LEFT JOIN from replicated table to a partitioned. > -- > > Key: IGNITE-5016 > URL: https://issues.apache.org/jira/browse/IGNITE-5016 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Sergi Vladykin > > Now we return duplicates: > IgniteCacheJoinPartitionedAndReplicatedTest.testReplicatedToPartitionedLeftJoin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5105) Simplify binary read/write routines
[ https://issues.apache.org/jira/browse/IGNITE-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5105: --- Assignee: (was: Vladimir Ozerov) > Simplify binary read/write routines > --- > > Key: IGNITE-5105 > URL: https://issues.apache.org/jira/browse/IGNITE-5105 > Project: Ignite > Issue Type: Task > Components: binary >Reporter: Vladimir Ozerov >Priority: Minor > > Currently binary read/write routines are excessively complex. There are code > duplicates and unnecessary null checks in several places. > We need to refactor them to common form. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4860) Empty leafs in BPlusTree
[
https://issues.apache.org/jira/browse/IGNITE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4860:
---
Assignee: (was: Sergi Vladykin)
> Empty leafs in BPlusTree
>
>
> Key: IGNITE-4860
> URL: https://issues.apache.org/jira/browse/IGNITE-4860
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Igor Seliverstov
>
> {{org.apache.ignite.internal.processors.database.BPlusTreeSelfTest#testMassiveRemove2_true}}
> The test fails approximately once out of 500 times with following error:
> {noformat}
> 10:34:30,394][INFO ][main][root] >>> Stopping test:
> BPlusTreeSelfTest#testMassiveRemove2_true in 49 ms <<<
> [10:34:30,392][ERROR][main][root] Test failed.
> java.lang.AssertionError: Empty leaf page.
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.fail(BPlusTree.java:1214)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateDownPages(BPlusTree.java:1285)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateDownPages(BPlusTree.java:1311)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateTree(BPlusTree.java:1102)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.doTestMassiveRemove(BPlusTreeSelfTest.java:853)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.testMassiveRemove2_true(BPlusTreeSelfTest.java:774)
> at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1811)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1726)
> at java.lang.Thread.run(Thread.java:745)
> java.lang.AssertionError: Empty leaf page.
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.fail(BPlusTree.java:1214)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateDownPages(BPlusTree.java:1285)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateDownPages(BPlusTree.java:1311)
> at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.validateTree(BPlusTree.java:1102)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.doTestMassiveRemove(BPlusTreeSelfTest.java:853)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.testMassiveRemove2_true(BPlusTreeSelfTest.java:774)
> at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1811)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1726)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> I've checked the test, seems a race happens while deleting pages, which
> prevents to merge empty leaf properly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5253) .NET: Fields query cursor metadata
[ https://issues.apache.org/jira/browse/IGNITE-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5253: Fix Version/s: (was: 2.3) > .NET: Fields query cursor metadata > -- > > Key: IGNITE-5253 > URL: https://issues.apache.org/jira/browse/IGNITE-5253 > Project: Ignite > Issue Type: Improvement > Components: platforms, sql >Reporter: Pavel Tupitsyn >Priority: Minor > Labels: .NET > > Same as IGNITE-5252 for .NET: > Provide a way to get fields information from the query cursor. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4445) Test suites improvements
[ https://issues.apache.org/jira/browse/IGNITE-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-4445: --- Assignee: (was: Vladimir Ozerov) > Test suites improvements > > > Key: IGNITE-4445 > URL: https://issues.apache.org/jira/browse/IGNITE-4445 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov > > This is an umbrella ticket for various improvement on Ignite test suites. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4445) Test suites improvements
[ https://issues.apache.org/jira/browse/IGNITE-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4445: Fix Version/s: (was: 2.3) > Test suites improvements > > > Key: IGNITE-4445 > URL: https://issues.apache.org/jira/browse/IGNITE-4445 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > > This is an umbrella ticket for various improvement on Ignite test suites. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-3054) Rework client connection handling from thread-per-client to NIO model.
[ https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3054: Fix Version/s: (was: 2.3) > Rework client connection handling from thread-per-client to NIO model. > -- > > Key: IGNITE-3054 > URL: https://issues.apache.org/jira/browse/IGNITE-3054 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov > > Currently both servers and clients has the same operational model - > thread-per-connection. While being more or less fine for servers, this could > be a problem for clients when their total number is too high (e.g. 1000 or > even more). > We should rework client handling model and employ standard NIO technique: one > or several acceptor threads + thread pool to server requests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4447) Remove "Ignite 150 Clients" suite.
[ https://issues.apache.org/jira/browse/IGNITE-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4447: Fix Version/s: (was: 2.3) > Remove "Ignite 150 Clients" suite. > -- > > Key: IGNITE-4447 > URL: https://issues.apache.org/jira/browse/IGNITE-4447 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Vadim Opolski >Priority: Minor > > It has only 1 tests. It runs for ~1m, but takes ~6m including build phase. > Let's just embed it into one of cache suites. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5730) .NET: Failed to load ignite.jni.dll when starting up multiple nodes
[
https://issues.apache.org/jira/browse/IGNITE-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-5730:
---
Assignee: Pavel Tupitsyn
> .NET: Failed to load ignite.jni.dll when starting up multiple nodes
> ---
>
> Key: IGNITE-5730
> URL: https://issues.apache.org/jira/browse/IGNITE-5730
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> When starting multiple nodes at once (with a script of some kind), failure to
> load unmanaged dll can occur:
> {code}
> for (int i = 0; i < 30; i++)
> {
> Process.Start(@"cmd.exe", @"/k Apache.Ignite.exe");
> }
> {code}
> Exception:
> {code}
> ERROR: System.TypeInitializationException: The type initializer for
> 'Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils' threw an exception. --->
> Apache.Ignite.Core.Common.IgniteException: Failed to load ignite.jni.dll: 126
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils..cctor()
>--- End of inner exception stack trace ---
>at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Initialize()
>at Apache.Ignite.Core.Impl.IgniteUtils.LoadDlls(String configJvmDllPath,
> ILogger log)
>at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
>at Apache.Ignite.IgniteRunner.Main(String[] args)
> {code}
> Error codes may be 5 (ERROR_ACCESS_DENIED) or 126 (ERROR_MOD_NOT_FOUND).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6157) C++: Query example: Incorrect output if run example with standalone node
[
https://issues.apache.org/jira/browse/IGNITE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6157:
---
Assignee: Igor Sapego
> C++: Query example: Incorrect output if run example with standalone node
>
>
> Key: IGNITE-6157
> URL: https://issues.apache.org/jira/browse/IGNITE-6157
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Assignee: Igor Sapego
>Priority: Minor
> Labels: c++
> Fix For: 2.3
>
>
> C++: Query example: Incorrect output if run example with standalone node
> without standalone node:
> {code}
> Following people have 'Master' in their resumes:
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
> Smith has Master Degree.]
> Following people have 'Bachelor' in their resumes:
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> {code}
> with standalone node (rows are repeated):
> {code}
> Following people have 'Master' in their resumes:
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
> Smith has Master Degree.]
> Following people have 'Bachelor' in their resumes:
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6157) C++: Query example: Incorrect output if run example with standalone node
[
https://issues.apache.org/jira/browse/IGNITE-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6157:
Fix Version/s: 2.3
> C++: Query example: Incorrect output if run example with standalone node
>
>
> Key: IGNITE-6157
> URL: https://issues.apache.org/jira/browse/IGNITE-6157
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Priority: Minor
> Labels: c++
> Fix For: 2.3
>
>
> C++: Query example: Incorrect output if run example with standalone node
> without standalone node:
> {code}
> Following people have 'Master' in their resumes:
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
> Smith has Master Degree.]
> Following people have 'Bachelor' in their resumes:
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> {code}
> with standalone node (rows are repeated):
> {code}
> Following people have 'Master' in their resumes:
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 1 : Person [orgId=1, lastName=Doe, firstName=John, salary=2000, resume=John
> Doe has Master Degree.]
> 4 : Person [orgId=2, lastName=Smith, firstName=Jane, salary=2000, resume=Jane
> Smith has Master Degree.]
> Following people have 'Bachelor' in their resumes:
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> 2 : Person [orgId=1, lastName=Doe, firstName=Jane, salary=1000, resume=Jane
> Doe has Bachelor Degree.]
> 3 : Person [orgId=2, lastName=Smith, firstName=John, salary=1000, resume=John
> Smith has Bachelor Degree.]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6179) Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
[
https://issues.apache.org/jira/browse/IGNITE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6179:
Fix Version/s: (was: 2.3)
> Test fail
> DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
>
>
> Key: IGNITE-6179
> URL: https://issues.apache.org/jira/browse/IGNITE-6179
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Dmitriy Govorukhin
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Attachments: log
>
>
> Test fail with assertion
> {code}
> [2017-08-24
> 18:34:06,207][ERROR][tcp-client-disco-msg-worker-#61%index.DynamicIndexReplicatedAtomicConcurrentSelfTest4%][IgniteClientReconnectAbstractTest$TestTcpDiscoverySpi]
> Failed to unmarshal discovery custom message.
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onSchemaFinishDiscovery(GridQueryProcessor.java:498)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onDiscovery(GridQueryProcessor.java:894)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2906)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:660)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:560)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2391)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processCustomMessage(ClientImpl.java:2297)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1874)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1758)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5615) .NET: IgniteConfiguration.LocalEventListeners
[
https://issues.apache.org/jira/browse/IGNITE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-5615:
---
Assignee: Pavel Tupitsyn
> .NET: IgniteConfiguration.LocalEventListeners
> -
>
> Key: IGNITE-5615
> URL: https://issues.apache.org/jira/browse/IGNITE-5615
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> Propagate {{IgniteConfiguration.LocalEventListeners}} to .NET. This allows
> catching all events right from the node start.
> * Can we unsubscribe from these events later? Does Java support this?
> * What about GetEvents for a cluster group, how do we handle local listeners
> in this case?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6138) JDBC driver metadata queries operate on cache/type instead of schema/table
[ https://issues.apache.org/jira/browse/IGNITE-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6138: Fix Version/s: 2.3 > JDBC driver metadata queries operate on cache/type instead of schema/table > -- > > Key: IGNITE-6138 > URL: https://issues.apache.org/jira/browse/IGNITE-6138 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.1 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev > Fix For: 2.3 > > > It has to use toUpperCase() to address the mismatch which isn't a correct > approach > Some additional information should be passed down from MetadataTask in > GridCacheSqlMetadata. > Also fetch actual name for primary key and use that if possible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6261: Fix Version/s: 2.3 > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Wish > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-6261: --- Assignee: (was: Igor Sapego) > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Wish > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6261: Fix Version/s: (was: 2.3) > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Wish > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6261: Priority: Major (was: Critical) > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Wish > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka >Assignee: Igor Sapego > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-6261: --- Assignee: Igor Sapego > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Wish > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka >Assignee: Igor Sapego > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5900) CPP: Add tests for CREATE/DROP table/index for C++ and ODBC
[ https://issues.apache.org/jira/browse/IGNITE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5900: Fix Version/s: (was: 2.3) > CPP: Add tests for CREATE/DROP table/index for C++ and ODBC > --- > > Key: IGNITE-5900 > URL: https://issues.apache.org/jira/browse/IGNITE-5900 > Project: Ignite > Issue Type: Task > Components: odbc, platforms >Affects Versions: 2.1 >Reporter: Igor Sapego >Assignee: Igor Sapego > > There is new statements in Ignite SQL - CREATE/DROP table/index. They should > work out of the box for C++ and ODBC, however, there are no tests for them. > Need to add tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5900) CPP: Add tests for CREATE/DROP table/index for C++ and ODBC
[ https://issues.apache.org/jira/browse/IGNITE-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-5900: --- Assignee: (was: Igor Sapego) > CPP: Add tests for CREATE/DROP table/index for C++ and ODBC > --- > > Key: IGNITE-5900 > URL: https://issues.apache.org/jira/browse/IGNITE-5900 > Project: Ignite > Issue Type: Task > Components: odbc, platforms >Affects Versions: 2.1 >Reporter: Igor Sapego > > There is new statements in Ignite SQL - CREATE/DROP table/index. They should > work out of the box for C++ and ODBC, however, there are no tests for them. > Need to add tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6092) Bulk Inserts are not Supported
[
https://issues.apache.org/jira/browse/IGNITE-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6092:
---
Assignee: Alexander Paschenko (was: Vladimir Ozerov)
> Bulk Inserts are not Supported
> ---
>
> Key: IGNITE-6092
> URL: https://issues.apache.org/jira/browse/IGNITE-6092
> Project: Ignite
> Issue Type: New Feature
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.3
>
>
> Presently the bulk inserts like these are not supported by Ignite's SQL
> engine:
> {code}
> INSERT INTO City (id, name)
> VALUES (1, 'Forest Hill'),
>(2, "Denver"),
>(3, "St. Petersburg")
> INSERT INTO Person (id, name, city_id)
> VALUES (1, 'John Doe', 3),
>(2, "Jane Roe", 2),
>(3, "Mary Major", 1),
>(4, "Richard Miles", 2)
> {code}
> Let's plan to support them for the nearest release. I've used DBeaver tool to
> validate the statements above:
> https://apacheignite-tools.readme.io/docs/dbeaver
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5879) .NET: Move TestPlatformPlugin to a separate module
[ https://issues.apache.org/jira/browse/IGNITE-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153301#comment-16153301 ] Yakov Zhdanov commented on IGNITE-5879: --- [~ptupitsyn] [~daradurvs] Changes look good to me. [~avinogradov] can you please review maven part and merge then? > .NET: Move TestPlatformPlugin to a separate module > -- > > Key: IGNITE-5879 > URL: https://issues.apache.org/jira/browse/IGNITE-5879 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Vyacheslav Daradur > Labels: .NET > Fix For: 2.3 > > > Move test plugin to a separate module and load it only for .NET tests so we > don't interfere with other tests. > Dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Plugins-in-tests-td20167.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6196) SQL: verify usability of template-based CREATE TABLE operations
[
https://issues.apache.org/jira/browse/IGNITE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6196:
Labels: usability (was: )
> SQL: verify usability of template-based CREATE TABLE operations
> ---
>
> Key: IGNITE-6196
> URL: https://issues.apache.org/jira/browse/IGNITE-6196
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Labels: usability
> Fix For: 2.3
>
>
> We do not have enough tests and examples on cache template usage for {{CREATE
> TABLE}}. I found only one test which used not template, but existing cache as
> a base for new cache. Let's add more tests with real pre-configured templates
> and extend our documentation accordingly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6260) Need to rename setDistributedJoins to setNonCollocatedJoins
[
https://issues.apache.org/jira/browse/IGNITE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6260:
Labels: Usability usability (was: usability)
> Need to rename setDistributedJoins to setNonCollocatedJoins
> ---
>
> Key: IGNITE-6260
> URL: https://issues.apache.org/jira/browse/IGNITE-6260
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, odbc, sql
>Reporter: Dmitriy Setrakyan
> Labels: Usability, usability
> Fix For: 2.3
>
>
> The name {{distributed join}} is very confusing, as all joins in Ignite are
> distributed. We should do the following:
> * Deprecate {{setDistributedJoins(...)}} property (it should be removed in
> 3.0)
> * Add {{setNonCollocatedJoins(...)}} property.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6263) .NET: Verify Java config parity with a unit test
Pavel Tupitsyn created IGNITE-6263:
--
Summary: .NET: Verify Java config parity with a unit test
Key: IGNITE-6263
URL: https://issues.apache.org/jira/browse/IGNITE-6263
Project: Ignite
Issue Type: Improvement
Components: platforms
Reporter: Pavel Tupitsyn
Write a unit test that compares .NET {{IgniteConfiguration}} and Java
{{IgniteConfiguration}} and fails if some properties are different.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6264) .NET: Verify Java API parity with a unit test
Pavel Tupitsyn created IGNITE-6264: -- Summary: .NET: Verify Java API parity with a unit test Key: IGNITE-6264 URL: https://issues.apache.org/jira/browse/IGNITE-6264 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Write a unit test that compares Java and .NET Ignite APIs (like Cache and Compute) to make sure that new APIs are not missed in platforms. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6260) Need to rename setDistributedJoins to setNonCollocatedJoins
[
https://issues.apache.org/jira/browse/IGNITE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6260:
Labels: usability (was: Usability usability)
> Need to rename setDistributedJoins to setNonCollocatedJoins
> ---
>
> Key: IGNITE-6260
> URL: https://issues.apache.org/jira/browse/IGNITE-6260
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, odbc, sql
>Reporter: Dmitriy Setrakyan
> Labels: usability
> Fix For: 2.3
>
>
> The name {{distributed join}} is very confusing, as all joins in Ignite are
> distributed. We should do the following:
> * Deprecate {{setDistributedJoins(...)}} property (it should be removed in
> 3.0)
> * Add {{setNonCollocatedJoins(...)}} property.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6249) .NET: IgniteConfiguration.ConsistentId
[
https://issues.apache.org/jira/browse/IGNITE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6249:
Labels: .NET usability (was: .NET)
> .NET: IgniteConfiguration.ConsistentId
> --
>
> Key: IGNITE-6249
> URL: https://issues.apache.org/jira/browse/IGNITE-6249
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, usability
> Fix For: 2.3
>
>
> Propagate {{IgniteConfiguration.ConsistentId}} to .NET.
> Java side requires {{Serializable}} there, and {{BinaryObject}} is
> {{Serializable}}, so we can provide any user-defined objects there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6216) .NET: Add CheckpointWriteOrder enum in persistent store configuration
[ https://issues.apache.org/jira/browse/IGNITE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6216: Labels: .NET MakeTeamcityGreenAgain usability (was: .NET MakeTeamcityGreenAgain) > .NET: Add CheckpointWriteOrder enum in persistent store configuration > - > > Key: IGNITE-6216 > URL: https://issues.apache.org/jira/browse/IGNITE-6216 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.1 >Reporter: Ivan Rakov >Assignee: Pavel Tupitsyn > Labels: .NET, MakeTeamcityGreenAgain, usability > Fix For: 2.3 > > > Since 2.2 we have CheckpointWriteOrder property in > PersistentStoreConfiguration. It should be possible to set through .NET > configuration classes. > Default value should be CheckpointWriteOrder#SEQUENTIAL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN
[
https://issues.apache.org/jira/browse/IGNITE-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-5949:
---
Assignee: (was: Alexander Paschenko)
> DDL: Support ALTER TABLE DROP COLUMN
>
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Andrew Mashenkov
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6054) SQL: Add option to store primitive keys in plain form for CREATE TABLE
[
https://issues.apache.org/jira/browse/IGNITE-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6054:
---
Assignee: (was: Alexander Paschenko)
> SQL: Add option to store primitive keys in plain form for CREATE TABLE
> --
>
> Key: IGNITE-6054
> URL: https://issues.apache.org/jira/browse/IGNITE-6054
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
> Labels: performance
>
> Currently we create separate internal type for primary key columns. This is
> necessary to avoid clashes between keys of the same type within the same
> caches (ironically, we do not allow multiple dynamic tables per cache).
> The most widely used PK is single-column key of {{Long}} or {{String}} data
> type. If we store a key plain {{long}}, it will consume 9 bytes. If we store
> it as an object with long field, it will consume 24 + 9 = 33 bytes. What is
> worse, in the latter case we will have to copy key object back and forth
> between page memory and application code many times, while for plain long key
> we simply do {{Unsafe.getLong}}.
> For this reason, it makes sense to introduce special mode for {{CREATE
> TABLE}} command, when key will not be wrapped into a class, and will be
> stored as is. Let's name it {{plainPrimaryKey}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-4726) SQL: benchmark DML operations
[
https://issues.apache.org/jira/browse/IGNITE-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4726:
---
Assignee: (was: Alexander Paschenko)
> SQL: benchmark DML operations
> -
>
> Key: IGNITE-4726
> URL: https://issues.apache.org/jira/browse/IGNITE-4726
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>
> We need to create benchmarks for DML operations similar to our cache
> benchmarks and compare common cases. Results of cache API benchmarks can be
> used as baseline for us.
> Preliminray list of benchmarks:
> 1) INSERT + DELETE (vs {{IgniteCache.put}} + {{IgniteCache.remove}})
> 2) Simple MERGE (vs {{IgniteCache.put}})
> 3) Simple UPDATE (vs {{IgniteCache.invoke}})
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4605) Apache Ignite R Library
[ https://issues.apache.org/jira/browse/IGNITE-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4605: Component/s: (was: platforms) > Apache Ignite R Library > --- > > Key: IGNITE-4605 > URL: https://issues.apache.org/jira/browse/IGNITE-4605 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct R language support for Apache > Ignite In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > R can be supported in several ways that have do be discussed on the dev list: > - Use SWIG (http://www.swig.org) to generate R API from Ignite.C++. > - Design and implement R API from scratch talking to underlying JVM that runs > the node. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4609) R: basic SQL Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4609: Component/s: (was: platforms) > R: basic SQL Grid API > - > > Key: IGNITE-4609 > URL: https://issues.apache.org/jira/browse/IGNITE-4609 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Implement basic SQL Grid API similar to the scope covered by C++ which > includes SQL queries and DML. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4606) R: module and build scripts
[ https://issues.apache.org/jira/browse/IGNITE-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4606: Component/s: (was: platforms) > R: module and build scripts > --- > > Key: IGNITE-4606 > URL: https://issues.apache.org/jira/browse/IGNITE-4606 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Create "ignite-r" module and implement a build procedure for it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4607) R: support binary format
[ https://issues.apache.org/jira/browse/IGNITE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4607: Component/s: (was: platforms) > R: support binary format > > > Key: IGNITE-4607 > URL: https://issues.apache.org/jira/browse/IGNITE-4607 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > R client has to support binary format natively by implementing a binary > marshaller logic directly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4608) R: basic Data Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4608: Component/s: (was: platforms) > R: basic Data Grid API > -- > > Key: IGNITE-4608 > URL: https://issues.apache.org/jira/browse/IGNITE-4608 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Implement basic Data Grid API similar to the scope covered by C++: > https://apacheignite-cpp.readme.io/docs/data-grid -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4604) Python: basic SQL Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4604: Component/s: (was: platforms) > Python: basic SQL Grid API > -- > > Key: IGNITE-4604 > URL: https://issues.apache.org/jira/browse/IGNITE-4604 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Implement basic SQL Grid API similar to the scope covered by C++ which > includes SQL queries and DML. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-1456) CPP: Implement Cache.Rebalance()
[ https://issues.apache.org/jira/browse/IGNITE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1456: Fix Version/s: 2.3 > CPP: Implement Cache.Rebalance() > > > Key: IGNITE-1456 > URL: https://issues.apache.org/jira/browse/IGNITE-1456 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Wuwei Lin > Labels: cpp > Fix For: 2.3 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4603) Python: basic Data Grid API
[ https://issues.apache.org/jira/browse/IGNITE-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4603: Component/s: (was: platforms) > Python: basic Data Grid API > --- > > Key: IGNITE-4603 > URL: https://issues.apache.org/jira/browse/IGNITE-4603 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Implement basic Data Grid API similar to the scope covered by C++: > https://apacheignite-cpp.readme.io/docs/data-grid -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4601) Python: support binary format
[ https://issues.apache.org/jira/browse/IGNITE-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4601: Component/s: (was: platforms) > Python: support binary format > - > > Key: IGNITE-4601 > URL: https://issues.apache.org/jira/browse/IGNITE-4601 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Python client has to support binary format natively by implementing a binary > marshaller logic directly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4602) Python: module and build scripts
[ https://issues.apache.org/jira/browse/IGNITE-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4602: Component/s: (was: platforms) > Python: module and build scripts > > > Key: IGNITE-4602 > URL: https://issues.apache.org/jira/browse/IGNITE-4602 > Project: Ignite > Issue Type: Sub-task >Reporter: Denis Magda > > Create "ignite-python" module and implement a build procedure for it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4600: Component/s: (was: platforms) > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4874) SQL engine should throw meaningful exception on query from local cache
[
https://issues.apache.org/jira/browse/IGNITE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4874:
Labels: usability (was: )
> SQL engine should throw meaningful exception on query from local cache
> --
>
> Key: IGNITE-4874
> URL: https://issues.apache.org/jira/browse/IGNITE-4874
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Priority: Minor
> Labels: usability
>
> To reproduce:
> Configure local cache
> Configure partitioned cache
> Extract data from local cache by sending query to partitioned cache.
> Got error on iteration of received result Cursor:
> {code}
> java.lang.AssertionError: GridCacheAdapter
> [locMxBean=org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl@492168ef,
>
> clusterMxBean=org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl@70abe2fc,
>
> aff=org.apache.ignite.internal.processors.cache.affinity.GridCacheAffinityImpl@510d8baf,
> igfsDataCache=false, mongoDataCache=false, mongoMetaCache=false,
> igfsDataCacheSize=null, igfsDataSpaceMax=0,
> asyncOpsSem=java.util.concurrent.Semaphore@7938449a[Permits = 500],
> name=c_local, size=77]
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.topology(GridCacheContext.java:828)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.hasMovingPartitions(GridReduceQueryExecutor.java:391)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.isPreloadingActive(GridReduceQueryExecutor.java:378)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:517)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1149)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-1456) CPP: Implement Cache.Rebalance()
[ https://issues.apache.org/jira/browse/IGNITE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153341#comment-16153341 ] Igor Sapego commented on IGNITE-1456: - There is no tests in PR. I'm going to add some tests to check if everything is working as intended and merge it then, if everything is OK. > CPP: Implement Cache.Rebalance() > > > Key: IGNITE-1456 > URL: https://issues.apache.org/jira/browse/IGNITE-1456 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Wuwei Lin > Labels: cpp > Fix For: 2.3 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6195) SQL: Do not allow JOINs on caches with different affinity functions
[
https://issues.apache.org/jira/browse/IGNITE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6195:
Labels: usability (was: )
> SQL: Do not allow JOINs on caches with different affinity functions
> ---
>
> Key: IGNITE-6195
> URL: https://issues.apache.org/jira/browse/IGNITE-6195
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
> Labels: usability
> Fix For: 2.3
>
>
> Currently it is possible to execute JOIN on non-colocated caches. No
> exceptions will appear, user just receive incorrect result. We need to detect
> such situations and throw errors instead.
> *Proposed solution*
> Correct SQL result is possible when either distributed joins are enabled, or
> data is co-located properly. Under *proper* co-location we mean:
> 1) Participating {{PARTITIONED}} caches use the same affinity function
> 2) This affinity function doesn't depend on it's own previous state, i.e. it
> doesn't rely on {{AffinityFunctionContext.previousAssignment}}. For instance,
> {{RendezvousAffinityFunction}} doesn't use, while {{FairAffinityFunction}}
> does.
> As such, the following procedure should be implemented in order to determine
> whether SQL can be executed:
> 1) If {{distributedJoins}} are enabled - return, SQL can be executed
> 2) Get the list of participating caches
> 3) Exclude {{REPLICATED}} caches from that list
> 4) If all remaining caches belong to the same cache group - return, SQL can
> be executed
> 5) Get affinity function of the first cache
> 6) Check if affinity function doesn't use
> {{AffinityFunctionContext.previousAssignment}}. This could be controlled
> either through annotation, or through new method on {{AffinityFunction}}
> interface, e.g. {{boolean isDependOnPreviousState}}. If {{false}} - throw an
> exception
> 7) Check if affinity functions of all caches are equal through standard
> {{equals()}} method. If {{false}} - throw an exception.
> 8) Otherwise - SQL can be executed safely.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6148) JDBC thin: improve error handling, support categorized SQLExceptions
[ https://issues.apache.org/jira/browse/IGNITE-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6148: Summary: JDBC thin: improve error handling, support categorized SQLExceptions (was: DBC thin: improve error handling, support categorized SQLExceptions) > JDBC thin: improve error handling, support categorized SQLExceptions > > > Key: IGNITE-6148 > URL: https://issues.apache.org/jira/browse/IGNITE-6148 > Project: Ignite > Issue Type: Task > Components: jdbc >Affects Versions: 2.1 >Reporter: Taras Ledkov > > Current implementation of the JDBC thin driver throws pure SQLException with > string message only. Appropriate subclasses of SQLException must be thrown in > special cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5929) Add application name to query
[ https://issues.apache.org/jira/browse/IGNITE-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5929: Labels: usability (was: ) > Add application name to query > - > > Key: IGNITE-5929 > URL: https://issues.apache.org/jira/browse/IGNITE-5929 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov > Labels: usability > > It will be useful feature to add application name to query. > This will allow to understand from logs and UI tools what application > executed some query. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-3870) Keeping SQL query result set in off heap tier
[ https://issues.apache.org/jira/browse/IGNITE-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-3870. --- > Keeping SQL query result set in off heap tier > - > > Key: IGNITE-3870 > URL: https://issues.apache.org/jira/browse/IGNITE-3870 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Denis Magda > > With the new off heap storage architectures (IGNITE-3477) it makes sense to > improve a part of the system that prepares an SQL query result set in a such > a way: > - result set should consist of wrappers objects that incorporate off heap > pointers to fields and values stored off heap; > - during the time the result set is being sent over the wire we shouldn't > move fields and values from off heap to Java heap but rather implement a > solution that will allow us to pass an off heap pointer to a sockets output > stream. Probably this can be done by leveraging Java's DirectBuffers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-3870) Keeping SQL query result set in off heap tier
[ https://issues.apache.org/jira/browse/IGNITE-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-3870. - Resolution: Won't Fix Closing as "Won't Fix", as this proposal doesn't fit to our architecture - we do not want to hold locks on pages for a long time. Instead, the result itslef could reside in special memory part, possibly offheap - this is good idea, but definitely out of scope of this ticket. > Keeping SQL query result set in off heap tier > - > > Key: IGNITE-3870 > URL: https://issues.apache.org/jira/browse/IGNITE-3870 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Denis Magda > > With the new off heap storage architectures (IGNITE-3477) it makes sense to > improve a part of the system that prepares an SQL query result set in a such > a way: > - result set should consist of wrappers objects that incorporate off heap > pointers to fields and values stored off heap; > - during the time the result set is being sent over the wire we shouldn't > move fields and values from off heap to Java heap but rather implement a > solution that will allow us to pass an off heap pointer to a sockets output > stream. Probably this can be done by leveraging Java's DirectBuffers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6265) BinaryObject fields nested deeper than one level cannot be updated via SQL
Alexandr Fedotov created IGNITE-6265:
Summary: BinaryObject fields nested deeper than one level cannot
be updated via SQL
Key: IGNITE-6265
URL: https://issues.apache.org/jira/browse/IGNITE-6265
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.1
Reporter: Alexandr Fedotov
Fix For: 2.3
SQL update of a BinaryObject field nested deeper than one level throws an
exception
Caused by: class org.apache.ignite.IgniteCheckedException: Non-binary object
received as a result of property extraction
[parent=org.apache.ignite.internal.processors.query.property.QueryBinaryProperty@1e86486b,
propName=nestedObj,
obj=org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl@1fc7875]
at
org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:105)
at
org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.setValue(QueryBinaryProperty.java:159)
at
org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.setColumnValue(H2RowDescriptor.java:348)
The problem is that only a BinaryObject is expected in the following part of
the {{QueryBinaryProperty.value}} method
{code:java}
if (!ctx.cacheObjects().isBinaryObject(obj))
throw new IgniteCheckedException("Non-binary object received as a result of
property extraction " + "[parent=" + parent + ", propName=" + propName + ",
obj=" + obj + ']');
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4739) CacheJdbcPojoStore: Add upsert support for PostgreSQL dialect
[ https://issues.apache.org/jira/browse/IGNITE-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4739: Component/s: (was: sql) > CacheJdbcPojoStore: Add upsert support for PostgreSQL dialect > - > > Key: IGNITE-4739 > URL: https://issues.apache.org/jira/browse/IGNITE-4739 > Project: Ignite > Issue Type: Task >Reporter: Andrey Novikov >Priority: Minor > > https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.5#INSERT_..._ON_CONFLICT_DO_NOTHING.2FUPDATE_.28.22UPSERT.22.29 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6265) BinaryObject fields nested deeper than one level cannot be updated via SQL
[
https://issues.apache.org/jira/browse/IGNITE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Fedotov updated IGNITE-6265:
-
Attachment: BinaryObjectNestedFieldsQueryTest.java
A reproducer test
> BinaryObject fields nested deeper than one level cannot be updated via SQL
> --
>
> Key: IGNITE-6265
> URL: https://issues.apache.org/jira/browse/IGNITE-6265
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Alexandr Fedotov
> Fix For: 2.3
>
> Attachments: BinaryObjectNestedFieldsQueryTest.java
>
>
> SQL update of a BinaryObject field nested deeper than one level throws an
> exception
> Caused by: class org.apache.ignite.IgniteCheckedException: Non-binary object
> received as a result of property extraction
> [parent=org.apache.ignite.internal.processors.query.property.QueryBinaryProperty@1e86486b,
> propName=nestedObj,
> obj=org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl@1fc7875]
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:105)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.setValue(QueryBinaryProperty.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.setColumnValue(H2RowDescriptor.java:348)
> The problem is that only a BinaryObject is expected in the following part of
> the {{QueryBinaryProperty.value}} method
> {code:java}
> if (!ctx.cacheObjects().isBinaryObject(obj))
> throw new IgniteCheckedException("Non-binary object received as a result
> of property extraction " + "[parent=" + parent + ", propName=" + propName +
> ", obj=" + obj + ']');
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6265) BinaryObject fields nested deeper than one level cannot be updated via SQL
[
https://issues.apache.org/jira/browse/IGNITE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153359#comment-16153359
]
Alexandr Fedotov commented on IGNITE-6265:
--
Allowing {{BinaryObjectBuilder}} in the condition resolves the issue, but it
should be checked thoroughly.
> BinaryObject fields nested deeper than one level cannot be updated via SQL
> --
>
> Key: IGNITE-6265
> URL: https://issues.apache.org/jira/browse/IGNITE-6265
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Alexandr Fedotov
> Fix For: 2.3
>
> Attachments: BinaryObjectNestedFieldsQueryTest.java
>
>
> SQL update of a BinaryObject field nested deeper than one level throws an
> exception
> Caused by: class org.apache.ignite.IgniteCheckedException: Non-binary object
> received as a result of property extraction
> [parent=org.apache.ignite.internal.processors.query.property.QueryBinaryProperty@1e86486b,
> propName=nestedObj,
> obj=org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl@1fc7875]
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:105)
> at
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.setValue(QueryBinaryProperty.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.setColumnValue(H2RowDescriptor.java:348)
> The problem is that only a BinaryObject is expected in the following part of
> the {{QueryBinaryProperty.value}} method
> {code:java}
> if (!ctx.cacheObjects().isBinaryObject(obj))
> throw new IgniteCheckedException("Non-binary object received as a result
> of property extraction " + "[parent=" + parent + ", propName=" + propName +
> ", obj=" + obj + ']');
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6258) .NET: Thin client: Define metadata exchange protocol
[
https://issues.apache.org/jira/browse/IGNITE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153383#comment-16153383
]
Pavel Tupitsyn commented on IGNITE-6258:
h4. Proposed operations
*Dynamic Type Registration:*
* {{void RegisterBinaryTypeName(int typeId, string typeName)}}
* {{string GetBinaryTypeName(int typeId)}}
*Binary Metadata*
* {{PutBinaryTypes(ICollection types)}}. BinaryType includes
{{TypeName}}, {{TypeId}}, {{AffinityKeyFieldName}}, {{FieldMap[Name, TypeId,
FieldId]}}, {{IsEnum}}, {{EnumFieldNames}}, {{Schemas}}
* {{BinaryType GetBinaryType(int typeId)}}
* {{ICollection GetBinaryTypes()}}
* {{BinaryType RegisterEnum(string typeName, Map fields)}}
*Optional*
* {{int[] GetSchema(int typeId, int schemaId)}} - this is not necessary, but
can be useful to avoid retrieving entire BinaryType when only schema is needed
for deserialization
> .NET: Thin client: Define metadata exchange protocol
>
>
> Key: IGNITE-6258
> URL: https://issues.apache.org/jira/browse/IGNITE-6258
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> IGNITE-6236 introduced some metadata operations in client protocol.
> Let's formalize these operations:
> * Which operations should be present? PutMeta, PutMetas, GetMeta, GetSchema,
> etc.
> * Do we need to retrieve schemas separately from entire metadata?
> * Dynamic type registration
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6152) Wrong response from grid via jdbc driver
[
https://issues.apache.org/jira/browse/IGNITE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6152:
Fix Version/s: (was: 2.3)
> Wrong response from grid via jdbc driver
>
>
> Key: IGNITE-6152
> URL: https://issues.apache.org/jira/browse/IGNITE-6152
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
> Environment: OS X 10.10.5
> java version "1.8.0_91"
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
>
> Now I'm testing command line tool - *sqlline* ([link to
> github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI
> grid via thin jdbc driver.
> When I was trying to get column list from AI grid and H2 database I got 2
> different responses from the same table.
> Ignite:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !columns person
> ++++
> | TABLE_CAT| TABLE_SCHEM |
> TABLE_NAME |
> ++++
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> ++++
> {noformat}
> H2:
> {noformat}
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE |
> TYPE_NAME | COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX |
> NULLABLE | REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB |
> CHAR_OCTE |
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TEST" | PUBLIC | PERSON | ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> | TEST" | PUBLIC | PERSON | NAME| 12 | VARCHAR
> | 2147483647 | 2147483647| 0 | 10 | 1
> | || 12| 0| 214748364 |
> | TEST" | PUBLIC | PERSON | CITY_ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5339) JDBC thin driver: validate compliance
[ https://issues.apache.org/jira/browse/IGNITE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153412#comment-16153412 ] Taras Ledkov commented on IGNITE-5339: -- [~vozerov], the branch is merged with master. Tests renames are removed. > JDBC thin driver: validate compliance > - > > Key: IGNITE-5339 > URL: https://issues.apache.org/jira/browse/IGNITE-5339 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Labels: important > Fix For: 2.3 > > > We need to make sure that all methods of our new driver are compliant with > JDBC spec, namely: > 1) Semantics of normal execution is correct > 2) Exceptions are thrown when excepted > I propose the following flow: > 1) Walk through interface classes (Connection -> Statement, PreparedStatement > -> ResultSet) > 2) For every method identify a set of tests to verify semantics (if any). > 3) Write those tests, even if they fail. > 4) Once all tests are ready, decide how to proceed with their fixes. > NB: we should write tests even for methods which throw "not-implemented > exception", so that we better understand the scope of remaining work. > Link to [JDBC > specification|http://download.oracle.com/otn-pub/jcp/jdbc-4_1-mrel-spec/jdbc4.1-fr-spec.pdf?AuthParam=1496141650_c2ec45f13eb8c532632bbfaede64f351] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6262) TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky.
[ https://issues.apache.org/jira/browse/IGNITE-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6262: --- Labels: MakeTeamcityGreenAgain (was: ) > TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear and > TxPessimisticDeadlockDetectionTest.testDeadlocksReplicated is failing flaky. > - > > Key: IGNITE-6262 > URL: https://issues.apache.org/jira/browse/IGNITE-6262 > Project: Ignite > Issue Type: Bug >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov > Labels: MakeTeamcityGreenAgain > > The problem is the same with IGNITE-5865. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-6152) Wrong response from grid via jdbc driver
[
https://issues.apache.org/jira/browse/IGNITE-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov closed IGNITE-6152.
> Wrong response from grid via jdbc driver
>
>
> Key: IGNITE-6152
> URL: https://issues.apache.org/jira/browse/IGNITE-6152
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
> Environment: OS X 10.10.5
> java version "1.8.0_91"
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
>
> Now I'm testing command line tool - *sqlline* ([link to
> github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI
> grid via thin jdbc driver.
> When I was trying to get column list from AI grid and H2 database I got 2
> different responses from the same table.
> Ignite:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !columns person
> ++++
> | TABLE_CAT| TABLE_SCHEM |
> TABLE_NAME |
> ++++
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> || PUBLIC | PERSON
> |
> ++++
> {noformat}
> H2:
> {noformat}
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE |
> TYPE_NAME | COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX |
> NULLABLE | REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB |
> CHAR_OCTE |
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> | TEST" | PUBLIC | PERSON | ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> | TEST" | PUBLIC | PERSON | NAME| 12 | VARCHAR
> | 2147483647 | 2147483647| 0 | 10 | 1
> | || 12| 0| 214748364 |
> | TEST" | PUBLIC | PERSON | CITY_ID | -5 | BIGINT
> | 19 | 19| 0 | 10 | 0
> | || -5| 0| 19|
> +---+-++-+-+---+-+---+++-+-++---+--+---+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6243) RazorSQL crash on try edit, describe and another actions with table.
[ https://issues.apache.org/jira/browse/IGNITE-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6243: Fix Version/s: 2.3 > RazorSQL crash on try edit, describe and another actions with table. > > > Key: IGNITE-6243 > URL: https://issues.apache.org/jira/browse/IGNITE-6243 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.1 >Reporter: Aleksey Chetaev > Fix For: 2.3 > > > 1. Install ODBC on Windows. > 2. Crete DSN for Ignite ODBC Driver. > 3. Connect by RazorSQL using ODBC. > 4. Create new table. > 5. Try to edit table, using right click. > RazorSQL crashed without error. > Need check that it's not crash of Apache Ignite ODBC driver. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6243) RazorSQL crash on try edit, describe and another actions with table.
[ https://issues.apache.org/jira/browse/IGNITE-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-6243: --- Assignee: Igor Sapego > RazorSQL crash on try edit, describe and another actions with table. > > > Key: IGNITE-6243 > URL: https://issues.apache.org/jira/browse/IGNITE-6243 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Assignee: Igor Sapego > Fix For: 2.3 > > > 1. Install ODBC on Windows. > 2. Crete DSN for Ignite ODBC Driver. > 3. Connect by RazorSQL using ODBC. > 4. Create new table. > 5. Try to edit table, using right click. > RazorSQL crashed without error. > Need check that it's not crash of Apache Ignite ODBC driver. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5344) JDBC thin driver: support Statement.closeOnCompletion
[
https://issues.apache.org/jira/browse/IGNITE-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153436#comment-16153436
]
Taras Ledkov edited comment on IGNITE-5344 at 9/5/17 10:25 AM:
---
[~vozerov], please take a look at the test
{{JdbcThinStatementSelfTest#testCloseOnCompletion}}. The test checks the case
described by you:
- Open result set;
- Set {{closeOnCompletion}} for statement;
- Close result set
- Check that statement is closed.
was (Author: tledkov-gridgain):
[~vozerov], please take a look at the test
{{JdbcThinStatementSelfTest#testCloseOnCompletion}}. The test check the case
described by you:
- Open result set;
- Set {{closeOnCompletion}} for statement;
- Close result set
- Check that statement is closed.
> JDBC thin driver: support Statement.closeOnCompletion
> -
>
> Key: IGNITE-5344
> URL: https://issues.apache.org/jira/browse/IGNITE-5344
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5344) JDBC thin driver: support Statement.closeOnCompletion
[
https://issues.apache.org/jira/browse/IGNITE-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153436#comment-16153436
]
Taras Ledkov commented on IGNITE-5344:
--
[~vozerov], please take a look at the test
{{JdbcThinStatementSelfTest#testCloseOnCompletion}}. The test check the case
described by you:
- Open result set;
- Set {{closeOnCompletion}} for statement;
- Close result set
- Check that statement is closed.
> JDBC thin driver: support Statement.closeOnCompletion
> -
>
> Key: IGNITE-5344
> URL: https://issues.apache.org/jira/browse/IGNITE-5344
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6258) .NET: Thin client: Define metadata exchange protocol
[ https://issues.apache.org/jira/browse/IGNITE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153450#comment-16153450 ] Pavel Tupitsyn commented on IGNITE-6258: Dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Thin-client-and-binary-metadata-td21642.html > .NET: Thin client: Define metadata exchange protocol > > > Key: IGNITE-6258 > URL: https://issues.apache.org/jira/browse/IGNITE-6258 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.3 > > > IGNITE-6236 introduced some metadata operations in client protocol. > Let's formalize these operations: > * Which operations should be present? PutMeta, PutMetas, GetMeta, GetSchema, > etc. > * Do we need to retrieve schemas separately from entire metadata? > * Dynamic type registration -- This message was sent by Atlassian JIRA (v6.4.14#64029)
