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

Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2025/06/06 05:51:00 UTC

[jira] [Comment Edited] (IGNITE-25409) Catalog API should use the QualifiedName construct

    [ https://issues.apache.org/jira/browse/IGNITE-25409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956380#comment-17956380 ] 

Maksim Zhuravkov edited comment on IGNITE-25409 at 6/6/25 5:50 AM:
-------------------------------------------------------------------

Resolved in https://issues.apache.org/jira/browse/IGNITE-25408


was (Author: JIRAUSER298618):
Resolved in https://issues.apache.org/jira/browse/IGNITE-25409

> Catalog API should use the QualifiedName construct
> --------------------------------------------------
>
>                 Key: IGNITE-25409
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25409
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 3.0
>            Reporter: Tiago Marques Godinho
>            Assignee: Maksim Zhuravkov
>            Priority: Major
>              Labels: ignite-3
>
> The Catalog API still uses a separate string for the Schema and Table names.
> Since the Qualified name construct was introduced, we should start using it in the Catalog API as well.



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