Ignite 3 uses the Configuration framework to describe table schema and it currently uses the following approach for storing columns and indices of a particular table: both of these are represented as Named Lists, where keys are sequentially ordered numbers converted into Strings and values are the corresponding View classes.
This is most likely a legacy feature needed when Named Lists didn't have an ordering guarantee and didn't have the functionality for retrieving values by index.
I propose to change this approach to a more simple one: use column/index names instead of sequentially ordered numbers in such Named Lists. This will make the code, that uses it, more straightforward. Consider the following example: