[
https://issues.apache.org/jira/browse/IGNITE-24254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914247#comment-17914247
]
Andrey Mashenkov commented on IGNITE-24254:
-------------------------------------------
[~ptupitsyn], we need a quite simple fix in client protocol before 3.0, to
prevent compatibility issues.
There is no need to wait for all Sql-Schema support tickets for 3.0 release,
but this issue looks very important.
> 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: Andrey Mashenkov
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0
>
>
> 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 wither
> serialize QualifiedName or transfer schema name together with table names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
