You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Erik Weathers (JIRA)" <ji...@apache.org> on 2016/03/01 03:51:18 UTC
[jira] [Commented] (MESOS-4735) CommandInfo.URI should allow
specifying target filename
[ https://issues.apache.org/jira/browse/MESOS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173129#comment-15173129 ]
Erik Weathers commented on MESOS-4735:
--------------------------------------
[~gyliu]: sure, I'm talking about the filename within the executor sandbox. e.g., say that the {{CommandInfo.URI.value}} has the following URL:
{code: title=Example CommandInfo.URI.value}
http://hadoop-namenode.com:50070/webhdfs/v1/user/foo/bar-executor-binary.tgz?op=OPEN
{code}
In that case, using the current mesos fetcher behavior as of mesos-0.27.0, the downloaded file in the executor sandbox would be:
{code: title=Example Current Result Filename}
bar-executor-binary.tgz?op=OPEN
{code}
However, I would like to be able to override this result filename in the executor sandbox to be something like:
{code: title=Desired Result Filename}
bar-executor-binary.tgz
{code}
Benefits:
* allows explicit avoidance of inclusion of query parameters from the URI in the filename (see MESOS-1686)
* the fetcher's extracting logic could actually extract such executor bundles (tar, zip, etc.) (see MESOS-3367)
> CommandInfo.URI should allow specifying target filename
> -------------------------------------------------------
>
> Key: MESOS-4735
> URL: https://issues.apache.org/jira/browse/MESOS-4735
> Project: Mesos
> Issue Type: Improvement
> Components: fetcher
> Affects Versions: 0.27.0
> Reporter: Erik Weathers
> Assignee: Guangya Liu
> Priority: Minor
>
> The {{CommandInfo.URI}} message should allow explicitly choosing the downloaded file's name, to better mimic functionality present in tools like {{wget}} and {{curl}}.
> This relates to issues when the {{CommandInfo.URI}} is pointing to a URL that has query parameters at the end of the path, resulting in the downloaded filename having those elements. This also prevents extracting of such files, since the extraction logic is simply looking at the file's suffix. See MESOS-3367, MESOS-1686, and MESOS-1509 for more info. If this issue was fixed, then I could workaround the other issues not being fixed by modifying my framework's scheduler to set the target filename.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)