You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2015/11/08 14:29:10 UTC

[jira] [Commented] (MESOS-3367) Mesos fetcher does not extract archives for URI with parameters

    [ https://issues.apache.org/jira/browse/MESOS-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995628#comment-14995628 ] 

Bernd Mathiske commented on MESOS-3367:
---------------------------------------

This ain't really a bug, it's a missing feature. The fetcher has never had the functionality desired here. But it's a good thing to provide it! I'll change the type of the ticket to improvement, OK?

> Mesos fetcher does not extract archives for URI with parameters
> ---------------------------------------------------------------
>
>                 Key: MESOS-3367
>                 URL: https://issues.apache.org/jira/browse/MESOS-3367
>             Project: Mesos
>          Issue Type: Bug
>          Components: fetcher
>    Affects Versions: 0.22.1, 0.23.0
>         Environment: DCOS 1.1
>            Reporter: Renat Zubairov
>            Assignee: haosdent
>            Priority: Minor
>              Labels: mesosphere
>
> I'm deploying using marathon applications with sources served from S3. I'm using a signed URL to give only temporary access to the S3 resources, so URL of the resource have some query parameters.
> So URI is 'https://foo.com/file.tgz?hasi' and fetcher stores it in the file with the name 'file.tgz?hasi', then it thinks that extension 'hasi' is not tgz hence extraction is skipped, despite the fact that MIME Type of the HTTP resource is 'application/x-tar'.
> Workaround - add additional parameter like '&workaround=.tgz'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)