[jira] [Commented] (DRILL-3520) Provide better logging around UDF loading and module loading
[ https://issues.apache.org/jira/browse/DRILL-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633884#comment-14633884 ] Daniel Barclay (Drill) commented on DRILL-3520: --- This DRILL-3520 might be partly covered by DRILL-3496 logging improvements (e.g., logging detection of drill-module.conf files and the pattern of logging the finding of storage plug-ins, functions, etc.). Provide better logging around UDF loading and module loading Key: DRILL-3520 URL: https://issues.apache.org/jira/browse/DRILL-3520 Project: Apache Drill Issue Type: Sub-task Reporter: Jacques Nadeau When adding an extension to Drill, sometimes it is hard to know what is going on. We should: - improve logging so that we report at INFO level information about all the Jar files that were included in Drill's consideration set (marked) and those that are not. (and include this debug analysis in the documentation) - If Drill fails to load a function, register an error function so that trying to invoke the UDF will provide the user with information about why the function failed to load. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3520) Provide better logging around UDF loading and module loading
[ https://issues.apache.org/jira/browse/DRILL-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634267#comment-14634267 ] Ted Dunning commented on DRILL-3520: I think that the function logging should become much more extensive if there are any functions that fail to load. A list of jars that had failed functions, a list that were loaded without error and so on would be very helpful, as would a dump of the classpath. The volume of logging isn't a big deal since this is a one-off that only occurs when things are borked. Provide better logging around UDF loading and module loading Key: DRILL-3520 URL: https://issues.apache.org/jira/browse/DRILL-3520 Project: Apache Drill Issue Type: Sub-task Reporter: Jacques Nadeau When adding an extension to Drill, sometimes it is hard to know what is going on. We should: - improve logging so that we report at INFO level information about all the Jar files that were included in Drill's consideration set (marked) and those that are not. (and include this debug analysis in the documentation) - If Drill fails to load a function, register an error function so that trying to invoke the UDF will provide the user with information about why the function failed to load. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
