Hey nick I guess my point is that parser context aka config properties for parsers and custom config files e.g., x.properties loaded from the classpath aren't configured from Tika app or server
Sent from my iPhone > On Jun 15, 2015, at 8:34 AM, Nick Burch <apa...@gagravarr.org> wrote: > >> On Mon, 15 Jun 2015, Mattmann, Chris A (3980) wrote: >> 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... > > Hmm? Both app and server optionally take a config file, don't they? And both > offer an option/flag/endpoint to tell you the parsers they found, the > detectors they found, parser decorations etc. > > I'd say that the app and the server are the easiest ways to know what's going > on with your Tika install, it's the pure-Java case where it's harder to know > what you do or don't have! > > Or have I mis-understood the use case? > > Nick
