[
https://issues.apache.org/jira/browse/NIFI-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802391#comment-17802391
]
ASF subversion and git services commented on NIFI-12382:
--------------------------------------------------------
Commit 8a55ceb67552f870be0de96858e10f4d46ac199d in nifi's branch
refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8a55ceb675 ]
NIFI-12382 Added DatabaseTableSchemaRegistry Service
- Added nifi-db-schema-registry-service-nar
This closes #8042
Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit 99c843f25ae50ad93f43dc98d67247abb2bd85a1)
> Add DatabaseSchemaRegistry service
> ----------------------------------
>
> Key: NIFI-12382
> URL: https://issues.apache.org/jira/browse/NIFI-12382
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.25.0, 2.0.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Sometimes it is necessary to get the table definition from a database as a
> NiFi Record Schema. This can help ensure that data in the flow adheres to the
> table definition rather than relying on type conversions and such.
> This case proposes to add a controller service called DatabaseSchemaRegistry
> that uses a DBCPService and a table name, fetches the table metadata from the
> database, and creates a RecordSchema from it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
