Chris - Thanks for your understanding.
Regarding the logging, forgive my ignorance, but could you explain to me how I (as a user of the Tika jar file) would modify the log level? This log call is made whenever TikaConfig.getDefaultConfig() is called, which is whenever AutoDetectParser is created. It's important to me because I'm streaming lots of documents through Tika, so I'm getting a huge amount of output from this. Thanks, Keith Chris Mattmann wrote: > > Hey Keith, > > No problem at all and I am fine with the commit first review later > policy. > I just want to make sure that Tika isn't driven by internal developer > deadlines: trust me you don't want to see the ones I have at JPL :) We'd > all > be huddled around our computers committing things every 5 minutes but > that's > another story ;) > > Anyhoo, about the MimeTypes.load() call logging message: would perhaps > setting the LOG level to LOG.fine() or LOG.finest() address your issue? > There's a bigger overall issue here and that's closing the loop on which > logging facilities we use in Tika (my +1 for JDK logging again). Because > once we've chosen a logging facility, a user can control whether or not > that > message gets printed in her local configuration by modifying the > appropriate > logging level and suppressing the others. > > Cheers, > Chris > > -- View this message in context: http://www.nabble.com/MimeTypes-MimeUtils-Refactoring-tf4649072.html#a13285090 Sent from the Apache Tika - Development mailing list archive at Nabble.com.
