[
https://issues.apache.org/jira/browse/HDDS-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDDS-563:
------------------------------
Description:
"I found that we need to support an url scheme where the volume comes from the
domain ([http://vol1.s3g/]...) but the bucket is used as path style
([http://vol1.s3g/bucket]). It seems that both goofys and the existing s3a unit
tests (not sure, but it seems) requires this schema."
So hybrid means that the volume is identified based on the host name but bucket
name comes from url postfix.
This Jira is created from [~elek] comments on HDDS-525 jira.
was:
a) the host HTTP header sometimes contains the port, sometimes not (with aws
cli we have the port, with mitm proxy we doesn't). Would be easier to remove it
anyway to make it easier to configure.
b) I found that we need to support an url scheme where the volume comes from
the domain ([http://vol1.s3g/]...) but the bucket is used as path style
([http://vol1.s3g/bucket]). It seems that both goofys and the existing s3a unit
tests (not sure, but it seems) requires this schema.
This Jira is created from [~elek] comments on HDDS-525 jira.
> Support hybrid VirtualHosty style URL
> -------------------------------------
>
> Key: HDDS-563
> URL: https://issues.apache.org/jira/browse/HDDS-563
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Priority: Major
> Labels: newbie
>
> "I found that we need to support an url scheme where the volume comes from
> the domain ([http://vol1.s3g/]...) but the bucket is used as path style
> ([http://vol1.s3g/bucket]). It seems that both goofys and the existing s3a
> unit tests (not sure, but it seems) requires this schema."
> So hybrid means that the volume is identified based on the host name but
> bucket name comes from url postfix.
> This Jira is created from [~elek] comments on HDDS-525 jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
