[
https://issues.apache.org/jira/browse/TIKA-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474718#comment-17474718
]
Hudson commented on TIKA-3645:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #414 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/414/])
TIKA-3645 -- improve flexibility of specifying maps as params for parsers in
TikaConfig (tallison:
[https://github.com/apache/tika/commit/0b93901c4aa1a48a885b59b95f7c5d6689067ab6])
* (edit) CHANGES.txt
* (add)
tika-core/src/test/resources/org/apache/tika/config/TIKA-3557-exiftool-example.xml
* (edit)
tika-core/src/test/java/org/apache/tika/parser/external2/ExternalParserTest.java
* (edit) tika-core/src/main/java/org/apache/tika/config/Param.java
* (add) tika-core/src/test/resources/test-documents/testOverlappingText.pdf
> Allow for key/value attrs in params within tika-config for parsers
> ------------------------------------------------------------------
>
> Key: TIKA-3645
> URL: https://issues.apache.org/jira/browse/TIKA-3645
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Major
>
> In working a bit more with the new external2.ExternalParser, it looks like we
> should extend the allowable syntax for specifying maps in tika-config. We
> had initially used the node name as the key and the text content of the
> element as the value. The problem with this is that naming keys with a ":"
> is problematic.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
