[
https://issues.apache.org/jira/browse/NIFI-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892382#comment-15892382
]
ASF GitHub Bot commented on NIFI-3540:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/1547
+1 LGTM, ran unit tests and tried on a live NiFi with SQL Server, MySQL,
Oracle, and Postgres connections. Thank you for the fix! Merging to master
> QueryDatabaseTable Failing to Track MS SQL Max Values
> -----------------------------------------------------
>
> Key: NIFI-3540
> URL: https://issues.apache.org/jira/browse/NIFI-3540
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Peter Wicks
> Assignee: Peter Wicks
> Priority: Blocker
> Fix For: 1.2.0
>
>
> A recent change was made to allow for EL to be used in QDB and GTF processors
> for dynamic table name and max value column tracking.
> Part of this change lead to table names being retrieved dynamically from the
> ResultSetMetadata rather then using the value returned by resolving the EL.
> In the MS SQL JDBC driver there is a known bug (for the last 10 years...)
> where sometimes getTableName returns an empty string rather then the
> table/view name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
