NIFI-2583 added the ability (via dynamic properties) to specify initial Max Values for columns, to enable the user to "pick up where they left off" if something happened with a flow, a NiFi instance, etc. where the state was stored but the processing did not complete successfully.
This feature would also be helpful in GenerateTableFetch, which also supports max-value columns.
NIFI-2881 adds incoming flow file support, it's more useful if Initial max values can be specified via flow file attributes. Because if a table name is dynamically passed via flow file attribute and Expression Language, user won't be able to configure dynamic processor attribute in advance for each possible table.
Add dynamic properties ('initial.maxvalue.<max_value_column>' same as QueryDatabaseTable) to specify initial max values statically, and also use incoming flow file attributes named 'initial.maxvalue.<max_value_column>' if any.