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

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2025/01/21 13:27:00 UTC

[jira] [Reopened] (IGNITE-24254) Sql schema. Fix Thin client protocol to use schema names

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

Pavel Tupitsyn reopened IGNITE-24254:
-------------------------------------

> Sql schema. Fix Thin client protocol to use schema names
> --------------------------------------------------------
>
>                 Key: IGNITE-24254
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24254
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>            Reporter: Andrey Mashenkov
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Table can be unambiguously identified either by id or by pair of schema name and table name.
> So, Thin Client protocol should be aware of schema name a table belongs to.
> ClientTables, *ClientTableGetRequest* and *ClientTablesGetRequest* should either read/write table canonical name (see `QualifiedName.toCanonicalName`) or transfer schema name with the table name.
> I'd prefer second approach with 2 separate Strings, to avoid excessive parsing and quoting names.



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