I had to set '-Djava.security.auth.login.config=/opt/splunk/splunk/etc/apps/splunk_app_db_connect/login.conf' as jvm option in server setting for tables/schemas to get listed. Apparently,this jvm options is not getting in effect when queried from SQL editor. I was able to get it working by adding this option in '/opt/splunk/splunk/etc/apps/splunk_app_db_connect/linux_x86_64/bin/command.sh' as below. export DRILL_OPTS="-Djava.security.auth.login.config=/opt/splunk/splunk/etc/apps/splunk_app_db_connect/login.conf" exec $JAVA_CMD $DRILL_OPTS $@ If there is any cleaner to specify jvm options required for JDBC driver , that would be great. ... View more

I was able to connect finally by creating directory ' DrillJDBC41-libs' in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers. The driver file name was 'DrillJDBC41.jar'. It was not clear from documentation regarding name to be used for dependent jar directory (Documentation says $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers/-libs) ... View more