> Would we just swap to throwing an Exception if a parser can't be found / loaded?
Y, that'd be my inclination. > what do we do if someone gives us a Tika Config that references a Parser that doesn't exist? My preference would be to throw early and often. I don't want problems to be hidden. What do you think? On Tue, Feb 9, 2021 at 6:24 AM Nick Burch <[email protected]> wrote: > > On Mon, 8 Feb 2021, Tim Allison wrote: > > Do we still need the LoadErrorHandler for TikaConfig 2.x? IIRC, we > > added that so that folks who didn't want a dependency could prevent > > the loading of the dependency and then silence complaints -- if set to > > ignore. > > Would we just swap to throwing an Exception if a parser can't be found / > loaded? With the changes to the more modular parser packaging, that seems > ok to me. > > Only related question - what do we do if someone gives us a Tika Config > that references a Parser that doesn't exist? That now seems much more > likely than getting a service file entry for a parser we don't have. eg > someone specifies PDFParser in their config with a bunch of parameters / > options, but didn't include tika-parser-pdf-module on the classpath. Warn? > Error? Ignore? > > Nick
