[
https://issues.apache.org/jira/browse/IMPALA-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826317#comment-16826317
]
Michael Ho commented on IMPALA-8453:
------------------------------------
This seems to me a misconfiguration in core-site.xml. I hit that problem in the
past when core-site.xml is missing. It may be useful if you take a look at
[https://github.com/apache/impala/blob/master/bin/create-test-configuration.sh]
to see how the environment is set up and see if you may be missing one of those
steps in the file.
Anyhow, this seems to be a misconfiguration issue, not a functional problem
with Impala. Please use the user-list of Impala for questions like this in the
future.
> fs.defaultFS (file:///) is not supported
> ----------------------------------------
>
> Key: IMPALA-8453
> URL: https://issues.apache.org/jira/browse/IMPALA-8453
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.2.0
> Reporter: Lycan
> Priority: Minor
>
> When I start impalad, I got the flowing problem.
> E0424 19:38:35.758591 2455 impala-server.cc:278] Currently configured
> default filesystem: ProxyLocalFileSystem. fs.defaultFS ([file:///]) is not
> supported.
> E0424 19:38:35.758623 2455 impala-server.cc:281] Aborting Impala Server
> startup due to improper configuration. Impalad exiting.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
