[
https://issues.apache.org/jira/browse/HADOOP-19854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071288#comment-18071288
]
Pavan Pothnis commented on HADOOP-19854:
----------------------------------------
[~manika137] / [~anujmodi] - could you please validated behavior when
_*BlobStorageEvents*_ is enabled along with soft delete as well while fixing
this issue.
Trying to make sure migration doesn't fail when Soft Delete _*and/or
BlobStorageEvents* is enabled on the Storage account that is being migrated to
access via *ABFSS, as we have seen many of our customer having both or at least
one of them enabled and avoid following error*_
_*This endpoint does not support BlobStorageEvents or SoftDelete. Please
disable these account features if you would like to use this endpoint.*_
_{*}{*}Also, please do add the timeline for fix and Version of hadoop, we are
looking forward for a fix in Hadoop Version *3.4.2 / 3.4.3.*_
> ABFS: Forced DFS Endpoint Usage Causes Failure on FNS-Blob Accounts with Soft
> Delete Enabled
> --------------------------------------------------------------------------------------------
>
> Key: HADOOP-19854
> URL: https://issues.apache.org/jira/browse/HADOOP-19854
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 3.5.0, 3.4.2, 3.4.3
> Reporter: Manika Joshi
> Assignee: Manika Joshi
> Priority: Major
>
> If _fs.azure.account.hns.enabled_ is not configured, ABFS driver issues a
> getAcl call +using the DFS endpoint+ to detect the account type (HNS or FNS)
> For FNS Blob accounts with Soft Delete enabled, this behavior leads to
> failures because the DFS endpoint used does not support Soft Delete semantics.
> Temporary fix is to explicitly set the configuration:
> _fs.azure.account.hns.enabled_ so the redundant DFS-based detection is
> bypassed and the issue does not occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
