[jira] [Commented] (IGNITE-10959) Memory leaks in continuous query handlers
[ https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155617#comment-17155617 ] Maxim Muzafarov commented on IGNITE-10959: -- [~alex_pl] Thank you for the review. I've merged changes to the master branch. I'll cherry-pick changes to the 2.9 branch at the beginning of the next week. > Memory leaks in continuous query handlers > - > > Key: IGNITE-10959 > URL: https://issues.apache.org/jira/browse/IGNITE-10959 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Denis Mekhanikov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.9 > > Attachments: CacheContinuousQueryMemoryUsageTest.java, > CacheContinuousQueryMemoryUsageTest.result, > CacheContinuousQueryMemoryUsageTest2.java, > Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt, > Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt, > Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt, > continuousquery_leak_profile.png, referencepath.PNG > > Time Spent: 4.5h > Remaining Estimate: 0h > > Continuous query handlers don't clear internal data structures after cache > events are processed. > A test, that reproduces the problem, is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-13244: --- Attachment: tx_commit_partition_loss.patch > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Attachments: tx_commit_partition_loss.patch > > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-13244: --- Description: Reproducer is attached. Steps: 1) Run startNode() 2) Run poorTransaction() in a separate JVM 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint 4) kill -9 first node while hanging on breakpoint 5) Result: tx.commit() succeeds, data is commited in partition 1 and not commited in partition 2 > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
Sergey Uttsel created IGNITE-13244: -- Summary: Transaction commit completes successfully if partition is lost on commit phase Key: IGNITE-13244 URL: https://issues.apache.org/jira/browse/IGNITE-13244 Project: Ignite Issue Type: Bug Reporter: Sergey Uttsel Assignee: Sergey Uttsel -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13243) Add tests for commands to manage metadata
[ https://issues.apache.org/jira/browse/IGNITE-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov resolved IGNITE-13243. --- Resolution: Invalid > Add tests for commands to manage metadata > - > > Key: IGNITE-13243 > URL: https://issues.apache.org/jira/browse/IGNITE-13243 > Project: Ignite > Issue Type: Test > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13243) Add tests for commands to manage metadata
[ https://issues.apache.org/jira/browse/IGNITE-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-13243: -- Description: (was: Adds tests for commands to manage metadata (see GG-29247)) > Add tests for commands to manage metadata > - > > Key: IGNITE-13243 > URL: https://issues.apache.org/jira/browse/IGNITE-13243 > Project: Ignite > Issue Type: Test > Components: sql >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13243) Add tests for commands to manage metadata
Taras Ledkov created IGNITE-13243: - Summary: Add tests for commands to manage metadata Key: IGNITE-13243 URL: https://issues.apache.org/jira/browse/IGNITE-13243 Project: Ignite Issue Type: Test Components: sql Reporter: Taras Ledkov Assignee: Taras Ledkov Adds tests for commands to manage metadata (see GG-29247) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155452#comment-17155452
]
Aleksey Plekhanov commented on IGNITE-13219:
[~ilyak], I think it's very fragile. Log4j uses the current value for system
property, but not initialization-time value.
Here is reproducer:
{code:java}
Ignite ignite1 = Ignition.start(new
IgniteConfiguration().setIgniteInstanceName("ignite1")
.setGridLogger(new Log4J2Logger("config/ignite-log4j2.xml")));
Ignite ignite2 = Ignition.start(new
IgniteConfiguration().setIgniteInstanceName("ignite2")
.setGridLogger(new Log4J2Logger("config/ignite-log4j2.xml")));
System.setProperty("nodeId", "test");
{code}
After ignite2 starts both nodes start writing to the same log, after
setProperty they both start writing to ignite-test.log.
> Slf4jLogger does not implement the LoggerNodeIdAware interface.
> ---
>
> Key: IGNITE-13219
> URL: https://issues.apache.org/jira/browse/IGNITE-13219
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the scenario of ignite + slf4j + log4j2, the generated log file is named
> ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger
> does not implement the
> LoggerNodeIdAware interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155269#comment-17155269
]
Aleksey Plekhanov edited comment on IGNITE-13219 at 7/10/20, 12:50 PM:
---
[~liyuj], thanks for the clarification. But there is no such default
configuration, where {{Slf4jLogger}} and {{config/ignite-log4j2.xml}} used
together. {{config/ignite-log4j2.xml}} only supposed to be used together with
{{Log4J2Logger}}.
was (Author: alex_pl):
[~liyuj], thanks for the clarification. But there is no such default
configuration, where {{Slf4jLogger}} and {{config/ignite-log4j2.xml}} used
together. {{config/ignite-log4j2.xml }}only supposed to be used together with
{{Log4J2Logger.}}
> Slf4jLogger does not implement the LoggerNodeIdAware interface.
> ---
>
> Key: IGNITE-13219
> URL: https://issues.apache.org/jira/browse/IGNITE-13219
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the scenario of ignite + slf4j + log4j2, the generated log file is named
> ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger
> does not implement the
> LoggerNodeIdAware interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13242) LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal fails
[ https://issues.apache.org/jira/browse/IGNITE-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155373#comment-17155373 ] Ivan Bessonov commented on IGNITE-13242: [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds2=buildTypeStatusDiv_IgniteTests24Java8=pull%2F8021%2Fhead] > LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal > fails > > > Key: IGNITE-13242 > URL: https://issues.apache.org/jira/browse/IGNITE-13242 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5966400795288779246=testDetails] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12307) Data types coverage for basic cache operations.
[
https://issues.apache.org/jira/browse/IGNITE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155345#comment-17155345
]
Ignite TC Bot commented on IGNITE-12307:
{panel:title=Branch: [pull/8015/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5453828]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = PRIMARY] - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8015/head] Base: [master] : New Tests
(1534)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Queries 2{color} [tests 210]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBigIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBinaryDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testTimestampDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBooleanDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDateDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testTinyIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testVarcharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDecimalDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testCharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testUUIDDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
... and 199 tests blockers
{color:#8b}Cache 9{color} [tests 364]
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testDoubleDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testStringDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testListDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC,
[jira] [Commented] (IGNITE-13174) C++: Add Windows support to CMake build system
[ https://issues.apache.org/jira/browse/IGNITE-13174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155340#comment-17155340 ] Ivan Daschinskiy commented on IGNITE-13174: --- [~isapego] [~alex_pl] I added patch, that supports cmake build on windows. Based on [Igor Sapego's work|https://github.com/apache/ignite/pull/7899/files]. What tested: # Debug and release build on VS 2017 # Tests completes successfully, including ODBC # Examples build and run successfully. I think that we can proceed with TC job. > C++: Add Windows support to CMake build system > -- > > Key: IGNITE-13174 > URL: https://issues.apache.org/jira/browse/IGNITE-13174 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.8.1 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Ticket IGNITE-13078 adds CMake build system support, but only for Linux. Need > make sure it works on Windows and create TC job for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12307) Data types coverage for basic cache operations.
[
https://issues.apache.org/jira/browse/IGNITE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155334#comment-17155334
]
Ignite TC Bot commented on IGNITE-12307:
{panel:title=Branch: [pull/8015/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5453828]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = PRIMARY] - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8015/head] Base: [master] : New Tests
(1534)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Queries 2{color} [tests 210]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBigIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBinaryDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testTimestampDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testBooleanDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDateDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#8b}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testTinyIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
FAILED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testVarcharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDecimalDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testCharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testUUIDDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=PRIMARY_SYNC, persistenceEnabled=false]
- PASSED{color}
... and 199 tests blockers
{color:#8b}Cache 9{color} [tests 364]
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testDoubleDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testStringDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testListDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC,
[jira] [Commented] (IGNITE-12320) Partial index rebuild fails in case indexed cache contains different datatypes
[
https://issues.apache.org/jira/browse/IGNITE-12320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155331#comment-17155331
]
Ignite TC Bot commented on IGNITE-12320:
{panel:title=Branch: [pull/8018/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8018/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [tests 2]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridIndexRebuildTest.testFullIndexRebuild - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridIndexRebuildTest.testPartialIndexRebuild - PASSED{color}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=f16bd9d4-ed63-4f28-bc1b-05a8d47a9a08, topVer=0,
nodeId8=ff9da309, msg=, type=NODE_JOINED, tstamp=1594359367176],
val2=AffinityTopologyVersion [topVer=-1438383085710073976, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=f16bd9d4-ed63-4f28-bc1b-05a8d47a9a08, topVer=0,
nodeId8=ff9da309, msg=, type=NODE_JOINED, tstamp=1594359367176],
val2=AffinityTopologyVersion [topVer=-1438383085710073976, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=c0649373371-c1b8883b-305b-4ccf-bbef-03e9870b06c1, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=67b811c6-4fc9-4f07-9b1d-2a3e5e5a616d, topVer=0, nodeId8=67b811c6,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594359367176]],
val2=AffinityTopologyVersion [topVer=-4967737502895895441, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=c0649373371-c1b8883b-305b-4ccf-bbef-03e9870b06c1, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=67b811c6-4fc9-4f07-9b1d-2a3e5e5a616d, topVer=0, nodeId8=67b811c6,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594359367176]],
val2=AffinityTopologyVersion [topVer=-4967737502895895441, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ce841eaf-10ad-4438-bd72-d7e37ab1177b, topVer=0,
nodeId8=2b694a03, msg=, type=NODE_JOINED, tstamp=1594366561737],
val2=AffinityTopologyVersion [topVer=-4796038760796845363, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=ce841eaf-10ad-4438-bd72-d7e37ab1177b, topVer=0,
nodeId8=2b694a03, msg=, type=NODE_JOINED, tstamp=1594366561737],
val2=AffinityTopologyVersion [topVer=-4796038760796845363, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=dcd07a73371-451d891c-75dd-47b2-aaea-36cd33070fb3, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=d6a9fe29-2fd7-4731-94d7-2687c3116260, topVer=0, nodeId8=d6a9fe29,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594366561737]],
val2=AffinityTopologyVersion [topVer=-1498921354376565740, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=dcd07a73371-451d891c-75dd-47b2-aaea-36cd33070fb3, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=d6a9fe29-2fd7-4731-94d7-2687c3116260, topVer=0, nodeId8=d6a9fe29,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594366561737]],
val2=AffinityTopologyVersion [topVer=-1498921354376565740, minorTopVer=0]]] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5453818buildTypeId=IgniteTests24Java8_RunAll]
> Partial index rebuild fails in case indexed cache contains different datatypes
> --
>
> Key: IGNITE-12320
> URL: https://issues.apache.org/jira/browse/IGNITE-12320
>
[jira] [Updated] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag
[ https://issues.apache.org/jira/browse/IGNITE-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-13185: - Fix Version/s: (was: 2.10) 2.9 > API to change Cluster Tag and notify about change of Cluster Tag > > > Key: IGNITE-13185 > URL: https://issues.apache.org/jira/browse/IGNITE-13185 > Project: Ignite > Issue Type: Improvement > Components: general, UI, visor >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.9 > > Time Spent: 40m > Remaining Estimate: 0h > > IGNITE-12111 introduced new feature to identify and distinguish different > clusters. > To make the feature more usable we need new command in CLI interface to > change Cluster Tag and new event to subscribe for changes of Cluster Tag. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag
[ https://issues.apache.org/jira/browse/IGNITE-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155321#comment-17155321 ] Ilya Kasnacheev commented on IGNITE-13185: -- I have cherry-picked this ticket to 2.9. > API to change Cluster Tag and notify about change of Cluster Tag > > > Key: IGNITE-13185 > URL: https://issues.apache.org/jira/browse/IGNITE-13185 > Project: Ignite > Issue Type: Improvement > Components: general, UI, visor >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.9 > > Time Spent: 40m > Remaining Estimate: 0h > > IGNITE-12111 introduced new feature to identify and distinguish different > clusters. > To make the feature more usable we need new command in CLI interface to > change Cluster Tag and new event to subscribe for changes of Cluster Tag. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13242) LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal fails
Ivan Bessonov created IGNITE-13242: -- Summary: LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal fails Key: IGNITE-13242 URL: https://issues.apache.org/jira/browse/IGNITE-13242 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5966400795288779246=testDetails] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155272#comment-17155272
]
Ilya Kasnacheev commented on IGNITE-13219:
--
Actually, I think it may make sense to do System.setProperty(NODE_ID,
U.id8(nodeId)); before initialization of logger, un-set this variable
afterwards. This will allow nodes which have different nodeId's but brought up
sequentially to configure their loggers properly [~alex_pl]
> Slf4jLogger does not implement the LoggerNodeIdAware interface.
> ---
>
> Key: IGNITE-13219
> URL: https://issues.apache.org/jira/browse/IGNITE-13219
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the scenario of ignite + slf4j + log4j2, the generated log file is named
> ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger
> does not implement the
> LoggerNodeIdAware interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13241) Get rid of Externalizable implementation for GridCacheAdapter
Alexey Goncharuk created IGNITE-13241: - Summary: Get rid of Externalizable implementation for GridCacheAdapter Key: IGNITE-13241 URL: https://issues.apache.org/jira/browse/IGNITE-13241 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk The cache implementation must not be serialized. For convenience, only user cache proxies support serialization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.
[
https://issues.apache.org/jira/browse/IGNITE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155269#comment-17155269
]
Aleksey Plekhanov commented on IGNITE-13219:
[~liyuj], thanks for the clarification. But there is no such default
configuration, where {{Slf4jLogger}} and {{config/ignite-log4j2.xml}} used
together. {{config/ignite-log4j2.xml }}only supposed to be used together with
{{Log4J2Logger.}}
> Slf4jLogger does not implement the LoggerNodeIdAware interface.
> ---
>
> Key: IGNITE-13219
> URL: https://issues.apache.org/jira/browse/IGNITE-13219
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the scenario of ignite + slf4j + log4j2, the generated log file is named
> ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger
> does not implement the
> LoggerNodeIdAware interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13240) JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION)
Chris Paraskeva created IGNITE-13240: Summary: JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION) Key: IGNITE-13240 URL: https://issues.apache.org/jira/browse/IGNITE-13240 Project: Ignite Issue Type: Bug Affects Versions: 2.8.1 Environment: OS: Windows 10 JRE version: Java(TM) SE Runtime Environment (11.0.5+10) (build 11.0.5+10-LTS) Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.5+10-LTS, mixed mode, tiered, compressed oops, g1 gc, windows-amd64) Reporter: Chris Paraskeva After some time of Apache Ignite is up & running using a sinle .NET Core node is crashing because of JAVA EXCEPTION_ACCESS_VIOLATION -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13228) Remote filter of IgniteEvents has to run with appropriate SecurityContext.
[
https://issues.apache.org/jira/browse/IGNITE-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155266#comment-17155266
]
Ignite TC Bot commented on IGNITE-13228:
{panel:title=Branch: [pull/8017/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8017/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=e0f54b5d-c576-4c0e-b600-3a7f501c7c69, topVer=0,
nodeId8=e4f9ecac, msg=, type=NODE_JOINED, tstamp=1594308984071],
val2=AffinityTopologyVersion [topVer=2466450831247344215, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=e0f54b5d-c576-4c0e-b600-3a7f501c7c69, topVer=0,
nodeId8=e4f9ecac, msg=, type=NODE_JOINED, tstamp=1594308984071],
val2=AffinityTopologyVersion [topVer=2466450831247344215, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=b0d78343371-81d7ddb5-d660-4812-888a-cac10a49ad0d, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=10f0a788-650c-4228-8a35-0dbbb5c0f5c1, topVer=0, nodeId8=10f0a788,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594308984071]],
val2=AffinityTopologyVersion [topVer=643918341653304699, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=b0d78343371-81d7ddb5-d660-4812-888a-cac10a49ad0d, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=10f0a788-650c-4228-8a35-0dbbb5c0f5c1, topVer=0, nodeId8=10f0a788,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594308984071]],
val2=AffinityTopologyVersion [topVer=643918341653304699, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=dea51943-0b93-4f87-b1f9-b494cf59aa13, topVer=0,
nodeId8=479013e2, msg=, type=NODE_JOINED, tstamp=1594309010355],
val2=AffinityTopologyVersion [topVer=-2607821228467649868, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=fe233443371-cdc3e128-fc79-4f77-ae8f-2fb2c5a79327, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=81566c9b-87c7-4449-81a9-740feb6e369f, topVer=0, nodeId8=81566c9b,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594309010355]],
val2=AffinityTopologyVersion [topVer=-3812830869319035847, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=fe233443371-cdc3e128-fc79-4f77-ae8f-2fb2c5a79327, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=81566c9b-87c7-4449-81a9-740feb6e369f, topVer=0, nodeId8=81566c9b,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594309010355]],
val2=AffinityTopologyVersion [topVer=-3812830869319035847, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=dea51943-0b93-4f87-b1f9-b494cf59aa13, topVer=0,
nodeId8=479013e2, msg=, type=NODE_JOINED, tstamp=1594309010355],
val2=AffinityTopologyVersion [topVer=-2607821228467649868, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Security{color} [tests 2]
* {color:#013220}SecurityTestSuite:
EventsRemoteSecurityContextCheckTest.testRemoteListen - PASSED{color}
* {color:#013220}SecurityTestSuite:
EventsRemoteSecurityContextCheckTest.testRemoteListenAsync - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5452153buildTypeId=IgniteTests24Java8_RunAll]
> Remote filter of IgniteEvents has to run with appropriate SecurityContext.
> --
>
> Key: IGNITE-13228
> URL: https://issues.apache.org/jira/browse/IGNITE-13228
> Project: Ignite
>
[jira] [Updated] (IGNITE-13218) System view walker generator wrong sorts imports
[
https://issues.apache.org/jira/browse/IGNITE-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-13218:
-
Priority: Trivial (was: Major)
> System view walker generator wrong sorts imports
>
>
> Key: IGNITE-13218
> URL: https://issues.apache.org/jira/browse/IGNITE-13218
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Priority: Trivial
> Labels: newbie
>
> {{SystemViewRowAttributeWalkerGenerator}} wrong sorts imports.
> 1. Run SystemViewRowAttributeWalkerGenerator
> 2. Run check codestyle to obtain the error:
> {noformat}
> ComputeJobViewWalker.java:23: Wrong lexicographical order for
> 'org.apache.ignite.spi.systemview.view.ComputeJobView' import. Should be
> before
> 'org.apache.ignite.spi.systemview.view.ComputeJobView.ComputeJobState'.
> [CustomImportOrder]
> Audit done.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13237) In some cases IgniteClient#query does not fire CacheQueryExecutedEvent
[
https://issues.apache.org/jira/browse/IGNITE-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-13237:
Description:
{{CacheQueryExecutedEvent}} fires for all query types (Scan, SQL) but in some
SQL cases (ddl queries, updates and commands) {{IgniteClient#query}} does not .
Reproducer:
{code:java|title=IgniteCacheAbstractQuerySelfTest.java}
@Test
public void testClientSqlQueryEvents() throws Exception {
CountDownLatch execLatch = new CountDownLatch(9);
IgnitePredicate lsnr = evt -> {
assert evt instanceof CacheQueryExecutedEvent;
System.out.println(">>> EVENT: " + evt);
CacheQueryExecutedEvent qe = (CacheQueryExecutedEvent)evt;
assertEquals("SQL_PUBLIC_TEST_TABLE", qe.cacheName());
assertNotNull(qe.clause());
assertNull(qe.scanQueryFilter());
assertNull(qe.continuousQueryFilter());
execLatch.countDown();
return true;
};
ignite().events().localListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
ClientConfiguration cc = new
ClientConfiguration().setAddresses(Config.SERVER);
try (IgniteClient client = Ignition.startClient(cc)) {
client.query(new SqlFieldsQuery("create table TEST_TABLE(key int
primary key, val int)"))
.getAll();
client.query(new SqlFieldsQuery("insert into TEST_TABLE values (?,
?)").setArgs(1, 1))
.getAll();
client.query(new SqlFieldsQuery("update TEST_TABLE set val = ?2 where
key = ?1").setArgs(1, 2))
.getAll();
client.query(new SqlFieldsQuery("select * from TEST_TABLE"))
.getAll();
client.query(new SqlFieldsQuery("create index idx_1 on
TEST_TABLE(key)"))
.getAll();
client.query(new SqlFieldsQuery("drop index idx_1"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE add column val2
int"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE drop val2"))
.getAll();
client.query(new SqlFieldsQuery("drop table TEST_TABLE"))
.getAll();
assertTrue(execLatch.await(3_000, MILLISECONDS));
}
finally {
ignite().events().stopLocalListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
}
}
{code}
was:
In some cases (ddl queries, updates and commands) {{IgniteClient#query}} does
not fire {{CacheQueryExecutedEvent}}.
Reproducer:
{code:java|title=IgniteCacheAbstractQuerySelfTest.java}
@Test
public void testClientSqlQueryEvents() throws Exception {
CountDownLatch execLatch = new CountDownLatch(9);
IgnitePredicate lsnr = evt -> {
assert evt instanceof CacheQueryExecutedEvent;
System.out.println(">>> EVENT: " + evt);
CacheQueryExecutedEvent qe = (CacheQueryExecutedEvent)evt;
assertEquals("SQL_PUBLIC_TEST_TABLE", qe.cacheName());
assertNotNull(qe.clause());
assertNull(qe.scanQueryFilter());
assertNull(qe.continuousQueryFilter());
execLatch.countDown();
return true;
};
ignite().events().localListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
ClientConfiguration cc = new
ClientConfiguration().setAddresses(Config.SERVER);
try (IgniteClient client = Ignition.startClient(cc)) {
client.query(new SqlFieldsQuery("create table TEST_TABLE(key int
primary key, val int)"))
.getAll();
client.query(new SqlFieldsQuery("insert into TEST_TABLE values (?,
?)").setArgs(1, 1))
.getAll();
client.query(new SqlFieldsQuery("update TEST_TABLE set val = ?2 where
key = ?1").setArgs(1, 2))
.getAll();
client.query(new SqlFieldsQuery("select * from TEST_TABLE"))
.getAll();
client.query(new SqlFieldsQuery("create index idx_1 on
TEST_TABLE(key)"))
.getAll();
client.query(new SqlFieldsQuery("drop index idx_1"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE add column val2
int"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE drop val2"))
.getAll();
client.query(new SqlFieldsQuery("drop table TEST_TABLE"))
.getAll();
assertTrue(execLatch.await(3_000, MILLISECONDS));
}
finally {
ignite().events().stopLocalListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
}
}
{code}
> In some cases IgniteClient#query does not fire CacheQueryExecutedEvent
> --
>
> Key: IGNITE-13237
> URL: https://issues.apache.org/jira/browse/IGNITE-13237
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
>
[jira] [Resolved] (IGNITE-12321) Rebalance doesn't happen after restart if node failed at the moment of rebalance.
[ https://issues.apache.org/jira/browse/IGNITE-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin resolved IGNITE-12321. -- Resolution: Won't Fix Will be implemented as part of [IGNITE-13003|https://issues.apache.org/jira/browse/IGNITE-13003] > Rebalance doesn't happen after restart if node failed at the moment of > rebalance. > - > > Key: IGNITE-12321 > URL: https://issues.apache.org/jira/browse/IGNITE-12321 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Steps to reproduce: > 1. Start 2 nodes in baseline > 2. Stream a lot of data. > 3. Stop the second node, clean the persistence and start it again(with the > same consistent id > 4. Kill the first node at the moment of rebalancing (make sure that not all > data was rebalanced) > 5. Partition loss will be detected. > 6. Return first node to the cluster. > 7. Result: > Data is not rebalanced, All data(primary and backup) is stored on the first > node only, while the second node has the same small subset of the data. It's > reproducible with any Partition loss policy. Resetting lost partitions, > activation/deactivation doesn't help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13237) In some cases IgniteClient#query does not fire CacheQueryExecutedEvent
[
https://issues.apache.org/jira/browse/IGNITE-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-13237:
Description:
In some cases (ddl queries, updates and commands) {{IgniteClient#query}} does
not fire {{CacheQueryExecutedEvent}}.
Reproducer:
{code:java|title=IgniteCacheAbstractQuerySelfTest.java}
@Test
public void testClientSqlQueryEvents() throws Exception {
CountDownLatch execLatch = new CountDownLatch(9);
IgnitePredicate lsnr = evt -> {
assert evt instanceof CacheQueryExecutedEvent;
System.out.println(">>> EVENT: " + evt);
CacheQueryExecutedEvent qe = (CacheQueryExecutedEvent)evt;
assertEquals("SQL_PUBLIC_TEST_TABLE", qe.cacheName());
assertNotNull(qe.clause());
assertNull(qe.scanQueryFilter());
assertNull(qe.continuousQueryFilter());
execLatch.countDown();
return true;
};
ignite().events().localListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
ClientConfiguration cc = new
ClientConfiguration().setAddresses(Config.SERVER);
try (IgniteClient client = Ignition.startClient(cc)) {
client.query(new SqlFieldsQuery("create table TEST_TABLE(key int
primary key, val int)"))
.getAll();
client.query(new SqlFieldsQuery("insert into TEST_TABLE values (?,
?)").setArgs(1, 1))
.getAll();
client.query(new SqlFieldsQuery("update TEST_TABLE set val = ?2 where
key = ?1").setArgs(1, 2))
.getAll();
client.query(new SqlFieldsQuery("select * from TEST_TABLE"))
.getAll();
client.query(new SqlFieldsQuery("create index idx_1 on
TEST_TABLE(key)"))
.getAll();
client.query(new SqlFieldsQuery("drop index idx_1"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE add column val2
int"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE drop val2"))
.getAll();
client.query(new SqlFieldsQuery("drop table TEST_TABLE"))
.getAll();
assertTrue(execLatch.await(3_000, MILLISECONDS));
}
finally {
ignite().events().stopLocalListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
}
}
{code}
was:
In some cases {{IgniteClient#query}} does not fire {{CacheQueryExecutedEvent}}.
Reproducer:
{code:java|title=IgniteCacheAbstractQuerySelfTest.java}
@Test
public void testClientSqlQueryEvents() throws Exception {
CountDownLatch execLatch = new CountDownLatch(9);
IgnitePredicate lsnr = evt -> {
assert evt instanceof CacheQueryExecutedEvent;
System.out.println(">>> EVENT: " + evt);
CacheQueryExecutedEvent qe = (CacheQueryExecutedEvent)evt;
assertEquals("SQL_PUBLIC_TEST_TABLE", qe.cacheName());
assertNotNull(qe.clause());
assertNull(qe.scanQueryFilter());
assertNull(qe.continuousQueryFilter());
execLatch.countDown();
return true;
};
ignite().events().localListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
ClientConfiguration cc = new
ClientConfiguration().setAddresses(Config.SERVER);
try (IgniteClient client = Ignition.startClient(cc)) {
client.query(new SqlFieldsQuery("create table TEST_TABLE(key int
primary key, val int)"))
.getAll();
client.query(new SqlFieldsQuery("insert into TEST_TABLE values (?,
?)").setArgs(1, 1))
.getAll();
client.query(new SqlFieldsQuery("update TEST_TABLE set val = ?2 where
key = ?1").setArgs(1, 2))
.getAll();
client.query(new SqlFieldsQuery("select * from TEST_TABLE"))
.getAll();
client.query(new SqlFieldsQuery("create index idx_1 on
TEST_TABLE(key)"))
.getAll();
client.query(new SqlFieldsQuery("drop index idx_1"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE add column val2
int"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE drop val2"))
.getAll();
client.query(new SqlFieldsQuery("drop table TEST_TABLE"))
.getAll();
assertTrue(execLatch.await(3_000, MILLISECONDS));
}
finally {
ignite().events().stopLocalListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
}
}
{code}
> In some cases IgniteClient#query does not fire CacheQueryExecutedEvent
> --
>
> Key: IGNITE-13237
> URL: https://issues.apache.org/jira/browse/IGNITE-13237
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Trivial
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In some cases (ddl queries, updates and commands) {{IgniteClient#query}} does
[jira] [Commented] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator
[
https://issues.apache.org/jira/browse/IGNITE-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155212#comment-17155212
]
Maxim Muzafarov commented on IGNITE-12930:
--
[~alex_pl]
Yes, I'll finish the review.
I think we should include this issue to 2.9 release since it fails the node in
rare cases when the TDE or Snapshot operation starts.
> DistributedProcess fails node if unable to send single message to coordinator
> -
>
> Key: IGNITE-12930
> URL: https://issues.apache.org/jira/browse/IGNITE-12930
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The
> [DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
> fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to
> send a message to the coordinator (e.g. the coordinator fails right before
> the single message is sent).
> {code:java}
> try {
> ctx.io().sendToGridTopic(p.crdId,
> GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
> }
> catch (IgniteCheckedException e) {
> log.error("Unable to send message to coordinator.", e);
> ctx.failure().process(new FailureContext(CRITICAL_ERROR,
> new Exception("Unable to send message to coordinator.",
> e)));
> }
> {code}
> h4. Expected behaviour
> If the {{ClusterTopologyCheckedException}} occurs need to wait for the
> NODE_LEFT event of the coordinator node and re-init the distributed process
> future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag
[ https://issues.apache.org/jira/browse/IGNITE-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155211#comment-17155211 ] Aleksey Plekhanov commented on IGNITE-13185: [~sergey-chugunov], I have no objections. > API to change Cluster Tag and notify about change of Cluster Tag > > > Key: IGNITE-13185 > URL: https://issues.apache.org/jira/browse/IGNITE-13185 > Project: Ignite > Issue Type: Improvement > Components: general, UI, visor >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > IGNITE-12111 introduced new feature to identify and distinguish different > clusters. > To make the feature more usable we need new command in CLI interface to > change Cluster Tag and new event to subscribe for changes of Cluster Tag. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag
[ https://issues.apache.org/jira/browse/IGNITE-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155210#comment-17155210 ] Sergey Chugunov commented on IGNITE-13185: -- [~alex_pl], I think this ticket could be cherry-picked to 2.9 branch as well as IGNITE-12111 is already there and this one improves usability of Cluster ID and Tag. What do you think? > API to change Cluster Tag and notify about change of Cluster Tag > > > Key: IGNITE-13185 > URL: https://issues.apache.org/jira/browse/IGNITE-13185 > Project: Ignite > Issue Type: Improvement > Components: general, UI, visor >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > IGNITE-12111 introduced new feature to identify and distinguish different > clusters. > To make the feature more usable we need new command in CLI interface to > change Cluster Tag and new event to subscribe for changes of Cluster Tag. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
[ https://issues.apache.org/jira/browse/IGNITE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13239: - Ignite Flags: (was: Docs Required,Release Notes Required) > Document APIs to view and change Cluster ID and Tag > --- > > Key: IGNITE-13239 > URL: https://issues.apache.org/jira/browse/IGNITE-13239 > Project: Ignite > Issue Type: Task >Reporter: Sergey Chugunov >Priority: Major > > In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and > Tag and change Tag. > These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
Sergey Chugunov created IGNITE-13239: Summary: Document APIs to view and change Cluster ID and Tag Key: IGNITE-13239 URL: https://issues.apache.org/jira/browse/IGNITE-13239 Project: Ignite Issue Type: Task Reporter: Sergey Chugunov In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and Tag and change Tag. These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155208#comment-17155208 ] Aleksey Plekhanov commented on IGNITE-12438: [~agoncharuk], "Fix version" for this ticket is 2.9, but the patch is not cherry-picked to 2.9 branch. Do you have plans to cherry-pick it? > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.9 > > Time Spent: 50m > Remaining Estimate: 0h > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13182) Document Cluster ID and Tag feature
[ https://issues.apache.org/jira/browse/IGNITE-13182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13182: - Ignite Flags: (was: Docs Required,Release Notes Required) > Document Cluster ID and Tag feature > --- > > Key: IGNITE-13182 > URL: https://issues.apache.org/jira/browse/IGNITE-13182 > Project: Ignite > Issue Type: Task >Reporter: Sergey Chugunov >Priority: Major > > IGNITE-12111 introduced new feature to identify and give a name to the > cluster: Cluster ID and Tag. > Feature in general and APIs to manage it in particular need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator
[
https://issues.apache.org/jira/browse/IGNITE-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155199#comment-17155199
]
Aleksey Plekhanov commented on IGNITE-12930:
Looks like review started, but not finished.
[~mmuzaf], do you have plans to finish the review to resolve the ticket in the
2.9 release?
> DistributedProcess fails node if unable to send single message to coordinator
> -
>
> Key: IGNITE-12930
> URL: https://issues.apache.org/jira/browse/IGNITE-12930
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The
> [DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
> fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to
> send a message to the coordinator (e.g. the coordinator fails right before
> the single message is sent).
> {code:java}
> try {
> ctx.io().sendToGridTopic(p.crdId,
> GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
> }
> catch (IgniteCheckedException e) {
> log.error("Unable to send message to coordinator.", e);
> ctx.failure().process(new FailureContext(CRITICAL_ERROR,
> new Exception("Unable to send message to coordinator.",
> e)));
> }
> {code}
> h4. Expected behaviour
> If the {{ClusterTopologyCheckedException}} occurs need to wait for the
> NODE_LEFT event of the coordinator node and re-init the distributed process
> future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12922) SqlViewMetricExporterSpi is redundant entity
[
https://issues.apache.org/jira/browse/IGNITE-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155196#comment-17155196
]
Aleksey Plekhanov commented on IGNITE-12922:
[~agura], [~nizhikov], does anyone have plans to work on this ticket to resolve
it in 2.9 release? Should we move this ticket to the next release?
> SqlViewMetricExporterSpi is redundant entity
> -
>
> Key: IGNITE-12922
> URL: https://issues.apache.org/jira/browse/IGNITE-12922
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.9
>
>
> {{SqlViewMetricExporterSpi}} is redundant entity both in terms of design and
> in terms of user experience.
> {{METRICS}} SQL view is the internal entity that could exist regardless of
> any exporters configuration. So it should be created on indexing module
> initialization. Also from an user stand point it is strange to configure
> special exporter in order to get access to the {{METRICS}} view via SQL.
> See also IGNITE-12921.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12921) System views design leads to bad user expirience.
[
https://issues.apache.org/jira/browse/IGNITE-12921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155194#comment-17155194
]
Aleksey Plekhanov commented on IGNITE-12921:
[~agura], [~nizhikov], does anyone have plans to work on this ticket to resolve
it in 2.9 release? Should we move this ticket to the next release?
> System views design leads to bad user expirience.
> -
>
> Key: IGNITE-12921
> URL: https://issues.apache.org/jira/browse/IGNITE-12921
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Andrey N. Gura
>Priority: Critical
> Labels: IEP-35
> Fix For: 2.9
>
>
> Current implementation of system views has broken system behavior which is
> related with querying system views.
> Before 2.8 system views were available via SQL queries (if indexing is
> enabled). It did not depend on any configuration.
> After implementation of IGNITE-12145 system views available only if
> {{SqlViewExporterSpi}} is passed to
> {{IgniteConfiguration.setSystemViewExporterSpi()}}. Now, if an user
> configures some {{SystemViewExporterSpi}} then provided user configuration
> will rewrite default configuration and {{SqlViewExporterSpi}} won't be
> initialized. As result it is impossible to query system views and any query
> to the views fails with exception. This behavior is not obvious for the user.
> See tests below.
> The second problem is kind of design problem. System view is internal part of
> the system and should be available regardless of any exporter configuration
> (at least via SQL) such as it was implemented before 2.8 release.
> My suggestion is the following: we should remove {{SqlViewExporterSpi}} and
> configure all views on indexing module initialization. {{SqlViewExporterSPI}}
> also doesn't make sense because:
> - it operates by some internal API ({{SchemaManager}}, {{GridKernalContext}},
> {{IgniteH2Indexing}}).
> - it doesn't allow to end user to add any new system view.
> Only thing that could be useful is a filtering. But it could be done with SQL.
> Reproducer of broken behavior:
> {code:java}
> package org.apache.ignite.internal.processors.cache.metric;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.cluster.ClusterState;
> import org.apache.ignite.configuration.DataRegionConfiguration;
> import org.apache.ignite.configuration.DataStorageConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.spi.systemview.jmx.JmxSystemViewExporterSpi;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.junit.Test;
> import java.util.HashSet;
> import java.util.List;
> import java.util.Set;
> import static java.util.Arrays.asList;
> import static
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest.queryProcessor;
> public class SystemViewTest extends GridCommonAbstractTest {
> private static boolean useDefaultSpi;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setConsistentId(igniteInstanceName);
> cfg.setDataStorageConfiguration(new DataStorageConfiguration()
> .setDataRegionConfigurations(
> new
> DataRegionConfiguration().setName("in-memory").setMaxSize(100L * 1024 * 1024))
> .setDefaultDataRegionConfiguration(
> new DataRegionConfiguration()
> .setPersistenceEnabled(true)));
> if (!useDefaultSpi) {
> // Configure user provided system view exporter SPI.
> cfg.setSystemViewExporterSpi(new JmxSystemViewExporterSpi());
> }
> return cfg;
> }
> /**
> * Will executed succefully.
> */
> @Test
> public void testSystemViewWithDefaultSpi() throws Exception {
> useDefaultSpi = true;
> doTestSystemView();
> }
> /**
> * Will fail with Table "VIEWS" not found.
> */
> @Test
> public void testSystemViewWithCustomSpi() throws Exception {
> useDefaultSpi = false;
> doTestSystemView();
> }
> private void doTestSystemView() throws Exception {
> try (IgniteEx ignite = startGrid()) {
> ignite.cluster().state(ClusterState.ACTIVE);
> Set cacheNames = new HashSet<>(asList("cache-1",
> "cache-2"));
> for (String name : cacheNames)
> ignite.getOrCreateCache(name);
> SqlFieldsQuery qry = new SqlFieldsQuery("SELECT * FROM
> SYS.VIEWS");
> List> res =
[jira] [Commented] (IGNITE-13142) SQL constraint not null added on key prevents correct inserts
[
https://issues.apache.org/jira/browse/IGNITE-13142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155193#comment-17155193
]
Aleksey Plekhanov commented on IGNITE-13142:
[~skalashnikov], looks good to me. Thanks for the contribution!
Merged to master, cherry-picked to 2.9.
> SQL constraint not null added on key prevents correct inserts
> -
>
> Key: IGNITE-13142
> URL: https://issues.apache.org/jira/browse/IGNITE-13142
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
>Priority: Major
> Fix For: 2.9
>
> Attachments: SqlNotNullKeyFielfTest.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is possible to configure {{QueryEntity}} so that subsequent inserts would
> fail.
> - lowercase {{keyFieldName}}
> - not null constraint on {{keyFieldName}}
> {code:java}
> new QueryEntity()
> .setTableName("Person")
> .setKeyFieldName("id")
> .setKeyType("java.lang.Integer")
> .setValueType("Person")
> .setFields(new LinkedHashMap<>(
> F.asMap("id", "java.lang.Integer",
> "name", "java.lang.String",
> "age", "java.lang.Integer")))
> .setNotNullFields(F.asSet("id", "name", "age"
> {code}
> The following SQL produces error: Null value is not allowed for column 'ID'
> {code}
> insert into Person (id, name, age) values (1, 'John Doe', 30)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13142) SQL constraint not null added on key prevents correct inserts
[
https://issues.apache.org/jira/browse/IGNITE-13142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155188#comment-17155188
]
Ignite TC Bot commented on IGNITE-13142:
{panel:title=Branch: [pull/7961/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7961/head] Base: [master] : New Tests
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [tests 6]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testQueryEntity[key=ID val=VAL] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testQuotedDDL[key=ID val=VAL] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testUnquotedDDL[key=ID val=VAL] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testQueryEntity[key=id val=val] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testQuotedDDL[key=id val=val] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlNotNullKeyValueFieldTest.testUnquotedDDL[key=id val=val] - PASSED{color}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=cf585f8e-97f6-4dca-9535-0329a1bfe769, topVer=0,
nodeId8=bc67cb33, msg=, type=NODE_JOINED, tstamp=1593117756068],
val2=AffinityTopologyVersion [topVer=2790516118756588940, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=cf585f8e-97f6-4dca-9535-0329a1bfe769, topVer=0,
nodeId8=bc67cb33, msg=, type=NODE_JOINED, tstamp=1593117756068],
val2=AffinityTopologyVersion [topVer=2790516118756588940, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8aac73de271-56b203db-074e-4d33-b892-7b73db6e08d6, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=e3e47a41-8897-4dfd-a2ae-094b923e9b42, topVer=0, nodeId8=e3e47a41,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1593117756068]],
val2=AffinityTopologyVersion [topVer=-4319664596444763260, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=8aac73de271-56b203db-074e-4d33-b892-7b73db6e08d6, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=e3e47a41-8897-4dfd-a2ae-094b923e9b42, topVer=0, nodeId8=e3e47a41,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1593117756068]],
val2=AffinityTopologyVersion [topVer=-4319664596444763260, minorTopVer=0]]] -
PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=953f81fa-db06-4110-a163-cab52e0eed5c, topVer=0,
nodeId8=dcaa2d32, msg=, type=NODE_JOINED, tstamp=1593117739931],
val2=AffinityTopologyVersion [topVer=-6283083835210186696, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=953f81fa-db06-4110-a163-cab52e0eed5c, topVer=0,
nodeId8=dcaa2d32, msg=, type=NODE_JOINED, tstamp=1593117739931],
val2=AffinityTopologyVersion [topVer=-6283083835210186696, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=f9b873de271-87c85835-de7d-455b-87d1-d66341f2d8db, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=baec8421-9b51-43a9-9b9d-9d3c10d2822c, topVer=0, nodeId8=baec8421,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1593117739931]],
val2=AffinityTopologyVersion [topVer=-6243374504219412140, minorTopVer=0]]] -
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=f9b873de271-87c85835-de7d-455b-87d1-d66341f2d8db, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=baec8421-9b51-43a9-9b9d-9d3c10d2822c, topVer=0, nodeId8=baec8421,
msg=null, type=DISCOVERY_CUSTOM_EVT,
[jira] [Created] (IGNITE-13238) Instant not supported whithin the scope of jdbc thin.
Alexander Lapin created IGNITE-13238:
Summary: Instant not supported whithin the scope of jdbc thin.
Key: IGNITE-13238
URL: https://issues.apache.org/jira/browse/IGNITE-13238
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.9
Reporter: Alexander Lapin
Reproducer:
org.apache.ignite.jdbc.thin.JdbcThinCacheToJdbcDataTypesCoverageTest#testInstantDataType
{code:java}
[2020-07-10
09:12:36,183][ERROR][client-connector-#196%thin.JdbcThinCacheToJdbcDataTypesCoverageTest0%][JdbcRequestHandler]
Failed to execute SQL query [reqId=11, req=JdbcQueryExecuteRequest
[schemaName=cachebb4b3282_3ad0_4ee3_9959_806c33521406, pageSize=1024,
maxRows=0, sqlQry=SELECT * FROM tablebb4b3282_3ad0_4ee3_9959_806c33521406 WHERE
_key = ?, args=Object[] [-292275055-05-16T16:47:04.192Z],
stmtType=SELECT_STATEMENT_TYPE, autoCommit=true, partResReq=false,
super=JdbcRequest [type=2, reqId=11]]]
javax.cache.CacheException: Failed to calculate derived partitions for query.
at
org.apache.ignite.internal.sql.optimizer.affinity.PartitionResult.calculatePartitions(PartitionResult.java:132)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelectDistributed(IgniteH2Indexing.java:1682)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelect0(IgniteH2Indexing.java:1412)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelect(IgniteH2Indexing.java:1291)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1128)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2779)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2775)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:3338)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$2(GridQueryProcessor.java:2795)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2833)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2769)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2727)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:647)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:320)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:257)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:200)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:54)
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:120)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
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)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to wrap
value[type=24, value=-292275055-05-16T16:47:04.192Z]
at
org.apache.ignite.internal.processors.query.h2.H2Utils.wrap(H2Utils.java:668)
at
org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:520)
at
org.apache.ignite.internal.processors.query.h2.affinity.H2PartitionResolver.partition(H2PartitionResolver.java:43)
at
org.apache.ignite.internal.sql.optimizer.affinity.PartitionParameterNode.applySingle(PartitionParameterNode.java:72)
at
org.apache.ignite.internal.sql.optimizer.affinity.PartitionSingleNode.apply(PartitionSingleNode.java:47)
at
org.apache.ignite.internal.sql.optimizer.affinity.PartitionResult.calculatePartitions(PartitionResult.java:114)
... 25 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
