[
https://issues.apache.org/jira/browse/TIKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871718#comment-17871718
]
Hudson commented on TIKA-4295:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika ยป tika-main-jdk11 #1733 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1733/])
TIKA-4295 -- allow user bypass for emitkey for bytes (#1891) (github:
[https://github.com/apache/tika/commit/fca6a25bd0f1f608c933bd746622623e000b0183])
* (edit)
tika-core/src/main/java/org/apache/tika/pipes/extractor/EmbeddedDocumentBytesConfig.java
* (edit)
tika-core/src/main/java/org/apache/tika/extractor/AbstractEmbeddedDocumentBytesHandler.java
> Allow bypass of emitKey in AbstractEmbeddedDocumentBytesHandler
> ---------------------------------------------------------------
>
> Key: TIKA-4295
> URL: https://issues.apache.org/jira/browse/TIKA-4295
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 3.0.0
>
>
> We currently algorithmically determine the emit path for the bytes from
> embedded documents based on the json emit key. In other words, if the primary
> emit key is {{/a/b/c.json}}, we emit to {{/a/b/c/c-1000.jpg}}, for example.
> We should allow users to set a custom emit key root path so that, for
> example, users could have the json going here: {{/a/b/json/abc.json}} and the
> bytes going here: {{/a/b/bytes/abc-0000.doc}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
