Hi Srivastan,
Ground investigation
1. Does this union explicitly exist in your code? If not, where are the
7 and 6 column counting coming from?
2. On 3.3.1 have you looked at spark UI and the relevant dag diagram
3. Check query execution plan using explain() functionality
4. Can
Hello Users,
I have been seeing some weird issues when I upgraded my
EMR setup to 6.11 (which uses spark 3.3.2) , the call stack seems to point
to a code location where there is no explicit union, also I have
unionByName everywhere in the codebase with allowMissingColumns set