Thanks for the suggestions. It helps in ways to work around it.
But also, I'm trying to understand the underlying engine behavior because there seems to be an inconsistency in how VOID is handled:
- TO_VARIANT_OBJECT accepts VOID in ARRAYs. Here is an example
- Also, even after casting to a different type, the PAYMENT_DATE column is still stored as a VOID type in the variant as seen below.
Since Variant natively supports VOID (as shown in both arrays and the final variant schema), why does TO_VARIANT_OBJECT strictly block VOID fields inside a STRUCT?
Is this an intentional schema-validation design choice for Structs?
