[
https://issues.apache.org/jira/browse/IGNITE-28693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082071#comment-18082071
]
Ignite TC Bot commented on IGNITE-28693:
----------------------------------------
{panel:title=Branch: [pull/13145/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13145/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9077340&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9077340
rerunBuildIds=9079186,9079188,9079190{color}
> Remove Calcite's MessageType enum
> ---------------------------------
>
> Key: IGNITE-28693
> URL: https://issues.apache.org/jira/browse/IGNITE-28693
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Priority: Minor
> Labels: IEP-132, ise
>
> Do we need an especial enum for Calcite's message like
> {_}org.apache.ignite.internal.processors.query.calcite.message.MessageType{_}?
> _CoreMessagesFactory_ registers messages as is. Messages are determined by
> their classes. Performance issues are doubtful here.
>
> Suggestion: let's simplify an shorten the code by removing of _MessageType._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
