Sed -e ‘1,3d’ /tmp/infobright/$db_table > $db_table.sql #This is used to get rid of the rubish at the top of the output Mysql-ib $schema -e “show create table $db_table\G” > $db_table #create the create table element as this will be deleted from the show commandĮcho create table $db_table “(” > $db_table.sql The infobright loader is great for smallish tables $db_table.sql
#Pentaho data integration looks weird update#
The community edition of Infobright does not contain Insert Update Delete or Truncate so some interesting ways of data loading are required.
You could also use the date as a sort criteria, see here for the use of Ordinal Expression In addition to this you can also include the day number from the variable v_1, this is an interger type as is very useful as a sorting column to get the data in the correct order. In this example I have called the new field Week_Day. The name of the date field from my source file is ACCOUNT_DATE, just substitute what ever the filed is from your file, the only caveat is that is has to be a date field.Ĭreate a Modified Java Script Value and enter the following scriptĪs you can see the return variable is called v_2, all you need to do is create a new field and tie the return field name in with what ever you wish to call your new field name. There is no direct getDayname function so using the getDayNumber build in function and a little bit of JavaScript gets the job done. I needed to add the day to my calendar file to make on of our dashboards look a bit more cool 🙂
#Pentaho data integration looks weird download#
You can download the xml Pentaho Trace Debug Transfornation If you want to get this working out of the box call the transformation “Trace Debug” you of course will need to change where to look for it in the Trace Debug step. The sub transformation job looks like this. You can down download the xml Pentaho Call Generic Logging then just copy and paste from the xml file into Spoon. I did start to use the internal name but if you want this in multiple parts of the same transformation it does not work so well. It looks like this, the only thing that you have to change is the Field Names and the Constant filename. I then created three steps that just need to be added to any transformation to create a logging transformation When in production the GLOBAL_DEBUG can be set to N. I therefore create global variables called GLOABL_DUBUG and GLOBAL_DEBUG_FILEPATH. I need to see the various outputs at some stages throughout the transformation process.
I am currently doing a bit of ETL work that is using a lot of variables to make some of it generic and flexible.
0 kommentar(er)
