You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Ramachandran (Jira)" <ji...@apache.org> on 2022/09/28 15:20:00 UTC

[jira] [Updated] (RANGER-3929) To support batching in SQL IN clause of SQL queries used in Ranger

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

Ramachandran updated RANGER-3929:
---------------------------------
    Attachment: 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch

> To support batching in SQL IN clause of SQL queries used in Ranger
> ------------------------------------------------------------------
>
>                 Key: RANGER-3929
>                 URL: https://issues.apache.org/jira/browse/RANGER-3929
>             Project: Ranger
>          Issue Type: Improvement
>          Components: admin
>    Affects Versions: 3.0.0
>            Reporter: Ramachandran
>            Assignee: Ramachandran
>            Priority: Major
>         Attachments: 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch
>
>
> As of  now, we are not handling the max values that will be passed into the IN clause SQL queries
> Most of the databases which support maximum of 1000 values in the IN clause 
>  
>  
> {code:java}
> getEntityManager()
> .createNamedQuery("XXPolicyRefUser.deleteByIds", tClass)
> .setParameter("ids", ids).executeUpdate();
>  
> {code}
> We will get the issue when the size grows more than 1000 otherwise we will not face any issue.
> We  need to fix this to avoid the potential bug in the later point of time
>  
>  



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