With the current solution created as part of the PR #924, we would consider only one of the extension when multiple extensions are configured (this is deterministic though). We need to come up with a generic solution that would support multiple extensions for same resource type. Discuss with the community and come to consensus on the solution.
Possible Options to consider:
Implement the Pathling way of creating parquet schema for extensions (i.e., map based).
Create a parquet schema at runtime which is a superset of all the configured extension schemas and use this superset schema for the conversions. There are libraries for merging Parquet/Avro schema (link
With the current solution created as part of the PR #924, we would consider only one of the extension when multiple extensions are configured (this is deterministic though). We need to come up with a generic solution that would support multiple extensions for same resource type. Discuss with the community and come to consensus on the solution.
Possible Options to consider: