[ https://issues.apache.org/jira/browse/NIFI-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888806#comment-15888806 ]
ASF GitHub Bot commented on NIFI-3540: -------------------------------------- GitHub user patricker opened a pull request: https://github.com/apache/nifi/pull/1547 NIFI-3540 @mattyb149, ran into a bug with the MS SQL JDBC driver where the change you made for NIFI-2881/#1407 causes problems. Small fix. ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/patricker/nifi NIFI-3540 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1547.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1547 ---- commit 626deeb460825309efb23c7160245c5af58fef9d Author: patricker <patric...@gmail.com> Date: 2017-02-28T20:18:36Z NIFI-3540 ---- > 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 > Affects Versions: 1.2.0 > Reporter: Peter Wicks > Assignee: Peter Wicks > Priority: Blocker > > 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)