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 set env variables ? #36

Open
kleysonr opened this issue Jun 17, 2024 · 3 comments
Open

How to set env variables ? #36

kleysonr opened this issue Jun 17, 2024 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@kleysonr
Copy link

Hi.

I need to set a new KETTLE_HOME value for the DAG execution.

Is that possible ?

@piffall piffall added the question Further information is requested label Jun 18, 2024
@piffall piffall self-assigned this Jun 18, 2024
@piffall
Copy link
Member

piffall commented Jun 18, 2024

Yes, just follow this instructions assuming that "pentaho_home" is the same as KETTLE_HOME.

@piffall piffall closed this as completed Jun 18, 2024
@kleysonr
Copy link
Author

kleysonr commented Jul 5, 2024

@piffall

I use a single kettle.properties inside each project to set the variables env dependent.

So when each dag runs, for each project, the pdi should read the kettle.properties inside the project folder.

I can't see how to use the pentaho_home as a solution per each individual kettle.properties files.

Can you provide an example of configuration for the use-case ?

Or, is it possible add a new extra parameter for kettle_home ?

Best Regards.
Kleyson Rios.

@piffall
Copy link
Member

piffall commented Jul 5, 2024

Hi @kleysonr . In the case that you have kettle deployed multiple times and assuming that each of this paths contains a full deployment of PDI, you can just set multiple connections, each having pentaho_home pointing to corresponding path.

/opt/kettle_a
/opt/kettle_b
/opt/kettle_c

@piffall piffall reopened this Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants