Hi Keith, > 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?
LOG levels can be modified programmatically, or via the use of external configuration files, within most of the Java-based logging toolkits. For instance, in JDK logging, you can get the LogManager, and then set the default log level programmatically via code, or you can create an external file called logging.properties, and load it via a System property, java.util.logging.config.file. I can explain a bit more about this once we've selected a logging API preference. Cheers, Chris > > 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 >> >> ______________________________________________ Chris Mattmann, Ph.D. [EMAIL PROTECTED] Cognizant Development Engineer Early Detection Research Network Project _________________________________________________ Jet Propulsion Laboratory Pasadena, CA Office: 171-266B Mailstop: 171-246 _______________________________________________________ Disclaimer: The opinions presented within are my own and do not reflect those of either NASA, JPL, or the California Institute of Technology.
