The PostgreSQL bulk loader is an experimental step in which we will to stream data from inside Kettle to the psql command using "COPY DATA FROM STDIN" into the database.
This way of loading data offers the best of both worlds : the performance of a bulk load and the flexibility of a Pentaho Data Integration transformation.
Make sure to check out the "Set up authentication" section below!
Note: This step does not work with a JNDI defined connection, only JDBC is supported.
Note: This step does not support timestamps at the moment (5.3). Timestamps should be converted to Date before this step. Using timestamps results in null-values in the table.
|Step name|| Name of the step.
|Connection|| Name of the database connection on which the target table resides.
Note: The password of this database connection is not used, see below in the "Set up authentication" section! Since PDI-1901 is fixed in 3.2.3, the username of the connection is used and added to the -U parameter, otherwise the logged in user acount would be taken.
|Target schema||The name of the Schema for the table to write data to. This is important for data sources that allow for table names with dots '.' in it.|
|Target table||Name of the target table.|
|psql path||Full path to the psql utility.|
|Load action|| Insert, Truncate. Insert inserts, truncate first truncates the table.
| Fields to load
|| This table contains a list of fields to load data from, properties include:
As you can see there is no way to specify a password for the database. It will always prompt for a password on the console no matter what.
To overcome this you need to set up trusted authentication on the PostgreSQL server.
To make this happen, change the pg_hba.conf file (on my box this is /etc/postgresql/8.2/main/pg_hba.conf) and add a line like this:
This basically means that everyone from the 192.168.1.0 network (mask 255.255.255.0) can log into postgres on all databases with any username. If you are running Kettle on the same server, change it to localhost:
This is much safer of-course. Make sure you don't invite any strangers onto your PostgreSQL database!