[IOTDB-3999] Avoid using PlanNodeType.ordinal() in serializing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: master branch, 0.10.2
• Component/s: Core/Engine
• Labels: pull-request-available
• Assignee: Eric Pai
• Reporter: Eric Pai
• Created: 29/Jul/22 04:18
• Updated: 29/Jul/22 07:22
• Resolved: 29/Jul/22 07:22

Description

The ordinal() of an Enum is changed via the element definition order. If one developer changes the order, there's no way to fingure out, bugs will happen.

So I think it's better to avoid using ordinal() in serializing.

The issue exists in WALNodeSerializing.

Issue Links

• links to: GitHub Pull Request #6835