[
https://issues.apache.org/jira/browse/NIFI-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdinand updated NIFI-7686:
----------------------------
Description:
{{SimpleDatabaseLookupService and DatabaseRecordLookupService}} require to
configure a _"Lookup Key Column"_. However, sometimes the database schema might
require you to lookup a record or attribute identified by a composite primary
key, i.e. using multiple keys. Wouldn't it be convenient to be able to specify
any amount of lookup key columns and {{AND}}-concatenate the respective values
in the [query's
{{WHERE}}-clause?|https://github.com/apache/nifi/blob/716ba992f5b4641c20465638d62d1e3ffe91d118/nifi-nar-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/main/java/org/apache/nifi/lookup/db/SimpleDatabaseLookupService.java#L139]?
Instead of a single string, {{LOOKUP_KEY_COLUMN}} (and the lookups processors'
respective fields) may accept a comma-separated list of column names /
identifiers.
What are your thoughts on this?
was:
{{SimpleDatabaseLookupService }}and{{ DatabaseRecordLookupService}} require to
configure a _"Lookup Key Column"_. However, sometimes the database schema might
require you to lookup a record or attribute identified by a composite primary
key, i.e. using multiple keys. Wouldn't it be convenient to be able to specify
any amount of lookup key columns and {{AND}}-concatenate the respective values
in the [query's
{{WHERE}}-clause?|https://github.com/apache/nifi/blob/716ba992f5b4641c20465638d62d1e3ffe91d118/nifi-nar-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/main/java/org/apache/nifi/lookup/db/SimpleDatabaseLookupService.java#L139]?]
Instead of a single string, {{LOOKUP_KEY_COLUMN}} (and the lookups processors'
respective fields) may accept a comma-separated list of column names /
identifiers.
What are your thoughts on this?
> Support multiple key columns in database lookup services
> --------------------------------------------------------
>
> Key: NIFI-7686
> URL: https://issues.apache.org/jira/browse/NIFI-7686
> Project: Apache NiFi
> Issue Type: Wish
> Components: Core Framework
> Reporter: Ferdinand
> Priority: Minor
>
> {{SimpleDatabaseLookupService and DatabaseRecordLookupService}} require to
> configure a _"Lookup Key Column"_. However, sometimes the database schema
> might require you to lookup a record or attribute identified by a composite
> primary key, i.e. using multiple keys. Wouldn't it be convenient to be able
> to specify any amount of lookup key columns and {{AND}}-concatenate the
> respective values in the [query's
> {{WHERE}}-clause?|https://github.com/apache/nifi/blob/716ba992f5b4641c20465638d62d1e3ffe91d118/nifi-nar-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/main/java/org/apache/nifi/lookup/db/SimpleDatabaseLookupService.java#L139]?
> Instead of a single string, {{LOOKUP_KEY_COLUMN}} (and the lookups
> processors' respective fields) may accept a comma-separated list of column
> names / identifiers.
> What are your thoughts on this?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
