Ciop-publish » History » Version 2
Herve Caumont, 2013-06-19 18:05
1 | 2 | Herve Caumont | h1. ciop-publish CLI reference |
---|---|---|---|
2 | 1 | Herve Caumont | |
3 | 2 | Herve Caumont | h2. Name |
4 | |||
5 | ciop-publish -- indicates to the framework the files or directory that are the output of the job. These files or directory published with this tool are passed as input for next job(s) (if any). |
||
6 | |||
7 | h2. Synopsis |
||
8 | |||
9 | ciop-publish [-b base_path] [-r] [-h] [File...] |
||
10 | |||
11 | |||
12 | File Parameter: |
||
13 | This is the path of the file or directory to publish. If none is passed as arguments, they are read via _stdin_. Paths may be absolute or relative. In this latter case, the file |
||
14 | base path is the task specific scratch place ('mapred_local_dir') |
||
15 | |||
16 | h2. Description |
||
17 | |||
18 | The following options are available: |
||
19 | |||
20 | > -h displays this help page |
||
21 | > [-b base_path] directory name of the base path to complete relative path (default: ${mapred_local_dir}) |
||
22 | > [-r] Turn on recursive finding for directory path. This option is important if the reference to pass must be all files in the directory and not just the directory (default: off) |
||
23 | |||
24 | h2. Output |
||
25 | |||
26 | |||
27 | h2. Exit status |
||
28 | |||
29 | > 0 publish executed successfully |
||
30 | > 1 an error occured during publish processing |
||
31 | > 255 file or directory not found |
||
32 | |||
33 | h2. Examples |