You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "María GH (JIRA)" <ji...@apache.org> on 2017/12/07 23:27:00 UTC
[jira] [Created] (BEAM-3315) PipelineOptions format documentation
needs to be corrected
María GH created BEAM-3315:
------------------------------
Summary: PipelineOptions format documentation needs to be corrected
Key: BEAM-3315
URL: https://issues.apache.org/jira/browse/BEAM-3315
Project: Beam
Issue Type: Bug
Components: website
Environment: Mac OS
Reporter: María GH
Assignee: Reuven Lax
Priority: Minor
Currently, both --option-name option-value are accepted, but out of the following list, the last doesn't actually work. The reason is how shells process extensions.
python -m ... --input /Users/mariagh/5000_gaming_data.csv
python -m ... --input ./5000_gaming_data.csv
python -m ... --input ~/5000_gaming_data.csv
python -m ... --input=/Users/mariagh/5000_gaming_data.csv
python -m ... --input=./5000_gaming_data.csv
python -m ... --input=~/5000_gaming_data.csv (doesn't work)
The documentation (*) includes only the last 3 options (with the equal sign). To be safe, it should either include all with a note about the different expansion for some shells, or just include the first three (with a space).
(*) https://beam.apache.org/documentation/programming-guide/#configuring-pipeline-options
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)