Canonical field name restrictions and @schema overrides


#1

Previous post, somewhat related

  1. What characters are allowed in canonical field names (i.e. the fields that get loaded from csv)
  2. What characters are allowed at the beginning of such field names

I have source system data columns containing “/”, “.”, and “_” and some starting with numbers currently. Planning to use something like @schema(fieldOverrides={‘Z0MYBADFIELD_A’: ‘0MYBADFIELD/A’}) in order to deal with it. If underscores are allowed as the beginning of a field name, then I could do _0MYBADFIELD_A


Field name restrictions
#2

You can pretty match use anything in column names then in your canonical use @ser(name="your-column-name") to map the column name into your Canonical field.

However, you may encounter some issues for instance with spaces in the column name like here