[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921554#comment-16921554 ] Aleksey Chetaev commented on IGNITE-5355: - [~dpavlov] Ok, if I understood correct, you think that we need some tool in Ignite which will be automatically create release note in HTML format using our specific? Right? > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev >Priority: Major > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915235#comment-16915235 ] Aleksey Chetaev commented on IGNITE-5355: - [~dpavlov] It's interesting question. Last time I used this PR in 2017, but if we look to release notes for 2.7.0 and 2.7.5 it's looking like my tool. I think we should ask last release engineer, how he genereate release notes. Do you know who it was? > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev >Priority: Major > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-9501) Exclude newly joining nodes from exchange latch
[
https://issues.apache.org/jira/browse/IGNITE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617841#comment-16617841
]
Aleksey Chetaev commented on IGNITE-9501:
-
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890763]]
* GridOrderedMessageCancelSelfTest.testTaskException (last started)
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 JVM
CRASH , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890681]]
* IgniteCacheAtomicNearEnabledFieldsQuerySelfTest.testSingleResultUsesFindOne
(last started)
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890762]]
*
GridCachePartitionedDataStructuresFailoverSelfTest.testCanCloseSetInInterruptedThread
(last started)
{color:#d04437}Cache 7 (With Persistence){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890765]]
* WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator (last started)
{color:#d04437}Cache 5{color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890761]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodes
- 0,0% fails in last 100 master runs.
* IgniteCacheGroupsPartitionLossPolicySelfTest.testIgnore (last started)
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890758]]
* CacheLockReleaseNodeLeaveTest.testTxLockRelease2 (last started)
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890720]]
* ZookeeperDiscoverySpiTest.testConcurrentStartStop1 (last started)
{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 0
TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890680]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Compute (Grid){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890685]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890757]]
* GridCacheStopSelfTest.testStopMultithreaded (last started)
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 JVM CRASH , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890679]]
* IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers2 (last
started)
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890749]]
*
IgniteAtomicLongChangingTopologySelfTest.testClientCollocatedSetCreateCloseFailover
(last started)
{color:#d04437}Java Thin Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890704]]
{color:#d04437}Cache (Failover) 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890750]]
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testAsyncFailover - 0,0% fails in last
100 master runs.
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testPutAllAsyncFailover - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890745]]
* IgniteCacheTestSuite6:
PartitionsExchangeCoordinatorFailoverTest.testNewCoordinatorCompletedExchange -
0,0% fails in last 100 master runs.
* IgniteCacheTestSuite6:
TxRollbackAsyncNearCacheTest.testMixedAsyncRollbackTypes - 0,0% fails in last
100 master runs.
* IgniteCacheTestSuite6: TxRollbackAsyncTest.testMixedAsyncRollbackTypes - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890770]]
* IgniteCacheTestSuite8:
GridCacheRebalancingSyncCheckDataTest.testDataRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890699]]
* IgniteClientTestSuite: ClientTcpDirectMultiNodeSelfTest.testTopologyListener
- 0,0% fails in last 100 master runs.
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890677]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridDiscoveryManagerAliveCacheSelfTest.testAlives - 0,0% fails in last 100
master runs.
{color:#d04437}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890774]]
* IgniteBasicTestSuite:
DataRegionMetricsSelfTest.testAllocationRateMultiThreaded - 0,0% fails in last
100 master runs.
* IgniteB
[jira] [Commented] (IGNITE-9501) Exclude newly joining nodes from exchange latch
[
https://issues.apache.org/jira/browse/IGNITE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617810#comment-16617810
]
Aleksey Chetaev commented on IGNITE-9501:
-
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890763]]
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 JVM
CRASH , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890681]]
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890762]]
*
GridCachePartitionedDataStructuresFailoverSelfTest.testCanCloseSetInInterruptedThread
(last started)
{color:#d04437}Cache 7 (With Persistence){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890765]]
* WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator (last started)
{color:#d04437}Cache 5{color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890761]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodes
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890758]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890720]]
* ZookeeperDiscoverySpiTest.testConcurrentStartStop1 (last started)
{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 0
TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890680]]
{color:#d04437}Compute (Grid){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890685]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890757]]
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 JVM CRASH , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890679]]
* IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers2 (last
started)
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890749]]
{color:#d04437}Java Thin Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890704]]
{color:#d04437}Cache (Failover) 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890750]]
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testAsyncFailover - 0,0% fails in last
100 master runs.
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testPutAllAsyncFailover - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890745]]
* IgniteCacheTestSuite6:
PartitionsExchangeCoordinatorFailoverTest.testNewCoordinatorCompletedExchange -
0,0% fails in last 100 master runs.
* IgniteCacheTestSuite6:
TxRollbackAsyncNearCacheTest.testMixedAsyncRollbackTypes - 0,0% fails in last
100 master runs.
* IgniteCacheTestSuite6: TxRollbackAsyncTest.testMixedAsyncRollbackTypes - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890770]]
* IgniteCacheTestSuite8:
GridCacheRebalancingSyncCheckDataTest.testDataRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890699]]
* IgniteClientTestSuite: ClientTcpDirectMultiNodeSelfTest.testTopologyListener
- 0,0% fails in last 100 master runs.
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890677]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridDiscoveryManagerAliveCacheSelfTest.testAlives - 0,0% fails in last 100
master runs.
{color:#d04437}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890774]]
* IgniteBasicTestSuite:
DataRegionMetricsSelfTest.testAllocationRateMultiThreaded - 0,0% fails in last
100 master runs.
* IgniteBasicTestSuite: GridNioSslSelfTest.testSimpleMessages - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache (Restarts) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890754]]
* IgniteCacheRestartTestSuite:
IgniteCacheCreateRestartSelfTest.testStopOriginatingNode - 0,0% fails in last
100 master runs.
{color:#d04437}PDS 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890736]]
* IgnitePdsTestSuite:
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyCachesAbruptlyWithoutChec
[jira] [Commented] (IGNITE-8545) If queryParallelism in nodes' caches configurations differ, query may hang, assert or return incomplete results
[
https://issues.apache.org/jira/browse/IGNITE-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615188#comment-16615188
]
Aleksey Chetaev commented on IGNITE-8545:
-
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1812431]]
*
GridCachePartitionedDataStructuresFailoverSelfTest.testFairReentrantLockConstantTopologyChangeNonFailoverSafe
(last started)
{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1812423]]
* GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutTenNodesTwoBackups
(last started)
{color:#d04437}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1842358]]
* IgniteBinaryCacheQueryTestSuite: SchemaExchangeSelfTest.testDynamicRestarts -
0,0% fails in last 100 master runs.
{color:#d04437}PDS (Direct IO) 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1812402]]
* IgnitePdsNativeIoTestSuite2:
IgniteNativeIoPdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption
- 1,7% fails in last 100 master runs.
{color:#d04437}Cache (Failover) 1{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=1812418]]
* IgniteCacheFailoverTestSuite:
IgniteChangingBaselineUpCacheRemoveFailoverTest.testPutAndRemove - 1,8% fails
in last 100 master runs.
* IgniteCacheFailoverTestSuite:
IgniteChangingBaselineUpCacheRemoveFailoverTest.testPutAndRemovePessimisticTx -
1,8% fails in last 100 master runs.
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1812405]]
* IgnitePdsTestSuite:
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyCachesAbruptlyWithoutCheckpoints
- 0,0% fails in last 100 master runs.
{color:#d04437}Continuous Query 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1812357]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryFailoverAtomicSelfTest.testOneBackupClientUpdate - 0,0%
fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1812446&buildTypeId=IgniteTests24Java8_RunAll]
> If queryParallelism in nodes' caches configurations differ, query may hang,
> assert or return incomplete results
> ---
>
> Key: IGNITE-8545
> URL: https://issues.apache.org/jira/browse/IGNITE-8545
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Pudov
>Priority: Critical
> Fix For: 2.7
>
> Attachments: IgniteSqlSplitterQueryParallelismTest.java
>
>
> I imagine it should not. See the attached file.
> It happens both with client nodes and with server nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7594) Tx performance drop after WAL optimization
[ https://issues.apache.org/jira/browse/IGNITE-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348575#comment-16348575 ] Aleksey Chetaev commented on IGNITE-7594: - [~agura] * tx-putAll have drop ~ 50% between your commit and previous. * another tx benchmarks have drop ~ 10-15% * In BackGround mode we don't have drop between this commits. * I don't have counts for LOG_ONLY and this commits. But between 2.3 and 2.4 branches we have increase ~ x10. e.x. 4 servers 8 clients atomic-put in 2.3 ~ 5700 per client in seconds and in 2.4 ~ 53000 per client in seconds. > Tx performance drop after WAL optimization > --- > > Key: IGNITE-7594 > URL: https://issues.apache.org/jira/browse/IGNITE-7594 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Aleksey Chetaev >Priority: Critical > > Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. > WAL Mode: Default > First bad commit: > [https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7594) Tx performance drop after WAL optimization
[ https://issues.apache.org/jira/browse/IGNITE-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-7594: Description: Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. WAL Mode: Default First bad commit: [https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d] was: Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. First bad commit: https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d > Tx performance drop after WAL optimization > --- > > Key: IGNITE-7594 > URL: https://issues.apache.org/jira/browse/IGNITE-7594 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Aleksey Chetaev >Priority: Critical > > Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. > WAL Mode: Default > First bad commit: > [https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7594) Tx performance drop after WAL optimization
[ https://issues.apache.org/jira/browse/IGNITE-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-7594: Summary: Tx performance drop after WAL optimization (was: Tx performance drop after WAL optimization, in DEFAULT WAL mode) > Tx performance drop after WAL optimization > --- > > Key: IGNITE-7594 > URL: https://issues.apache.org/jira/browse/IGNITE-7594 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Aleksey Chetaev >Priority: Critical > > Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. > First bad commit: > https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7594) Tx performance drop after WAL optimization, in DEFAULT WAL mode
[ https://issues.apache.org/jira/browse/IGNITE-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-7594: Summary: Tx performance drop after WAL optimization, in DEFAULT WAL mode (was: Tx performance drop after WAL optimization in DEFAULT WAL mode) > Tx performance drop after WAL optimization, in DEFAULT WAL mode > --- > > Key: IGNITE-7594 > URL: https://issues.apache.org/jira/browse/IGNITE-7594 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Aleksey Chetaev >Priority: Critical > > Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. > First bad commit: > https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7594) Tx performance drop after WAL optimization in DEFAULT WAL mode
[ https://issues.apache.org/jira/browse/IGNITE-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-7594: Summary: Tx performance drop after WAL optimization in DEFAULT WAL mode (was: Tx performance drop after WAL optimization ) > Tx performance drop after WAL optimization in DEFAULT WAL mode > -- > > Key: IGNITE-7594 > URL: https://issues.apache.org/jira/browse/IGNITE-7594 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Aleksey Chetaev >Priority: Critical > > Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. > First bad commit: > https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7594) Tx performance drop after WAL optimization
Aleksey Chetaev created IGNITE-7594: --- Summary: Tx performance drop after WAL optimization Key: IGNITE-7594 URL: https://issues.apache.org/jira/browse/IGNITE-7594 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Aleksey Chetaev Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. First bad commit: https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7094) Javadoc warnings in ml module
Aleksey Chetaev created IGNITE-7094: --- Summary: Javadoc warnings in ml module Key: IGNITE-7094 URL: https://issues.apache.org/jira/browse/IGNITE-7094 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.4 Reporter: Aleksey Chetaev [14:20:11][Step 18/41] [WARNING] Javadoc Warnings [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link:illegal character: "47" in "/*SparseDistributedVector" [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link:illegal character: "42" in "/*SparseDistributedVector" [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link: reference not found: /*SparseDistributedVector [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/ColumnDecisionTreeTrainerInput.java:28: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/ColumnDecisionTreeTrainerInput.j
[jira] [Updated] (IGNITE-7094) Javadoc warnings in ml module
[
https://issues.apache.org/jira/browse/IGNITE-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-7094:
Description:
{code:java}
[14:20:11][Step 18/41] [WARNING] Javadoc Warnings
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43:
warning - Tag @link:illegal character: "47" in "/*SparseDistributedVector"
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43:
warning - Tag @link:illegal character: "42" in "/*SparseDistributedVector"
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43:
warning - Tag @link: reference not found: /*SparseDistributedVector
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/ColumnDecisionTreeTrainerInput.java:28:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
class/interface, constructor, field, method.
[14:20:11][Step 18/41] [WARNING]
/var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/ColumnDecisionTreeTrainerInput.java:28:
warning - Tag @see cannot be used in inline documentation. It can only be
used in the following types of documentation: overview, package,
[jira] [Updated] (IGNITE-6374) Web Console SQL doesn't work with 2.2.0 RC1
[
https://issues.apache.org/jira/browse/IGNITE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-6374:
Component/s: wizards
> Web Console SQL doesn't work with 2.2.0 RC1
> ---
>
> Key: IGNITE-6374
> URL: https://issues.apache.org/jira/browse/IGNITE-6374
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Affects Versions: 2.2
>Reporter: Denis Magda
>Assignee: Pavel Konstantinov
>Priority: Blocker
> Labels: important
> Fix For: 2.3
>
>
> Start a couple of nodes using 2.2.0-rc1 binary bundle:
> {code}
> ./ignite.sh ../examples/config/example-ignite.xml
> {code}
> Preload data using SQLLine tool and the SQL script as described here:
> https://github.com/dmagda/ignite_world_demo
> Go to Web Console SQL tab and send the simplest query possible:
> {code}
> select * from city
> {code}
> To get the exception like that:
> {code}
> [14:42:33,440][SEVERE][rest-#54%null%][GridTaskCommandHandler] Failed to
> execute task [name=o.a.i.i.v.compute.VisorGatewayTask, clientId=null]
> class org.apache.ignite.IgniteCheckedException: Failed to find constructor
> for task argument
> [taskName=org.apache.ignite.internal.visor.query.VisorQueryTask, argsCnt=8,
> args=[SQL_PUBLIC_CITY, select * from city, false, false, false, false, 100,
> false]]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7229)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:257)
> at
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsync(GridTaskCommandHandler.java:163)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:268)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:91)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:157)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to find
> constructor for task argument
> [taskName=org.apache.ignite.internal.visor.query.VisorQueryTask, argsCnt=8,
> args=[SQL_PUBLIC_CITY, select * from city, false, false, false, false, 100,
> false]]
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:400)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6608)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1115)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1385)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:640)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:749)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskPro
[jira] [Updated] (IGNITE-6822) IgfsMapReduceExample raise exception in multi nodes run
[
https://issues.apache.org/jira/browse/IGNITE-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-6822:
Attachment: example.log
grid.o.a.i.e.igfs.IgfsNodeStartup.1.log
grid.o.a.i.e.igfs.IgfsNodeStartup.2.log
grid.o.a.i.e.igfs.IgfsNodeStartup.3.log
> IgfsMapReduceExample raise exception in multi nodes run
> ---
>
> Key: IGNITE-6822
> URL: https://issues.apache.org/jira/browse/IGNITE-6822
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
>Reporter: Aleksey Chetaev
>Priority: Minor
> Attachments: example.log, grid.o.a.i.e.igfs.IgfsNodeStartup.1.log,
> grid.o.a.i.e.igfs.IgfsNodeStartup.2.log,
> grid.o.a.i.e.igfs.IgfsNodeStartup.3.log
>
>
> All logs in attachments.
> Exception:
> {code:java}
> class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
> interrupted
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7538)
> at
> org.apache.ignite.internal.MarshallerMappingFileStore.fileLock(MarshallerMappingFileStore.java:254)
> at
> org.apache.ignite.internal.MarshallerMappingFileStore.writeMapping(MarshallerMappingFileStore.java:95)
> at
> org.apache.ignite.internal.MappingStoreTask.run(MappingStoreTask.java:57)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6687)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6822) IgfsMapReduceExample raise exception in multi nodes run
Aleksey Chetaev created IGNITE-6822:
---
Summary: IgfsMapReduceExample raise exception in multi nodes run
Key: IGNITE-6822
URL: https://issues.apache.org/jira/browse/IGNITE-6822
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Reporter: Aleksey Chetaev
Priority: Minor
All logs in attachments.
Exception:
{code:java}
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7538)
at
org.apache.ignite.internal.MarshallerMappingFileStore.fileLock(MarshallerMappingFileStore.java:254)
at
org.apache.ignite.internal.MarshallerMappingFileStore.writeMapping(MarshallerMappingFileStore.java:95)
at org.apache.ignite.internal.MappingStoreTask.run(MappingStoreTask.java:57)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6687)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5739) JVM crash on node deactivation
[ https://issues.apache.org/jira/browse/IGNITE-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5739: Issue Type: Bug (was: Task) > JVM crash on node deactivation > -- > > Key: IGNITE-5739 > URL: https://issues.apache.org/jira/browse/IGNITE-5739 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Alexey Kuznetsov >Assignee: Alexey Goncharuk > Fix For: 2.3 > > Attachments: hs_err_pid16076.log, ignite-c43368bb.log > > > Start one node (with persistence). > Activate > Deactivate - node crashed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-2670) Add ability to perfom mass operations
[ https://issues.apache.org/jira/browse/IGNITE-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-2670: Description: Such ability will be useful in case when user wants to change the same property for example to several (10) caches.(was: Such ability will be useful in case when user wants to change the same property for example to several (10) caches.) > Add ability to perfom mass operations > - > > Key: IGNITE-2670 > URL: https://issues.apache.org/jira/browse/IGNITE-2670 > Project: Ignite > Issue Type: Task >Reporter: Pavel Konstantinov > > Such ability will be useful in case when user wants to change the same > property for example to several (10) caches. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5899) Thin client: cache.Get for primitives
[
https://issues.apache.org/jira/browse/IGNITE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5899:
Description:
Implement {{cache.Get}} for primitive data types via thin client protocol.
This will include:
* New client type in {{SqlListenerNioListener}}
* {{PlatformRequestHandler implements SqlListenerRequestHandler}},
{{PlatformMessageParser implements SqlListenerMessageParser}}
* Integration test in .NET (just because .NET is the first platform to adopt
this; we could do tests in Java as well, but this is redundant for now)
Support only primitive types for now to avoid dealing with bynary type
metadata, schemas, compact footers, etc.
was:
Implement {{cache.Get}} for primitive data types via thin client protocol.
This will include:
* New client type in {{SqlListenerNioListener}}
* {{PlatformRequestHandler implements SqlListenerRequestHandler}},
{{PlatformMessageParser implements SqlListenerMessageParser}}
* Integration test in .NET (just because .NET is the first platform to adopt
this; we could do tests in Java as well, but this is redundant for now)
Support only primitive types for now to avoid dealing with bynary type
metadata, schemas, compact footers, etc.
> Thin client: cache.Get for primitives
> -
>
> Key: IGNITE-5899
> URL: https://issues.apache.org/jira/browse/IGNITE-5899
> Project: Ignite
> Issue Type: Task
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> Implement {{cache.Get}} for primitive data types via thin client protocol.
> This will include:
> * New client type in {{SqlListenerNioListener}}
> * {{PlatformRequestHandler implements SqlListenerRequestHandler}},
> {{PlatformMessageParser implements SqlListenerMessageParser}}
> * Integration test in .NET (just because .NET is the first platform to adopt
> this; we could do tests in Java as well, but this is redundant for now)
> Support only primitive types for now to avoid dealing with bynary type
> metadata, schemas, compact footers, etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5899) Thin client: cache.Get for primitives
[
https://issues.apache.org/jira/browse/IGNITE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5899:
Description:
Implement {{cache.Get}} for primitive data types via thin client protocol.
This will include:
* New client type in {{SqlListenerNioListener}}
* {{PlatformRequestHandler implements SqlListenerRequestHandler}},
{{PlatformMessageParser implements SqlListenerMessageParser}}
* Integration test in .NET (just because .NET is the first platform to adopt
this; we could do tests in Java as well, but this is redundant for now)
Support only primitive types for now to avoid dealing with bynary type
metadata, schemas, compact footers, etc.
was:
Implement {{cache.Get}} for primitive data types via thin client protocol.
This will include:
* New client type in {{SqlListenerNioListener}}
* {{PlatformRequestHandler implements SqlListenerRequestHandler}},
{{PlatformMessageParser implements SqlListenerMessageParser}}
* Integration test in .NET (just because .NET is the first platform to adopt
this; we could do tests in Java as well, but this is redundant for now)
Support only primitive types for now to avoid dealing with bynary type
metadata, schemas, compact footers, etc.
> Thin client: cache.Get for primitives
> -
>
> Key: IGNITE-5899
> URL: https://issues.apache.org/jira/browse/IGNITE-5899
> Project: Ignite
> Issue Type: Task
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> Implement {{cache.Get}} for primitive data types via thin client protocol.
> This will include:
> * New client type in {{SqlListenerNioListener}}
> * {{PlatformRequestHandler implements SqlListenerRequestHandler}},
> {{PlatformMessageParser implements SqlListenerMessageParser}}
> * Integration test in .NET (just because .NET is the first platform to adopt
> this; we could do tests in Java as well, but this is redundant for now)
> Support only primitive types for now to avoid dealing with bynary type
> metadata, schemas, compact footers, etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6479) IndexOutOfBoundsException jdbc2
[
https://issues.apache.org/jira/browse/IGNITE-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-6479:
Description:
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
was:
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
> IndexOutOfBoundsException jdbc2
> ---
>
> Key: IGNITE-6479
> URL: https://issues.apache.org/jira/browse/IGNITE-6479
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
> Fix For: 2.3
>
>
> I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
> {noformat}
> when I tried to get list of tables I got exception:
> {noformat}
> 0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
> java.lang.IndexOutOfBoundsException: Index: 0
> at java.util.Collections$EmptyList.get(Collections.java:4454)
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
> at sqlline.Rows.isPrimaryKey(Rows.java:68)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
> at sqlline.TableOutputFormat.print(TableOutpu
[jira] [Updated] (IGNITE-5817) Change checksum calculation methods
[ https://issues.apache.org/jira/browse/IGNITE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5817: Issue Type: Task (was: Bug) > Change checksum calculation methods > --- > > Key: IGNITE-5817 > URL: https://issues.apache.org/jira/browse/IGNITE-5817 > Project: Ignite > Issue Type: Task >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin >Priority: Blocker > Fix For: 2.3 > > > Neither sha1 nor md5 are trustful checksum calculation methods. We should be > switching to at least sha265 or higher. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6210) Inefficient memory consumption for checkpoint buffer
[
https://issues.apache.org/jira/browse/IGNITE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-6210:
Summary: Inefficient memory consumption for checkpoint buffer (was:
inefficient memory consumption for checkpoint buffer)
> Inefficient memory consumption for checkpoint buffer
>
>
> Key: IGNITE-6210
> URL: https://issues.apache.org/jira/browse/IGNITE-6210
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.3
>
>
> Current implementation allows configure checkpoint buffer size in
> PersistentStoreConfiguration, but checkpoint buffer will be created for each
> memory configuration with size equals the one indicated in
> PersistentStoreConfiguration.
> For example:
> {code}
> PersistentStoreConfiguration prCfg = new
> PersistentStoreConfiguration();
> prCfg.setCheckpointingFrequency(5L * 1024L * 1024L * 1024L); // 5GB.
> MemoryConfiguration memCfg = new MemoryConfiguration();
> MemoryPolicyConfiguration pl1 = new MemoryPolicyConfiguration();
> pl1.setMaxSize(100L * 1024L * 1024L); // 100 Mb.
> MemoryPolicyConfiguration pl2 = new MemoryPolicyConfiguration();
> pl2.setMaxSize(10L * 1024L * 1024L * 1024L); // 10GB.
> memCfg.setMemoryPolicies(pl1, pl2);
> {code}
> pl1(max size 10Gb) will be have checkpoint buffer = 5GB and pl2(max size
> 100Mb) buffer= 5GB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-4591) File interop_target.h is missing from source-release
[
https://issues.apache.org/jira/browse/IGNITE-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-4591:
Labels: cpp (was: )
> File interop_target.h is missing from source-release
>
>
> Key: IGNITE-4591
> URL: https://issues.apache.org/jira/browse/IGNITE-4591
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Igor Sapego
> Labels: cpp
> Fix For: 2.2
>
>
> File
> {{modules\platforms\cpp\core\include\ignite\impl\interop\interop_target.h}}
> missing from source releases of versions 1.7.0 and 1.8.0. It is present,
> however, in repository and binary releases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152407#comment-16152407 ] Aleksey Chetaev commented on IGNITE-5355: - [~ntikhonov] * I changed org.json to com.googlecode.json-simple. org.json license don't support by apache license policy. * I tried to fix all style issues. * Change code to use StringBuffer * This don't need to have test, because it's not part of Ignite Node, it's tools needed for release process changes. > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- 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 ] Aleksey Chetaev updated IGNITE-6243: Summary: RazorSQL crash on try edit, describe and another actions with table. (was: RazorSQL crashed on try edit, describe and another actions with table.) > 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 > > 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] [Created] (IGNITE-6243) RazorSQL crashed on try edit, describe and another actions with table.
Aleksey Chetaev created IGNITE-6243: --- Summary: RazorSQL crashed 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 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] [Updated] (IGNITE-5337) CPP: linux examples: names of executable files should be the same type
[ https://issues.apache.org/jira/browse/IGNITE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5337: Description: C++ linux examples: make executable file names the same type: ignate--example now names are: ignite-continuous-query-example ignite-odbcexample ignite-putgetexample ignite-queryexample was: C++ linux examples: make executable file names the same type: ignate--example now names are: ignite-continuous-query-example ignite-odbcexample ignite-putgetexample ignite-queryexample > CPP: linux examples: names of executable files should be the same type > -- > > Key: IGNITE-5337 > URL: https://issues.apache.org/jira/browse/IGNITE-5337 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Irina Zaporozhtseva >Assignee: Igor Sapego >Priority: Minor > Labels: cpp, examples > Fix For: 2.1 > > > C++ linux examples: make executable file names the same type: > ignate--example > now names are: > ignite-continuous-query-example > ignite-odbcexample > ignite-putgetexample > ignite-queryexample -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4720) Sporadically fails for Hadoop
[ https://issues.apache.org/jira/browse/IGNITE-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-4720: Description: hadoop example aggregatewordcount under apache ignite hadoop edition grid with 4 nodes for hadoop-2_6_4 and hadoop-2_7_2: aggregatewordcount returns 999712 instead of 100 was: hadoop example aggregatewordcount under apache ignite hadoop edition grid with 4 nodes for hadoop-2_6_4 and hadoop-2_7_2: aggregatewordcount returns 999712 instead of 100 > Sporadically fails for Hadoop > - > > Key: IGNITE-4720 > URL: https://issues.apache.org/jira/browse/IGNITE-4720 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: 1.8 >Reporter: Irina Zaporozhtseva >Assignee: Ivan Veselovsky > Fix For: 1.9 > > > hadoop example aggregatewordcount under apache ignite hadoop edition grid > with 4 nodes for hadoop-2_6_4 and hadoop-2_7_2: > aggregatewordcount returns 999712 instead of 100 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4898) Add path to ODBC driver installers to platforms\cpp\odbc\README.txt
[ https://issues.apache.org/jira/browse/IGNITE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-4898: Description: Add path to ODBC driver installers (/cpp/bin/odbc/) to platforms\cpp\odbc\README.txt: "There are two ways to install ODBC driver currently. The first one is to use 32-bit or 64-bit installer. This is the most simple way and you are recommended to stick to it by default." was: Add path to ODBC driver installers (/cpp/bin/odbc/) to platforms\cpp\odbc\README.txt: "There are two ways to install ODBC driver currently. The first one is to use 32-bit or 64-bit installer. This is the most simple way and you are recommended to stick to it by default." > Add path to ODBC driver installers to platforms\cpp\odbc\README.txt > --- > > Key: IGNITE-4898 > URL: https://issues.apache.org/jira/browse/IGNITE-4898 > Project: Ignite > Issue Type: Bug > Components: documentation, platforms >Reporter: Irina Zaporozhtseva >Assignee: Denis Magda > Fix For: 2.0 > > > Add path to ODBC driver installers (/cpp/bin/odbc/) to > platforms\cpp\odbc\README.txt: > "There are two ways to install ODBC driver currently. The first one is to use > 32-bit or 64-bit installer. This is the most simple way and you are > recommended to stick to it by default." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5506) Datagrid.StoreExample fails when run with standalone Apache Ignite.NET node
[
https://issues.apache.org/jira/browse/IGNITE-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5506:
Description:
{{Datagrid.StoreExample}} fails when run with standalone Apache Ignite.NET node
{code}
Apache.Ignite.Core.Cache.CacheException was unhandled
HResult=-2146233088
Message=class org.apache.ignite.IgniteCheckedException: Could not load file
or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467,
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies.
The system cannot find the file specified.
Source=Apache.Ignite.Core
StackTrace:
at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32
stackTraceCharsLen, Void* errData, Int32 errDataLen)
at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.TargetInLongOutLong(Void*
ctx, Void* target, Int32 opType, Int64 val)
at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInLongOutLong(IUnmanagedTarget
target, Int32 opType, Int64 memPtr)
at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Clear()
at Apache.Ignite.Examples.Datagrid.StoreExample.Main() in
C:\work\gridgain-professional-fabric-2.1.1.b3_23\platforms\dotnet\examples\Apache.Ignite.Examples\Datagrid\StoreExample.cs:line
67
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[]
args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:
HResult=-2146233088
Message=Could not load file or assembly 'Apache.Ignite.ExamplesDll,
Version=1.0.6375.29467, Culture=neutral, PublicKeyToken=c27524977cb332ce' or
one of its dependencies. The system cannot find the file specified.
InnerException:
HResult=-2146233088
JavaClassName=javax.cache.CacheException
JavaMessage=class org.apache.ignite.IgniteCheckedException: Could
not load file or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467,
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies.
The system cannot find the file specified.
Message=javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Could not load file or assembly
'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467, Culture=neutral,
PublicKeyToken=c27524977cb332ce' or one of its dependencies. The system cannot
find the file specified.
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1323)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2629)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.clear(IgniteCacheProxy.java:2049)
at
org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInLongOutLong(PlatformCache.java:1088)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inLongOutLong(PlatformTargetProxyImpl.java:53)
Caused by: class org.apache.ignite.IgniteCheckedException: Could not load file
or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467,
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies.
The system cannot find the file specified.
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7229)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:166)
at
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.clearLocally(GridCacheProxyImpl.java:974)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$GlobalClearAllJob.localExecute(GridCacheAdapter.java:5142)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6099)
at
org.apache.ignite.internal.proc
[jira] [Updated] (IGNITE-5898) .NET: Datagrid.QueryDmlExample: Incorrect result if run example with standalone Apache Ignite.NET node
[
https://issues.apache.org/jira/browse/IGNITE-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5898:
Description:
{{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone
Apache Ignite.NET node
without standalone node:
{code}
>>> Inserted data
>>> 1: John Doe, ASF, 4000
>>> 2: Jane Roe, ASF, 5000
>>> 3: Mary Major, Eclipse, 2000
>>> 4: Richard Miles, Eclipse, 3000
>>> Update salary for ASF employees
>>> 1: John Doe, ASF, 4400
>>> 2: Jane Roe, ASF, 5500
>>> 3: Mary Major, Eclipse, 2000
>>> 4: Richard Miles, Eclipse, 3000
>>> Delete non-ASF employees
>>> 1: John Doe, ASF, 4400
>>> 2: Jane Roe, ASF, 5500
{code}
with standalone node:
{code}
>>> Inserted data
>>> 1: John Doe, ASF, 4000
>>> 3: Mary Major, Eclipse, 2000
>>> Update salary for ASF employees
>>> 1: John Doe, ASF, 4400
>>> 3: Mary Major, Eclipse, 2000
>>> Delete non-ASF employees
>>> 1: John Doe, ASF, 4400
{code}
was:
{{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone
Apache Ignite.NET node
without standalone node:
{code}
>>> Inserted data
>>> 1: John Doe, ASF, 4000
>>> 2: Jane Roe, ASF, 5000
>>> 3: Mary Major, Eclipse, 2000
>>> 4: Richard Miles, Eclipse, 3000
>>> Update salary for ASF employees
>>> 1: John Doe, ASF, 4400
>>> 2: Jane Roe, ASF, 5500
>>> 3: Mary Major, Eclipse, 2000
>>> 4: Richard Miles, Eclipse, 3000
>>> Delete non-ASF employees
>>> 1: John Doe, ASF, 4400
>>> 2: Jane Roe, ASF, 5500
{code}
with standalone node:
{code}
>>> Inserted data
>>> 1: John Doe, ASF, 4000
>>> 3: Mary Major, Eclipse, 2000
>>> Update salary for ASF employees
>>> 1: John Doe, ASF, 4400
>>> 3: Mary Major, Eclipse, 2000
>>> Delete non-ASF employees
>>> 1: John Doe, ASF, 4400
{code}
> .NET: Datagrid.QueryDmlExample: Incorrect result if run example with
> standalone Apache Ignite.NET node
> ---
>
> Key: IGNITE-5898
> URL: https://issues.apache.org/jira/browse/IGNITE-5898
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.9, 2.1
>Reporter: Irina Zaporozhtseva
>Priority: Minor
> Labels: .NET
>
> {{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone
> Apache Ignite.NET node
> without standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 2: Jane Roe, ASF, 5000
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> {code}
> with standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 3: Mary Major, Eclipse, 2000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 3: Mary Major, Eclipse, 2000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution
[
https://issues.apache.org/jira/browse/IGNITE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5919:
Description:
EntryProcessorExample closes immediately after execution. Please, add:
Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit ...");
Console.ReadKey();
was:
EntryProcessorExample closes immediately after execution. Please, add:
Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit ...");
Console.ReadKey();
> .NET: EntryProcessorExample closes immediately after execution
> --
>
> Key: IGNITE-5919
> URL: https://issues.apache.org/jira/browse/IGNITE-5919
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Priority: Minor
> Labels: .NET
>
> EntryProcessorExample closes immediately after execution. Please, add:
> Console.WriteLine();
> Console.WriteLine(">>> Example finished, press any key to exit ...");
> Console.ReadKey();
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5525) C++ ODBC example fails
[ https://issues.apache.org/jira/browse/IGNITE-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5525: Description: C++ ODBC example fails: >>> Cache ODBC example started. [15:12:08,620][SEVERE][sql-connector-#38%null%][OdbcRequestHandler] Failed to execute SQL query [reqId=1, req=OdbcQueryExecuteRequest [schema=PUBLIC, sqlQry=INSERT INTO Person (_key, orgId, firstName, lastName, resume, salary) VALUES (?, ?, ?, ?, ?, ?)�, args=[1, 1, John, Doe, Master Degree., 2200.0]]] class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: INSERT INTO Person (_key, orgId, firstName, lastName, resume, salary) VALUES (?, ?, ?, ?, ?, ?) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1293) at org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856) at org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852) at org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36) at org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293) at org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860) at org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler.executeQuery(OdbcRequestHandler.java:177) at org.apache.ignite.internal.processors.odbc.odbc.OdbcRequestHandler.handle(OdbcRequestHandler.java:116) at org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152) at org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44) at org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279) at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109) at org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70) 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) Caused by: org.h2.jdbc.JdbcSQLException: Table "PERSON" not found; SQL statement: INSERT INTO Person (_key, orgId, firstName, lastName, resume, salary) VALUES (?, ?, ?, ?, ?, ?) [42102-195] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:179) at org.h2.message.DbException.get(DbException.java:155) at org.h2.command.Parser.readTableOrView(Parser.java:5506) at org.h2.command.Parser.readTableOrView(Parser.java:5483) at org.h2.command.Parser.parseInsert(Parser.java:1056) at org.h2.command.Parser.parsePrepared(Parser.java:416) at org.h2.command.Parser.parse(Parser.java:320) at org.h2.command.Parser.parse(Parser.java:292) at org.h2.command.Parser.prepareCommand(Parser.java:257) at org.h2.engine.Session.prepareLocal(Session.java:573) at org.h2.engine.Session.prepareCommand(Session.java:514) at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204) at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73) at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:288) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:398) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1273) ... 17 more An error occurred: Failed to execute prepared statement: HY000: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: INSERT INTO Person (_key, orgId, firstName, lastName, resume, salary) VALUES (?, ?, ?, ?, ?, ?) >>> Example finished, press 'Enter' to exit ... was: C++ ODBC example fails: >>> Cache ODBC example started. [15:12:08,620][SEVERE][sql-connector-#38%null%][OdbcRequestHandler] Failed to execute SQL query [reqId=1, req=OdbcQueryExecuteRequest [schema=PUBLIC, sqlQry=INSERT INTO Person (_key, orgId, firstName, lastName, resume, salary) VALUES (?, ?, ?, ?, ?, ?)�, args=[1, 1, John, Doe, Master Degree., 2200.0]]] class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: INSERT INTO Pers
[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
]
Aleksey Chetaev updated IGNITE-6157:
Description:
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}
was:
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}
> 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++
>
> 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.]
>
[jira] [Updated] (IGNITE-6189) Benchmarks for check LFS used disk space
[ https://issues.apache.org/jira/browse/IGNITE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6189: Description: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. Step: how often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. was: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. Step: how often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. > Benchmarks for check LFS used disk space > > > Key: IGNITE-6189 > URL: https://issues.apache.org/jira/browse/IGNITE-6189 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Chetaev >Assignee: Oleg Ostanin > > Need to create new benchmarks for test how many space we use for store n keys > in LFS. > Benchmark should content arguments: > 1. Range of entries which will be put. > 2. Step: how often we show store size. > Case for e.x. params (range 1_000_000, step 100_000): > 1. Put 100_000 entries, save time for put > 2. Wait for checkpoint finished on all nodes. > 3. Calc db size on each server. > 4. Write size and time to benchmarks results. > ... > 6. Repeat first 4 steps while entries count in cache less that 1_000_000. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6189) Benchmarks for check LFS used disk space
[ https://issues.apache.org/jira/browse/IGNITE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6189: Description: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. Step: how often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. was: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. Step: how often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. > Benchmarks for check LFS used disk space > > > Key: IGNITE-6189 > URL: https://issues.apache.org/jira/browse/IGNITE-6189 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Chetaev >Assignee: Oleg Ostanin > > Need to create new benchmarks for test how many space we use for store n keys > in LFS. > Benchmark should content arguments: > 1. Range of entries which will be put. > 2. Step: how often we show store size. > Case for e.x. params (range 1_000_000, step 100_000): > 1. Put 100_000 entries, save time for put > 2. Wait for checkpoint finished on all nodes. > 3. Calc db size on each server. > 4. Write size and time to benchmarks results. > ... > 6. Repeat first 4 steps while entries count in cache less that 1_000_000. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6189) Benchmarks for check LFS used disk space
[ https://issues.apache.org/jira/browse/IGNITE-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6189: Description: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. Step: how often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. was: Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. How often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. > Benchmarks for check LFS used disk space > > > Key: IGNITE-6189 > URL: https://issues.apache.org/jira/browse/IGNITE-6189 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Chetaev > > Need to create new benchmarks for test how many space we use for store n keys > in LFS. > Benchmark should content arguments: > 1. Range of entries which will be put. > 2. Step: how often we show store size. > Case for e.x. params (range 1_000_000, step 100_000): > 1. Put 100_000 entries, save time for put > 2. Wait for checkpoint finished on all nodes. > 3. Calc db size on each server. > 4. Write size and time to benchmarks results. > ... > 6. Repeat first 4 steps while entries count in cache less that 1_000_000. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6189) Benchmarks for check LFS used disk space
Aleksey Chetaev created IGNITE-6189: --- Summary: Benchmarks for check LFS used disk space Key: IGNITE-6189 URL: https://issues.apache.org/jira/browse/IGNITE-6189 Project: Ignite Issue Type: Improvement Reporter: Aleksey Chetaev Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. How often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[ https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5273: Description: Improvements already made for linked ticket need to be ported on .NET side. (was: Improvements already made for linked ticket need to be ported on .NET side.) > .NET: MemoryMetrics API improvements to be ported to .NET > - > > Key: IGNITE-5273 > URL: https://issues.apache.org/jira/browse/IGNITE-5273 > Project: Ignite > Issue Type: Task > Components: general, platforms >Reporter: Sergey Chugunov >Assignee: Pavel Tupitsyn > Labels: .NET, important > Fix For: 2.1 > > > Improvements already made for linked ticket need to be ported on .NET side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6139) JDBC driver should return actual values for get*Version()
[ https://issues.apache.org/jira/browse/IGNITE-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6139: Description: Right now it returns: Database version 1.0 (suggested - actual version from server nodes) JDBC version 1.0 (suggested - 4.1, that's what's in Java 7) Driver version 1.0 (suggested - actual version of running Ignite code) Database product name is "Ignite Cache", probably keep that. was: Right now it returns: Database version 1.0 (suggested - actual version from server nodes) JDBC version 1.0 (suggested - 4.1, that's what's in Java 7) Driver version 1.0 (suggested - actual version of running Ignite code) Database product name is "Ignite Cache", probably keep that. > JDBC driver should return actual values for get*Version() > - > > Key: IGNITE-6139 > URL: https://issues.apache.org/jira/browse/IGNITE-6139 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev > > Right now it returns: > Database version 1.0 (suggested - actual version from server nodes) > JDBC version 1.0 (suggested - 4.1, that's what's in Java 7) > Driver version 1.0 (suggested - actual version of running Ignite code) > Database product name is "Ignite Cache", probably keep that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6108) Hangs in streamer when using store
[ https://issues.apache.org/jira/browse/IGNITE-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6108: Description: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named "logs_without memory_policy". * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. was: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named: * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. > Hangs in streamer when using store > -- > > Key: IGNITE-6108 > URL: https://issues.apache.org/jira/browse/IGNITE-6108 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Attachments: logs_without memory_policy.zip, > log_with_memory_policy.zip > > > I have hangs in IgniteStreamer benchmarks when using store with WAL mode > different from NONE. > Configuration: 1 client 4 servers.Cache mode: transaction. Range > 400_000_000. > Problems: > * Time for next 100_000_000 entries every is always greater than for the > previous one. > * We can found hangs for greater that 1 minutes in drivers logs for example > 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". > Time for every 100_000_000 in seconds in log named "logs_without > memory_policy". > * 100_000_000 = 209 > * 200_000_000 = 323 > * 300_000_000 = 547 > * 400_000_000 = 722 > Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6108) Hangs in streamer when using store
[ https://issues.apache.org/jira/browse/IGNITE-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6108: Description: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs. E.x. 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named "logs_without memory_policy". * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. was: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named "logs_without memory_policy". * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. > Hangs in streamer when using store > -- > > Key: IGNITE-6108 > URL: https://issues.apache.org/jira/browse/IGNITE-6108 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Attachments: logs_without memory_policy.zip, > log_with_memory_policy.zip > > > I have hangs in IgniteStreamer benchmarks when using store with WAL mode > different from NONE. > Configuration: 1 client 4 servers.Cache mode: transaction. Range > 400_000_000. > Problems: > * Time for next 100_000_000 entries every is always greater than for the > previous one. > * We can found hangs for greater that 1 minutes in drivers logs. E.x. > 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". > Time for every 100_000_000 in seconds in log named "logs_without > memory_policy". > * 100_000_000 = 209 > * 200_000_000 = 323 > * 300_000_000 = 547 > * 400_000_000 = 722 > Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6108) Hangs in streamer when using store
[ https://issues.apache.org/jira/browse/IGNITE-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6108: Description: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named: * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. was: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Yardstick logs in attachments. > Hangs in streamer when using store > -- > > Key: IGNITE-6108 > URL: https://issues.apache.org/jira/browse/IGNITE-6108 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Attachments: logs_without memory_policy.zip, > log_with_memory_policy.zip > > > I have hangs in IgniteStreamer benchmarks when using store with WAL mode > different from NONE. > Configuration: 1 client 4 servers.Cache mode: transaction. Range > 400_000_000. > Problems: > * Time for next 100_000_000 entries every is always greater than for the > previous one. > * We can found hangs for greater that 1 minutes in drivers logs for example > 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". > Time for every 100_000_000 in seconds in log named: > * 100_000_000 = 209 > * 200_000_000 = 323 > * 300_000_000 = 547 > * 400_000_000 = 722 > Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6108) Hangs in streamer when using store
[ https://issues.apache.org/jira/browse/IGNITE-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-6108: Attachment: log_with_memory_policy.zip logs_without memory_policy.zip > Hangs in streamer when using store > -- > > Key: IGNITE-6108 > URL: https://issues.apache.org/jira/browse/IGNITE-6108 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Attachments: logs_without memory_policy.zip, > log_with_memory_policy.zip > > > I have hangs in IgniteStreamer benchmarks when using store with WAL mode > different from NONE. > Configuration: 1 client 4 servers.Cache mode: transaction. Range > 400_000_000. > Problems: > * Time for next 100_000_000 entries every is always greater than for the > previous one. > * We can found hangs for greater that 1 minutes in drivers logs for example > 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". > Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6108) Hangs in streamer when using store
Aleksey Chetaev created IGNITE-6108: --- Summary: Hangs in streamer when using store Key: IGNITE-6108 URL: https://issues.apache.org/jira/browse/IGNITE-6108 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Aleksey Chetaev Priority: Critical I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid
[ https://issues.apache.org/jira/browse/IGNITE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5920: Summary: CacheClientBinaryQueryExample return different results if we add nodes to grid (was: CacheClientBinaryQueryExample return different results if we add non local node) > CacheClientBinaryQueryExample return different results if we add nodes to grid > -- > > Key: IGNITE-5920 > URL: https://issues.apache.org/jira/browse/IGNITE-5920 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Chetaev > > 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> > Employees working for GridGain" isn't empty. > 2. Start 3 node and after that start example. section ">>> Employees working > for GridGain" is empty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add non local node
Aleksey Chetaev created IGNITE-5920: --- Summary: CacheClientBinaryQueryExample return different results if we add non local node Key: IGNITE-5920 URL: https://issues.apache.org/jira/browse/IGNITE-5920 Project: Ignite Issue Type: Bug Reporter: Aleksey Chetaev 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> Employees working for GridGain" isn't empty. 2. Start 3 node and after that start example. section ">>> Employees working for GridGain" is empty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-1084: Labels: 1 Muted_test (was: Muted_test) > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.1 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-1084: Labels: Muted_test (was: 1 Muted_test) > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.1 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
[ https://issues.apache.org/jira/browse/IGNITE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042449#comment-16042449 ] Aleksey Chetaev commented on IGNITE-5434: - [~vozerov] Full logs in attachments. > Yardstick sql benchmarks broken on Ignite-5267 branch > - > > Key: IGNITE-5434 > URL: https://issues.apache.org/jira/browse/IGNITE-5434 > Project: Ignite > Issue Type: Bug > Components: sql, yardstick >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Labels: important > Fix For: 2.1 > > Attachments: IGNITE-5434.zip > > > Yardstick benchmarks: > * sql-query > * sql-query-join > * sql-query-put > broken in Ignite-5267 branch, in master all ok. > Exception: > <00:39:22> Starting warmup. > > > > > Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] > > > > > ERROR: Shutting down benchmark driver to unexpected exception. > > > > > Type '--help' for usage. > > > > > javax.cache.CacheException: class > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM > "query"."Person" WHERE salary >= ? and salary <= ? > > > at > org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) > > > > at > org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) > > > > at > org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) > > > > at > org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) > > > > > at java.lang.Thread.run(Thread.java:745) > > > > > Caused by: class > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM > "query"."Person" WHERE salary >= ? and salary <= ? > > > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) >
[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
[ https://issues.apache.org/jira/browse/IGNITE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5434: Attachment: IGNITE-5434.zip > Yardstick sql benchmarks broken on Ignite-5267 branch > - > > Key: IGNITE-5434 > URL: https://issues.apache.org/jira/browse/IGNITE-5434 > Project: Ignite > Issue Type: Bug > Components: sql, yardstick >Affects Versions: 2.1 >Reporter: Aleksey Chetaev >Priority: Critical > Labels: important > Fix For: 2.1 > > Attachments: IGNITE-5434.zip > > > Yardstick benchmarks: > * sql-query > * sql-query-join > * sql-query-put > broken in Ignite-5267 branch, in master all ok. > Exception: > <00:39:22> Starting warmup. > > > > > Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] > > > > > ERROR: Shutting down benchmark driver to unexpected exception. > > > > > Type '--help' for usage. > > > > > javax.cache.CacheException: class > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM > "query"."Person" WHERE salary >= ? and salary <= ? > > > at > org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) > > > > at > org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) > > > > at > org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) > > > > at > org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) > > > > > at java.lang.Thread.run(Thread.java:745) > > > > > Caused by: class > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM > "query"."Person" WHERE salary >= ? and salary <= ? > > > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) > >
[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
[ https://issues.apache.org/jira/browse/IGNITE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5434: Description: Yardstick benchmarks: * sql-query * sql-query-join * sql-query-put broken in Ignite-5267 branch, in master all ok. Exception: <00:39:22> Starting warmup. Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] ERROR: Shutting down benchmark driver to unexpected exception. Type '--help' for usage. javax.cache.CacheException: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196) at org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)
[jira] [Created] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
Aleksey Chetaev created IGNITE-5434: --- Summary: Yardstick sql benchmarks broken on Ignite-5267 branch Key: IGNITE-5434 URL: https://issues.apache.org/jira/browse/IGNITE-5434 Project: Ignite Issue Type: Bug Components: sql, yardstick Affects Versions: 2.1 Reporter: Aleksey Chetaev Priority: Critical Yardstick benchmarks: *sql-query *sql-query-join *sql-query-put broken in Ignite-5267 branch, in master all ok. Exception: <00:39:22> Starting warmup. Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] ERROR: Shutting down benchmark driver to unexpected exception. Type '--help' for usage. javax.cache.CacheException: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196)
[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
[ https://issues.apache.org/jira/browse/IGNITE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5434: Description: Yardstick benchmarks: * sql-query * sql-query-join * sql-query-put broken in Ignite-5267 branch, in master all ok. Exception: <00:39:22> Starting warmup. Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] ERROR: Shutting down benchmark driver to unexpected exception. Type '--help' for usage. javax.cache.CacheException: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196) at org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)
[jira] [Updated] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
[ https://issues.apache.org/jira/browse/IGNITE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5434: Description: Yardstick benchmarks: * sql-query * sql-query-join * sql-query-put broken in Ignite-5267 branch, in master all ok. Exception: <00:39:22> Starting warmup. Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] ERROR: Shutting down benchmark driver to unexpected exception. Type '--help' for usage. javax.cache.CacheException: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSql(IgniteH2Indexing.java:1196) at org.apache.ignite.internal.processors.query.GridQueryProcessor$8.applyx(GridQueryProcessor.java:1947)
[jira] [Updated] (IGNITE-5208) CPP: Segfault on Put
[
https://issues.apache.org/jira/browse/IGNITE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5208:
Summary: CPP: Segfault on Put (was: C++ Segfault on Put)
> CPP: Segfault on Put
>
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
> Labels: c++, cpp
> Fix For: 2.1
>
>
> The following segfault happens when:
> - using multiple caches (suffixed with number as in X_\{number\}),
> - caches contain same type of object but not the same objects,
> - doing multithreaded `::Put` operation, only one put is done on each cache
> concurrently, independent caches (X_1, X_2, ...) can be operated on and
> called `::Put` on concurrently, but that should not be relevant as cache api
> is thread safe.
> {code:none}
> C [test+0xf8116a] std::less::operator()(int const&, int const&)
> const+0x14
> C [test+0x1106305] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::_M_lower_bound(std::_Rb_tree_node ignite::common::concurrent::SharedPointer
> > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C [test+0x1105a9d] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x45
> C [test+0x1104e7f] std::map ignite::common::concurrent::SharedPointer,
> std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x23
> C [test+0x1104031]
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)+0x6f
> C [test+0xe6de2d] void
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject
> >(std::shared_ptr const&)+0xbb
> C [test+0xe6cd48]
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C [test+0x1128cf1]
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C [test+0x1128f67] ignite::impl::interop::InteropTarget::OutOp(int,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C [test+0x1125f41]
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&,
> ignite::IgniteError&)+0x2d
> C [test+0xe5539a] ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr
> >::Put(std::__cxx11::basic_string,
> std::allocator > const&, std::shared_ptr const&,
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4 0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at
> src/impl/binary/binary_type_manager.cpp:56
> 56 std::map::iterator it =
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5273) .NET: MemoryMetrics API improvements to be ported to .NET
[ https://issues.apache.org/jira/browse/IGNITE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5273: Labels: .NET important (was: important) > .NET: MemoryMetrics API improvements to be ported to .NET > - > > Key: IGNITE-5273 > URL: https://issues.apache.org/jira/browse/IGNITE-5273 > Project: Ignite > Issue Type: Task > Components: general, platforms >Reporter: Sergey Chugunov >Assignee: Pavel Tupitsyn > Labels: .NET, important > Fix For: 2.1 > > > Improvements already made for linked ticket need to be ported on .NET side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5337) CPP: linux examples: names of executable files should be the same type
[ https://issues.apache.org/jira/browse/IGNITE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5337: Summary: CPP: linux examples: names of executable files should be the same type (was: C++ linux examples: names of executable files should be the same type) > CPP: linux examples: names of executable files should be the same type > -- > > Key: IGNITE-5337 > URL: https://issues.apache.org/jira/browse/IGNITE-5337 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.0 >Reporter: Irina Zaporozhtseva >Assignee: Igor Sapego >Priority: Minor > Labels: cpp, examples > Fix For: 2.1 > > > C++ linux examples: make executable file names the same type: > ignate--example > now names are: > ignite-continuous-query-example > ignite-odbcexample > ignite-putgetexample > ignite-queryexample -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5208) C++ Segfault on Put
[
https://issues.apache.org/jira/browse/IGNITE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5208:
Labels: c++ cpp (was: c++)
> C++ Segfault on Put
> ---
>
> Key: IGNITE-5208
> URL: https://issues.apache.org/jira/browse/IGNITE-5208
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.0
>Reporter: Tolga HOŞGÖR
>Assignee: Igor Sapego
>Priority: Critical
> Labels: c++, cpp
> Fix For: 2.1
>
>
> The following segfault happens when:
> - using multiple caches (suffixed with number as in X_\{number\}),
> - caches contain same type of object but not the same objects,
> - doing multithreaded `::Put` operation, only one put is done on each cache
> concurrently, independent caches (X_1, X_2, ...) can be operated on and
> called `::Put` on concurrently, but that should not be relevant as cache api
> is thread safe.
> {code:none}
> C [test+0xf8116a] std::less::operator()(int const&, int const&)
> const+0x14
> C [test+0x1106305] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::_M_lower_bound(std::_Rb_tree_node ignite::common::concurrent::SharedPointer
> > >*, std::_Rb_tree_node_base*, int const&)+0x41
> C [test+0x1105a9d] std::_Rb_tree ignite::common::concurrent::SharedPointer
> >, std::_Select1st ignite::common::concurrent::SharedPointer
> > >, std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x45
> C [test+0x1104e7f] std::map ignite::common::concurrent::SharedPointer,
> std::less, std::allocator ignite::common::concurrent::SharedPointer
> > > >::find(int const&)+0x23
> C [test+0x1104031]
> ignite::impl::binary::BinaryTypeManager::GetHandler(std::__cxx11::basic_string std::char_traits, std::allocator > const&, int)+0x6f
> C [test+0xe6de2d] void
> ignite::impl::binary::BinaryWriterImpl::WriteTopObject
> >(std::shared_ptr const&)+0xbb
> C [test+0xe6cd48]
> ignite::impl::In2Operation std::char_traits, std::allocator >, std::shared_ptr
> >::ProcessInput(ignite::impl::binary::BinaryWriterImpl&)+0x3e
> C [test+0x1128cf1]
> ignite::impl::interop::InteropTarget::WriteTo(ignite::impl::interop::InteropMemory*,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0xa9
> C [test+0x1128f67] ignite::impl::interop::InteropTarget::OutOp(int,
> ignite::impl::InputOperation&, ignite::IgniteError&)+0x65
> C [test+0x1125f41]
> ignite::impl::cache::CacheImpl::Put(ignite::impl::InputOperation&,
> ignite::IgniteError&)+0x2d
> C [test+0xe5539a] ignite::cache::Cache std::char_traits, std::allocator >, std::shared_ptr
> >::Put(std::__cxx11::basic_string,
> std::allocator > const&, std::shared_ptr const&,
> ignite::IgniteError&)+0x52
> {code}
> There seems to be some kind of race situation:
> {code:none}
> 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x= reading variable>, __y=@0x7fff80846e04: 2066246303) at
> /usr/include/c++/6.3.1/bits/stl_function.h:386
> {code}
> {code:none}
> #4 0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler
> (this=0x1a560d0, typeName="test.data", typeId=2066246303) at
> src/impl/binary/binary_type_manager.cpp:56
> 56 std::map::iterator it =
> snapshots0.find(typeId);
> (gdb) print snapshots0
> $10 = std::map with 42286576 elements = {[42312864] = {ptr = 0x285a4a0, impl
> = 0x0}...}
> (gdb) print snapshot
> $11 = {ptr = 0x7fffda4f, impl = 0x11}
> {code}
> `impl` pointers seems to be corrupted on multiple places.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5315) .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll)
[ https://issues.apache.org/jira/browse/IGNITE-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5315: Labels: .NET (was: ) > .NET: Failing query tests due to IGNITE-5287 (sqlEscapeAll) > --- > > Key: IGNITE-5315 > URL: https://issues.apache.org/jira/browse/IGNITE-5315 > Project: Ignite > Issue Type: Task > Components: platforms, sql >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > Changes introduced in IGNITE-5287 caused multiple failures in .NET suites. > Need to investigate why and fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5160) C++ Continuous Queries example has to demonstrate the filter usage
[ https://issues.apache.org/jira/browse/IGNITE-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5160: Labels: cpp important (was: important) > C++ Continuous Queries example has to demonstrate the filter usage > -- > > Key: IGNITE-5160 > URL: https://issues.apache.org/jira/browse/IGNITE-5160 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, important > Fix For: 2.1 > > > The existing continuous queries example [1] has to be extended to the usage > of a remote filter explained here [2]. > [1] > https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/continuous-query-example/src/continuous_query_example.cpp > [2] > https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5160) CPP: Continuous Queries example has to demonstrate the filter usage
[ https://issues.apache.org/jira/browse/IGNITE-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5160: Summary: CPP: Continuous Queries example has to demonstrate the filter usage (was: C++ Continuous Queries example has to demonstrate the filter usage) > CPP: Continuous Queries example has to demonstrate the filter usage > --- > > Key: IGNITE-5160 > URL: https://issues.apache.org/jira/browse/IGNITE-5160 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda >Assignee: Igor Sapego > Labels: cpp, important > Fix For: 2.1 > > > The existing continuous queries example [1] has to be extended to the usage > of a remote filter explained here [2]. > [1] > https://github.com/apache/ignite/blob/master/modules/platforms/cpp/examples/continuous-query-example/src/continuous_query_example.cpp > [2] > https://apacheignite-cpp.readme.io/docs/continuous-queries#section-remote-filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5154) CPP: Add remote filter to continuous queries C++ example.
[ https://issues.apache.org/jira/browse/IGNITE-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5154: Labels: cpp important (was: important) > CPP: Add remote filter to continuous queries C++ example. > - > > Key: IGNITE-5154 > URL: https://issues.apache.org/jira/browse/IGNITE-5154 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.9 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: cpp, important > Fix For: 2.1 > > > As we have added support for the remote filters for Ignite C++ (IGNITE-3575), > we now need to modify continuous queries C++ example by adding remote filter > to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-5135) .NET: Improve remote error propagation
[
https://issues.apache.org/jira/browse/IGNITE-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5135:
Labels: .NET (was: )
> .NET: Improve remote error propagation
> --
>
> Key: IGNITE-5135
> URL: https://issues.apache.org/jira/browse/IGNITE-5135
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.1
>
>
> When we rethrow remote exceptions, we should wrap them in another exception
> to preserve remote stack traces.
> For example, {{ComputeAbstractClosureTask.OnResult}} uses {{throw err}},
> where {{err}} is a deserialized remote exception. This call causes remote
> stack trace loss.
> Instead we should do {{throw new IgniteException("Remote computation failed",
> err)}} which will preserve remote stack trace.
> Same should be done for other remote invocation scenarios (event listeners
> and so on).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup
[
https://issues.apache.org/jira/browse/IGNITE-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-5001:
Labels: .net (was: )
> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Labels: .net
> Fix For: 2.1
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)
> * Replace try-catch with {{Assert.Throws}} where possible
> * Make sure {{Ignition.StopAll}} is present where needed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev updated IGNITE-5355: Fix Version/s: (was: 2.1) > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5355) Create task with release tools
[ https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Chetaev reassigned IGNITE-5355: --- Assignee: Aleksey Chetaev > Create task with release tools > -- > > Key: IGNITE-5355 > URL: https://issues.apache.org/jira/browse/IGNITE-5355 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Chetaev >Assignee: Aleksey Chetaev > > 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5355) Create task with release tools
Aleksey Chetaev created IGNITE-5355: --- Summary: Create task with release tools Key: IGNITE-5355 URL: https://issues.apache.org/jira/browse/IGNITE-5355 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Chetaev Fix For: 2.1 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
