Github user joeymcallister commented on a diff in the pull request:
https://github.com/apache/geode/pull/366#discussion_r98112556
--- Diff:
geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
---
@@ -44,3 +44,14 @@ After executing a Geode query or calling `region.get`,
you can use the following
- `toJSONByteArray`. Reads a PdxInstance and returns a JSON byte array.
For more information on using the JSONFormatter, see the Java API
documentation for `org.apache.geode.pdx.JSONFormatter`.
+
+# Sorting Behavior of Serialized JSON Fields
+
+By default, Geode serialization creates a unique pdx typeID for each
unique JSON document, even if the
+only difference between the JSON documents is the order in which their
fields are specified.
+
+If you prefer that JSON documents which differ only in the order in which
their fields are specified
+map to the same typeID, set the property
`gemfire.pdx.mapper.sort-json-field-names` to `true`. This
+tells the system to sort the JSON fields prior to serialization, allowing
the system to identify
+matching entries, and helps reduce the number of pdx typIDs that are
generated by the serialization
--- End diff --
Change "typIDs" to "typeIDs"
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
