Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to use 4mc tool for linux fs batch processing and logging #43

Open
gabrieljames opened this issue Aug 18, 2019 · 2 comments
Open

how to use 4mc tool for linux fs batch processing and logging #43

gabrieljames opened this issue Aug 18, 2019 · 2 comments

Comments

@gabrieljames
Copy link

gabrieljames commented Aug 18, 2019

Having difficulty with using the command line tool (linux) to process a directory of uncompressed text files to produce a directory of compressed files with the stdout redirected to a log file.

4mc [input] seems fine with wildcards, however, i cannot get wildcards working with [output] names, and cannot get the stdout to log to a file.

4mc -vz2 ./*.txt ./* >> log.txt

It is good to have a command line tool to test, but seems very limited for doing batch workloads on the local filesystem before uploading hdfs. Was expecting bash or gzip style basic input output log operations would work using a similar command syntax. If these operations are supported, could some documentation be added to describe the syntax, ideally in the -h help

@carlomedas
Copy link
Collaborator

The work mode and syntax should be similar to most of standard compression tools (like e.g. tar and gzip) that can take multiple inputs but then it compress to a single file?

@gabrieljames
Copy link
Author

The main issues were with using a paths and wildcards for input and output operations, and with logging verbose operations to a log file.

`4mz -vz2 /inputdir/inputfiles*.txt /outputdir/* >> logfilename.txt'

Was unable to get custom output directories and unable to get logging working.

Found it a bit light on error checking and created unwanted blank files under some conditions. Overall, didn't feel like a robust tool, got fustrated after several hours of trying to get stdout working.

Can post some examples if helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants