[
https://issues.apache.org/jira/browse/TIKA-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501572#comment-17501572
]
Hudson commented on TIKA-3691:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #478 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/478/])
TIKA-3691 -- allow an empty/null basePath in the FileSystemFetcher (tallison:
[https://github.com/apache/tika/commit/de664ba870f1197bbac4ce6cbf3cf7f79c9a0210])
* (edit)
tika-core/src/main/java/org/apache/tika/pipes/fetcher/fs/FileSystemFetcher.java
* (edit) tika-core/src/test/java/org/apache/tika/config/TikaPipesConfigTest.java
> Allow a null/empty basePath in FileSystemFetcher
> ------------------------------------------------
>
> Key: TIKA-3691
> URL: https://issues.apache.org/jira/browse/TIKA-3691
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 2.3.1
>
>
> There are some use cases where there's enough security around access to the
> tika-server and in permissions for the tika-server process that users may
> want to enable sending in a full file path to pull from different drives.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
