Hello NiFi Team, As far as I can see, in NiFi 2.5 "Custom Query" option for QueryDatabaseTable processor does not work properly at least for MSSQL Server 2019 when "Maximum-value Columns" and initial maxvalue are specified. It looks like the whole table is obtained from the database (query on the server side does not have WHERE condition) and then filtered internally somehow (in NiFi probably). So the result is correct at the end but the fact that the whole table needs to be obtained (when initial maxvalue is specified or state variable exists) makes it not usable for big enough tables. At the same time, for example, for MariaDB it works properly, as far as I can see, since WHERE condition is observed in query on the server side. Also in NiFi 1.27 "Custom Query" works properly with both MSSQL Server and MariaDB.
Could you, please, have a look at this and confirm the issue? Best regards, Dmitry
