lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Gazzarini <>
Subject Re: using extract handler: data not extracted
Date Sun, 12 Jan 2014 10:05:44 GMT
A premise: as Erik explained, most probably this issue has nothing to do
with SOLR.
So, these are the options that, in my mind, you have

*OPTION #1 : Using Tika as command line tool*a) Download Tika. Make sure
the same version of your SOLR
b) Read here: There a
section called "Using Tika as a command line utility", you can give it your
file, set the verbose flag and see what is the output

*OPTIONS #2  (if you are a Java dev)*a) create a simple Java project in
your workspace and set in the build path the tika libs from your SOLR
b) Read here: Creates and
start a sample main parser. Here you should have a more deep control on
what happens.

*OPTIONS #3 Set the log level on SOLR*
As far as I rememberr the old (pre 4.x) version of solr listed all packages
found in classloader under the logging tab, so you could be able to set the
appropiate level for each of them.
Instead, I'm seeing that on 4.x (at least 4.4.0), after starting SOLR with
tika libs, I don't see those packages in the log tree.

You can

a) if you are using linux, set the FINEST level on the *org.apache* package
and grep the output log (otherwise you will get a loooot of messages)
b) directly change the under $JETTY_HOME/etc (or your
servlet engine log configuration files if you are not using jetty)

More on (SOLR) logging


On Sun, Jan 12, 2014 at 10:13 AM, sweety <> wrote:

> ya right all 3 points are right.
> Let me solve the 1 first, there is some errror in tika level indexing, for
> that i need to debug at tika level right??
>  but how to do that?? Solr admin does not show package wise logging.
> --
> View this message in context:
> Sent from the Solr - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message