[
https://issues.apache.org/jira/browse/TIKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845229#comment-17845229
]
Hudson commented on TIKA-4252:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk11 #1625 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1625/])
TIKA-4252: add request metadata (#1753) (github:
[https://github.com/apache/tika/commit/b068e4290ad311b1e5f1ddaa6afa40be9e7bd797])
* (edit)
tika-core/src/main/java/org/apache/tika/pipes/fetcher/fs/FileSystemFetcher.java
* (edit) tika-core/src/test/java/org/apache/tika/pipes/fetcher/MockFetcher.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/fetcher/EmptyFetcher.java
* (edit)
tika-pipes/tika-fetchers/tika-fetcher-http/src/main/java/org/apache/tika/pipes/fetcher/http/HttpFetcher.java
* (edit)
tika-core/src/main/java/org/apache/tika/pipes/fetcher/url/UrlFetcher.java
* (edit)
tika-pipes/tika-fetchers/tika-fetcher-gcs/src/main/java/org/apache/tika/pipes/fetcher/gcs/GCSFetcher.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/fetcher/Fetcher.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/fetcher/RangeFetcher.java
* (edit) tika-core/src/test/java/org/apache/tika/pipes/async/MockFetcher.java
* (edit)
tika-pipes/tika-fetchers/tika-fetcher-az-blob/src/main/java/org/apache/tika/pipes/fetcher/azblob/AZBlobFetcher.java
* (edit)
tika-pipes/tika-fetchers/tika-fetcher-s3/src/main/java/org/apache/tika/pipes/fetcher/s3/S3Fetcher.java
> PipesClient#process - seems to lose the Fetch input metadata?
> -------------------------------------------------------------
>
> Key: TIKA-4252
> URL: https://issues.apache.org/jira/browse/TIKA-4252
> Project: Tika
> Issue Type: Bug
> Reporter: Nicholas DiPiazza
> Priority: Major
> Fix For: 3.0.0
>
>
> when calling:
> PipesResult pipesResult = pipesClient.process(new
> FetchEmitTuple(request.getFetchKey(),
> new FetchKey(fetcher.getName(), request.getFetchKey()),
> new EmitKey(), tikaMetadata, HandlerConfig.DEFAULT_HANDLER_CONFIG,
> FetchEmitTuple.ON_PARSE_EXCEPTION.SKIP));
> the tikaMetadata is not present in the fetch data when the fetch method is
> called.
>
> It's OK through this part:
> UnsynchronizedByteArrayOutputStream bos =
> UnsynchronizedByteArrayOutputStream.builder().get();
> try (ObjectOutputStream objectOutputStream = new
> ObjectOutputStream(bos))
> { objectOutputStream.writeObject(t); }
> byte[] bytes = bos.toByteArray();
> output.write(CALL.getByte());
> output.writeInt(bytes.length);
> output.write(bytes);
> output.flush();
>
> i verified the bytes have the expected metadata from that point.
>
> UPDATE: found issue
>
> org.apache.tika.pipes.PipesServer#parseFromTuple
>
> is using a new Metadata when it should only use empty metadata if fetch tuple
> metadata is null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
