[
https://issues.apache.org/jira/browse/TIKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407527#comment-17407527
]
Hudson commented on TIKA-3542:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #324 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/324/])
TIKA-3542 -- add optional range parameters to FetchKey (tallison:
[https://github.com/apache/tika/commit/4625f1994da31c0db37105e41a5eca83f73c5a91])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/fetcher/FetchKey.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit)
tika-pipes/tika-pipes-iterators/tika-pipes-iterator-jdbc/src/main/java/org/apache/tika/pipes/pipesiterator/jdbc/JDBCPipesIterator.java
* (edit)
tika-serialization/src/main/java/org/apache/tika/metadata/serialization/JsonFetchEmitTuple.java
* (edit)
tika-serialization/src/test/java/org/apache/tika/metadata/serialization/JsonFetchEmitTupleTest.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/FetcherStreamFactory.java
* (edit) CHANGES.txt
> Add optional range parameters to fetchkey
> -----------------------------------------
>
> Key: TIKA-3542
> URL: https://issues.apache.org/jira/browse/TIKA-3542
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.1.1
>
>
> There are some use cases where it is helpful to fetch a range of bytes. We
> should allow users and pipesiterators to specify a rangeStart and rangeEnd in
> the fetchkey.
> I do not propose handling multiple ranges as you can in an http range
> fetch...just a single range per fetch key.
> Obviously, these will only work with fetchers that implement RangeFetcher.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
