You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2022/09/27 11:21:00 UTC
[jira] [Assigned] (IGNITE-17677) Refactoring of usage IgniteObjectName utility class
[ https://issues.apache.org/jira/browse/IGNITE-17677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov reassigned IGNITE-17677:
-----------------------------------------
Assignee: Konstantin Orlov
> Refactoring of usage IgniteObjectName utility class
> ---------------------------------------------------
>
> Key: IGNITE-17677
> URL: https://issues.apache.org/jira/browse/IGNITE-17677
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> As of now we do normalize of any schema object names in different places of intenal part of code, It looks as mess and error prone.
> What should we do:
> 1) normalize all object schema related strings in public API (org.apache.ignite.table.manager.IgniteTables) methods and pass it prepared to internal code
> 2) keep in configuration only prepared schame related object names.
> Need to check all usages of org.apache.ignite.internal.schema.SchemaUtils and do refactoing according to the rules above.
> Also point of view is usage : IgniteObjectName.parseCanonicalName
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)