Store enum as keyword VS integer

We have a layer on top of Elasticsearch to translate enums into their numeric values before querying and indexing, but I am wondering if that's necessary at all for storage savings and query performance when compared with storing these enums as keywords.
From this post a long time ago: Are ENUM stored efficiently?, it seems storing enum values as keywords is already the optimized way?

We try to optimise all data structures, irrespective of their underlying type.

And I can't quantify this, but if they are actually numeric it seems to me converting them seems to be a the best approach as you're explicitly setting them, rather than treating it as a number in a text field.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.