You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2025/01/22 14:24:00 UTC

[jira] [Updated] (IGNITE-24289) Sql. SQL-schemas. Extend test coverage.

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

Andrey Mashenkov updated IGNITE-24289:
--------------------------------------
    Description: 
Integration tests
* Ensure we have tests for Catalog commands.
* Ensure we have tests for Catalog commands validator: name uniqueness, respectful to system names.
* Ensure different schemas can contain objects with the same simple names.
* PUBLIC schema behavior is the same as any other user schema: can be dropped/changed/re-created.
End-to-end tests
* Ensure PUBLIC schema is created automatically.
* Ensure schema names are correctly resolved via Table API, Cache API and Compute API.
* Ensure the correct exception is thrown, when schema wasn’t found. E.g. if PUBLIC was dropped.
* ThinClient has the same guarantees/capabilities.
* JDBC/ODBC clients support default schema overriding.

  was:Let's remove deprecated methods and make code cleanup after the feature will be implemented and all mandatory tickets will be resolved.


> Sql. SQL-schemas. Extend test coverage.
> ---------------------------------------
>
>                 Key: IGNITE-24289
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24289
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.1
>
>
> Integration tests
> * Ensure we have tests for Catalog commands.
> * Ensure we have tests for Catalog commands validator: name uniqueness, respectful to system names.
> * Ensure different schemas can contain objects with the same simple names.
> * PUBLIC schema behavior is the same as any other user schema: can be dropped/changed/re-created.
> End-to-end tests
> * Ensure PUBLIC schema is created automatically.
> * Ensure schema names are correctly resolved via Table API, Cache API and Compute API.
> * Ensure the correct exception is thrown, when schema wasn’t found. E.g. if PUBLIC was dropped.
> * ThinClient has the same guarantees/capabilities.
> * JDBC/ODBC clients support default schema overriding.



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