[ https://issues.apache.org/jira/browse/IGNITE-24301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky updated IGNITE-24301: ---------------------------------------- Summary: Sql schema. Fix Thin client protocol to use schema names (was: CLONE - Sql schema. Fix Thin client protocol to use schema names) > Sql schema. Fix Thin client protocol to use schema names > -------------------------------------------------------- > > Key: IGNITE-24301 > URL: https://issues.apache.org/jira/browse/IGNITE-24301 > Project: Ignite > Issue Type: Improvement > Components: thin client > Reporter: Evgeny Stanilovsky > Priority: Major > Labels: ignite-3 > Fix For: 3.1 > > > 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, *ClientTableGetRequestV2* and *ClientTablesGetRequestV2* 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. > Check this issue mention after ignite-24033 was merged -- This message was sent by Atlassian Jira (v8.20.10#820010)