Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.218.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=xW4X9nTlyZ/VBnTHVi6oJxZfoiUyUYp7l1xpQB5h7ywMxIwhl8dWnwcBwAvEWBKZEG
         QZ/lOst1X5WgGGPbp9+2OaB26h4qJdNFf14fXby5/AUuAqZllfr0j3Md07hEQmZ8fU6+
         Fo+CphCiqsharpStW2hVkzwaULxQA9zHSXivc=
MIME-Version: 1.0
In-Reply-To: <8f70390911241153l56758814pd0023bf5e4dba738@mail.gmail.com>
References: <8f70390911241153l56758814pd0023bf5e4dba738@mail.gmail.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Wed, 25 Nov 2009 14:26:41 +0100
Message-ID: <510143ac0911250526t4cf0d440t2557850d2badd067@mail.gmail.com>
Subject: Re: detect a failed text extraction?
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Tue, Nov 24, 2009 at 8:53 PM, Paco Avila <monkiki@gmail.com> wrote:
> There is any way to detect a failed text extraction ? I know, I can
> see the log but the failure it not associated to a file or path.
> [...]
> I have posted this question in the user list, but I think it is
> interesting talking about how it can be achieved.

Could we solve this by improving the level of logging in the indexer?

Alternatively, if you don't have easy access to the log files, we
could possibly inject some special unique term to the index as a
marker of failed text extraction. That way you could query for all
nodes for which text extraction failed.

Finally, as a debugging tool we could add a feature to the Jackrabbit
webapp that allows you to download the extracted text content of a
binary instead of the binary itself. We'd simply run a new text
extraction pass on the stored binary and return the extracted text or
any encountered errors to he client.

BR,

Jukka Zitting