NIFI QueryDatabaseTable Maximum-value Columns gets ignored if in double quotes

[#1]

Hi

I have issue with Maximum-value Column state on QueryDatabaseTable processor 1.6. I am using PostgreSQL database in which columns are in double quotes and if used in Maximum-value Column are ignored.

Screen shots looks like this and DEBUG mode shows attached.

State of the "locationId" is stored but not used in the SQL also attached.

With this configuration processor loads every time full load and ignores Maximum-value Column.

Do you know what could be the problem of this weird issue?

@Matt Burgess

[#2]

The column name itself has double quotes?

[#3 · Accepted solution]

What version of NiFi are you using? I tried this on the latest snapshot (to become NiFi 1.8.0) and using double-quotes in the Maximum Value Column worked for me (i.e. it does incremental fetching). Looking at the code it seems like it should work in NiFi 1.7.x as well, I'm wondering if there was a bug in your version that we've since fixed.

[#4]

Hi Matt,

Thanks for feedback. Indeed seems there was the issue on version 1.6. I made a check on version 1.7.1 and everything works fine with double quotes.