[
https://issues.apache.org/jira/browse/HADOOP-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405171#comment-17405171
]
Steve Loughran commented on HADOOP-17853:
-----------------------------------------
What about creating a regularly rebased branch in apache/hadoop for this so
even if a chain of patches go in -allowing for a bit of instability during the
process without breaking trunk.
The final bit of work can go in though a merge commit, so the change history
isn't lost.
I have mixed feelings there because we're doing work on those input streams &c
ourselves -a long-lived branch will be a pain. But if changes are split into
"abfs changes to aid plugging in a new transport" and "the actual new
transport", then the abfs changes can go in on trunk and HADOOP-17853;
transport support only on the new branch. Call
> ABFS: Enable optional store connectivity over azure specific protocol for
> data egress
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-17853
> URL: https://issues.apache.org/jira/browse/HADOOP-17853
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.4.0
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This Jira is to provide an option to enable store access on read path over an
> Azure specific protocol. This will only work on Azure VMs and hence will be
> disabled by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
