[
https://issues.apache.org/jira/browse/IGNITE-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912947#comment-17912947
]
Andrey Mashenkov edited comment on IGNITE-24211 at 1/14/25 3:34 PM:
--------------------------------------------------------------------
Does it affects compatibility? and should the PR be targeted to 3.0 version
while we have such option for now?.
was (Author: amashenkov):
Does it affects compatibility? and should be moved to 3.0 version while we have
such option for now?.
> Sql. Avoid accessing of Catalog object directly from outside the module.
> ------------------------------------------------------------------------
>
> Key: IGNITE-24211
> URL: https://issues.apache.org/jira/browse/IGNITE-24211
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3, tech-debt
> Fix For: 3.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Catalog object is an internal container for descriptors and wasn't designed
> to be used directly outside the module.
> The class has public modifier just to allow Catalog commands access it from
> the different package of the same (ignite-catalog) module moved for better
> code organization.
> Now, ignite-rest and ignite-table modules access Catalog object directly.
> Moreover, they exploits it's internals in wrong way: cache table descriptors
> by "canonical name" as concatenation of schemaName and tableName via dot
> notation without escaping.
> Let's avoid direct using of Catalog objects.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
