[
https://issues.apache.org/jira/browse/NIFI-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zenkovac updated NIFI-11058:
----------------------------
Description:
when running an incremental query with QueryDatabaseTable, the field under
"Maximum-value Columns" is used in subsequent queries to create an incremental
ingest of data, but such field is used in the query "as is", so oracle becomes
un-performant.
make an improvent providing the ability to set the "Maximum-value Columns" as
an oracle bind variable.
explanation: [https://www.akadia.com/services/ora_bind_variables.html]
was:
when running an incremental query with QueryDatabaseTable, the field under
"Maximum-value Columns" is used in subsequent queries to create an incremental
ingest of data, but such field is used in the queri "as is", so oracle become
un-performant.
make an improvent providing the ability to set the "Maximum-value Columns" as
an oracle bind variable.
explanation: https://www.akadia.com/services/ora_bind_variables.html
> QueryDatabaseTable Maximum-value Columns oracle performance
> -----------------------------------------------------------
>
> Key: NIFI-11058
> URL: https://issues.apache.org/jira/browse/NIFI-11058
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: nifi up to latest 1.19.1
> Reporter: Zenkovac
> Priority: Major
>
> when running an incremental query with QueryDatabaseTable, the field under
> "Maximum-value Columns" is used in subsequent queries to create an
> incremental ingest of data, but such field is used in the query "as is", so
> oracle becomes un-performant.
> make an improvent providing the ability to set the "Maximum-value Columns" as
> an oracle bind variable.
> explanation: [https://www.akadia.com/services/ora_bind_variables.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
