2

I wonder if Kettle (AKA Pentaho PDI) supports metadata changing at run-time.

I've implemented a couple of custom plugins:

  • The first plugin sends data to the second plugin. The metadata of the rows sent in output can change when some conditions occur. In practice, this means that processRow() starts with a certain metadata and then, after a while, it changes it. Of course, the row sent in output through putRow() is always synchronized with the related metadata.
  • The second plugin receives data from the first plugin, calling getInputRowMeta() for understanding the metadata of the received row. However, such metadata seems to not be synchronized with the received row.

Given the results of this simple example, I wonder if the Kettle engine supports this kind of run-time behavior --- i.e. if getInputRowMeta() returns the correct metadata for the specific row that has been received.

Is anybody able of providing evidence that metadata changing is actually not possible ? Otherwise, is there any safe way for getting the metadata of the specific row received in processRow() ?

Claudio
  • 10,614
  • 4
  • 31
  • 71
  • We can use 'Select Values step' after changing the metadata of original stream and it will pick up the new metadata from there, but at the end final step (like CSV output,table output etc) will need to have metadata defined so we need to be sure about last data type of each filed. – suraj08 Jun 13 '16 at 07:28

1 Answers1

0

From page 616 of the book Pentaho Kettle Solutions:

The calculation of the output row metadata is something that needs to happen once and only once because the layout of all the output rows needs to be the same.

Claudio
  • 10,614
  • 4
  • 31
  • 71