[jira] [Assigned] (IGNITE-18798) Sql. Custom types. UUID literal.
[
https://issues.apache.org/jira/browse/IGNITE-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov reassigned IGNITE-18798:
-
Assignee: Konstantin Orlov
> Sql. Custom types. UUID literal.
>
>
> Key: IGNITE-18798
> URL: https://issues.apache.org/jira/browse/IGNITE-18798
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-beta2
>Reporter: Maksim Zhuravkov
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
>
> At the moment in order to specify a UUID user must use a cast operator
> (string -> uuid) or rely on implicit casts (which only work in some
> contexts). Implement UUID literal in parser to allow to define a UUID literal.
> {code:java}
> SELECT UUID 'fd10556e-fc27-4a99-b5e4-89b8344cb3ce';
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18763) Parallel Meta Storage Watch processing
[ https://issues.apache.org/jira/browse/IGNITE-18763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-18763: - Summary: Parallel Meta Storage Watch processing (was: Concurrent Meta Storage Watch processing) > Parallel Meta Storage Watch processing > -- > > Key: IGNITE-18763 > URL: https://issues.apache.org/jira/browse/IGNITE-18763 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Sergey Chugunov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently Meta Storage Watches follow the given contract: > # All listeners are processed sequentially in the order that they have been > registered; > # All listeners are processed in the same thread; > # All notifications are grouped by a particular revision. After all events > for a particular revision get processed, all modified keys are persisted into > the Vault. > Some components may rely on this to ensure that dependent components can > observe the most recent component state, because they registered their Meta > Storage listeners after the component they depend on, therefore it is > guaranteed that that component has already processed current Meta Storage > revision. > This approach can be improved in terms of performance by enabling concurrent > Watch processing in multiple threads. In order to do that, we need to check > and fix the following places: > # If a component depends on another component's state, this state must be > extracted into a Versioned Value; > # If a component updates its state, relying on the fact, that this state is > always updated in a single thread, concurrent primitives must be introduced > to ensure thread safety; > # Check if it is possible to persist updated keys in the Vault individually, > thus making it possible not to wait for all Watches for a particular revision > to complete before starting to process updates belonging to the next > revision. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18980) Fix REST status code in case of failed request
[
https://issues.apache.org/jira/browse/IGNITE-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698771#comment-17698771
]
Ignite TC Bot commented on IGNITE-18980:
{panel:title=Branch: [pull/10586/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10586/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Java Client{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7085426]]
* {color:#013220}GridRestSuite:
RestProcessorAuthorizationTest.testOldClusterStateChange - PASSED{color}
* {color:#013220}GridRestSuite:
RestProcessorAuthorizationTest.testClusterStateChange - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7085486buildTypeId=IgniteTests24Java8_RunAll]
> Fix REST status code in case of failed request
> --
>
> Key: IGNITE-18980
> URL: https://issues.apache.org/jira/browse/IGNITE-18980
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Nikita Amelchev
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
> Attachments: RestProcessorSuccessStatusTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> _GridRestResponse_ should obtain proper 'not-OK' status on error. Often,
> _GridRestResponse#getSuccessStatus()_ is `GridRestResponse#STATUS_SUCCESS`
> even if the response is actually an error.
> Probably, we should revise _GridRestResponse#setError(String)_. It should
> set/check an error status like _GridRestResponse(int status, @Nullable String
> err)_
> A test attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17945) Change message in case watchdog thread observes freeze
[ https://issues.apache.org/jira/browse/IGNITE-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina reassigned IGNITE-17945: --- Assignee: (was: Julia Bakulina) > Change message in case watchdog thread observes freeze > -- > > Key: IGNITE-17945 > URL: https://issues.apache.org/jira/browse/IGNITE-17945 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitry Pavlov >Priority: Minor > Labels: ise, newbie > Fix For: 2.15 > > Time Spent: 1h > Remaining Estimate: 0h > > In Long JVM pause detector we warn user that the thread wasn't alive for a > threshold > Possible too long JVM pause: 500+ milliseconds. > But it is often treated as a GC pause. > We can change that warning to > Possible too long JVM pause: 500+ milliseconds. (GC pause or hardware > temporary freeze) > To enlist possible reasons behind that behaviour -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18996) Remove org.checkerframework from dependencies and code usage.
Evgeny Stanilovsky created IGNITE-18996: --- Summary: Remove org.checkerframework from dependencies and code usage. Key: IGNITE-18996 URL: https://issues.apache.org/jira/browse/IGNITE-18996 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 3.0.0-beta1 Reporter: Evgeny Stanilovsky Remove org.checkerframework from dependencies. All work is done at [1] need to port changes. [1] https://github.com/apache/ignite-3/pull/1651/files -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
[
https://issues.apache.org/jira/browse/IGNITE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18995:
---
Description:
Sometimes tests fails with following stacktraces:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
at
org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
or:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:216)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.cacheMetadataLocally(CacheObjectBinaryProcessorImpl.java:1076)
at
org.apache.ignite.internal.cdc.CdcMain.lambda$updateTypes$4(CdcMain.java:617)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at org.apache.ignite.internal.cdc.CdcMain.updateTypes(CdcMain.java:628)
at org.apache.ignite.internal.cdc.CdcMain.updateMetadata(CdcMain.java:589)
at
org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:464)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:325)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
Reason should be investigated and fixed.
Build logs with failures:
* [^_TESTS_CDC_408.log.zip]
* [^_TESTS_CDC_417.log.zip]
was:
Sometimes tests fails with following stacktraces:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
at
org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
or:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
[jira] [Updated] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
[
https://issues.apache.org/jira/browse/IGNITE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18995:
---
Description:
Sometimes tests fails with following stacktraces:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
at
org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
or:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:216)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.cacheMetadataLocally(CacheObjectBinaryProcessorImpl.java:1076)
at
org.apache.ignite.internal.cdc.CdcMain.lambda$updateTypes$4(CdcMain.java:617)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at org.apache.ignite.internal.cdc.CdcMain.updateTypes(CdcMain.java:628)
at org.apache.ignite.internal.cdc.CdcMain.updateMetadata(CdcMain.java:589)
at
org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:464)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:325)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
Reason should be investigated and fixed.
Build logs with failures: [^_TESTS_CDC_408.log.zip] [^_TESTS_CDC_417.log.zip]
was:
Sometimes tests fails with following stacktraces:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
at
org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
or:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
[jira] [Updated] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
[
https://issues.apache.org/jira/browse/IGNITE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18995:
---
Attachment: _TESTS_CDC_417.log.zip
> CDC test failures on BinaryMetadataFileStore.restoreMetadata
>
>
> Key: IGNITE-18995
> URL: https://issues.apache.org/jira/browse/IGNITE-18995
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
> Attachments: _TESTS_CDC_408.log.zip, _TESTS_CDC_417.log.zip
>
>
> Sometimes tests fails with following stacktraces:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
> at
> org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
> ... 6 more
> {noformat}
> or:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:216)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.cacheMetadataLocally(CacheObjectBinaryProcessorImpl.java:1076)
> at
> org.apache.ignite.internal.cdc.CdcMain.lambda$updateTypes$4(CdcMain.java:617)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
> at
> java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
> at
> java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
> at
> java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
> at
> java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
> at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
> at org.apache.ignite.internal.cdc.CdcMain.updateTypes(CdcMain.java:628)
> at org.apache.ignite.internal.cdc.CdcMain.updateMetadata(CdcMain.java:589)
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:464)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:325)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
> ... 6 more
> {noformat}
> Reason should be investigated and fixed.
> Build logs with failures:
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
[
https://issues.apache.org/jira/browse/IGNITE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18995:
---
Attachment: _TESTS_CDC_408.log.zip
> CDC test failures on BinaryMetadataFileStore.restoreMetadata
>
>
> Key: IGNITE-18995
> URL: https://issues.apache.org/jira/browse/IGNITE-18995
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Priority: Minor
> Labels: IEP-59, ise
> Attachments: _TESTS_CDC_408.log.zip, _TESTS_CDC_417.log.zip
>
>
> Sometimes tests fails with following stacktraces:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
> at
> org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
> ... 6 more
> {noformat}
> or:
> {noformat}
> Caused by: java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:216)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.cacheMetadataLocally(CacheObjectBinaryProcessorImpl.java:1076)
> at
> org.apache.ignite.internal.cdc.CdcMain.lambda$updateTypes$4(CdcMain.java:617)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
> at
> java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
> at
> java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
> at
> java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
> at
> java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
> at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
> at org.apache.ignite.internal.cdc.CdcMain.updateTypes(CdcMain.java:628)
> at org.apache.ignite.internal.cdc.CdcMain.updateMetadata(CdcMain.java:589)
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:464)
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:325)
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
> ... 6 more
> {noformat}
> Reason should be investigated and fixed.
> Build logs with failures:
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
[
https://issues.apache.org/jira/browse/IGNITE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-18995:
---
Description:
Sometimes tests fails with following stacktraces:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:207)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:370)
at
org.apache.ignite.internal.cdc.CdcMain.startStandaloneKernal(CdcMain.java:375)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:301)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
or:
{noformat}
Caused by: java.lang.AssertionError
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:299)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:120)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:92)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10662)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:222)
at
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:216)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.cacheMetadataLocally(CacheObjectBinaryProcessorImpl.java:1076)
at
org.apache.ignite.internal.cdc.CdcMain.lambda$updateTypes$4(CdcMain.java:617)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at org.apache.ignite.internal.cdc.CdcMain.updateTypes(CdcMain.java:628)
at org.apache.ignite.internal.cdc.CdcMain.updateMetadata(CdcMain.java:589)
at
org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:464)
at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:325)
at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:267)
... 6 more
{noformat}
Reason should be investigated and fixed.
Build logs with failures:
was:
CdcKafkaReplicationAppsTest can fail with a following error:
{noformat}
java.lang.RuntimeException: java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.TopicExistsException: Topic 'source-dest-meta'
already exists.
at
org.apache.kafka.streams.integration.utils.KafkaEmbedded.createTopic(KafkaEmbedded.java:187)
at
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.createTopic(EmbeddedKafkaCluster.java:218)
at
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.createTopic(EmbeddedKafkaCluster.java:203)
at
org.apache.ignite.cdc.kafka.CdcKafkaReplicationTest.beforeTest(CdcKafkaReplicationTest.java:75)
at
org.apache.ignite.cdc.kafka.CdcKafkaReplicationAppsTest.beforeTest(CdcKafkaReplicationAppsTest.java:91)
{noformat}
Reason should be investigated and fixed.
Build: [TC2 #346 at 14 Jan
09:49|https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6998555?hideProblemsFromDependencies=false=false=true=true]
Build log: [^_TESTS_CDC_346.log.zip]
> CDC test failures on BinaryMetadataFileStore.restoreMetadata
>
>
> Key: IGNITE-18995
> URL: https://issues.apache.org/jira/browse/IGNITE-18995
> Project: Ignite
> Issue Type: Test
> Components: extensions
>
[jira] [Created] (IGNITE-18995) CDC test failures on BinaryMetadataFileStore.restoreMetadata
Ilya Shishkov created IGNITE-18995:
--
Summary: CDC test failures on
BinaryMetadataFileStore.restoreMetadata
Key: IGNITE-18995
URL: https://issues.apache.org/jira/browse/IGNITE-18995
Project: Ignite
Issue Type: Test
Components: extensions
Reporter: Ilya Shishkov
CdcKafkaReplicationAppsTest can fail with a following error:
{noformat}
java.lang.RuntimeException: java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.TopicExistsException: Topic 'source-dest-meta'
already exists.
at
org.apache.kafka.streams.integration.utils.KafkaEmbedded.createTopic(KafkaEmbedded.java:187)
at
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.createTopic(EmbeddedKafkaCluster.java:218)
at
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.createTopic(EmbeddedKafkaCluster.java:203)
at
org.apache.ignite.cdc.kafka.CdcKafkaReplicationTest.beforeTest(CdcKafkaReplicationTest.java:75)
at
org.apache.ignite.cdc.kafka.CdcKafkaReplicationAppsTest.beforeTest(CdcKafkaReplicationAppsTest.java:91)
{noformat}
Reason should be investigated and fixed.
Build: [TC2 #346 at 14 Jan
09:49|https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/6998555?hideProblemsFromDependencies=false=false=true=true]
Build log: [^_TESTS_CDC_346.log.zip]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18994) SQL requests within RW transactions should not see their own changes.
[
https://issues.apache.org/jira/browse/IGNITE-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-18994:
-
Component/s: sql
> SQL requests within RW transactions should not see their own changes.
> -
>
> Key: IGNITE-18994
> URL: https://issues.apache.org/jira/browse/IGNITE-18994
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ignite-3
>
> Following requests
> {code:java}
> INSERT INTO bigtable SELECT * FROM bigtable{code}
> should not see their own changes.
> Consider following reproducer for more details:
> {code:java}
> // ItDmlTest.java
> @Test
> @WithSystemProperty(key = "IMPLICIT_PK_ENABLED", value = "true")
> public void test() {
> sql("CREATE TABLE test (x INT)");
> long size = 1024;
> // initial state
> sql("INSERT INTO test SELECT * FROM TABLE(system_range(1, ?))", size);
> for (int i = 0; i < 5; i++) {
> sql("INSERT INTO test SELECT * FROM test");
> assertQuery("SELECT count(*) FROM test")
> .returns(size * 2)
> .check();
> size *= 2;
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18994) SQL requests within RW transactions should not see their own changes.
Alexander Lapin created IGNITE-18994:
Summary: SQL requests within RW transactions should not see their
own changes.
Key: IGNITE-18994
URL: https://issues.apache.org/jira/browse/IGNITE-18994
Project: Ignite
Issue Type: Improvement
Reporter: Alexander Lapin
Following requests
{code:java}
INSERT INTO bigtable SELECT * FROM bigtable{code}
should not see their own changes.
Consider following reproducer for more details:
{code:java}
// ItDmlTest.java
@Test
@WithSystemProperty(key = "IMPLICIT_PK_ENABLED", value = "true")
public void test() {
sql("CREATE TABLE test (x INT)");
long size = 1024;
// initial state
sql("INSERT INTO test SELECT * FROM TABLE(system_range(1, ?))", size);
for (int i = 0; i < 5; i++) {
sql("INSERT INTO test SELECT * FROM test");
assertQuery("SELECT count(*) FROM test")
.returns(size * 2)
.check();
size *= 2;
}
} {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[
https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky reassigned IGNITE-18993:
Assignee: Ivan Daschinsky
> ODBC: Regression. Missed handling of single quotes
> --
>
> Key: IGNITE-18993
> URL: https://issues.apache.org/jira/browse/IGNITE-18993
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: c++, odbc
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with
> single comma), it returns an empty table list.
> It is a quite common way of calling this procedure (i.e. by INFORMATICA)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[
https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-18993:
-
Description:
When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with single
comma), it returns an empty table list.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
was:
When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with single
comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
> ODBC: Regression. Missed handling of single quotes
> --
>
> Key: IGNITE-18993
> URL: https://issues.apache.org/jira/browse/IGNITE-18993
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14
>Reporter: Ivan Daschinsky
>Priority: Major
> Labels: c++, odbc
>
> When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with
> single comma), it returns an empty table list.
> It is a quite common way of calling this procedure (i.e. by INFORMATICA)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[
https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-18993:
-
Description:
When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with single
comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
was:
When `SQLTables` is called with param 'table type' `'TABLES'` (with single
comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
> ODBC: Regression. Missed handling of single quotes
> --
>
> Key: IGNITE-18993
> URL: https://issues.apache.org/jira/browse/IGNITE-18993
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14
>Reporter: Ivan Daschinsky
>Priority: Major
> Labels: c++, odbc
>
> When {{SQLTables}} is called with param 'table type' {{'TABLES'}} (with
> single comma), it returns empty table lists.
> It is a quite common way of calling this procedure (i.e. by INFORMATICA)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[
https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-18993:
-
Description:
When `SQLTables` is called with param 'table type' `'TABLES'` (with single
comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
was:
When {code}SQLTables{code} is called with param 'table type'
{code}'TABLES'{code} (with single comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
> ODBC: Regression. Missed handling of single quotes
> --
>
> Key: IGNITE-18993
> URL: https://issues.apache.org/jira/browse/IGNITE-18993
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14
>Reporter: Ivan Daschinsky
>Priority: Major
> Labels: c++, odbc
>
> When `SQLTables` is called with param 'table type' `'TABLES'` (with single
> comma), it returns empty table lists.
> It is a quite common way of calling this procedure (i.e. by INFORMATICA)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[
https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-18993:
-
Description:
When {code}SQLTables{code} is called with param 'table type'
{code}'TABLES'{code} (with single comma), it returns empty table lists.
It is a quite common way of calling this procedure (i.e. by INFORMATICA)
> ODBC: Regression. Missed handling of single quotes
> --
>
> Key: IGNITE-18993
> URL: https://issues.apache.org/jira/browse/IGNITE-18993
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14
>Reporter: Ivan Daschinsky
>Priority: Major
> Labels: c++, odbc
>
> When {code}SQLTables{code} is called with param 'table type'
> {code}'TABLES'{code} (with single comma), it returns empty table lists.
> It is a quite common way of calling this procedure (i.e. by INFORMATICA)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[ https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18993: - Component/s: platforms > ODBC: Regression. Missed handling of single quotes > -- > > Key: IGNITE-18993 > URL: https://issues.apache.org/jira/browse/IGNITE-18993 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14 >Reporter: Ivan Daschinsky >Priority: Major > Labels: c++, odbc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[ https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18993: - Affects Version/s: 2.14 2.13 2.12 2.11 2.10 2.9 2.8 > ODBC: Regression. Missed handling of single quotes > -- > > Key: IGNITE-18993 > URL: https://issues.apache.org/jira/browse/IGNITE-18993 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14 >Reporter: Ivan Daschinsky >Priority: Major > Labels: c++, odbc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[ https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18993: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > ODBC: Regression. Missed handling of single quotes > -- > > Key: IGNITE-18993 > URL: https://issues.apache.org/jira/browse/IGNITE-18993 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Daschinsky >Priority: Major > Labels: c++, odbc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
[ https://issues.apache.org/jira/browse/IGNITE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18993: - Labels: c++ odbc (was: ) > ODBC: Regression. Missed handling of single quotes > -- > > Key: IGNITE-18993 > URL: https://issues.apache.org/jira/browse/IGNITE-18993 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Daschinsky >Priority: Major > Labels: c++, odbc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18993) ODBC: Regression. Missed handling of single quotes
Ivan Daschinsky created IGNITE-18993: Summary: ODBC: Regression. Missed handling of single quotes Key: IGNITE-18993 URL: https://issues.apache.org/jira/browse/IGNITE-18993 Project: Ignite Issue Type: Bug Reporter: Ivan Daschinsky -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17177) Implement incremental snapshots
[ https://issues.apache.org/jira/browse/IGNITE-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin resolved IGNITE-17177. - Reviewer: Nikolay Izhikov Resolution: Fixed > Implement incremental snapshots > --- > > Key: IGNITE-17177 > URL: https://issues.apache.org/jira/browse/IGNITE-17177 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-89, ise > Fix For: 2.15 > > Time Spent: 40m > Remaining Estimate: 0h > > Solution is incremental snapshots based on the Consistent Cut algorithm and > collecting WAL segments. > IEP-89: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-89%3A+Incremental+Snapshots -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18956) Test SqlSchemaProvider without Thread.sleep()
[ https://issues.apache.org/jira/browse/IGNITE-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-18956: -- Assignee: Aleksandr > Test SqlSchemaProvider without Thread.sleep() > - > > Key: IGNITE-18956 > URL: https://issues.apache.org/jira/browse/IGNITE-18956 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > > SqlSchemaProviderTest.testProviderWith1secTimeout is flaky because of its > Thread.sleep logic. We have to test async behavior somehow else. I think the > Awaitility library might be useful. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18513) .NET: Thin 3.0: Don't throw exception when tx is already committed or rolled back
[ https://issues.apache.org/jira/browse/IGNITE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698555#comment-17698555 ] Pavel Tupitsyn commented on IGNITE-18513: - Merged to main: 5d05ac362a746f996b19f36e8ee108febbf338b5 > .NET: Thin 3.0: Don't throw exception when tx is already committed or rolled > back > - > > Key: IGNITE-18513 > URL: https://issues.apache.org/jira/browse/IGNITE-18513 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > See how IGNITE-18324 changes the behavior on Java side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18992) Use single partition topic for metadata updates
Ilya Shishkov created IGNITE-18992:
--
Summary: Use single partition topic for metadata updates
Key: IGNITE-18992
URL: https://issues.apache.org/jira/browse/IGNITE-18992
Project: Ignite
Issue Type: Task
Components: extensions
Reporter: Ilya Shishkov
In order to read data with guaranteed order, metadata topic must have only one
partition. To achieve this we should:
* Write binary types and marshaller mappings only to a single partition in
{{IgniteToKafkaCdcStreamer#onMappings}} and {{#onTypes}}.
* Assign {{KafkaConsumer}} in {{KafkaToIgniteMetadataUpdater}} to a single
partition.
* Print warnings into logs, when topic has more than one partition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18513) .NET: Thin 3.0: Don't throw exception when tx is already committed or rolled back
[ https://issues.apache.org/jira/browse/IGNITE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698489#comment-17698489 ] Igor Sapego commented on IGNITE-18513: -- [~ptupitsyn] Looks good to me. > .NET: Thin 3.0: Don't throw exception when tx is already committed or rolled > back > - > > Key: IGNITE-18513 > URL: https://issues.apache.org/jira/browse/IGNITE-18513 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-beta2 > > > See how IGNITE-18324 changes the behavior on Java side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-18928:
Fix Version/s: (was: 2.15)
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=builds
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=overview=builds#all-projects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-18928:
Fix Version/s: 2.15
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Fix For: 2.15
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=builds
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=overview=builds#all-projects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov resolved IGNITE-18928.
-
Resolution: Fixed
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=builds
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=overview=builds#all-projects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-18928:
Ignite Flags: (was: Docs Required,Release Notes Required)
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=builds
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=overview=builds#all-projects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698458#comment-17698458
]
Mikhail Petrov commented on IGNITE-18928:
-
AOP extensions suite run result:
https://ci2.ignite.apache.org/viewLog.html?buildId=7085309=buildResultsDiv=IgniteExtensions_Tests_Aop
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=builds
> #
> https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Aop?branch=%3Cdefault%3E=overview=builds#all-projects
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18990) Partial redesign of TableManager to solve the problems related to huge load of metastorage updates
[
https://issues.apache.org/jira/browse/IGNITE-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-18990:
---
Description:
The exception does not connect with placement driver directly, but the feature
increases probability of the problem.
The root cause of the issue is in SqlSchemaManagerImpl#schemasVv that is
updated depending on table creation and the configuration revision update in
the same time. To got rid of the issue, required waiting of table creation
event (TableEvent.CREATE) before complete the versioned value object
(schemasVv).
{noformat}
WARNING: Error occurred while updating tables.
java.util.concurrent.CompletionException: java.lang.AssertionError: Token must
be greater than actual [token=6734, actual=6734]
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1081)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
at
org.apache.ignite.internal.causality.VersionedValue.completeInternal(VersionedValue.java:335)
at
org.apache.ignite.internal.causality.VersionedValue.lambda$completeOnRevision$3(VersionedValue.java:493)
at
java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
at
java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
at
org.apache.ignite.internal.raft.RaftGroupServiceImpl.lambda$sendWithRetry$38(RaftGroupServiceImpl.java:525)
at
java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
at
java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
at
org.apache.ignite.network.DefaultMessagingService.onInvokeResponse(DefaultMessagingService.java:349)
at
org.apache.ignite.network.DefaultMessagingService.onMessage(DefaultMessagingService.java:314)
at
org.apache.ignite.network.DefaultMessagingService.lambda$onMessage$3(DefaultMessagingService.java:292)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.AssertionError: Token must be greater than actual
[token=6734, actual=6734]
at
org.apache.ignite.internal.causality.VersionedValue.checkToken(VersionedValue.java:597)
at
org.apache.ignite.internal.causality.VersionedValue.update(VersionedValue.java:403)
at
org.apache.ignite.internal.sql.engine.schema.SqlSchemaManagerImpl.onTableCreated(SqlSchemaManagerImpl.java:210)
at
org.apache.ignite.internal.sql.engine.SqlQueryProcessor$TableCreatedListener.notify(SqlQueryProcessor.java:580)
at
org.apache.ignite.internal.sql.engine.SqlQueryProcessor$TableCreatedListener.notify(SqlQueryProcessor.java:572)
at org.apache.ignite.internal.manager.Producer.fireEvent(Producer.java:108)
at org.apache.ignite.internal.manager.Producer.fireEvent(Producer.java:129)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$36(TableManager.java:1158)
at
org.apache.ignite.internal.util.IgniteUtils.inBusyLock(IgniteUtils.java:861)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableLocally$37(TableManager.java:1158)
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
... 19 more
{noformat}
After the issue will be fixed, placement driver ready to include in the node
start workflow.
> Partial redesign of TableManager to solve the problems related to huge load
> of metastorage updates
> --
>
> Key: IGNITE-18990
> URL: https://issues.apache.org/jira/browse/IGNITE-18990
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Chudov
>Priority: Major
> Labels: ignite-3
>
> The exception does not connect with placement driver directly, but the
> feature increases probability of
[jira] [Commented] (IGNITE-18928) AOP test suite tests fails with SecurityException
[
https://issues.apache.org/jira/browse/IGNITE-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698442#comment-17698442
]
Ignite TC Bot commented on IGNITE-18928:
{panel:title=Branch: [pull/10573/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10573/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7072983buildTypeId=IgniteTests24Java8_RunAll]
> AOP test suite tests fails with SecurityException
> -
>
> Key: IGNITE-18928
> URL: https://issues.apache.org/jira/browse/IGNITE-18928
> Project: Ignite
> Issue Type: Test
> Components: extensions
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> AOP test suite [1, 2] tests fails with exception:
> {noformat}
> [2023-03-01T08:01:25,477][ERROR][main][] Test failed
> [test=NonSpringAopSelfTest#testDefaultContinuous, duration=124]
> org.apache.ignite.compute.gridify.GridifyRuntimeException: Undeclared
> exception thrown: Access to Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:130)
> ~[classes/:?]
> at
> org.apache.ignite.gridify.TestAopTarget.gridifyDefault(TestAopTarget.java:35)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.checkDefault(AbstractAopTest.java:398)
> ~[test-classes/:?]
> at
> org.apache.ignite.gridify.AbstractAopTest.testDefaultContinuous(AbstractAopTest.java:82)
> ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_341]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_341]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_341]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_341]
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> ~[junit-4.12.jar:4.12]
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> ~[junit-4.12.jar:4.12]
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
> ~[ignite-core-2.15.0-SNAPSHOT-tests.jar:2.15.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_341]
> Caused by: org.apache.ignite.plugin.security.SecurityException: Access to
> Ignite Internal tasks is restricted
> [task=org.apache.ignite.compute.gridify.aop.GridifyDefaultTask, job=class
> org.apache.ignite.internal.util.gridify.GridifyJobAdapter]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1783)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:754)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:449)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeHandler.executeAsync(IgniteComputeHandler.java:320)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:251)
> ~[ignite-core-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
> at
> org.apache.ignite.compute.gridify.aop.aspectj.GridifyAspectJAspect.gridify(GridifyAspectJAspect.java:107)
> ~[classes/:?]
> ... 13 more
> {noformat}
> It seems, that fails relates to a ticket: IGNITE-15322.
> Links:
> #
>
[jira] [Updated] (IGNITE-14858) Calcite integration. New Thin JDBC driver for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-14858: --- Description: JDBC API is widely used in various projects/systems. It is worth having a JDBC driver for better UX, easier integration with other systems, easier migration from the other DBs. Let's implement new JDBC driver Calcite for Ignite 3.0. was: JDBC API is widely used in various projects/systems. It is worth having a JDBC driver for better UX, easier integration with other systems, easier migration from the other DBs. Let's implement new JDBC driver Calcite for Ignite 3.0 > Calcite integration. New Thin JDBC driver for 3.0 > - > > Key: IGNITE-14858 > URL: https://issues.apache.org/jira/browse/IGNITE-14858 > Project: Ignite > Issue Type: Epic > Components: jdbc >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > JDBC API is widely used in various projects/systems. > It is worth having a JDBC driver for better UX, easier integration with other > systems, easier migration from the other DBs. > Let's implement new JDBC driver Calcite for Ignite 3.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15247) JDBC driver for 3.0: Error handling.
[ https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15247: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Error handling. > > > Key: IGNITE-15247 > URL: https://issues.apache.org/jira/browse/IGNITE-15247 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > *Motivation:* > JDBC driver must throws exceptions of java.sql.SQLException kind with a > SQLState code (XOPEN type or the SQL:2003 type). > Standard says SQLState is implementation-defined thing and define the > SQLState format, some predefined categories and ability to specify > vendor-code of 'int' type. > Vendor codes must be well-documented. > Let's map Ignite exceptions/error codes to proper SQLException with SQLState. > 1. As we always know at what phase the query execution (in JDBC driver or in > SQL engine) was failed, we can use proper standard SQLState category. > 2. We use IGN-XXX-nnn format (where XXX is a group name and nnn is an unique > error code within a group) [1], we can't map Ignite error code to SQL vendor > code directly. > So, we should convert non-SQL origins to IGN-SQL-nnn somehow(?) and use 'nnn' > as vendor code(?). > https://issues.apache.org/jira/browse/IGNITE-14931 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16219) JDBC driver for 3.0: ItJdbcJoinsSelfTest test fix
[ https://issues.apache.org/jira/browse/IGNITE-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16219: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: ItJdbcJoinsSelfTest test fix > - > > Key: IGNITE-16219 > URL: https://issues.apache.org/jira/browse/IGNITE-16219 > Project: Ignite > Issue Type: Bug > Components: jdbc, sql >Reporter: Vladimir Ermakov >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > ItJdbcJoinsSelfTest.testJoin runs correctly in local, but in teamcity > java.lang.AssertionError is appeared. Should be investigated. Logs: > https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_ModuleRunner/6343350 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16203) JDBC driver for 3.0: Parameter metadata.
[ https://issues.apache.org/jira/browse/IGNITE-16203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16203: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Parameter metadata. > > > Key: IGNITE-16203 > URL: https://issues.apache.org/jira/browse/IGNITE-16203 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18984) Sql. Jdbc. Migrate batched methods on new internal API
[
https://issues.apache.org/jira/browse/IGNITE-18984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18984:
---
Epic Link: IGNITE-14858
> Sql. Jdbc. Migrate batched methods on new internal API
> --
>
> Key: IGNITE-18984
> URL: https://issues.apache.org/jira/browse/IGNITE-18984
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> After IGNITE-18983, the next part is a migration of batched methods
> (*Statement#executeBatch). Here we need to replace call to
> {{QueryProcessor#queryAsync}} with {{{}QueryProcessor#querySingleAsync{}}}.
> NB: need to not forget about session recovery; depending on implementation
> introduced in IGNITE-18983, it may or may not require explicit handling .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16204) Calcite integration. Add JDBC tests when INDEX support is appeared
[ https://issues.apache.org/jira/browse/IGNITE-16204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16204: --- Epic Link: IGNITE-14858 > Calcite integration. Add JDBC tests when INDEX support is appeared > -- > > Key: IGNITE-16204 > URL: https://issues.apache.org/jira/browse/IGNITE-16204 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > > Let's remove muted test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18983) Sql. Jdbc. Migrate JDBC handler on new internal API
[
https://issues.apache.org/jira/browse/IGNITE-18983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18983:
---
Epic Link: IGNITE-14858
> Sql. Jdbc. Migrate JDBC handler on new internal API
> ---
>
> Key: IGNITE-18983
> URL: https://issues.apache.org/jira/browse/IGNITE-18983
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> h3. Problem
> Currently, JDBC implementation uses old entrypoint to QueryProcessor:
> {{{}QueryProcessor#queryAsync(...){}}}. It lacks proper integration with
> transaction, as well as session management.
> As a first step, let's migrate only subset of {{execute*}} methods:
> {{executeQuery}} and {{{}executeUpdate{}}}. Execution of the arbitrary script
> ({{{}Statement#execute{}}}), as well as execution of batched methods
> ({{{}*Statement#executeBatch{}}}) will be addressed in the follow up tickets.
> h3. Implementation notes
> This task consists of two parts.
> The first one is the session management. JdbcConnection should create new
> session with the very first request and reuse it while it is valid. The
> session may unexpectedly be invalidated for number of reasons, thus some
> recovery procedure is needed. An approximate algorithm might look like this:
> h4. Session initialization
> 1) with the very first request, client sends sessions params alongside with
> the request
> 2) server issues client connection id (ccId) and save these params alonside
> with ccId in connection context
> 3) server creates new session with provided params and save session id in the
> connection context
> 4) server executes request within created session
> 5) server respond to the client with response and ccId from the p.2
> 6) client saves ccId
> 7) from this point, all following request must include ccId
> h4. Session recovery
> 1) server receives the request with ccId
> 2) server retrieves the context by ccId
> 3) server retrieves the sessionId from context
> 4) server tries to execute request within the session
> 5) if session is invalidated, server tries to recreate the session and
> retries the operation (pp.3-5 from previous algorithm)
>
> The second part is just migration from queryAsync to querySingleAsync. Looks
> pretty straitforward to me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16207) JDBC driver for 3.0: Calcite throws class cast exception
[ https://issues.apache.org/jira/browse/IGNITE-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16207: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Calcite throws class cast exception > > > Key: IGNITE-16207 > URL: https://issues.apache.org/jira/browse/IGNITE-16207 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Vladimir Ermakov >Assignee: Vladimir Ermakov >Priority: Blocker > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Calcite throws > java.lang.ClassCastException: class java.lang.String cannot be cast to class > java.lang.Integer (java.lang.String and java.lang.Integer are in module > java.base of loader 'bootstrap') > when > ItJdbcComplexDmlDdlSelfTest#testCreateSelectDrop() test running after > ItJdbcInsertStatementSelfTest#testDuplicateKeys(). > However, single run passed correctly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16205) Calcite integration: Add JDBC tests when query cancelation is supported.
[ https://issues.apache.org/jira/browse/IGNITE-16205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16205: --- Epic Link: IGNITE-14858 > Calcite integration: Add JDBC tests when query cancelation is supported. > > > Key: IGNITE-16205 > URL: https://issues.apache.org/jira/browse/IGNITE-16205 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15185) JDBC driver for 3.0: Implements Driver & Connection
[
https://issues.apache.org/jira/browse/IGNITE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-15185:
---
Epic Link: IGNITE-14858
> JDBC driver for 3.0: Implements Driver & Connection
> ---
>
> Key: IGNITE-15185
> URL: https://issues.apache.org/jira/browse/IGNITE-15185
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, sql
>Reporter: Taras Ledkov
>Assignee: Vladimir Ermakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> Implements JDBC driver & Connection according with
> [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0].
> See more at Ignite 2.x:
> - driver implementation: {{IgniteJdbcThinDriver}}
> - connection properties: {{ConnectionPropertiesImpl}}
> Create ticket to documentation JDBC connection string & connection properties
> (for now it will only be network properties).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16201) JDBC driver for 3.0: Batch execution.
[ https://issues.apache.org/jira/browse/IGNITE-16201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16201: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Batch execution. > - > > Key: IGNITE-16201 > URL: https://issues.apache.org/jira/browse/IGNITE-16201 > Project: Ignite > Issue Type: New Feature > Components: jdbc >Reporter: Vladimir Ermakov >Assignee: Vladimir Ermakov >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 2h > Remaining Estimate: 0h > > Let's implement batch execution in JDBC driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18985) Sql. Jdbc. Integration with transaction
[
https://issues.apache.org/jira/browse/IGNITE-18985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18985:
---
Epic Link: IGNITE-14858
> Sql. Jdbc. Integration with transaction
> ---
>
> Key: IGNITE-18985
> URL: https://issues.apache.org/jira/browse/IGNITE-18985
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
>
> Current implementation of JDBC misses integration with transactions.
> So, new command should be introduced to client-server protocol:
> {{{}finishTx(commit: bool){}}}. According handler should be provided on a
> server side. This command may be issued by invocation of commit/rollback
> methods on {{{}JdbcConnection{}}}.
> Also, we need to handle {{setAutoCommit}} method invocation as well.
> Finally, depending on current mode of autoCommit and presence of valid
> transaction in connection context, the new transaction should or should not
> be issued before query execution. It looks like we can rely on implicit
> transactions right now, thus if autoCommit set to true, it seems to safe to
> provide null instead of actual transaction. However, autoCommit=false mode
> must be handled explicitly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15507) JDBC driver for 3.0: Implements Time API support
[ https://issues.apache.org/jira/browse/IGNITE-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15507: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Implements Time API support > > > Key: IGNITE-15507 > URL: https://issues.apache.org/jira/browse/IGNITE-15507 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > > Calcite currently works with old java Date API in queries only. After > integration with new java Time API will be implemented, it is necessary to > support it in JDBC driver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15251) JDBC driver for 3.0: Support DML/DDL queries.
[ https://issues.apache.org/jira/browse/IGNITE-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15251: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Support DML/DDL queries. > - > > Key: IGNITE-15251 > URL: https://issues.apache.org/jira/browse/IGNITE-15251 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Extend Statement functionality for DML/DDL queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15508) JDBC driver for 3.0: Support JDBC driver loading by ServiceLoader
[ https://issues.apache.org/jira/browse/IGNITE-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15508: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Support JDBC driver loading by ServiceLoader > - > > Key: IGNITE-15508 > URL: https://issues.apache.org/jira/browse/IGNITE-15508 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Vladimir Ermakov >Assignee: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 40m > Remaining Estimate: 0h > > Support JDBC driver loading by ServiceLoader. > All is needed is to add classname to META_INF/services/java.sql.Driver file. > It is also necessary to check whether the driver needs to be registered > additionally via a static block. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15250) JDBC driver for 3.0: Support SET command on client.
[ https://issues.apache.org/jira/browse/IGNITE-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15250: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Support SET command on client. > --- > > Key: IGNITE-15250 > URL: https://issues.apache.org/jira/browse/IGNITE-15250 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Let's support SET command on Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15186) JDBC driver for 3.0: Implements Statements
[ https://issues.apache.org/jira/browse/IGNITE-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15186: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Implements Statements > -- > > Key: IGNITE-15186 > URL: https://issues.apache.org/jira/browse/IGNITE-15186 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Taras Ledkov >Assignee: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 19h > Remaining Estimate: 0h > > Implements minimal functionality of Statement, PreparedStatement and > ResultSet that is sifficient for running a query. > Extends > [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0] > with new commands. > We can add temporary methods for query execution to Client API, which will be > replaced with native SQL API later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15188) JDBC driver for 3.0: Implements DatabaseMetadata
[
https://issues.apache.org/jira/browse/IGNITE-15188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-15188:
---
Epic Link: IGNITE-14858
> JDBC driver for 3.0: Implements DatabaseMetadata
>
>
> Key: IGNITE-15188
> URL: https://issues.apache.org/jira/browse/IGNITE-15188
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Reporter: Taras Ledkov
>Assignee: Vladimir Ermakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Implements DatabaseMetadata.
> Extends
> [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0]
> with new commands.
> Take a look at the common approach for the metadata / view at the Ignite 2.x:
> {{SystemViewRowAttributeWalker}}, {{SchemaManager}}. Looks like we should use
> best practice from Ignite 2.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15648) JDBC driver for 3.0: Add integration tests that depend on the data layer.
[ https://issues.apache.org/jira/browse/IGNITE-15648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15648: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Add integration tests that depend on the data layer. > -- > > Key: IGNITE-15648 > URL: https://issues.apache.org/jira/browse/IGNITE-15648 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Vladimir Ermakov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Time Spent: 1.5h > Remaining Estimate: 0h > > Subj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15249) JDBC driver for 3.0: Internal SQL API.
[ https://issues.apache.org/jira/browse/IGNITE-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15249: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Internal SQL API. > -- > > Key: IGNITE-15249 > URL: https://issues.apache.org/jira/browse/IGNITE-15249 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Design internal API for SQL queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15187) JDBC driver for 3.0: Implements ResultSetMetadata
[ https://issues.apache.org/jira/browse/IGNITE-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15187: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Implements ResultSetMetadata > - > > Key: IGNITE-15187 > URL: https://issues.apache.org/jira/browse/IGNITE-15187 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Taras Ledkov >Assignee: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Implements ResultSetMetadata. > Extends > [IEP-76|https://cwiki.apache.org/confluence/display/IGNITE/IEP-76+Thin+Client+Protocol+for+Ignite+3.0] > with new commands. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15428) JDBC driver for 3.0: Implements SSL connection
[ https://issues.apache.org/jira/browse/IGNITE-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-15428: --- Epic Link: IGNITE-14858 > JDBC driver for 3.0: Implements SSL connection > -- > > Key: IGNITE-15428 > URL: https://issues.apache.org/jira/browse/IGNITE-15428 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14858) Calcite integration. New Thin JDBC driver for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-14858: --- Epic Name: JDBC 3.0 > Calcite integration. New Thin JDBC driver for 3.0 > - > > Key: IGNITE-14858 > URL: https://issues.apache.org/jira/browse/IGNITE-14858 > Project: Ignite > Issue Type: Epic > Components: jdbc >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > JDBC API is widely used in various projects/systems. > It is worth having a JDBC driver for better UX, easier integration with other > systems, easier migration from the other DBs. > Let's implement new JDBC driver Calcite for Ignite 3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14858) Calcite integration. New Thin JDBC driver for 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-14858: --- Issue Type: Epic (was: New Feature) > Calcite integration. New Thin JDBC driver for 3.0 > - > > Key: IGNITE-14858 > URL: https://issues.apache.org/jira/browse/IGNITE-14858 > Project: Ignite > Issue Type: Epic > Components: jdbc >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > JDBC API is widely used in various projects/systems. > It is worth having a JDBC driver for better UX, easier integration with other > systems, easier migration from the other DBs. > Let's implement new JDBC driver Calcite for Ignite 3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18741) Implement PD-side logic for an initialization phase of group lease management
[ https://issues.apache.org/jira/browse/IGNITE-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698418#comment-17698418 ] Vladislav Pyatkov commented on IGNITE-18741: Merged 62e6788a1e6ea089ce1a4d3efa1f1463af8109da > Implement PD-side logic for an initialization phase of group lease management > - > > Key: IGNITE-18741 > URL: https://issues.apache.org/jira/browse/IGNITE-18741 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Attachments: PlacementDriverManagerClasses.drawio.png, Снимок экрана > от 2023-02-07 15-49-29.png, Снимок экрана от 2023-02-07 16-23-51.png > > Time Spent: 3.5h > Remaining Estimate: 0h > > h3. Motivation > There are two phases of lease management: > * *initialization* - _new_ leases management. // marked with greed > * *maintenance* - already existing leases management. // marked with orange > !Снимок экрана от 2023-02-07 15-49-29.png! > Given ticket is about new leases management on the placement driver side(the > active actor one). So it covers the *flow* from the detection of a > replication group appearance in the logical topology *to* sending leaseGrant > message to the primary replica candidate. > h3. Definition of Done > # All triggers related to new primary replica candidate appearance are > covered. > # Placement driver starts primary replica candidate promotion event loop. > h3. Implementation Notes > 1.Following events should be considered as triggers related to new primary > replica candidate appearance: > * MetaStorage based logical topology updates. We use MS and not CMG events > here in order to linearize logical topology updates with other configuration > events. Please pay attention that DistributionZone logic is responsible for > population ms with logical topology, following key > DISTRIBUTION_ZONE_LOGICAL_TOPOLOGY_KEY is used and yep we may rename it. > * Replication group assignment updates. > As usual, we should first register listeners and then initialize the flow > according to already existing assignments and logical topology. > 2. Following steps inside primary replica candidate promotion event loop are > expected > !Снимок экрана от 2023-02-07 16-23-51.png! > *UPD:* > During implementation, the issue was reformulated and slightly redesigned. By > the redesign result, a class diagram was drawn. > !PlacementDriverManagerClasses.drawio.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18741) Implement PD-side logic for an initialization phase of group lease management
[ https://issues.apache.org/jira/browse/IGNITE-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698417#comment-17698417 ] Denis Chudov commented on IGNITE-18741: --- [~v.pyatkov] LGTM > Implement PD-side logic for an initialization phase of group lease management > - > > Key: IGNITE-18741 > URL: https://issues.apache.org/jira/browse/IGNITE-18741 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > Attachments: PlacementDriverManagerClasses.drawio.png, Снимок экрана > от 2023-02-07 15-49-29.png, Снимок экрана от 2023-02-07 16-23-51.png > > Time Spent: 3.5h > Remaining Estimate: 0h > > h3. Motivation > There are two phases of lease management: > * *initialization* - _new_ leases management. // marked with greed > * *maintenance* - already existing leases management. // marked with orange > !Снимок экрана от 2023-02-07 15-49-29.png! > Given ticket is about new leases management on the placement driver side(the > active actor one). So it covers the *flow* from the detection of a > replication group appearance in the logical topology *to* sending leaseGrant > message to the primary replica candidate. > h3. Definition of Done > # All triggers related to new primary replica candidate appearance are > covered. > # Placement driver starts primary replica candidate promotion event loop. > h3. Implementation Notes > 1.Following events should be considered as triggers related to new primary > replica candidate appearance: > * MetaStorage based logical topology updates. We use MS and not CMG events > here in order to linearize logical topology updates with other configuration > events. Please pay attention that DistributionZone logic is responsible for > population ms with logical topology, following key > DISTRIBUTION_ZONE_LOGICAL_TOPOLOGY_KEY is used and yep we may rename it. > * Replication group assignment updates. > As usual, we should first register listeners and then initialize the flow > according to already existing assignments and logical topology. > 2. Following steps inside primary replica candidate promotion event loop are > expected > !Снимок экрана от 2023-02-07 16-23-51.png! > *UPD:* > During implementation, the issue was reformulated and slightly redesigned. By > the redesign result, a class diagram was drawn. > !PlacementDriverManagerClasses.drawio.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18868) Recursive update of pendingInvokes in ReplicaService
[
https://issues.apache.org/jira/browse/IGNITE-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-18868:
Assignee: Vladislav Pyatkov
> Recursive update of pendingInvokes in ReplicaService
>
>
> Key: IGNITE-18868
> URL: https://issues.apache.org/jira/browse/IGNITE-18868
> Project: Ignite
> Issue Type: Bug
>Reporter: Konstantin Orlov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> Take a look at the code below:
> {code:java}
> // ReplicaService#sendToReplica
>if (errResp.throwable() instanceof ReplicaUnavailableException) {
> pendingInvokes.compute(targetNodeConsistentId,
> (clusterNode, fut) -> {
> if (fut == null) {
> AwaitReplicaRequest awaitReplicaReq = ...
> fut = messagingService.invoke(...)
> .whenComplete((response0, throwable0)
> -> {
>
> pendingInvokes.remove(targetNodeConsistentId);
> });
> }
> {code}
> In case {{messagingService}} respond immediately, {{whenComplete}} callback
> will be executed in the same thread causing recursive update ({{{}remove{}}}
> inside of {{{}compute{}}}) which is not allowed.
> {code:java}
> Caused by: java.lang.IllegalStateException: Recursive update
> at
> java.base/java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1167)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1102)
> at
> org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$0(ReplicaService.java:125)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at
> java.base/java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:883)
> at
> java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2251)
> at
> org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$3(ReplicaService.java:124)
> {code}
> a
> h3. Definition of Done
> Need to move
> {code:java}
> .whenComplete(
> (response0, throwable0) -> {
> pendingInvokes.remove(targetNodeConsistentId); }
> );
> {code}
> from the _compute_ block and add it to the future which is returned from the
> {_}compute{_}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18767) Reuse deleted rowIds and version chains
[ https://issues.apache.org/jira/browse/IGNITE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-18767: Assignee: Denis Chudov > Reuse deleted rowIds and version chains > --- > > Key: IGNITE-18767 > URL: https://issues.apache.org/jira/browse/IGNITE-18767 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > *Motivation* > New RowId is generated every time when row insert happens. Old rowIds point > to tombstones and are cleared only on vacuum. This leads to the garbage > stockpiling in index storages and version chains, necessity for scanning > multiple rows even for unique indexes and possibility of having multiple > write intents for single key within one transaction. We can reuse tombstone > rows for inserts. > *Definition of done* > New rowIds are generated only for new rows when there are now tombstones to > reuse. > *Implementation notes* > For tx rollbacks, we should also remove index entries for write intents that > are to be aborted, but only in case when version chain's tail is write intent > (i.e. in case of abortion of this write intent there will be no entry in > versioned storage on which the index entry could point). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15287) Yardstick's -cwd params does not clean persistence and wal directories
[
https://issues.apache.org/jira/browse/IGNITE-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15287:
-
Fix Version/s: (was: 2.10)
> Yardstick's -cwd params does not clean persistence and wal directories
> --
>
> Key: IGNITE-15287
> URL: https://issues.apache.org/jira/browse/IGNITE-15287
> Project: Ignite
> Issue Type: Bug
> Environment: -
>Reporter: Anton Vinogradov
>Priority: Major
>
> The current code at IgniteNode.java is
> {noformat}
> if (args.cleanWorkDirectory() && !clientMode)
> FileUtils.cleanDirectory(U.workDirectory(c.getWorkDirectory(),
> c.getIgniteHome()));
> {noformat}
> and we should append {{dataStorageConfiguration#storagePath}} and
> {{dataStorageConfiguration#walPath}} clean-up as well.
> Why it's important:
> For example, hawing following configuration
> {noformat}
> class="org.apache.ignite.configuration.DataStorageConfiguration">
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
> We will use same persistence each time we running benchmarks, this means
> we'll gain different numbers each time :(
> {{/mnt/ssd/wal}} will grow until possible, and {{/mnt/ssd/persistence}} will
> be different before each benchmark start.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16985) Design table management flow (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-16985: -- Issue Type: Task (was: Improvement) > Design table management flow (part 1) > - > > Key: IGNITE-16985 > URL: https://issues.apache.org/jira/browse/IGNITE-16985 > Project: Ignite > Issue Type: Task >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > As a part of the issue planed: > # Draw a time diagram of all operations: createTable(), dropTable(), > table(), tables(). > # Emphases of correctness work of causality tokens: tablesByIdVv. > # Reflect cross components interactions. Components: Schema manager, SQL > manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). > > The task for this ticket is to make a detailed diagram of the current flow, > to ease the design itself. > Definition of done: > We have detailed and clear description of table manager flows and the ticket > IGNITE-18989 is enriched with details about the flaws we want to fix. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16985) Design table management flow (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-16985: -- Description: As a part of the issue planed: # Draw a time diagram of all operations: createTable(), dropTable(), table(), tables(). # Emphases of correctness work of causality tokens: tablesByIdVv. # Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). The task for this ticket is to make a detailed diagram of the current flow, to ease the design itself. Definition of done: We have detailed and clear description of table manager flows and the ticket IGNITE-18989 is enriched with details about the flaws we want to fix. was: As a part of the issue planed: # Draw a time diagram of all operations: createTable(), dropTable(), table(), tables(). # Emphases of correctness work of causality tokens: tablesByIdVv. # Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). The task for this ticket is to make a detailed diagram of the current flow, to ease the design itself. > Design table management flow (part 1) > - > > Key: IGNITE-16985 > URL: https://issues.apache.org/jira/browse/IGNITE-16985 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > As a part of the issue planed: > # Draw a time diagram of all operations: createTable(), dropTable(), > table(), tables(). > # Emphases of correctness work of causality tokens: tablesByIdVv. > # Reflect cross components interactions. Components: Schema manager, SQL > manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). > > The task for this ticket is to make a detailed diagram of the current flow, > to ease the design itself. > Definition of done: > We have detailed and clear description of table manager flows and the ticket > IGNITE-18989 is enriched with details about the flaws we want to fix. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18991) Remove assignments from table configuration
Kirill Gusakov created IGNITE-18991: --- Summary: Remove assignments from table configuration Key: IGNITE-18991 URL: https://issues.apache.org/jira/browse/IGNITE-18991 Project: Ignite Issue Type: Task Reporter: Kirill Gusakov We need to remove assignments from table configuration and rebind whole logic connected with it to metastore-based assignments -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18990) Partial redesign of TableManager to solve the problems related to huge load of metastorage updates
Denis Chudov created IGNITE-18990: - Summary: Partial redesign of TableManager to solve the problems related to huge load of metastorage updates Key: IGNITE-18990 URL: https://issues.apache.org/jira/browse/IGNITE-18990 Project: Ignite Issue Type: Task Reporter: Denis Chudov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18989) Design table management flow (part 2)
[ https://issues.apache.org/jira/browse/IGNITE-18989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-18989: -- Description: After making the diagram of current flow, we should design the new flow and a plan for descomposition of TableManager by different components having more narrow responsibility. > Design table management flow (part 2) > - > > Key: IGNITE-18989 > URL: https://issues.apache.org/jira/browse/IGNITE-18989 > Project: Ignite > Issue Type: Task >Reporter: Denis Chudov >Priority: Major > Labels: ignite-3 > > After making the diagram of current flow, we should design the new flow and a > plan for descomposition of TableManager by different components having more > narrow responsibility. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16985) Design table management flow (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-16985: -- Description: As a part of the issue planed: # Draw a time diagram of all operations: createTable(), dropTable(), table(), tables(). # Emphases of correctness work of causality tokens: tablesByIdVv. # Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). The task for this ticket is to make a detailed diagram of the current flow, to ease the design itself. was: As a part of the issue planed: # Draw a time diagram of all operations: createTable(), dropTable(), table(), tables(). # Emphases of correctness work of causality tokens: tablesByIdVv. # Reflect cross components interactions. Components: Schema manager, SQL manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). Description of the following flows are needed: # As it is now # As it should be # Possible fast improvements that could help to solve hot problems > Design table management flow (part 1) > - > > Key: IGNITE-16985 > URL: https://issues.apache.org/jira/browse/IGNITE-16985 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > As a part of the issue planed: > # Draw a time diagram of all operations: createTable(), dropTable(), > table(), tables(). > # Emphases of correctness work of causality tokens: tablesByIdVv. > # Reflect cross components interactions. Components: Schema manager, SQL > manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). > > The task for this ticket is to make a detailed diagram of the current flow, > to ease the design itself. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18989) Design table management flow (part 2)
Denis Chudov created IGNITE-18989: - Summary: Design table management flow (part 2) Key: IGNITE-18989 URL: https://issues.apache.org/jira/browse/IGNITE-18989 Project: Ignite Issue Type: Task Reporter: Denis Chudov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16985) Design table management flow (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-16985: -- Summary: Design table management flow (part 1) (was: Design table management flow) > Design table management flow (part 1) > - > > Key: IGNITE-16985 > URL: https://issues.apache.org/jira/browse/IGNITE-16985 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > As a part of the issue planed: > # Draw a time diagram of all operations: createTable(), dropTable(), > table(), tables(). > # Emphases of correctness work of causality tokens: tablesByIdVv. > # Reflect cross components interactions. Components: Schema manager, SQL > manager (SqlQueryProcessor), Affinity manager (it is not dedicated for now). > > Description of the following flows are needed: > # As it is now > # As it should be > # Possible fast improvements that could help to solve hot problems -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-15248) JDBC driver for 3.0: Transactions support.
[ https://issues.apache.org/jira/browse/IGNITE-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-15248. Resolution: Duplicate duplicate of IGNITE-18985 > JDBC driver for 3.0: Transactions support. > -- > > Key: IGNITE-15248 > URL: https://issues.apache.org/jira/browse/IGNITE-15248 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0 > > > Implement Driver interface and connection management on top of Ignite client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-16432) JDBC driver for 3.0: Call COMMIT and ROLLBACK queries when sql transaction support is done
[ https://issues.apache.org/jira/browse/IGNITE-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-16432. Resolution: Invalid > JDBC driver for 3.0: Call COMMIT and ROLLBACK queries when sql transaction > support is done > -- > > Key: IGNITE-16432 > URL: https://issues.apache.org/jira/browse/IGNITE-16432 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vladimir Ermakov >Assignee: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > > It is necessary to add "COMMIT" and "ROLLBACK" calls in JdbcConnection#commit > and JdbcConnection#rollback methods after transaction support for sql engine > is done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18988) Add missing test dependencies to DIRECT-IO
[ https://issues.apache.org/jira/browse/IGNITE-18988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18988: - Fix Version/s: 2.15 > Add missing test dependencies to DIRECT-IO > -- > > Key: IGNITE-18988 > URL: https://issues.apache.org/jira/browse/IGNITE-18988 > Project: Ignite > Issue Type: Test >Affects Versions: 2.14 >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.15 > > Time Spent: 10m > Remaining Estimate: 0h > > [Failing > suite|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsDirectIo1?branch=%3Cdefault%3E=overview=builds=false=true=false#7085007] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18988) Add missing test dependencies to DIRECT-IO
[ https://issues.apache.org/jira/browse/IGNITE-18988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18988: - Affects Version/s: 2.14 > Add missing test dependencies to DIRECT-IO > -- > > Key: IGNITE-18988 > URL: https://issues.apache.org/jira/browse/IGNITE-18988 > Project: Ignite > Issue Type: Test >Affects Versions: 2.14 >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > [Failing > suite|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsDirectIo1?branch=%3Cdefault%3E=overview=builds=false=true=false#7085007] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-15250) JDBC driver for 3.0: Support SET command on client.
[ https://issues.apache.org/jira/browse/IGNITE-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-15250. Resolution: Invalid > JDBC driver for 3.0: Support SET command on client. > --- > > Key: IGNITE-15250 > URL: https://issues.apache.org/jira/browse/IGNITE-15250 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Let's support SET command on Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18858) Prepare technical design for the distribution zones filter feature
[ https://issues.apache.org/jira/browse/IGNITE-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-18858: - Fix Version/s: 3.0.0-beta2 (was: 3.0.0-beta1) > Prepare technical design for the distribution zones filter feature > -- > > Key: IGNITE-18858 > URL: https://issues.apache.org/jira/browse/IGNITE-18858 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > We need to prepare technical design for the distribution zones filter feature > and prepare breakdown on tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-18744) Implement primary replica side leaseGrant handler
[ https://issues.apache.org/jira/browse/IGNITE-18744 ] Denis Chudov deleted comment on IGNITE-18744: --- was (Author: denis chudov): PR: [https://github.com/apache/ignite-3/pull/1765] Some integration tests started to fail, investigation in progress > Implement primary replica side leaseGrant handler > - > > Key: IGNITE-18744 > URL: https://issues.apache.org/jira/browse/IGNITE-18744 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > h3. Motivation > Primary replica candidate should properly handle leaseGrant message. In case > of RAFT following steps are expected: > * After receiving leaseGrant(force = false) message primary replica > candidate (the one that have received the message) should check whether group > is ready (meaning that leader is elected) or await leader election. So, > reactive communication is expected here. > * On leader election or on leader detection: > ** if leader isn't collocated with primary replica candidate, primary > replica candidate should send leaseGrantResp that assumes primary replica > redirect. > ** send leaseGrantResp[OK] > h3. Definition of Done > * PD retrieves leaseGranted > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18744) Implement primary replica side leaseGrant handler
[ https://issues.apache.org/jira/browse/IGNITE-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698365#comment-17698365 ] Denis Chudov commented on IGNITE-18744: --- PR: [https://github.com/apache/ignite-3/pull/1765] Some integration tests started to fail, investigation in progress > Implement primary replica side leaseGrant handler > - > > Key: IGNITE-18744 > URL: https://issues.apache.org/jira/browse/IGNITE-18744 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Denis Chudov >Priority: Major > Labels: ignite-3 > > h3. Motivation > Primary replica candidate should properly handle leaseGrant message. In case > of RAFT following steps are expected: > * After receiving leaseGrant(force = false) message primary replica > candidate (the one that have received the message) should check whether group > is ready (meaning that leader is elected) or await leader election. So, > reactive communication is expected here. > * On leader election or on leader detection: > ** if leader isn't collocated with primary replica candidate, primary > replica candidate should send leaseGrantResp that assumes primary replica > redirect. > ** send leaseGrantResp[OK] > h3. Definition of Done > * PD retrieves leaseGranted > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-18858) Prepare technical design for the distribution zones filter feature
[ https://issues.apache.org/jira/browse/IGNITE-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev resolved IGNITE-18858. -- Fix Version/s: 3.0.0-beta1 Resolution: Done > Prepare technical design for the distribution zones filter feature > -- > > Key: IGNITE-18858 > URL: https://issues.apache.org/jira/browse/IGNITE-18858 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > > We need to prepare technical design for the distribution zones filter feature > and prepare breakdown on tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-15249) JDBC driver for 3.0: Internal SQL API.
[ https://issues.apache.org/jira/browse/IGNITE-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich resolved IGNITE-15249. Resolution: Invalid > JDBC driver for 3.0: Internal SQL API. > -- > > Key: IGNITE-15249 > URL: https://issues.apache.org/jira/browse/IGNITE-15249 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Design internal API for SQL queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16204) Calcite integration. Add JDBC tests when INDEX support is appeared
[ https://issues.apache.org/jira/browse/IGNITE-16204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-16204: --- Description: Let's remove muted test > Calcite integration. Add JDBC tests when INDEX support is appeared > -- > > Key: IGNITE-16204 > URL: https://issues.apache.org/jira/browse/IGNITE-16204 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Vladimir Ermakov >Priority: Major > Labels: ignite-3 > > Let's remove muted test -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18988) Add missing test dependencies to DIRECT-IO
[ https://issues.apache.org/jira/browse/IGNITE-18988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-18988: - Description: [Failing suite|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsDirectIo1?branch=%3Cdefault%3E=overview=builds=false=true=false#7085007] > Add missing test dependencies to DIRECT-IO > -- > > Key: IGNITE-18988 > URL: https://issues.apache.org/jira/browse/IGNITE-18988 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > > [Failing > suite|https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsDirectIo1?branch=%3Cdefault%3E=overview=builds=false=true=false#7085007] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18988) Add missing test dependencies to DIRECT-IO
Ivan Daschinsky created IGNITE-18988: Summary: Add missing test dependencies to DIRECT-IO Key: IGNITE-18988 URL: https://issues.apache.org/jira/browse/IGNITE-18988 Project: Ignite Issue Type: Test Reporter: Ivan Daschinsky Assignee: Ivan Daschinsky -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18980) Fix REST status code in case of failed request
[ https://issues.apache.org/jira/browse/IGNITE-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Amelchev updated IGNITE-18980: - Summary: Fix REST status code in case of failed request (was: Fix REST status code in case of failed cluster state change) > Fix REST status code in case of failed request > -- > > Key: IGNITE-18980 > URL: https://issues.apache.org/jira/browse/IGNITE-18980 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Nikita Amelchev >Priority: Major > Labels: ise > Fix For: 2.15 > > Attachments: RestProcessorSuccessStatusTest.java > > Time Spent: 10m > Remaining Estimate: 0h > > _GridRestResponse_ should obtain proper 'not-OK' status on error. Often, > _GridRestResponse#getSuccessStatus()_ is `GridRestResponse#STATUS_SUCCESS` > even if the response is actually an error. > Probably, we should revise _GridRestResponse#setError(String)_. It should > set/check an error status like _GridRestResponse(int status, @Nullable String > err)_ > A test attached. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18963) Altering filters must recalculate data nodes
[
https://issues.apache.org/jira/browse/IGNITE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-18963:
-
Description:
{*}Motivation{*}:
Altering filters form the SQL must lead to data nodes recalculation.
*Definition of done:*
* Altering filters form the SQL leads to data nodes recalculation.
* Any scale up timers must be canceled and corresponding nodes must be included
in data nodes if filter were altered and data nodes recalculation was
triggered.
*Implementation details:*
Proper algorithm must be implemented under the ticket, currently is unclear how
we guarantee atomic cancel of existing scale up timers and data nodes
recalculation.
The list of open questions that we have to address to implement this feature
properly:
1) How should we handle situation, when alter filter event and scale up event
happen at the same time?
1.1) We should be able to handle the situation, when we had concurrent scale
up and alter filter event, and if we decide to cancel scale up, it is possible,
that new scale up with the greater revision has already rescheduled this timer
concurrently, so if we cancel that scale up, we could loose the latest scale up
event.
Scenario would look like this:
Topology = [A,B,C], filter is (A, B), data nodes = [A,B]
# Node D is added, timers for scale up are set to 5 minutes
# Node E is added, timers for scale up are rescheduled
# Change filter to filter(A, B, D, E) before scale up timer is up, revision of
event is 10
# Node F is added concurrently, with revision 11, which is also fits the
filter, timer is rescheduled
#* Here we come to the situation, where change filter event must cancel scale
up, but it cannot cancel it, because node F was added and scale up for that
must be triggered later.
#* Event about node F adding is not visible for change filter (in topology
augmentation map), because it has higher revision
# Nodes [A, B, D, E] will be as data nodes after filter change event
# Scale Up is triggered and [A, B, D, E, F] is a new data nodes.
2) Currently, we have topologyAugmentationMap and data nodes are stored as map
node -> counter. When we apply filter, we don't want to remove corresponding
node from the map in metastore, if node do not pass filter. The reason is
because filter could be changed in the future, and node could pass filter after
that, meaning that we must be able to understand, do we need to include this
node according to the scale up/scale down events.
Taking into account scenario 1, I propose to not cancel scale up timers after
filter was changed and treat that event as immediate scale up. In terms of
code, filter change will immediately call
{{DistributionZoneManager#saveDataNodesToMetaStorageOnScaleUp(zoneId, rev)}}
where {{rev}} is the revision of the filter change. With that solution, we
automatically defenced against any concurrent scale up, because we trigger
{{saveDataNodesToMetaStorageOnScaleUp}} with the corresponding revision of the
event.
Lets consider some examples:
1)
Topology = [A,B,C], filter is (A, B), data nodes = [A,B]
# Node D is added, timers for scale up are set to 5 minutes
# Node E is added, timers for scale up are rescheduled, revision of the event
is 7
# Change filter to filter(A, B, D, E) before scale up timer is up, revision of
event is 10
# {{saveDataNodesToMetaStorageOnScaleUp(rev = 10)}} is triggered, nodes [A, B,
D, E, F] will be as data nodes after filter change event, set
{{zoneScaleUpChangeTriggerKey}} as 10
# Scale up event with the revision 7 is running,
saveDataNodesToMetaStorageOnScaleUp(rev = 7) is triggered it will not pass the
condition for {{zoneScaleUpChangeTriggerKey}} and just will be skipped
2)
# Node D is added, timers for scale up are set to 5 minutes
# Node E is added, timers for scale up are rescheduled, revision of the event
is 7
# Change filter to filter(A, B, D, E) before scale up timer is up, revision of
event is 10
# Node F is added concurrently, with revision 11, which is also fits the
filter, timer is rescheduled
# saveDataNodesToMetaStorageOnScaleUp(rev = 10) is triggered, nodes [A, B, D,
E] will be as data nodes after filter change event, set
zoneScaleUpChangeTriggerKey as 10
# Scale up event with the revision 11 is running,
{{saveDataNodesToMetaStorageOnScaleUp(rev = 11) is triggered}} and data nodes
will be recalculated to [A, B, D, E, F]
was:
{*}Motivation{*}:
Altering filters form the SQL must lead to data nodes recalculation.
*Definition of done:*
* Altering filters form the SQL leads to data nodes recalculation.
* Any scale up timers must be canceled and corresponding nodes must be included
in data nodes if filter were altered and data nodes recalculation was
triggered.
*Implementation details:*
Proper algorithm must be implemented under the ticket, currently is unclear how
we guarantee atomic cancel of existing scale up
[jira] [Assigned] (IGNITE-18910) Add ability for Ignite Plugins to register their classes as trusted by Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-18910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov reassigned IGNITE-18910: --- Assignee: Mikhail Petrov > Add ability for Ignite Plugins to register their classes as trusted by > Ignite. > --- > > Key: IGNITE-18910 > URL: https://issues.apache.org/jira/browse/IGNITE-18910 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We are currently skipping security checks for the internal classes (e.g. > after [IGNITE-15322|https://issues.apache.org/jira/browse/IGNITE-15322] we > skip authorization of internal tasks.). We recognize internal class as those > that are located in the security-core.jar. > We need to provide the ability for Ignite Plugins to declare their own > classes as Ignite internal classes. It helps to skip unnecessary security > checks for custom plugin code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18916) .NET: Thin 3.0 Add SQL tests with UUID columns
[ https://issues.apache.org/jira/browse/IGNITE-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-18916: --- Assignee: Pavel Tupitsyn > .NET: Thin 3.0 Add SQL tests with UUID columns > -- > > Key: IGNITE-18916 > URL: https://issues.apache.org/jira/browse/IGNITE-18916 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Now when UUID support is implemented for SQL core > (https://issues.apache.org/jira/browse/IGNITE-16376), we need to add tests > with UUID columns to clients to ensure that everything works well in clients. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18546) Add cache clear command to control.sh
[
https://issues.apache.org/jira/browse/IGNITE-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698256#comment-17698256
]
Ignite TC Bot commented on IGNITE-18546:
{panel:title=Branch: [pull/10589/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10589/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7084705buildTypeId=IgniteTests24Java8_RunAll]
> Add cache clear command to control.sh
> --
>
> Key: IGNITE-18546
> URL: https://issues.apache.org/jira/browse/IGNITE-18546
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Maksim Timonin
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> IgniteCache provides a functionality for clearing cache (IgniteCache#clear).
> Users might want clear cache for test purposes by remote job (Jenkins, etc.).
> Then it will be useful to provide opportunity to clean cache by control.sh
> util.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
