Thank you Nick and everyone who has helped me with my questions.
I'm now understand Tika much better vs. where I was at last week when I
first looked at it.
Steve
On Thu, Feb 11, 2016 at 8:18 AM, Nick Burch wrote:
> On Wed, 10 Feb 2016, Steven White wrote:
>
>> I'm
x-post to Tika user's
Y and n. If you run tika app as:
java -jar tika-app.jar
It runs tika-batch under the hood (TIKA-1330 as part of TIKA-1302). This
creates a parent and child process, if the child process notices a hung thread,
it dies, and the parent restarts it. Or if your OS gets
On Wed, 10 Feb 2016, Steven White wrote:
I'm including tika-app-1.11.jar with my application and see that Tika
includes "slf4j".
The Tika App single jar is intended for standalone use. It's not generally
recommended to be included as part of a wider application, as it tends to
include
Right. If you can't dump to a mirrored output directory, then you'll have to
do your own monitoring.
If you can dump to a mirrored output directory, then tika-app will do all of
the watchdog stuff for you.
If you can't, then, y, you're on your own.
If you want to get fancy, you could try
Plan C: if you’re willing to store a mirror set of directories with the text
versions of the files, just run tika-app.jar on your “input” directory and run
your SolrJ loader on the “text/export” directory:
java -jar tika-app.jar
And, if you’re feeling jsonic:
java -jar tika-app.jar –J -t –i