You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2025/03/31 09:53:00 UTC
[jira] [Resolved] (IGNITE-24922) Get rid of IgniteNameUtils.parse method
[ https://issues.apache.org/jira/browse/IGNITE-24922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Mashenkov resolved IGNITE-24922.
---------------------------------------
Fix Version/s: (was: 3.1)
Resolution: Invalid
> Get rid of IgniteNameUtils.parse method
> ---------------------------------------
>
> Key: IGNITE-24922
> URL: https://issues.apache.org/jira/browse/IGNITE-24922
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3, newbie
>
> As for now, IgniteNameUtils have 2 methods with same signature, which do the same:
> {code:java}
> List<String> parse(String name) {
> List<String> parseName(String name) {
> {code}
> The last one follow more strict contract, implements argument validation, and non-confusing javadoc.
> Let's get rid of the first one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)