[jira] [Updated] (HIVE-24925) Query materialized view invalidation info can cause ORA-01795

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-24925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stamatis Zampetakis updated HIVE-24925:
---------------------------------------
    Fix Version/s:     (was: 4.0.0)

I cleared the fixVersion field since this ticket is still open. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED.

According to the [JIRA guidelines|https://cwiki.apache.org/confluence/display/Hive/HowToContribute] the fixVersion should be set only when the issue is resolved/closed.

> Query materialized view invalidation info can cause ORA-01795
> -------------------------------------------------------------
>
>                 Key: HIVE-24925
>                 URL: https://issues.apache.org/jira/browse/HIVE-24925
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Krisztian Kasa
>            Priority: Major
>
> Query materialized view invalidation info assemble direct sql query to pull update/delete completed transactions on source tables since the last rebuild of the materialized view.
> Invalid writeIds are also used to filter the result. These writeIds are passed using an *in* operator. 
> Depend on the size of invalid writeId list the operands of the *in* operator or the overall query text can exceed limitations. Example: in case of Oracle backend db maximum number of expressions in a list is 1000.
> {code}
> SELECT "CTC_UPDATE_DELETE"
> FROM "COMPLETED_TXN_COMPONENTS"
> WHERE "CTC_UPDATE_DELETE" ='Y'
> AND ( ("CTC_DATABASE"=? AND "CTC_TABLE"=? AND ("CTC_WRITEID" > 1 OR "CTC_WRITEID" IN (<invalid writeId1>, <invalid writeId2> ... <invalid writeIdn>)) ) OR
>       ("CTC_DATABASE"=? AND "CTC_TABLE"=? AND ("CTC_WRITEID" > 1) )
>       )
> AND "CTC_TXNID" <= 16
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)