[
https://issues.apache.org/jira/browse/TIKA-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116135#comment-18116135
]
ASF GitHub Bot commented on TIKA-4897:
--------------------------------------
tballison commented on PR #3184:
URL: https://github.com/apache/tika/pull/3184#issuecomment-5701961323
I'm refactoring to add this protection on Metadata.set() so that it is done
on write. This way we won't have to look for 18 places where we may or may not
be serializing. Let me know if there are concerns.
> Handle unpaired surrogates more robustly
> ----------------------------------------
>
> Key: TIKA-4897
> URL: https://issues.apache.org/jira/browse/TIKA-4897
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> An unpaired surrogate causes less than ideal behavior during serialization.
> We should handle this more robustly.
>
> After a bit of agentic digging, this is a smile-only issue, so it only hits
> in IPC between tika-pipes client and server. This does not affect our
> standard json serdes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
