We also need to be mindful of Tika app and sever where there is no current way to see config other than Tika config file and multiple conflicting ways to set it...
Sent from my iPhone > On Jun 15, 2015, at 8:02 AM, Nick Burch <[email protected]> wrote: > >> On Mon, 15 Jun 2015, Allison, Timothy B. wrote: >> Agreed. They are two separate but related issues. TIKA-1508 should be >> fairly straightforward. Should I start coding it? Any other >> recommendations/concerns? > > My personal view is that properties/configuration which apply to all > documents of a type should be set at Parser creation time, either from a Tika > Config object or someone in code doing "Parser p = new FooParser(); > p.setblah();". Properties/config which vary from document to document should > be set on the ParseContext > > Not sure if we had consensus on that as a policy though? > > > In terms of TIKA-1508, any chance you could pick two parsers which are > currently configured some how, and update the issue to show how they are > configured now, and how you'd see them being configured in Tika Config? I > think it might be easier to review with some concrete cases, rather than the > abstract idea we have now > > Nick
