Koji Kawamura 2007c207ab NIFI-4393: Handle database specific identifier escape characters ...

QueryDatabaseTable and GenerateTableFetch processors were not able to
use max value state as expected, if max value column was wrapped with
escape characters. Due to a mis-match between computed state keys
and actual keys used in the managed state. State keys computed by
getStateKey method included escape characters while actual stored keys
did not. Resulted querying the same dataset again and again.

This commit added unwrapIdentifier method to DatabaseAdapter class to
remove database specific escape characters for identifiers such as table
and column names, so that max value state keys are populated correctly
even if identifiers are wrapped with escape characters.

This commit also added new DatabaseAdapter for MySQL, to handle MySQL
specific identifier escape with back-ticks.

This closes #2424

Signed-off-by: Mike Thomsen <mikerthomsen@gmail.com>

2018-05-03 09:06:05 -04:00

..

src

NIFI-4393: Handle database specific identifier escape characters

2018-05-03 09:06:05 -04:00

pom.xml

NIFI-4995-RC3 prepare for next development iteration

2018-04-03 08:28:34 -07:00