[
https://issues.apache.org/jira/browse/DRILL-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716578#comment-15716578
]
Paul Rogers commented on DRILL-5091:
------------------------------------
Further tests show that the {{StoragePluginRegistryImpl.createPlugins()}}
method does not load the test bootstrap plugins because the local plugin
directory already exists: {{/tmp/drill/sys.storage_plugins}}.
Not sure how this could have ever worked if this directory exists and has
contents:
{code}
cp.sys.drill dfs.sys.drill s3.sys.drill
{code}
The JDBC test uses a {{LocalPersistentStore}} while the working unit tests use
{{NoWriteLocalStore}}. The reason is that {{LocalPersistentStoreProvider}}
checks {{ExecConstants.SYS_STORE_PROVIDER_LOCAL_ENABLE_WRITE}}
({{drill.exec.sys.store.provider.local.write}}). This is set in
{{BaseTestQuery}}:
{code}
put(ExecConstants.SYS_STORE_PROVIDER_LOCAL_ENABLE_WRITE, "false");
{code}
Adding this to the {{JdbcAssert.getDefaultProperties()}} solves the problem.
This does not answer the question as to why the tests succeed for others. Do
they delete /tmp/drill?
> JDBC unit test fails to set up test storage plugin config on Java 8
> -------------------------------------------------------------------
>
> Key: DRILL-5091
> URL: https://issues.apache.org/jira/browse/DRILL-5091
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.8.0
> Environment: Java 8
> Reporter: Paul Rogers
>
> Run the {{TestJDBCQuery}} unit tests. They will fail with errors relating to
> the default name space.
> The problem is due to a failure (that is ignored, DRILL-5090) to set up the
> test DFS name space.
> The "dfs_test" storage plugin is not found in the plugin registry, resulting
> in a null object and NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
