fix: JSONConverter raises KeyError on ByteStream sources without file_path

[mittalpk]

Related Issues

• No existing issue filed; found via a direct code audit of JSONConverter, in the same pass as fix: MSGToDocument raises KeyError on ByteStream sources without file_path #12207.

Proposed Changes

All three exception handlers in _get_content_and_meta() — invalid UTF-8 decoding, a jq_schema filter that fails to apply, and malformed JSON — log a warning using source.meta["file_path"], an unconditional dict-key access. A bare ByteStream (e.g. ByteStream.from_string(...), the exact pattern shown in this component's own docstring usage examples) has empty meta by default, so on any of these three error paths the error-handling code itself raises KeyError: 'file_path', masking the real error (UnicodeDecodeError, filter failure, or JSONDecodeError) and crashing run() entirely instead of logging a warning and skipping that one source, which is the documented/intended behavior.

Two prior merged PRs (#8775, #11980) touched this exact function, but both only tested via file-path sources, which auto-populate file_path in meta — so this bug survived both.

Fixed by using source.meta.get("file_path", "unknown") at all three call sites, consistent with how run() itself already safely does bytestream.meta.get("file_path") a few lines below.

How did you test it?

Reproduced the crash directly against main (JSONConverter(content_key="text").run(sources=[ByteStream(data=b"\xff\xfe not valid utf-8")])), confirmed the KeyError.

Added three new tests, one per exception path, each using a bare ByteStream mirroring the repo's existing file-path-based tests for the same three paths (test_run_with_bad_filter, test_run_with_bad_encoding, test_run_with_malformed_json_and_content_key). Confirmed all three fail on unpatched json.py (git stash) with the same KeyError, and pass after the fix. Ran the full converters unit suite (hatch run test:unit test/components/converters/) — 265 passed, no regressions. hatch run test:types — no issues. hatch run fmt — clean.

Notes for the reviewer

Same shape of bug and same root cause as #12207 (MSGToDocument), found in the same audit pass — flagging in case a reviewer wants to look at both together, though they're independent files/components and can be merged separately.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have added unit tests and updated the docstrings.
• I've used a conventional commit type (fix:) for the PR title.
• I have added a release note file.
• I have run hatch run fmt / hatch run test:types / hatch run test:unit and fixed any issue.

This PR was developed with AI-assisted tooling (Claude Code); I reviewed the diagnosis, the fix, and the tests, and ran the test suite and quality checks locally as noted above.

[vercel]

@mittalpk is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.