[
https://issues.apache.org/jira/browse/IGNITE-28693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-28693:
--------------------------------------
Description:
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._
was:
Do we need especial enum for message type 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._
> 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)
