Object Key Set Comparison
Compare own key sets of two JSON objects; values and inherited names are not compared.
Description
Compare own key sets of two JSON objects; values and inherited names are not compared.
Comparing object key sets reveals which field names are shared or exclusive. This can expose differences in record shapes without requiring their values to match.
When to use this tool
Compare own key sets of two JSON objects; values and inherited names are not compared.
- Prepare the supplied leftJson, rightJson fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter leftJson, rightJson. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.onlyLeft, result.onlyRight, result.shared. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Decode both inputs as objects. Return onlyLeft and shared in left-key enumeration order and onlyRight in right-key enumeration order.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| leftJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| rightJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "leftJson",
"decoded": {
"a": 1,
"b": 2
}
},
{
"field": "rightJson",
"decoded": {
"b": 3,
"c": 4
}
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.onlyLeft | The only left list in the ordering and representation described above. |
| result.onlyRight | The only right list in the ordering and representation described above. |
| result.shared | The shared list in the ordering and representation described above. |
{
"input": {
"leftJson": "{\"a\":1,\"b\":2}",
"rightJson": "{\"b\":3,\"c\":4}"
},
"output": {
"result": {
"onlyLeft": [
"a"
],
"onlyRight": [
"c"
],
"shared": [
"b"
]
}
}
}Limitations and assumptions
- Values and nested shapes are ignored. Names are compared exactly without normalization, and JavaScript's object-key enumeration rules determine the displayed order.
- Decoded JSON is bounded to 20,000 nodes and 32 nesting levels; record arrays have at most 128 records. Parsed number values use JavaScript floating point rather than arbitrary-precision decimal arithmetic.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
For document-wide requirements, combine these structural inventories with an explicit JSON Schema. Preserve the distinction between missing properties and null values, and between numbers and numeric-looking strings when building joins or indexes.
References
Similar or alternative tools
- Object Key Prefix Partitioner
Partition own JSON object members by exact literal key prefix; does not strip prefixes or interpret patterns.
- Object Key Rename Map
Simultaneously rename own JSON object keys from an explicit map; reject collisions with renamed or untouched keys.