[
https://issues.apache.org/jira/browse/TIKA-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083466#comment-18083466
]
ASF GitHub Bot commented on TIKA-4737:
--------------------------------------
tballison opened a new pull request, #2836:
URL: https://github.com/apache/tika/pull/2836
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
Thanks for your contribution to [Apache Tika](https://tika.apache.org/)!
Your help is appreciated!
Before opening the pull request, please verify that
* there is an open issue on the [Tika issue
tracker](https://issues.apache.org/jira/projects/TIKA) which describes the
problem or the improvement. We cannot accept pull requests without an issue
because the change wouldn't be listed in the release notes.
* the issue ID (`TIKA-XXXX`)
- is referenced in the title of the pull request
- and placed in front of your commit messages surrounded by square
brackets (`[TIKA-XXXX] Issue or pull request title`)
* commits are squashed into a single one (or few commits for larger changes)
* Tika is successfully built and unit tests pass by running `./mvnw clean
test`
* there should be no conflicts when merging the pull request branch into the
*recent* `main` branch. If there are conflicts, please try to rebase the pull
request branch on top of a freshly pulled `main` branch
* if you add new module that downstream users will depend upon add it to
relevant group in `tika-bom/pom.xml`.
We will be able to faster integrate your pull request if these conditions
are met. If you have any questions how to fix your problem or about using Tika
in general, please sign up for the [Tika mailing
list](http://tika.apache.org/mail-lists.html). Thanks!
> tika-4.0.0-alpha1 - Batch mode is confusing
> -------------------------------------------
>
> Key: TIKA-4737
> URL: https://issues.apache.org/jira/browse/TIKA-4737
> Project: Tika
> Issue Type: Bug
> Environment: Windows 11 with Java 17
> Reporter: Adrian Bird
> Priority: Major
>
> Looking at the documentation I've found it very confusing for using what I'll
> call 'standard' mode vs 'batch' mode.
> # [Batch
> Processing|https://tika.apache.org/docs/4.0.0-SNAPSHOT/using-tika/cli/index.html#_batch_processing_tika_async_cli]
> says 'For processing large numbers of files, use {{{}tika-async-cli{}}}. It
> uses the Tika Pipes architecture with forked JVM processes for fault
> tolerance.'
> The examples uses 'tika-async-cli.jar' but this doesn't exist, but the
> example runs with the 'tika-app.jar'.
> # By using 'tika-app.jar' it is not clear what makes it run in 'batch' or
> 'standard ' mode. My assumption is that it is the presence of the '-i' and
> '-o' options.
> # The help from the 'batch' process differs quite a lot from the options
> specified in the Batch Processing page above and in the 'standard' help
> output.
> # The Batch Processing page above doesn't say anything about how to use a
> config file, but the help does.
> # It is confusing to have 2 different ways of specifying the config file,
> depending whether you are using the 'standard' '–config=file.json' or 'batch'
> '-c file.json'.
> # It would also be useful if a message was output saying whether it was
> 'standard' or 'batch' mode.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
