You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
When we were designing initial version of Snowflake Loader, we made a decision to leave all contexts as ARRAY type (because we always have zero or more of them, always wrapped in array) and OBJECT for unstructured events (because it is a JSON-object).
From my understanding ARRAY and OBJECT are both subtypes of VARIANT. However we're having a user who claims that OBJECT type breaks an escaping (for |-symbol), whereas it works for VARIANT. From my point of view, this is an unexpected behavior and should not happen.
We're investigating this with Snowflake engineers, but if it will turn out that this is an expected behavior then we'll need to change type of all self-describing types to VARIANT. Adding to 0.4.0 so far, but probably it won't be necessary.
The text was updated successfully, but these errors were encountered:
When we were designing initial version of Snowflake Loader, we made a decision to leave all contexts as
ARRAY
type (because we always have zero or more of them, always wrapped in array) andOBJECT
for unstructured events (because it is a JSON-object).From my understanding
ARRAY
andOBJECT
are both subtypes ofVARIANT
. However we're having a user who claims thatOBJECT
type breaks an escaping (for|
-symbol), whereas it works forVARIANT
. From my point of view, this is an unexpected behavior and should not happen.We're investigating this with Snowflake engineers, but if it will turn out that this is an expected behavior then we'll need to change type of all self-describing types to
VARIANT
. Adding to 0.4.0 so far, but probably it won't be necessary.The text was updated successfully, but these errors were encountered: