On Mon, 24 Aug 2015, Mikhail Titov wrote:
This approach however works partly for me. It occurred to me that *detect* method in *CompositeDetector* does not pass-in current *type* while trying detectors and testing for specialization[1]. Thus there is no way for me to know whether detector is being run for a case of specialization test or on a brand new file without testing (e.g. for office file) the 2nd time. Another option would be a "composite parser", but this is not possible at this moment according to tika web page[2].

Currently, Tika runs each detector independently, in priority order, and allows on detector to "improve" (specialise) the results of a previous one.

I'm not sure why you want to pass the results of one detector to another - any chance you could clarify the use-case for that? Either in text, or in code, whatever's easiest!

Thanks
Nick

Reply via email to