[EPIC] Schema metadata handling / bugs

[alamb]

Is your feature request related to a problem or challenge?

As described by @wiedld on #12729

A #11989 (and released in 42.0.0) has added a check that the logical and physical plan input schemas (to an aggregate node) are the same.

This check fails for us in several different queries now downstream in InfluxDB and this ticket tracks the list of issues we found

Issues

• Field Metadata Lost on COUNT DISTINCT queries resulting in Internal Error: Physical input schema should be the same as the one converted from logical input schema #12687
• Field Metadata Lost on CROSS JOIN #12734
• Field Metadata Lost on UNION #12735
• Document Schema metadata expectations #12736
• Fix logical vs physical schema mismatch for aliased now() #12951
• UNION ALL with null constants results in Schema error #13010
• nullable Expr being constant fold to value can cause schema change and internal error #13190
• [EPIC] Schema metadata handling / bugs #12733

[wiedld]

This check fails for us in several different queries now downstream in InfluxDB and this ticket tracks the list of issues we found

If anyone finds other bugs, feel free to add to the epic. 🙏🏼

[alamb]

@wiedld has found several more issues:

• Fix logical vs physical schema mismatch for aliased now() #12951
• Fix logical vs physical schema mismatch for UNION where some inputs are constants #12954

[eejbyfeldt]

Found another issue that triggers a schema issue here: #13190

[alamb]

Found another issue that triggers a schema issue here: #13190

Thanks -- added to the list

Note I now have added the config option to work around the issue in #13176 for anyone who hits these

[wiedld]

Found another schema issue here: #13305. Reproducer test cases are also included.