[
https://issues.apache.org/jira/browse/NIFI-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduardo Mota Fontes updated NIFI-9211:
--------------------------------------
Description:
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.
was:
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, a 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.
> 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
> Priority: Major
>
> 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)
