You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2024/11/26 12:10:00 UTC

[jira] [Updated] (IGNITE-23743) No errors returned when users create a distribution zone with an invalid storage profile

     [ https://issues.apache.org/jira/browse/IGNITE-23743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-23743:
-----------------------------------------
    Labels: ignite-3  (was: )

> No errors returned when users create a distribution zone with an invalid storage profile
> ----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-23743
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23743
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Pligin
>            Priority: Major
>              Labels: ignite-3
>
> Currently it is possible to create a zone with invalid storage profile, but a user receives no sign of error.
> An error happens only when a user tries to interact with a table in the zone, for example insert values. The error is Unknown error Failed to get the primary replica [tablePartitionId=23_part_0, awaitTimestamp=HybridTimestamp [physical=2024-11-19 13:12:44:718 +0000, logical=0, composite=113509791479758848]].
> {{}}
> {code:java}
> sql-cli> CREATE ZONE IF NOT EXISTS exampleZone1 WITH STORAGE_PROFILES='defaul' Updated 0 rows. 
> sql-cli> CREATE TABLE IF NOT EXISTS Person4 ( id int primary key, city_id int, name varchar, age int, company varch ar) ZONE exampleZone1 Updated 0 rows. 
> sql-cli> INSERT INTO Person4 VALUES (1,2,'carl', 32, 'clover') Unknown error Failed to get the primary replica [tablePartitionId=23_part_0, awaitTimestamp=HybridTimestamp [physical=2024-11-19 13:12:44:718 +0000, logical=0, composite=113509791479758848]] {code}
> {{}}
> This should be changed somehow. The current behavior most likely appeared as a consequence of https://issues.apache.org/jira/browse/IGNITE-23128.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)