[
https://issues.apache.org/jira/browse/HBASE-18462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114994#comment-16114994
]
Zach York commented on HBASE-18462:
-----------------------------------
HBase uses the Hadoop Filesystem interface even for the local filesystem.
This limitation is because the Path that Hadoop Filesystems uses ultimately
uses URI under the hood, hence why it throws that exception. I'm not saying
that this works with S3 or HDFS (It will not). I'm just saying that in S3 you
can create an object "path" with spaces in it (Outside of HBase). In that case,
HBase won't be able to read it.
> HBase server fails to start when rootdir contains spaces
> --------------------------------------------------------
>
> Key: HBASE-18462
> URL: https://issues.apache.org/jira/browse/HBASE-18462
> Project: HBase
> Issue Type: Bug
> Components: hbase, test
> Affects Versions: 1.3.1, 1.2.6
> Reporter: Ismaël Mejía
> Priority: Minor
>
> As part of the tests for the HBase connector for Beam I discovered that when
> you start an HBase server instance from a directory that contains spaces
> (rootdir) it does not start correctly. This happens both with the
> HBaseTestingUtility server and with the binary distribution too.
> The concrete exception says:
> {quote}
> Caused by: java.net.URISyntaxException: Illegal character in path at index
> 89:
> file:/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_JDK_Versions_Test/jdk/JDK
> 1.7
> (latest)/label/beam/sdks/java/io/hbase/target/test-data/b11a0828-4628-4fe9-885d-073fb641ddc9
> at java.net.URI$Parser.fail(URI.java:2829)
> at java.net.URI$Parser.checkChars(URI.java:3002)
> at java.net.URI$Parser.parseHierarchical(URI.java:3086)
> at java.net.URI$Parser.parse(URI.java:3034)
> at java.net.URI.<init>(URI.java:595)
> at java.net.URI.create(URI.java:857)
> ... 37 more
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
