[
https://issues.apache.org/jira/browse/TIKA-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337642#comment-17337642
]
Hudson commented on TIKA-3371:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #215 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/215/])
TIKA-3371 -- add id to fetchtuple (tallison:
[https://github.com/apache/tika/commit/93abeafbdde35d3241bde314f980f64a9e574915])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/FetchEmitTuple.java
* (edit)
tika-serialization/src/main/java/org/apache/tika/metadata/serialization/JsonFetchEmitTuple.java
* (add) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncResult.java
* (edit)
tika-serialization/src/test/java/org/apache/tika/metadata/serialization/JsonFetchEmitTupleListTest.java
* (edit)
tika-serialization/src/test/java/org/apache/tika/metadata/serialization/JsonFetchEmitTupleTest.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncClient.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncProcessor.java
> Add "id" to FetchEmitTuple
> --------------------------
>
> Key: TIKA-3371
> URL: https://issues.apache.org/jira/browse/TIKA-3371
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
>
> We're currently using the fetchkey as the id for fetchemittuples. There are
> use cases where it is better to decouple the task id from the fetchkey for
> logging and status handlers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
