[
https://issues.apache.org/jira/browse/RANGER-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4480:
-----------------------------------
Description:
In case of GDS we cannot apply pagination from DB side Directly as some filters
are after the DB results with pagination enabled (i.e without
pageSize,startIndex as query params)we get result in batch size of 200 (default
pageSize) then this result is incomplete to apply filters which are after the
DB result (i.e filters which are in code only)
Example
1)GET shared resource API we have a query param 'resourceContains' using this
we can get shared-resource which has resource value matching with the query
param
Problem is if we have more than 200 shared resources (i.e beyond default
pageSize) in DB and we pass this param and the actual object resides in DB
beyond the pageSize limit and we dont have pageSize,startIndex in the request
then we will only retrive from DB only 200 shared-resources and further filters
will only get applied on those 200 objects but we did not retrive the actual
object we expect at response as it was beyond the default pageSize
So in case of GDS APIs we need to disable pagination
was:In case of GDS we cannot apply pagination from DB side Directly as some
filters are after the DB results with pagination enabled we get result in batch
size of 200 then this result is incomplete to apply filters which are after the
DB result (i.e filters which are in code only)
> Disable pagination for GDS APIs
> -------------------------------
>
> Key: RANGER-4480
> URL: https://issues.apache.org/jira/browse/RANGER-4480
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Prashant Satam
> Assignee: Prashant Satam
> Priority: Major
>
> In case of GDS we cannot apply pagination from DB side Directly as some
> filters are after the DB results with pagination enabled (i.e without
> pageSize,startIndex as query params)we get result in batch size of 200
> (default pageSize) then this result is incomplete to apply filters which are
> after the DB result (i.e filters which are in code only)
> Example
> 1)GET shared resource API we have a query param 'resourceContains' using this
> we can get shared-resource which has resource value matching with the query
> param
> Problem is if we have more than 200 shared resources (i.e beyond default
> pageSize) in DB and we pass this param and the actual object resides in DB
> beyond the pageSize limit and we dont have pageSize,startIndex in the request
> then we will only retrive from DB only 200 shared-resources and further
> filters will only get applied on those 200 objects but we did not retrive the
> actual object we expect at response as it was beyond the default pageSize
> So in case of GDS APIs we need to disable pagination
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
