-
Notifications
You must be signed in to change notification settings - Fork 4
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
Database Source and Target #1
Comments
That would not surprise me, the developers kind of rushed toward the end because their company got bought out and they needed to finish up quickly. Do feel free to contribute changes and updates to this, it's why we pushed it out to share. There are several people looking at it now, but this is the first feedback, Thanks! |
The source and target connections are set up as JNDI. These JNDI connections should be setup in the simple-jndi/jdbc.properties file in your Data Integration intall. What steps are hard coded? Brian |
Hi Tony, Every KTR file seems to have hard coded connection information that Additional seemingly unnecessary connections are also specified and must be I am new to Pentaho but not new to ETL and BI, so you may know tricks about Thanks for your time, -Kevin Kevin Ernest Long 503.888.6879 On Wed, Oct 7, 2015 at 11:42 AM, bcestes [email protected] wrote:
|
Brian... that seems like an error that needs to be addressed quickly |
You will need to post a screen shot of what you are seeing and point out hard coded values. All the KJB's and KTR's have EMR Source and EMR Target JNDI connections which are not hard coded to a connection of any type. A JNDI connection isn't specific to Pentaho. These JNDI connections should be setup in the simple-jndi/jdbc.properties file in your Data Integration intall. |
Hi all,
Thanks for reading.
It seem that the source and target of many of the steps are still hard coded in the individual transformations and that attempts to parameterize them at the top level are incomplete.
Is this the case or am I missing a configuration step?
Has anyone but the original authors on the original systems run these scripts?
Thanks again!
-Kevin
The text was updated successfully, but these errors were encountered: