This feature is a very nice one for object metadata tracking and re-using common transformations, but I think it would be even a nicer feature a process metadata tracking - meaning someone can track which process which kind of object dependencies introduces.
@swedish2000no If you are interested in this information, check out the "Data Lineage and auditing" chapter in our new book called Pentaho Kettle Solutions. It has a few neat tricks in there.
@mattcasters Hi Matt, thanks for the kind answer. It was helpful, but... when overviewing Impact Analysis on row level, I see that on SQL generated inputs, because of the actual current setup, someone cannot tell the table of origin. What I think it would be nice in the future, to have some sort of Query Designer or other kind of tool that forces the user the pick the tables and columns so that the source query can contain this kind of input metadata information. Just a thought of course...
@swedish2000no It's a valid remark. I'm working on a few solutions in this area that will see the light of day in 2011, so please a little bit more patience and we'll get there ;-)
This feature is a very nice one for object metadata tracking and re-using common transformations, but I think it would be even a nicer feature a process metadata tracking - meaning someone can track which process which kind of object dependencies introduces.
swedish2000no 1 year ago
@swedish2000no If you are interested in this information, check out the "Data Lineage and auditing" chapter in our new book called Pentaho Kettle Solutions. It has a few neat tricks in there.
mattcasters 1 year ago
@mattcasters Hi Matt, thanks for the kind answer. It was helpful, but... when overviewing Impact Analysis on row level, I see that on SQL generated inputs, because of the actual current setup, someone cannot tell the table of origin. What I think it would be nice in the future, to have some sort of Query Designer or other kind of tool that forces the user the pick the tables and columns so that the source query can contain this kind of input metadata information. Just a thought of course...
swedish2000no 1 year ago
@swedish2000no It's a valid remark. I'm working on a few solutions in this area that will see the light of day in 2011, so please a little bit more patience and we'll get there ;-)
mattcasters 1 year ago
Very Cool! We had a client ask for this feature a while ago...
bizcubed 1 year ago