rdblue commented on code in PR #10981:
URL: https://github.com/apache/iceberg/pull/10981#discussion_r1907674111
##########
format/spec.md:
##########
@@ -1506,6 +1523,8 @@ This serialization scheme is for storing single values as
individual binary valu
| **`struct`** | **`JSON object by field ID`** | `{"1": 1,
"2": "bar"}` | Stores struct fields using the field ID as
the JSON field name; field values are stored using this JSON single-value
format |
| **`list`** | **`JSON array of values`** | `[1, 2, 3]`
| Stores a JSON array of values that are
serialized using this JSON single-value format |
| **`map`** | **`JSON object of key and value arrays`** | `{ "keys":
["a", "b"], "values": [1, 2] }` | Stores arrays of keys and values; individual
keys and values are serialized using this JSON single-value format |
+| **`geometry`** | **`JSON string`** | `POINT (30
10)` | Stored using WKT representation, see
[Appendix G](#appendix-g-geospatial-notes) |
+| **`geography`** | **`JSON string`** | `POINT (30
10)` | Stored using WKT representation, see
[Appendix G](#appendix-g-geospatial-notes) |
Review Comment:
Like above, this table covers arbitrary `geometry` and `geography` objects.
I think it is fine to use WKT here and not have a separate way to store points,
but we should be aware that the implication is that WKT is required for any
JSON representation.
--
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: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
