jsonpath

Use strata.query(data, expression) for in-memory dicts, lists, or tuples, and strata.search(path, expression) for .json, .ndjson, or .jsonl files and directories. For repeated queries, strata.compile(expression) returns a CompiledPath whose execute method runs over a cursor.

Strata supports a subset of RFC 9535: the $ root, dot and bracket field access, wildcards, array indices including negatives, slices, recursive descent (..field), and filters with ==, !=, >, >=, <, <= against numeric or quoted-string values. Unions, $..*, && / ||, nested filter paths, and regex are not supported.

query() accepts only Python dict, list, or tuple objects and raises TypeError otherwise, while search() accepts only file or directory paths. The law search(f, e) == query(load(f), e) holds by construction, with search optionally using a faster SAX streaming evaluator for plain paths.

The SAX streaming evaluator only handles plain paths made of Field, Wildcard, and non-negative Index steps under the default FirstWins duplicate-key policy. Recursive descent, slices, filters, negative indices, other policies, and NDJSON inputs fall back to load-then-query, which is definitionally exact.

The PyObject-native evaluator behind query() and search() preserves exact integers at any size. The C++ DOM evaluator behind CompiledPath.execute converts numbers to doubles, so integers above 2^53 lose precision on that path.

A negative slice step parses successfully but the evaluators only loop for step greater than zero, so the result is an empty list. This is a documented silent quirk of the current implementation, not a parse error.