LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Node Release: Tar Archive

    Employee
    Posted 07-26-2010 09:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Node Name: Tar Archive
    Node Category: Publishing
    Use Case: Consider using this node when attempting to store output data in a tar archive
    Tested on Release: 4.1.6
    External Dependencies: None
    Practical Usage Example: An example use of this node has been provided in the prototype examples graph which is released in conjunction with the prototype library. Please see that graph for a executable use case.
    Node Documentation:

    Functional Description:
    This node will archive files in a .gz compressed archive file.
    Parameters:
    • FileName: To archive a single file, enter the full path and file name here
    • FileNameExpr: To archive multiple files, enter the name of the input field containing the file paths here. Should be used in conjunction with a Directory List node or similar
    • ArchivePath: Full path to the archive file which is to be created.
    • GZip: If true, the resulting archive file will be compressed using gzip. In this case, you should include a .tar.gz extension on the filename given in ArchivePath.
    • DeleteSourceFile: If true, the original source file will be deleted after archival.
    Known Limitations: None


  • 2.  RE: Node Release: Tar Archive

    Employee
    Posted 10-11-2010 02:35

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: mgajdosik

    Hi,

    using tar archive with options set to gzip and delete original files has one issue I think. If the node is stopped during the run, then created tar.gzip file is corrupted and original files are gone. Can this be solved either by removing the files only once all of them are archived? Or by some other way how to prevent the loss of data?

    Thanks
    Marek


  • 3.  RE: Node Release: Tar Archive

    Employee
    Posted 11-23-2010 09:15

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: mgajdosik

    Hi,

    have found that in python code on line 70 there should be:

    os.remove(self.Filename)

    instead of os.remove(filename)

    this is for single file archiving, when filename is not recognized variable as it is declared only if multiple inputs are present.

    Marek


  • 4.  RE: Node Release: Tar Archive

    Employee
    Posted 11-29-2010 14:43

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: mmarinelli

    I have updated the library posting with a new version which corrects the filename coding described above. This affects the Tar Archive and Zip Archive nodes.