[
https://issues.apache.org/jira/browse/NIFI-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792213#comment-16792213
]
ASF subversion and git services commented on NIFI-6082:
-------------------------------------------------------
Commit 4db5446c878a9be1d621429686f2835dc642d550 in nifi's branch
refs/heads/master from Koji Kawamura
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4db5446 ]
NIFI-6082: Refactor the way to handle fields nullable
- Make enriched fields nullable at LookupRecord.
- Removed unnecessary AvroConversionOptions and reader schema creation,
because ResultSetRecordSet can generate NiFi Record Schema from RS
directly. No Avro schema is needed to do that.
> Create a Database LookupService
> -------------------------------
>
> Key: NIFI-6082
> URL: https://issues.apache.org/jira/browse/NIFI-6082
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The contribution for NIFI-3404 was originally intended to include a
> DatabaseLookupService, but due to various reasons it was excluded from the
> final PR that was merged.
> This Jira proposes to add a DatabaseLookupService controller service, where
> values can be retrieved from an external RDBMS (through the use of a
> DBCPService). Design considerations include which key(s) to accept, whether
> to locally cache no/some/all queries, result sets, etc. The major requirement
> is to be able to enrich record-based flow file values (via LookupRecord) from
> an external RDBMS source.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
