Pipelines require that schemas going into a non-joiner stage are exactly the same.
When we fixed CDAP-16736, this triggered a bug in the pipeline validation logic where schemas with the exact same fields but not the exact same names would get treated as different, leading to errors like:
Two different input schema were set for the stage sink
when deploying the pipeline. This is made even more confusing by the fact that the UI doesn't display the actual schema name, but always uses a hardcoded value 'etlSchemaBody'.