For conciseness of JSON representation and secondarily for backward compatibility, include new attributes like this that have a "legacy" value (ASC in this case) as OPTIONAL. Only include them in the planner generated JSON output when they have a non-legacy non-default value but flexibly support the default value whether implicit or explicit when reading the JSON in the EE or the planner.