You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Jinmei Liao (JIRA)" <ji...@apache.org> on 2017/03/02 18:01:45 UTC

[jira] [Assigned] (GEODE-2417) Generate zip file HTTP URL and manage deletion of zip files

     [ https://issues.apache.org/jira/browse/GEODE-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao reassigned GEODE-2417:
----------------------------------

    Assignee: Jinmei Liao

> Generate zip file HTTP URL and manage deletion of zip files
> -----------------------------------------------------------
>
>                 Key: GEODE-2417
>                 URL: https://issues.apache.org/jira/browse/GEODE-2417
>             Project: Geode
>          Issue Type: Sub-task
>          Components: configuration, gfsh
>            Reporter: Jared Stewart
>            Assignee: Jinmei Liao
>
> Once a locator has built the aggregated zip file described by GEODE-2416, we need that locator to expose an endpoint through the Admin REST api to allow access to that file (perhaps e.g. /exportedArtifact?exportId=foo or /exportedArtifact?name=myLogs.zip).  After the zip file has been successfully downloaded, it should be deleted and the URL invalidated.  Also, the URL should only be valid for some time period (say 24hrs) after which the file will be deleted and URL invalidated even if it is not downloaded, to prevent exported zip files from polluting the locator's disk.  This URL should be returned in the 'export log' command result JSON rather than the file contents.  [Cluster:Read] permissions should be required to access the URL if integrated security is enabled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)