Suggestion: Separate input and output path vairables
Posted: Wed May 17, 2006 3:47 am
All of our jobs have a "ROOT" parameter, which specifies th root directory where all files are to be located. This parameter is different, for example, for development, QA, and production runs. The three values are "/home/migration/Dev", "/home/migration/QA", and "/home/migration/Prod".
My suggestion is that if you are going to use a system like this, you should instead implement two parameters: input and output (or source and destination); "IROOT" and "OROOT", or "SROOT" and "DROOT" depending on your preference.
Recently I have wanted to run the development version of a job, but read the source data from the QA environment while still sending output to the development environment. I have done this by making a CopyOf the job, and editing all the source file paths to insert a hard-coded value instead of the parameter. If I had thought of this earlier, and implemented two parameters instead of one, then this kind of run would be much easier.
I am interested to hear other suggestions as to how file locations are parameterised in other peoples' projects.
My suggestion is that if you are going to use a system like this, you should instead implement two parameters: input and output (or source and destination); "IROOT" and "OROOT", or "SROOT" and "DROOT" depending on your preference.
Recently I have wanted to run the development version of a job, but read the source data from the QA environment while still sending output to the development environment. I have done this by making a CopyOf the job, and editing all the source file paths to insert a hard-coded value instead of the parameter. If I had thought of this earlier, and implemented two parameters instead of one, then this kind of run would be much easier.
I am interested to hear other suggestions as to how file locations are parameterised in other peoples' projects.