ianmcook commented on issue #25078: URL: https://github.com/apache/arrow/issues/25078#issuecomment-3648956444
I wonder if we should consider a notation that keeps the JSON flatter by representing each type and its parameters (if any), children (if any), attributes (e.g. whether dictionary is ordered, whether map keys are sorted), and nullability all in a single string. For example we could use `[]` to enclose parameters, `<>` to enclose children, and `?` to represent nullability. This seems like it'd be more concise, user-friendly, and readable (compared to the alternative of using nested JSON dictionary and array structures), but it would require special string parsing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
