[
https://issues.apache.org/jira/browse/NIFI-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajmund Takacs updated NIFI-13311:
----------------------------------
Status: Patch Available (was: In Progress)
> Turn DB adapters into controller services
> -----------------------------------------
>
> Key: NIFI-13311
> URL: https://issues.apache.org/jira/browse/NIFI-13311
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 2.0.0-M3, 2.0.0-M2, 2.0.0-M1
> Reporter: Rajmund Takacs
> Assignee: Rajmund Takacs
> Priority: Major
> Labels: enhancement, migration, poc
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Most of the SQL processors have a property now, where the user is supposed to
> select a dialect their database understands. The list of supported dialects
> is currently hard-coded into the standard processors, and therefore there is
> no way to add a new one as an end-user, without forking NiFi.
> On the other hand, the user is allowed to supply their own DBCP controller
> service, by just dropping in the nar. So having a fixed list of supported SQL
> dialects is a serious limitation, since the user can have an unsupported
> database, and while they can create the necessary DBCP, they cannot add
> support for the dialect.
> We could resolve this problem by turning these fixed lists into controller
> services, so letting users fully interfacing NiFi with their own database.
> With NiFi 2.x, there is a property migration framework, that could be
> utilized in order to avoid breaking existing flows after upgrade.
> For 1.x line, we could probably introduce an option to pick the controller
> service too, by having an option in these fixed lists like 'Use Controller
> Service'. This could also be the default option, educating existing users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
