I would be very interested in seeing this question answered, as well!

FYI, what we're doing - as a band-aid solution - is, in the Delta Filter Section, stating the following:

CR_TIMESTAMP >= 20210101000000.0 AND CH_TIMESTAMP >= 20220601000000.0

This is obviously not a Dynamic Parameter and, as such needs to be changed periodically..

I have no visibility on values being calculated incorrectly, but what you're describing (2147483647) is the maximum value allowed for an Integer type.

I don't know if there is a way to combine TODAY(), YEAR(), etc. in order to achieve a dynamic result (should it maybe be a STRING?), but I would be very interested in seeing that done

I hope this sheds some light on the issue, despite not resolving it

Best Regards,

Vasco Carona

Hi @anton.kozhi,

We handle this by using a helper table that stores the correct values of the parameters as a single row, and create a pool-parameter based on this table. By running the transformation directly after the extraction, it updates itself.

Follow these steps:

1. Format your column as a character due to integer restrictions (in vertica (the SQL dialect in Data Integration, an integer should have 19 decimals (INTEGER (vertica.com)), but since @vasco.caron11 checked this, maybe the pool parameter integer type is restricted)
2. Create a transformation and let it create a table -> CREATE TABLE (vertica.com)
3. Populate one column with the max timestamp value and set it as a string/char
4. Create a dynamic text pool parameter based on this table, and use the max value option. It will load the entry of point 2.
5. Now use this parameter in your extractions.

It is quite an ugly workaround, but yeah, it works in our cases.

I hope this helps you.

Kind regards,

Jan-peter