[
https://issues.apache.org/jira/browse/NIFI-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427761#comment-17427761
]
ASF subversion and git services commented on NIFI-9211:
-------------------------------------------------------
Commit e681d4767a4d461cd0c0011d88dbc57e27322b4a in nifi's branch
refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e681d47 ]
NIFI-9211: Fixed NPE when non-existing variable configured for a property with
dynamicallyModifiesClasspath (#5382)
> DBCPConnectionPool import error when using variable in "Database Driver
> Location(s)" property
> ---------------------------------------------------------------------------------------------
>
> Key: NIFI-9211
> URL: https://issues.apache.org/jira/browse/NIFI-9211
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.14.0
> Reporter: Eduardo Mota Fontes
> Assignee: Peter Turcsanyi
> Priority: Major
> Fix For: 1.15.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When using a non-existing variable in "Database Driver Location(s)" property
> of a DBCPConnectionPool, UI gives error message "An unexpected error has
> occurred. Please check the logs for additional details." without any details
> in logs. Same error when using an existing variable, commit it to NiFi
> Registry or export flow's JSON and import as new.
>
> 1) If I use a non-existing variable, I got error;
> 2) If I use an existing variable, it's ok, BUT;
> 3) If I use an existing variable AND commit the flow to the NiFi Registry, I
> can't import that flow anymore. I got same error as case #1;
> 4) If same case as #3, I can import a early version (without import
> problems), then "change version" to the problematic one, it works fine. Seems
> the issue is when creating new components with variable references in the
> import process, along with using non-existing variable in UI.
>
> I've tested with processors and other controller services, and with other
> properties in DBCPConnectionPool, but it seems to be a very specific issue
> with property "Database Driver Location(s)" in DBCPConnectionPool controller
> service.
>
> It seems to me it's a regression from NIFI-8429.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
