jorisvandenbossche commented on code in PR #41257:
URL: https://github.com/apache/arrow/pull/41257#discussion_r1585935670
##########
docs/source/format/CanonicalExtensions.rst:
##########
@@ -251,6 +251,27 @@ Variable shape tensor
Values inside each **data** tensor element are stored in
row-major/C-contiguous
order according to the corresponding **shape**.
+.. _json_extension:
+
+JSON
+====
+
+* Extension name: `arrow.json`.
+
+* The storage type of this extension is ``StringArray`` or
+ or ``LargeStringArray`` or ``StringViewArray``.
+ Only UTF-8 encoded JSON is supported.
+
+* Extension type parameters:
+
+ This type does not have any parameters.
+
+* Description of the serialization:
+
+ Metadata is either an empty string or a JSON string with an empty object.
+ In the future, additional fields may be added, but they are not required
+ to interpret the array.
Review Comment:
> I think we should also add language that specifies what happens when you
receive non-conformant JSON or see any kind of parse errors. I think it's
important for components that sit in between producers and consumers (and thus
act as both).
Is it needed to specify anything about that? To me that seems a decision
that an application that will actually use the JSON data will need or want to
decide for themselves how to treat invalid input, while in many cases an Arrow
implementation receiving such data might just be passing it along, and will
typically not do any validation at all.
--
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: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
