[jira] [Updated] (IGNITE-22162) Add support for using selected affinity function in distribution zones
[
https://issues.apache.org/jira/browse/IGNITE-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-22162:
--
Labels: iep-101 ignite-3 (was: ignite-3)
> Add support for using selected affinity function in distribution zones
> --
>
> Key: IGNITE-22162
> URL: https://issues.apache.org/jira/browse/IGNITE-22162
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: iep-101, ignite-3
>
> According to
> [IEP-101|https://cwiki.apache.org/confluence/display/IGNITE/IEP-101%253A+Distribution+Zones]
> the user can select a different affinity function when creating a
> distribution zone.
> For example:
> {code:SQL}
> CREATE ZONE test WITH AFFINITY_FUNCTION='fair_affinity'...
> {code}
> The provided value is not currently processed in any way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22162) Add support for using selected affinity function in distribution zones
Pavel Pereslegin created IGNITE-22162:
-
Summary: Add support for using selected affinity function in
distribution zones
Key: IGNITE-22162
URL: https://issues.apache.org/jira/browse/IGNITE-22162
Project: Ignite
Issue Type: Improvement
Reporter: Pavel Pereslegin
According to
[IEP-101|https://cwiki.apache.org/confluence/display/IGNITE/IEP-101%253A+Distribution+Zones]
the user can select a different affinity function when creating a distribution
zone.
For example:
{code:SQL}
CREATE ZONE test WITH AFFINITY_FUNCTION='fair_affinity'...
{code}
The provided value is not currently processed in any way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22159) Sql. Update outdated muted tests
[ https://issues.apache.org/jira/browse/IGNITE-22159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843002#comment-17843002 ] Iurii Gerzhedovich commented on IGNITE-22159: - [~zstan] could you please review the patch? > Sql. Update outdated muted tests > > > Key: IGNITE-22159 > URL: https://issues.apache.org/jira/browse/IGNITE-22159 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We have a bunch of muted tests which have already been fixed. > Let's unmute it and close relevant tickets: > IGNITE-17374 > IGNITE-18379 > IGNITE-18656 > IGNITE-18657 > IGNITE-18658 > IGNITE-18659 > IGNITE-18660 > IGNITE-18661 > IGNITE-18671 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22161) Sql. Infinity error-loop for simple query
[
https://issues.apache.org/jira/browse/IGNITE-22161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-22161:
Priority: Blocker (was: Major)
> Sql. Infinity error-loop for simple query
> -
>
> Key: IGNITE-22161
> URL: https://issues.apache.org/jira/browse/IGNITE-22161
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Blocker
> Labels: ignite-3
>
> An infinity error loop for the following query occurred:
> {code:java}
> CREATE TABLE cc_(key int, val varchar DEFAULT \"defaultValue\" primary
> key){code}
> error:
> {code:java}
> [2024-05-02T17:04:41,397][ERROR][%isaat_n_1%JRaft-FSMCaller-Disruptormetastorage_stripe_0-0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue]]
> java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.andTree(CompletableFuture.java:1527)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.allOf(CompletableFuture.java:2419)
> ~[?:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:258)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> ~[main/:?]
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:842) [?:?]
> Caused by: java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at java.base/java.lang.Enum.valueOf(Enum.java:273) ~[?:?]
> at
> org.apache.ignite.internal.schema.DefaultValueGenerator.valueOf(DefaultValueGenerator.java:29)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:138)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:162)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaUtils.prepareSchemaDescriptor(SchemaUtils.java:37)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreatedOrAltered(SchemaManager.java:147)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreated(SchemaManager.java:119)
> ~[main/:?]
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> ~[main/:?]
> ... 6 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22161) Sql. Infinity error-loop for simple query
Iurii Gerzhedovich created IGNITE-22161:
---
Summary: Sql. Infinity error-loop for simple query
Key: IGNITE-22161
URL: https://issues.apache.org/jira/browse/IGNITE-22161
Project: Ignite
Issue Type: Improvement
Reporter: Iurii Gerzhedovich
An infinity error loop for the following query occurred:
{code:java}
CREATE TABLE cc_(key int, val varchar DEFAULT \"defaultValue\" primary
key){code}
error:
{code:java}
[2024-05-02T17:04:41,397][ERROR][%isaat_n_1%JRaft-FSMCaller-Disruptormetastorage_stripe_0-0][FailureProcessor]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=java.util.concurrent.CompletionException:
java.lang.IllegalArgumentException: No enum constant
org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue]]
java.util.concurrent.CompletionException: java.lang.IllegalArgumentException:
No enum constant
org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.andTree(CompletableFuture.java:1527)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture.allOf(CompletableFuture.java:2419)
~[?:?]
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:258)
~[main/:?]
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
~[main/:?]
at
java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
~[?:?]
at
java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
~[?:?]
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
~[?:?]
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
~[?:?]
at java.base/java.lang.Thread.run(Thread.java:842) [?:?]
Caused by: java.lang.IllegalArgumentException: No enum constant
org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
at java.base/java.lang.Enum.valueOf(Enum.java:273) ~[?:?]
at
org.apache.ignite.internal.schema.DefaultValueGenerator.valueOf(DefaultValueGenerator.java:29)
~[main/:?]
at
org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:138)
~[main/:?]
at
org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:162)
~[main/:?]
at
org.apache.ignite.internal.schema.SchemaUtils.prepareSchemaDescriptor(SchemaUtils.java:37)
~[main/:?]
at
org.apache.ignite.internal.schema.SchemaManager.onTableCreatedOrAltered(SchemaManager.java:147)
~[main/:?]
at
org.apache.ignite.internal.schema.SchemaManager.onTableCreated(SchemaManager.java:119)
~[main/:?]
at
org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
~[main/:?]
at
org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
~[main/:?]
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
~[main/:?]
at
org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
~[main/:?]
at
org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
~[main/:?]
at
org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
~[main/:?]
at
org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
~[main/:?]
... 6 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22161) Sql. Infinity error-loop for simple query
[
https://issues.apache.org/jira/browse/IGNITE-22161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-22161:
Component/s: sql
> Sql. Infinity error-loop for simple query
> -
>
> Key: IGNITE-22161
> URL: https://issues.apache.org/jira/browse/IGNITE-22161
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> An infinity error loop for the following query occurred:
> {code:java}
> CREATE TABLE cc_(key int, val varchar DEFAULT \"defaultValue\" primary
> key){code}
> error:
> {code:java}
> [2024-05-02T17:04:41,397][ERROR][%isaat_n_1%JRaft-FSMCaller-Disruptormetastorage_stripe_0-0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue]]
> java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.andTree(CompletableFuture.java:1527)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.allOf(CompletableFuture.java:2419)
> ~[?:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:258)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> ~[main/:?]
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:842) [?:?]
> Caused by: java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at java.base/java.lang.Enum.valueOf(Enum.java:273) ~[?:?]
> at
> org.apache.ignite.internal.schema.DefaultValueGenerator.valueOf(DefaultValueGenerator.java:29)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:138)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:162)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaUtils.prepareSchemaDescriptor(SchemaUtils.java:37)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreatedOrAltered(SchemaManager.java:147)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreated(SchemaManager.java:119)
> ~[main/:?]
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> ~[main/:?]
> ... 6 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17973) SQL. Using quotes in query break TableImpl
[
https://issues.apache.org/jira/browse/IGNITE-17973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich resolved IGNITE-17973.
-
Resolution: Cannot Reproduce
> SQL. Using quotes in query break TableImpl
> --
>
> Key: IGNITE-17973
> URL: https://issues.apache.org/jira/browse/IGNITE-17973
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> if execute the following statement
> {code:java}
> CREATE TABLE cc_(key int primary key, val varchar DEFAULT "defaultValue")
> {code}
> then got the exception
> {code:java}
> Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:4bda3acb-2622-40f5-bfb1-ec6fe1c1ca0b Argument for @NotNull parameter
> 'schemaReg' of org/apache/ignite/internal/table/TableImpl.schemaView must not
> be null at
> org.apache.ignite.internal.table.distributed.TableManager.getRootCause(TableManager.java:1281)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsyncInternal$38(TableManager.java:1170)
> ... 15 more Caused by: [CIRCULAR REFERENCE:
> java.lang.IllegalArgumentException: Argument for @NotNull parameter
> 'schemaReg' of org/apache/ignite/internal/table/TableImpl.schemaView must not
> be null]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22161) Sql. Infinity error-loop for simple query
[
https://issues.apache.org/jira/browse/IGNITE-22161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-22161:
Labels: ignite-3 (was: )
> Sql. Infinity error-loop for simple query
> -
>
> Key: IGNITE-22161
> URL: https://issues.apache.org/jira/browse/IGNITE-22161
> Project: Ignite
> Issue Type: Improvement
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> An infinity error loop for the following query occurred:
> {code:java}
> CREATE TABLE cc_(key int, val varchar DEFAULT \"defaultValue\" primary
> key){code}
> error:
> {code:java}
> [2024-05-02T17:04:41,397][ERROR][%isaat_n_1%JRaft-FSMCaller-Disruptormetastorage_stripe_0-0][FailureProcessor]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue]]
> java.util.concurrent.CompletionException:
> java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.andTree(CompletableFuture.java:1527)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture.allOf(CompletableFuture.java:2419)
> ~[?:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:258)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.lambda$notifyWatches$3(WatchProcessor.java:181)
> ~[main/:?]
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
> ~[?:?]
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:842) [?:?]
> Caused by: java.lang.IllegalArgumentException: No enum constant
> org.apache.ignite.internal.schema.DefaultValueGenerator.defaultValue
> at java.base/java.lang.Enum.valueOf(Enum.java:273) ~[?:?]
> at
> org.apache.ignite.internal.schema.DefaultValueGenerator.valueOf(DefaultValueGenerator.java:29)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:138)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.catalog.CatalogToSchemaDescriptorConverter.convert(CatalogToSchemaDescriptorConverter.java:162)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaUtils.prepareSchemaDescriptor(SchemaUtils.java:37)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreatedOrAltered(SchemaManager.java:147)
> ~[main/:?]
> at
> org.apache.ignite.internal.schema.SchemaManager.onTableCreated(SchemaManager.java:119)
> ~[main/:?]
> at
> org.apache.ignite.internal.event.AbstractEventProducer.fireEvent(AbstractEventProducer.java:88)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl.access$000(CatalogManagerImpl.java:91)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:562)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.CatalogManagerImpl$OnUpdateHandlerImpl.handle(CatalogManagerImpl.java:529)
> ~[main/:?]
> at
> org.apache.ignite.internal.catalog.storage.UpdateLogImpl$UpdateListener.onUpdate(UpdateLogImpl.java:314)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.Watch.onUpdate(Watch.java:67)
> ~[main/:?]
> at
> org.apache.ignite.internal.metastorage.server.WatchProcessor.notifyWatches(WatchProcessor.java:233)
> ~[main/:?]
> ... 6 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22160) Sql. Usability for error message in case of numeric overflow
[
https://issues.apache.org/jira/browse/IGNITE-22160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-22160:
Summary: Sql. Usability for error message in case of numeric overflow
(was: Sql. Usability for )
> Sql. Usability for error message in case of numeric overflow
> -
>
> Key: IGNITE-22160
> URL: https://issues.apache.org/jira/browse/IGNITE-22160
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> Let's consider error messages for the following queries:
> SELECT '1'::DECIMAL(3, 3)::VARCHAR;
> SELECT '-1'::DECIMAL(3, 3)::VARCHAR;
> SELECT '0.1'::DECIMAL(3, 4);
> Right now the queries expected to fail, but we have not so user-friendly
> error messages like a
> {code:java}
> IGN-SQL-9 TraceId:0460f382-120f-49a4-9ee2-e09ee90d4764 Numeric field
> overflow{code}
> For example, an error in PG looks so:
> {code:java}
> ERROR: numeric field overflow DETAIL: A field with precision 3, scale 4 must
> round to an absolute value less than 10^-1.
>
> {code}
> Let's improve error messages.
> Start point is using of
> {code:java}
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator#NUMERIC_FIELD_OVERFLOW_ERROR{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22160) Sql. Usability for
Iurii Gerzhedovich created IGNITE-22160:
---
Summary: Sql. Usability for
Key: IGNITE-22160
URL: https://issues.apache.org/jira/browse/IGNITE-22160
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Iurii Gerzhedovich
Let's consider error messages for the following queries:
SELECT '1'::DECIMAL(3, 3)::VARCHAR;
SELECT '-1'::DECIMAL(3, 3)::VARCHAR;
SELECT '0.1'::DECIMAL(3, 4);
Right now the queries expected to fail, but we have not so user-friendly error
messages like a
{code:java}
IGN-SQL-9 TraceId:0460f382-120f-49a4-9ee2-e09ee90d4764 Numeric field
overflow{code}
For example, an error in PG looks so:
{code:java}
ERROR: numeric field overflow DETAIL: A field with precision 3, scale 4 must
round to an absolute value less than 10^-1.
{code}
Let's improve error messages.
Start point is using of
{code:java}
org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator#NUMERIC_FIELD_OVERFLOW_ERROR{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22160) Sql. Usability of error message in case of numeric overflow
[
https://issues.apache.org/jira/browse/IGNITE-22160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-22160:
Summary: Sql. Usability of error message in case of numeric overflow
(was: Sql. Usability for error message in case of numeric overflow )
> Sql. Usability of error message in case of numeric overflow
>
>
> Key: IGNITE-22160
> URL: https://issues.apache.org/jira/browse/IGNITE-22160
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> Let's consider error messages for the following queries:
> SELECT '1'::DECIMAL(3, 3)::VARCHAR;
> SELECT '-1'::DECIMAL(3, 3)::VARCHAR;
> SELECT '0.1'::DECIMAL(3, 4);
> Right now the queries expected to fail, but we have not so user-friendly
> error messages like a
> {code:java}
> IGN-SQL-9 TraceId:0460f382-120f-49a4-9ee2-e09ee90d4764 Numeric field
> overflow{code}
> For example, an error in PG looks so:
> {code:java}
> ERROR: numeric field overflow DETAIL: A field with precision 3, scale 4 must
> round to an absolute value less than 10^-1.
>
> {code}
> Let's improve error messages.
> Start point is using of
> {code:java}
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator#NUMERIC_FIELD_OVERFLOW_ERROR{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17287) SchemaSerializerImpl and ClientMessagePacker have the same types (un)pack code functionality, deduplication needed.
[
https://issues.apache.org/jira/browse/IGNITE-17287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-17287.
---
Resolution: Invalid
SchemaSerializerImpl was removed in IGNITE-19744
> SchemaSerializerImpl and ClientMessagePacker have the same types (un)pack
> code functionality, deduplication needed.
> ---
>
> Key: IGNITE-17287
> URL: https://issues.apache.org/jira/browse/IGNITE-17287
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Priority: Major
> Labels: ignite-3
>
> ByteBuffer vs Netty.ByteBuf are also difference, but seems its not a problem.
> Check for example:
> ClientMessagePacker#packDateTime:
> {code:java}
> public void packDateTime(LocalDateTime val) {
> packExtensionTypeHeader(ClientMsgPackType.DATETIME);
> buf.writeInt(val.getYear());
> buf.writeByte(val.getMonthValue());
> buf.writeByte(val.getDayOfMonth());
> buf.writeByte(val.getHour());
> buf.writeByte(val.getMinute());
> buf.writeByte(val.getSecond());
> buf.writeInt(val.getNano());
> }
> {code}
> SchemaSerializerImpl#appendDefaultValue
> {code:java}
> case DATETIME: {
> LocalDateTime date = (LocalDateTime) val;
> buf.putInt(date.getYear());
> buf.put((byte) date.getMonthValue());
> buf.put((byte) date.getDayOfMonth());
> buf.put((byte) date.getHour());
> buf.put((byte) date.getMinute());
> buf.put((byte) date.getSecond());
> buf.putInt(date.getNano());
> break;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18659) Sql. Decimal-decimal overflow cast error does not occur
[
https://issues.apache.org/jira/browse/IGNITE-18659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18659:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal-decimal overflow cast error does not occur
> ---
>
> Key: IGNITE-18659
> URL: https://issues.apache.org/jira/browse/IGNITE-18659
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> Casting from one decimal type to another does not produce errors when
> scale/precision is changed:
> {code:java}
> statement error
> SELECT 10.00::DECIMAL(4,2)::DECIMAL(2,1);
> {code}
> See skipif-ed examples in decimal_decimal_overflow_cast.test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22156) Improve test coverage for UpgradingRowAdapter.
[ https://issues.apache.org/jira/browse/IGNITE-22156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-22156: -- Fix Version/s: 3.0.0-beta2 > Improve test coverage for UpgradingRowAdapter. > -- > > Key: IGNITE-22156 > URL: https://issues.apache.org/jira/browse/IGNITE-22156 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Critical > Labels: ignite-3, tech-debt > Fix For: 3.0.0-beta2 > > > As fow now, we have no unit tests for UpgradingRowAdapter class at all. > `UpgradingRowAdapter` class inherits a bunch of methods from various > interfaces, which are implemented in parent classes. We found few issues when > some of these methods must be overridden in `UpgradingRowAdapter` due to > different semantic. > Also, with the current approach, the one may add a method that implementation > will have incorrect behavior in UpgradingRowAdapter. > Most likely, `inheritance` from base `Row` class should be changed to > `delegation`, and a `Row` be an interface. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22156) Improve test coverage for UpgradingRowAdapter.
[ https://issues.apache.org/jira/browse/IGNITE-22156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-22156: - Assignee: Andrey Mashenkov > Improve test coverage for UpgradingRowAdapter. > -- > > Key: IGNITE-22156 > URL: https://issues.apache.org/jira/browse/IGNITE-22156 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Critical > Labels: ignite-3, tech-debt > > As fow now, we have no unit tests for UpgradingRowAdapter class at all. > `UpgradingRowAdapter` class inherits a bunch of methods from various > interfaces, which are implemented in parent classes. We found few issues when > some of these methods must be overridden in `UpgradingRowAdapter` due to > different semantic. > Also, with the current approach, the one may add a method that implementation > will have incorrect behavior in UpgradingRowAdapter. > Most likely, `inheritance` from base `Row` class should be changed to > `delegation`, and a `Row` be an interface. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22159) Sql. Update outdated muted tests
[ https://issues.apache.org/jira/browse/IGNITE-22159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-22159: Description: We have a bunch of muted tests which have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18379 IGNITE-18656 IGNITE-18657 IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 was: We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18379 IGNITE-18656 IGNITE-18657 IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 > Sql. Update outdated muted tests > > > Key: IGNITE-22159 > URL: https://issues.apache.org/jira/browse/IGNITE-22159 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We have a bunch of muted tests which have already been fixed. > Let's unmute it and close relevant tickets: > IGNITE-17374 > IGNITE-18379 > IGNITE-18656 > IGNITE-18657 > IGNITE-18658 > IGNITE-18659 > IGNITE-18660 > IGNITE-18661 > IGNITE-18671 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22159) Sql. Update outdated muted tests
[ https://issues.apache.org/jira/browse/IGNITE-22159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-22159: Description: We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18379 IGNITE-18656 IGNITE-18657 IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 was: We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18656 IGNITE-18657 IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 > Sql. Update outdated muted tests > > > Key: IGNITE-22159 > URL: https://issues.apache.org/jira/browse/IGNITE-22159 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We have a bunch of muted tests wich have already been fixed. > Let's unmute it and close relevant tickets: > IGNITE-17374 > IGNITE-18379 > IGNITE-18656 > IGNITE-18657 > IGNITE-18658 > IGNITE-18659 > IGNITE-18660 > IGNITE-18661 > IGNITE-18671 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22159) Sql. Update outdated muted tests
[ https://issues.apache.org/jira/browse/IGNITE-22159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich reassigned IGNITE-22159: --- Assignee: Iurii Gerzhedovich > Sql. Update outdated muted tests > > > Key: IGNITE-22159 > URL: https://issues.apache.org/jira/browse/IGNITE-22159 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We have a bunch of muted tests wich have already been fixed. > Let's unmute it and close relevant tickets: > IGNITE-17374 > IGNITE-18656 > IGNITE-18657 > IGNITE-18658 > IGNITE-18659 > IGNITE-18660 > IGNITE-18661 > IGNITE-18671 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22159) Sql. Update outdated muted tests
[ https://issues.apache.org/jira/browse/IGNITE-22159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-22159: Description: We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18656 IGNITE-18657 IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 was: We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18656 IGNITE-18657IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 > Sql. Update outdated muted tests > > > Key: IGNITE-22159 > URL: https://issues.apache.org/jira/browse/IGNITE-22159 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Priority: Major > Labels: ignite-3 > > We have a bunch of muted tests wich have already been fixed. > Let's unmute it and close relevant tickets: > IGNITE-17374 > IGNITE-18656 > IGNITE-18657 > IGNITE-18658 > IGNITE-18659 > IGNITE-18660 > IGNITE-18661 > IGNITE-18671 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22159) Sql. Update outdated muted tests
Iurii Gerzhedovich created IGNITE-22159: --- Summary: Sql. Update outdated muted tests Key: IGNITE-22159 URL: https://issues.apache.org/jira/browse/IGNITE-22159 Project: Ignite Issue Type: Improvement Components: sql Reporter: Iurii Gerzhedovich We have a bunch of muted tests wich have already been fixed. Let's unmute it and close relevant tickets: IGNITE-17374 IGNITE-18656 IGNITE-18657IGNITE-18658 IGNITE-18659 IGNITE-18660 IGNITE-18661 IGNITE-18671 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21998) .NET: TestSchemaUpdateWhileStreaming is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-21998.
-
Resolution: Cannot Reproduce
> .NET: TestSchemaUpdateWhileStreaming is flaky
> -
>
> Key: IGNITE-21998
> URL: https://issues.apache.org/jira/browse/IGNITE-21998
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.0.0-beta2
>
>
> https://ci.ignite.apache.org/test/4007460749051703227?currentProjectId=ApacheIgnite3xGradle_Test=%3Cdefault%3E=true
> Fails due to a 15s timeout or throws an exception:
> {code}
> Apache.Ignite.IgniteException : Table schema was updated after the
> transaction was started [table=108, startSchema=1, operationSchema=2]
> > Apache.Ignite.IgniteException :
> org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
> IGN-TX-12 TraceId:e32316b9-eb22-49b2-a45b-01ecb067da4f Table schema was
> updated after the transaction was started [table=108, startSchema=1,
> operationSchema=2]
> at
> org.apache.ignite.internal.table.distributed.replicator.SchemaCompatibilityValidator.failIfSchemaChangedAfterTxStart(SchemaCompatibilityValidator.java:238)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.failIfSchemaChangedSinceTxStart(PartitionReplicaListener.java:3788)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$validateWriteAgainstSchemaAfterTakingLocks$215(PartitionReplicaListener.java:3713)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateWriteAgainstSchemaAfterTakingLocks(PartitionReplicaListener.java:3712)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processMultiEntryAction$106(PartitionReplicaListener.java:2377)
> at
> java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> at
> java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processMultiEntryAction(PartitionReplicaListener.java:2349)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processOperationRequest$11(PartitionReplicaListener.java:644)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1926)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequest(PartitionReplicaListener.java:644)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequestWithTxRwCounter(PartitionReplicaListener.java:3923)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$5(PartitionReplicaListener.java:440)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> 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)
>at Apache.Ignite.Internal.ClientSocket.DoOutInOpAsyncInternal(ClientOp
> clientOp, PooledArrayBuffer request, Boolean expectNotifications) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite/Internal/ClientSocket.cs:line
> 626
>at
> Apache.Ignite.Internal.ClientFailoverSocket.DoOutInOpAndGetSocketAsync(ClientOp
> clientOp, Transaction tx, PooledArrayBuffer request, PreferredNode
> preferredNode, IRetryPolicy retryPolicyOverride, Boolean expectNotifications)
> in
>
[jira] [Commented] (IGNITE-21998) .NET: TestSchemaUpdateWhileStreaming is flaky
[
https://issues.apache.org/jira/browse/IGNITE-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842950#comment-17842950
]
Pavel Tupitsyn commented on IGNITE-21998:
-
Fixed by IGNITE-20416. 100% stable in *main* for the last 83 runs.
> .NET: TestSchemaUpdateWhileStreaming is flaky
> -
>
> Key: IGNITE-21998
> URL: https://issues.apache.org/jira/browse/IGNITE-21998
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.0.0-beta2
>
>
> https://ci.ignite.apache.org/test/4007460749051703227?currentProjectId=ApacheIgnite3xGradle_Test=%3Cdefault%3E=true
> Fails due to a 15s timeout or throws an exception:
> {code}
> Apache.Ignite.IgniteException : Table schema was updated after the
> transaction was started [table=108, startSchema=1, operationSchema=2]
> > Apache.Ignite.IgniteException :
> org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException:
> IGN-TX-12 TraceId:e32316b9-eb22-49b2-a45b-01ecb067da4f Table schema was
> updated after the transaction was started [table=108, startSchema=1,
> operationSchema=2]
> at
> org.apache.ignite.internal.table.distributed.replicator.SchemaCompatibilityValidator.failIfSchemaChangedAfterTxStart(SchemaCompatibilityValidator.java:238)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.failIfSchemaChangedSinceTxStart(PartitionReplicaListener.java:3788)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$validateWriteAgainstSchemaAfterTakingLocks$215(PartitionReplicaListener.java:3713)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyNow(CompletableFuture.java:680)
> at
> java.base/java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:658)
> at
> java.base/java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:2094)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.validateWriteAgainstSchemaAfterTakingLocks(PartitionReplicaListener.java:3712)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processMultiEntryAction$106(PartitionReplicaListener.java:2377)
> at
> java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1106)
> at
> java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2235)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processMultiEntryAction(PartitionReplicaListener.java:2349)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processOperationRequest$11(PartitionReplicaListener.java:644)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.appendTxCommand(PartitionReplicaListener.java:1926)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequest(PartitionReplicaListener.java:644)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.processOperationRequestWithTxRwCounter(PartitionReplicaListener.java:3923)
> at
> org.apache.ignite.internal.table.distributed.replicator.PartitionReplicaListener.lambda$processRequest$5(PartitionReplicaListener.java:440)
> at
> java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1072)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
> 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)
>at Apache.Ignite.Internal.ClientSocket.DoOutInOpAsyncInternal(ClientOp
> clientOp, PooledArrayBuffer request, Boolean expectNotifications) in
> /opt/buildagent/work/b8d4df1365f1f1e5/modules/platforms/dotnet/Apache.Ignite/Internal/ClientSocket.cs:line
> 626
>at
> Apache.Ignite.Internal.ClientFailoverSocket.DoOutInOpAndGetSocketAsync(ClientOp
> clientOp, Transaction tx, PooledArrayBuffer request, PreferredNode
> preferredNode, IRetryPolicy retryPolicyOverride, Boolean expectNotifications)
> in
>
[jira] [Commented] (IGNITE-21962) ignite-client-handler tests fail due to hardcoded handshake response size
[ https://issues.apache.org/jira/browse/IGNITE-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842945#comment-17842945 ] Pavel Tupitsyn commented on IGNITE-21962: - Merged to main: [ef50f41d934ed7edd327155184809db4ea9c5e9f|https://github.com/apache/ignite-3/commit/ef50f41d934ed7edd327155184809db4ea9c5e9f] > ignite-client-handler tests fail due to hardcoded handshake response size > - > > Key: IGNITE-21962 > URL: https://issues.apache.org/jira/browse/IGNITE-21962 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > The following tests fail if you change *IgniteProductVersion.CURRENT_VERSION* > so that the string length is different, because handshake response size > changes: > > * > *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22158) Sql. incorrect result of NATURAL JOIN for BIGINTEGER column on condition
Iurii Gerzhedovich created IGNITE-22158:
---
Summary: Sql. incorrect result of NATURAL JOIN for BIGINTEGER
column on condition
Key: IGNITE-22158
URL: https://issues.apache.org/jira/browse/IGNITE-22158
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Iurii Gerzhedovich
If we do natural join for tables containing BIGINT columns we have an incorrect
empty result.
{code:java}
CREATE TABLE t1 (a INTEGER, b INTEGER)
INSERT INTO t1 VALUES (1, 2)
CREATE TABLE t2 (a BIGINT, c BIGINT)
INSERT INTO t2 VALUES (1, 3), (2, 4)
SELECT * FROM t1 NATURAL JOIN t2 - return nothing {code}
reference - test/sql/join/natural/natural_join.test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21962) ignite-client-handler tests fail due to hardcoded handshake response size
[ https://issues.apache.org/jira/browse/IGNITE-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842928#comment-17842928 ] Igor Sapego commented on IGNITE-21962: -- Looks good to me. > ignite-client-handler tests fail due to hardcoded handshake response size > - > > Key: IGNITE-21962 > URL: https://issues.apache.org/jira/browse/IGNITE-21962 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > The following tests fail if you change *IgniteProductVersion.CURRENT_VERSION* > so that the string length is different, because handshake response size > changes: > > * > *org.apache.ignite.client.handler.ItClientHandlerMetricsTest#testBytesSentReceived* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeWithAuthenticationValidCredentials* > * > *org.apache.ignite.client.handler.ItClientHandlerTest#testHandshakeValidReturnsSuccess* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18657) Sql. Decimal casts DECIMAL::VARCHAR
[
https://issues.apache.org/jira/browse/IGNITE-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18657:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal casts DECIMAL::VARCHAR
> ---
>
> Key: IGNITE-18657
> URL: https://issues.apache.org/jira/browse/IGNITE-18657
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following test cases in test_decimal.test do not fail:
> {code:java}
> # any value >= 1 becomes out of range, though
> skipif ignite3
> statement error
> SELECT '1'::DECIMAL(3, 3)::VARCHAR;
> skipif ignite3
> statement error
> SELECT '-1'::DECIMAL(3, 3)::VARCHAR;
> # various error conditions
> # scale must be bigger than or equal to width
> skipif ignite3
> statement error
> SELECT '0.1'::DECIMAL(3, 4);
> # width/scale out of range
> skipif ignite3
> statement error
> SELECT '0.1'::DECIMAL(1000);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18658) Sql. Decimal overflow error is not raised in arithmetic operations
[
https://issues.apache.org/jira/browse/IGNITE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18658:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal overflow error is not raised in arithmetic operations
> --
>
> Key: IGNITE-18658
> URL: https://issues.apache.org/jira/browse/IGNITE-18658
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following test cases are expected to fail
> {code:java}
> skipif ignite3
> statement error
> SELECT d+1000.0 FROM decimals
> skipif ignite3
> statement error
> SELECT -1000.0-d FROM decimals
> skipif ignite3
> statement error
> SELECT 2*d FROM decimals {code}
> There are other examples in decimal_overflow.test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17374) Sql. Unable to insert default value to VARBINARY column
[
https://issues.apache.org/jira/browse/IGNITE-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-17374:
---
Assignee: Iurii Gerzhedovich (was: Maksim Zhuravkov)
> Sql. Unable to insert default value to VARBINARY column
> ---
>
> Key: IGNITE-17374
> URL: https://issues.apache.org/jira/browse/IGNITE-17374
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Iurii Gerzhedovich
>Priority: Major
> Labels: ignite-3
>
> Exception is thrown when inserting a tuple with omitted VARBINARY column with
> specified default.
> Consider the following case:
> {code:java}
> CREATE TABLE t (id INT PRIMARY KEY, val VARBINARY DEAFULT x'010203');
> INSERT INTO t (id) VALUES (0);{code}
> Exception is:
> {noformat}
> org.apache.ignite.lang.IgniteException: IGN-CMN-1 Trace
> ID:a1504c58-d305-464a-aa87-2a137c3b88aa Compiling "SC" in Line 1, Column 1:
> Line 1, Column 13: Compiling
> "execute(org.apache.ignite.internal.sql.engine.exec.ExecutionContext ctx,
> Object in1, Object out)": Line 3, Column 52
> at
> org.apache.ignite.internal.sql.engine.AsyncSqlCursorImpl.lambda$requestNextAsync$0(AsyncSqlCursorImpl.java:74)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl$DistributedQueryManager.acknowledgeFragment(ExecutionServiceImpl.java:404)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl.onMessage(ExecutionServiceImpl.java:278)
> at
> org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImpl.lambda$start$3(ExecutionServiceImpl.java:172)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:174)
> at
> org.apache.ignite.internal.sql.engine.message.MessageServiceImpl.lambda$onMessage$4(MessageServiceImpl.java:137)
> at
> org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:80)
> 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: org.apache.ignite.lang.IgniteException: IGN-CMN-1 Trace
> ID:a1504c58-d305-464a-aa87-2a137c3b88aa Compiling "SC" in Line 1, Column 1:
> Line 1, Column 13: Compiling
> "execute(org.apache.ignite.internal.sql.engine.exec.ExecutionContext ctx,
> Object in1, Object out)": Line 3, Column 52
> at
> org.apache.ignite.internal.sql.engine.util.Commons.compile(Commons.java:487)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.compile(ExpressionFactoryImpl.java:364)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.lambda$scalar$4(ExpressionFactoryImpl.java:285)
> at
> com.github.benmanes.caffeine.cache.BoundedLocalCache.lambda$doComputeIfAbsent$13(BoundedLocalCache.java:2457)
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)
> at
> com.github.benmanes.caffeine.cache.BoundedLocalCache.doComputeIfAbsent(BoundedLocalCache.java:2455)
> at
> com.github.benmanes.caffeine.cache.BoundedLocalCache.computeIfAbsent(BoundedLocalCache.java:2438)
> at
> com.github.benmanes.caffeine.cache.LocalCache.computeIfAbsent(LocalCache.java:107)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.scalar(ExpressionFactoryImpl.java:284)
> at
> org.apache.ignite.internal.sql.engine.exec.exp.ExpressionFactoryImpl.project(ExpressionFactoryImpl.java:219)
> at
> org.apache.ignite.internal.sql.engine.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:201)
> at
> org.apache.ignite.internal.sql.engine.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:109)
> at
> org.apache.ignite.internal.sql.engine.rel.IgniteProject.accept(IgniteProject.java:92)
> at
> org.apache.ignite.internal.sql.engine.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:701)
> at
> org.apache.ignite.internal.sql.engine.exec.LogicalRelImplementor.visit(LogicalRelImplementor.java:711)
> at
>
[jira] [Commented] (IGNITE-21629) Add TLSv1_3 to o.a.i.client.SslProtocol
[ https://issues.apache.org/jira/browse/IGNITE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842910#comment-17842910 ] Pavel Tupitsyn commented on IGNITE-21629: - Merged to master: [9d9446d2ee956bcda35bcd51d7a10c8bb827b797|https://github.com/apache/ignite/commit/9d9446d2ee956bcda35bcd51d7a10c8bb827b797] > Add TLSv1_3 to o.a.i.client.SslProtocol > --- > > Key: IGNITE-21629 > URL: https://issues.apache.org/jira/browse/IGNITE-21629 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > *TLSv1_3* will be used automatically when supported by the JDK if you keep > the default *SslProtocol.TLS* in *ClientConfiguration*. However, it is not > possible to specify explicitly - we should add a enum entry to *SslProtocol*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18671) Sql. Cast to BigInt with overflow does not produce an error.
[
https://issues.apache.org/jira/browse/IGNITE-18671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18671:
---
Assignee: Iurii Gerzhedovich
> Sql. Cast to BigInt with overflow does not produce an error.
>
>
> Key: IGNITE-18671
> URL: https://issues.apache.org/jira/browse/IGNITE-18671
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Environment: See test_sum.test
> Query
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> CREATE TABLE bigints(b BIGINT);
> # a bunch of huge values
> statement ok
> INSERT INTO bigints SELECT * FROM table(system_range(4611686018427387904,
> 4611686018427388903, 1));
> # this is too big for a bigint.
> # should fail but returns the result below
> query I
> SELECT SUM(b)::BIGINT FROM bigints
>
> 499500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21629) Add TLSv1_3 to o.a.i.client.SslProtocol
[ https://issues.apache.org/jira/browse/IGNITE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-21629: Release Note: Added TLSv1_3 to o.a.i.client.SslProtocol. > Add TLSv1_3 to o.a.i.client.SslProtocol > --- > > Key: IGNITE-21629 > URL: https://issues.apache.org/jira/browse/IGNITE-21629 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > *TLSv1_3* will be used automatically when supported by the JDK if you keep > the default *SslProtocol.TLS* in *ClientConfiguration*. However, it is not > possible to specify explicitly - we should add a enum entry to *SslProtocol*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18661) Sql. Decimal multiplication could not be performed exactly: throw error
[
https://issues.apache.org/jira/browse/IGNITE-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18661:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal multiplication could not be performed exactly: throw error
> ---
>
> Key: IGNITE-18661
> URL: https://issues.apache.org/jira/browse/IGNITE-18661
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following query is expected to fail but it does not.
> {code:java}
> SELECT '0.01'::DECIMAL(38,30) *
> '0.01'::DECIMAL(38,30)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18660) Sql. Decimal out of range error does not occur
[
https://issues.apache.org/jira/browse/IGNITE-18660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18660:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal out of range error does not occur
> --
>
> Key: IGNITE-18660
> URL: https://issues.apache.org/jira/browse/IGNITE-18660
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> The following query is expected to fail but it does not.
> {code:java}
> statement error
> SELECT ('0.54321543215432154321543215432154321'::DECIMAL(35,35) +
> 1)::VARCHAR
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-18656) Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
[
https://issues.apache.org/jira/browse/IGNITE-18656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich reassigned IGNITE-18656:
---
Assignee: Iurii Gerzhedovich
> Sql. Decimal conversion in overflow: SELECT '9223372036854788.758'::DECIMAL
>
>
> Key: IGNITE-18656
> URL: https://issues.apache.org/jira/browse/IGNITE-18656
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Iurii Gerzhedovich
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> # overflow in conversion
> skipif ignite3
> statement error
> SELECT '9223372036854788.758'::DECIMAL; {code}
> {code:java}
> Not expected result at: (test_decimal.test:40). Statement: SELECT
> '9223372036854788.758'::DECIMAL;. Error: an instance of java.lang.String ==>
> Expected java.lang.Throwable to be thrown, but nothing was thrown.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22064) General MapReduce API
[ https://issues.apache.org/jira/browse/IGNITE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842899#comment-17842899 ] Mikhail Pochatkin commented on IGNITE-22064: LGTM! Thanks Merged to main cb34325ecc033c68885d146b83f63602af58fd4e > General MapReduce API > - > > Key: IGNITE-22064 > URL: https://issues.apache.org/jira/browse/IGNITE-22064 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: compute, ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part of IEP related to Compute API. > # ComputeTask > # TaskExecution > # Modify IgniteCompute > # ComputeJobRunner > # TaskContext > The part about colocation is not a target for this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22157) [Ignite Website] Update website banners
[ https://issues.apache.org/jira/browse/IGNITE-22157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842884#comment-17842884 ] Vladislav Pyatkov commented on IGNITE-22157: Merged 52f3dfa4db9a463f698413cd1d651bc7638cd130 > [Ignite Website] Update website banners > --- > > Key: IGNITE-22157 > URL: https://issues.apache.org/jira/browse/IGNITE-22157 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Priority: Major > > Ignite Summit dates changed so for now have to remove banners featuring 2024 > event. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22157) [Ignite Website] Update website banners
[ https://issues.apache.org/jira/browse/IGNITE-22157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Alexandrov resolved IGNITE-22157. Resolution: Resolved > [Ignite Website] Update website banners > --- > > Key: IGNITE-22157 > URL: https://issues.apache.org/jira/browse/IGNITE-22157 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Priority: Major > > Ignite Summit dates changed so for now have to remove banners featuring 2024 > event. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21629) Add TLSv1_3 to o.a.i.client.SslProtocol
[ https://issues.apache.org/jira/browse/IGNITE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842882#comment-17842882 ] Igor Sapego commented on IGNITE-21629: -- Looks good to me. > Add TLSv1_3 to o.a.i.client.SslProtocol > --- > > Key: IGNITE-21629 > URL: https://issues.apache.org/jira/browse/IGNITE-21629 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > *TLSv1_3* will be used automatically when supported by the JDK if you keep > the default *SslProtocol.TLS* in *ClientConfiguration*. However, it is not > possible to specify explicitly - we should add a enum entry to *SslProtocol*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22128) Balancing partitions across stripes
[
https://issues.apache.org/jira/browse/IGNITE-22128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-22128:
---
Reviewer: Alexey Scherbakov
> Balancing partitions across stripes
> ---
>
> Key: IGNITE-22128
> URL: https://issues.apache.org/jira/browse/IGNITE-22128
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> Right now, we use a hash to balance partitions.
> {code:java}
> public int getStripe(NodeId nodeId) {
> return Math.abs(nodeId.hashCode() % stripes);
> }
> {code}
> This approach might lead to a skew.
> h3. Definition of done
> Partition is distributed statically by the honest round-robin algorithm.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22128) Balancing partitions across stripes
[
https://issues.apache.org/jira/browse/IGNITE-22128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842876#comment-17842876
]
Vladislav Pyatkov commented on IGNITE-22128:
[~ascherbakov] Please, look at the patch in the attachment.
> Balancing partitions across stripes
> ---
>
> Key: IGNITE-22128
> URL: https://issues.apache.org/jira/browse/IGNITE-22128
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> Right now, we use a hash to balance partitions.
> {code:java}
> public int getStripe(NodeId nodeId) {
> return Math.abs(nodeId.hashCode() % stripes);
> }
> {code}
> This approach might lead to a skew.
> h3. Definition of done
> Partition is distributed statically by the honest round-robin algorithm.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21661) Test scenario where all stable nodes are lost during a partially completed rebalance
[ https://issues.apache.org/jira/browse/IGNITE-21661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21661: --- Description: Following case is possible: * Nodes A, B and C for a partition * B and C go offline * new distribution is A, D and E * EDIT: rebalance can only be started with one more "resetPartitions" * full state transfer from A to D is completed * full state transfer from A to E is not * A goes offline * we perform "resetPartitions" Ideally, we should use D as a new leader somehow, but the bare minimum should be a partition that is functional, maybe an empty one. We should test the case This might be a good place to add more tests. was: Following case is possible: * Nodes A, B and C for a partition * B and C go offline * new distribution is A, D and E * full state transfer from A to D is completed * full state transfer from A to E is not * A goes offline * we perform "resetPartitions" Ideally, we should use D as a new leader somehow, but the bare minimum should be a partition that is functional, maybe an empty one. We should test the case This might be a good place to add more tests. > Test scenario where all stable nodes are lost during a partially completed > rebalance > > > Key: IGNITE-21661 > URL: https://issues.apache.org/jira/browse/IGNITE-21661 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > > Following case is possible: > * Nodes A, B and C for a partition > * B and C go offline > * new distribution is A, D and E > * EDIT: rebalance can only be started with one more "resetPartitions" > * full state transfer from A to D is completed > * full state transfer from A to E is not > * A goes offline > * we perform "resetPartitions" > Ideally, we should use D as a new leader somehow, but the bare minimum should > be a partition that is functional, maybe an empty one. We should test the case > > This might be a good place to add more tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22137) Rename RocksDb storage engine to "rocksdb" in configuration
[
https://issues.apache.org/jira/browse/IGNITE-22137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev reassigned IGNITE-22137:
Assignee: Aleksandr Polovtsev
> Rename RocksDb storage engine to "rocksdb" in configuration
> ---
>
> Key: IGNITE-22137
> URL: https://issues.apache.org/jira/browse/IGNITE-22137
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Polovtsev
>Assignee: Aleksandr Polovtsev
>Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently {{RocksDbStorageEngine}} is called "rocksDb" in configuration which
> is inconsistent with other storage engines, like "aipersist" and "aimem". I
> propose to rename to "rocksdb". However, this is an incompatible change in
> terms of configuration API, so extra caution must be taken.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21629) Add TLSv1_3 to o.a.i.client.SslProtocol
[
https://issues.apache.org/jira/browse/IGNITE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842858#comment-17842858
]
Ignite TC Bot commented on IGNITE-21629:
{panel:title=Branch: [pull/11335/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=8079014]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Snapshots 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=8079016]]
{panel}
{panel:title=Branch: [pull/11335/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=8075002buildTypeId=IgniteTests24Java8_RunAll]
> Add TLSv1_3 to o.a.i.client.SslProtocol
> ---
>
> Key: IGNITE-21629
> URL: https://issues.apache.org/jira/browse/IGNITE-21629
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *TLSv1_3* will be used automatically when supported by the JDK if you keep
> the default *SslProtocol.TLS* in *ClientConfiguration*. However, it is not
> possible to specify explicitly - we should add a enum entry to *SslProtocol*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22123) Critical thread blocked on 2 node cluster with intensive create tables
[
https://issues.apache.org/jira/browse/IGNITE-22123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842851#comment-17842851
]
Roman Puchkovskiy commented on IGNITE-22123:
Are full logs available? Without them, there is nothing that can be said, just
'something went wrong, probably the JVM is overloaded with GC'
> Critical thread blocked on 2 node cluster with intensive create tables
> --
>
> Key: IGNITE-22123
> URL: https://issues.apache.org/jira/browse/IGNITE-22123
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Alexander Belyak
>Priority: Major
> Labels: ignite-3
>
> # Start 2 nodes cluster (I use single host for both nodes)
> # Connect to the first node and do in cycle:
> ## create table (different 8 columns PK)
> ## insert a few rows in it
> ## select a row from table
> Expected result: test pass without errors
> Actual result:
> client get:
> {noformat}
> 16:45:20.253 [junit-timeout-thread-119] INFO
> o.g.a.t.teststeps.ThinClientSteps - Query: drop table if exists
> eight_different_types_TINYINT_INTEGER_FLOAT_TINYINT_TINYINT_TINYINT_TINYINT_TINYINT
> Apr 26, 2024 4:45:20 PM org.apache.ignite.internal.logger.IgniteLogger
> logInternal
> INFO: Partition assignment change notification received
> [remoteAddress=localhost:10800]
> 16:45:20.266 [junit-timeout-thread-119] INFO
> o.g.a.t.teststeps.ThinClientSteps - Query: create table
> eight_different_types_TINYINT_INTEGER_FLOAT_TINYINT_TINYINT_TINYINT_TINYINT_TINYINT(keyTINYINT0
> TINYINT not null, keyINTEGER1 INTEGER not null, keyFLOAT2 FLOAT not null,
> keyTINYINT3 TINYINT not null, keyTINYINT4 TINYINT not null, keyTINYINT5
> TINYINT not null, keyTINYINT6 TINYINT not null, keyTINYINT7 TINYINT not null,
> val INTEGER not null, primary key (keyTINYINT0, keyINTEGER1, keyFLOAT2,
> keyTINYINT3, keyTINYINT4, keyTINYINT5, keyTINYINT6, keyTINYINT7))
> 16:45:28.570 [junit-timeout-thread-119] INFO
> o.g.a.t.teststeps.ThinClientSteps - Query: insert into
> eight_different_types_TINYINT_INTEGER_FLOAT_TINYINT_TINYINT_TINYINT_TINYINT_TINYINT(keyTINYINT0,
> keyINTEGER1, keyFLOAT2, keyTINYINT3, keyTINYINT4, keyTINYINT5, keyTINYINT6,
> keyTINYINT7, val) values (-96, 25781810, 5.0, -93, -92, -91, -90, -89,
> 116513)org.apache.ignite.sql.SqlException: IGN-PLACEMENTDRIVER-1
> TraceId:e21f4eb1-4ecb-4ea2-aaf7-62a08b677f20 Failed to get the primary
> replica [tablePartitionId=85_part_18, awaitTimestamp=HybridTimestamp
> [physical=2024-04-26 16:45:28:599 +0300, logical=0,
> composite=112337821931864064]]
> at
> java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
> at
> org.apache.ignite.internal.util.ExceptionUtils$1.copy(ExceptionUtils.java:765)
> at
> org.apache.ignite.internal.util.ExceptionUtils$ExceptionFactory.createCopy(ExceptionUtils.java:699)
> at
> org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:525)
> at
> org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCauseInternal(ExceptionUtils.java:634)
> at
> org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:476)
> at
> org.apache.ignite.internal.client.sql.ClientSql.execute(ClientSql.java:94)
> at
> org.gridgain.ai3tests.tests.teststeps.ThinClientSteps.lambda$executeQuery$0(ThinClientSteps.java:61)
> at io.qameta.allure.Allure.lambda$step$1(Allure.java:127)
> at io.qameta.allure.Allure.step(Allure.java:181)
> at io.qameta.allure.Allure.step(Allure.java:125)
> at
> org.gridgain.ai3tests.tests.teststeps.ThinClientSteps.executeQuery(ThinClientSteps.java:61)
> at
> org.gridgain.ai3tests.tests.PrimaryKeyConstraintsTest.testTypes(PrimaryKeyConstraintsTest.java:167)
> at
> org.gridgain.ai3tests.tests.PrimaryKeyConstraintsTest.test8Columns(PrimaryKeyConstraintsTest.java:120)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> io.qameta.allure.junit5.AllureJunit5.interceptTestTemplateMethod(AllureJunit5.java:59)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> 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:829)
> Caused by: java.util.concurrent.CompletionException:
> org.apache.ignite.sql.SqlException: IGN-PLACEMENTDRIVER-1
> TraceId:e21f4eb1-4ecb-4ea2-aaf7-62a08b677f20 Failed to get the primary
> replica [tablePartitionId=85_part_18, awaitTimestamp=HybridTimestamp
> [physical=2024-04-26 16:45:28:599 +0300, logical=0,
> composite=112337821931864064]]
> at
>
