[ 
https://issues.apache.org/jira/browse/TIKA-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108608#comment-18108608
 ] 

Hudson commented on TIKA-4843:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk17 #1583 (See 
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1583/])
TIKA-4843: fix per-request parse-context config for parsers with lock… (#3076) 
(github: 
[https://github.com/apache/tika/commit/2d1e43ab32a3f3e868bb9185119a26e4c6e4cf61])
* (add) 
tika-parsers/tika-parsers-ml/tika-parser-tess4j-module/src/test/java/org/apache/tika/parser/ocr/tess4j/Tess4JRuntimeConfigMergeTest.java
* (add) 
tika-parsers/tika-parsers-ml/tika-inference/src/test/java/org/apache/tika/inference/ImageEmbeddingRuntimeConfigMergeTest.java
* (edit) CHANGES.txt
* (add) 
tika-serialization/src/test/java/org/apache/tika/config/loader/JsonMergeUtilsTest.java
* (edit) 
tika-serialization/src/main/java/org/apache/tika/config/loader/JsonMergeUtils.java
* (add) 
tika-parsers/tika-parsers-ml/tika-vlm/src/test/java/org/apache/tika/parser/vlm/VLMRuntimeConfigMergeTest.java


> Per-request parse-context config throws for parsers with locked config fields
> -----------------------------------------------------------------------------
>
>                 Key: TIKA-4843
>                 URL: https://issues.apache.org/jira/browse/TIKA-4843
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> JsonMergeUtils.mergeWithDefaults deep-copies the default config via 
> mapper.convertValue() before merging caller JSON. That round-trip re-applies 
> every value through the setters, and RuntimeConfig subclasses override their 
> setters to reject caller input -- often as "any non-empty value is a 
> modification attempt". The config's own defaults therefore trip its own 
> guards and the copy fails before the caller's JSON is read.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to