[
https://issues.apache.org/jira/browse/RANGER-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609464#comment-17609464
]
Ramachandran edited comment on RANGER-3929 at 9/26/22 4:24 PM:
---------------------------------------------------------------
The review is available here:https://reviews.apache.org/r/74138/
cc >> [[email protected]] [~vel]
was (Author: JIRAUSER295265):
The review is available here:[https://reviews.apache.org/r/74138/diff
|https://reviews.apache.org/r/74138/dif]
cc >> [[email protected]] [~vel]
> 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
>
> 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)
