[
https://issues.apache.org/jira/browse/HBASE-20774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520735#comment-16520735
]
Steve Loughran commented on HBASE-20774:
----------------------------------------
as the S3A javadocs say, "Override getCanonicalServiceName because we don't
support token in S3A
you will have to fall back to getting the fully qualified path of the root dir
fs.makeQualified("/") and then compare by path equality
> FSHDFSUtils#isSameHdfs doesn't handle S3 filesystems correctly.
> ---------------------------------------------------------------
>
> Key: HBASE-20774
> URL: https://issues.apache.org/jira/browse/HBASE-20774
> Project: HBase
> Issue Type: Bug
> Components: Filesystem Integration
> Reporter: Austin Heyne
> Priority: Major
> Labels: S3, S3Native, s3
>
> FSHDFSUtils#isSameHdfs retrieves the Canonical Service Name from Hadoop to
> determine if source and destination are on the same filesystem.
> NativeS3FileSystem, S3FileSystem and presumably S3NativeFileSystem
> (com.amazon) always return null in getCanonicalServiceName() which
> incorrectly causes isSameHdfs to return false even when they could be the
> same.
> Error encountered while trying to perform bulk load from S3 to HBase on S3
> backed by the same bucket. This is causing bulk loads from S3 to copy all the
> data to the workers and back up to S3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
