Hello Team,
We have our Input files in Parquet format but they're not XDM compatible. As per the Adobe documentation & Community posts, we observed that AEP will only allow Parquet file if it is in XDM compatible format.
So when we're trying multiple options, we identified that using mapping sets we can do source to destination schema (XDM) mapping using Mapping Sets end point API. We tested on a sample Non XDM Parquet file using mapping sets API & file ingested successfully. We would like to proceed further with this approach as it reduces lot of efforts to convert existing Parquet files from Non XDM compatible to XDM compatible.
Based on this, can you please provide response for below
- Can we go ahead with mapping Sets API for loading Non XDM compatible Parquet file to XDM Schema?
- If yes, any specific Parquet formats only allowed with this approach or this applicable for all Parquet files (Nested or Simple)
- If no, any specific reason for us to not proceed further with this approach?
- Is it a recommended approach or best practices by Adobe to ingest Non XDM Parquet file.
- Will Adobe support this approach at later stages in case of issues?
Thanks for your support!!
