You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Eli Collins (Created) (JIRA)" <ji...@apache.org> on 2011/10/24 19:56:34 UTC

[jira] [Created] (BIGTOP-153) Build should detect invalid archives in the dl directory

Build should detect invalid archives in the dl directory
--------------------------------------------------------

                 Key: BIGTOP-153
                 URL: https://issues.apache.org/jira/browse/BIGTOP-153
             Project: Bigtop
          Issue Type: Improvement
          Components: General
            Reporter: Eli Collins


The build isn't user friendly if you have an invalid tarball in your dl directory (eg because you cntrl-c'd the build while it was running or it just got a bad file). It would be useful if the build did some basic verification of the tarballs, eg checked they were valid archive files, or (perhaps optionally) checked the md5 sums.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (BIGTOP-153) Build should detect invalid archives in the dl directory

Posted by "Anatoli Fomenko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anatoli Fomenko reassigned BIGTOP-153:
--------------------------------------

    Assignee: Anatoli Fomenko
    
> Build should detect invalid archives in the dl directory
> --------------------------------------------------------
>
>                 Key: BIGTOP-153
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-153
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>            Reporter: Eli Collins
>            Assignee: Anatoli Fomenko
>             Fix For: 0.5.0
>
>
> The build isn't user friendly if you have an invalid tarball in your dl directory (eg because you cntrl-c'd the build while it was running or it just got a bad file). It would be useful if the build did some basic verification of the tarballs, eg checked they were valid archive files, or (perhaps optionally) checked the md5 sums.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (BIGTOP-153) Build should detect invalid archives in the dl directory

Posted by "Anatoli Fomenko (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442255#comment-13442255 ] 

Anatoli Fomenko commented on BIGTOP-153:
----------------------------------------

The following components have available md5s for the downloaded tarballs, and they can have md5 check performed post-download:
Hadoop, Pig, Hive, Sqoop, Oozie, Whirr, Mahout, Flume, Bigtop-jsvc, Bigtop-tomcat

The remaining components may need checking for validity of downloaded tar.gz:
Zookeeper, HBase, Giraph, Hue, DataFu 
                
> Build should detect invalid archives in the dl directory
> --------------------------------------------------------
>
>                 Key: BIGTOP-153
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-153
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>            Reporter: Eli Collins
>             Fix For: 0.5.0
>
>
> The build isn't user friendly if you have an invalid tarball in your dl directory (eg because you cntrl-c'd the build while it was running or it just got a bad file). It would be useful if the build did some basic verification of the tarballs, eg checked they were valid archive files, or (perhaps optionally) checked the md5 sums.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira