Object Key Prefix Partitioner
Partition own JSON object members by exact literal key prefix; does not strip prefixes or interpret patterns.
Description
Partition own JSON object members by exact literal key prefix; does not strip prefixes or interpret patterns.
A literal prefix can separate namespaced object members from other fields. Partitioning preserves each value without interpreting the prefix as a nested path.
When to use this tool
Partition own JSON object members by exact literal key prefix; does not strip prefixes or interpret patterns.
- Prepare the supplied objectJson, prefix 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 objectJson, prefix. 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.matching, result.other. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Decode objectJson as an object and split own entries according to case-sensitive startsWith(prefix), returning matching and other objects.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| objectJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| prefix | prefix. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
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": "objectJson",
"decoded": {
"ab": 1,
"b": 2
}
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.matching | The matching value under the stated formula or text convention. |
| result.other | The other value under the stated formula or text convention. |
{
"input": {
"objectJson": "{\"ab\":1,\"b\":2}",
"prefix": "a"
},
"output": {
"result": {
"matching": {
"ab": 1
},
"other": {
"b": 2
}
}
}
}Limitations and assumptions
- The operation is shallow and literal. An empty prefix matches every key; it does not perform regex matching, case folding or recursive traversal.
- 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 Rename Map
Simultaneously rename own JSON object keys from an explicit map; reject collisions with renamed or untouched keys.
- Ordered Object Key Selector
Select own object members in explicit order as entries, avoiding JavaScript integer-key reorder ambiguity; report absent names separately.