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

Aditya Gupta updated ATLAS-5163:
--------------------------------
    Description: 
*Jira Summary:* Fixes a bug in Relationship Search where the {{approxCount}} 
field was incorrectly calculated based on the requested {{limit}} value, rather 
than the actual total number of relationships found.

Relationship Search API was supposed to tell you the *total number of related 
entities* (the {{{}approxCount{}}}), even if you only asked for a small set of 
results on one page (using the {{limit}} parameter).

*The problem was* that the system would often lie about the total count. 
Instead of giving you the true total (say, 30), it would just give you the 
value you set for the {{{}limit{}}}.
h3. Consider Total Realtionship = 30(hive_table_db)
h3. Example of the Bug (Total is 30)
 * If you searched and set the page {{limit}} to {*}5{*}, the API incorrectly 
reported the total count ({{{}approxCount{}}}) as {*}5{*}, even though there 
were actually 30 relationships.

 * If you set the page {{limit}} to {*}29{*}, the API reported the total count 
as {*}29{*}.



h3. Example After the Fix (Total is 30)
 * Regardless of whether you set the page {{limit}} to {*}1{*}, {*}10{*}, or 
{*}35{*}, the API now correctly and consistently reports the total number of 
relationships ({{{}approxCount{}}}) as {*}30{*}.

> Relationship Search API approximateCount returns pageLimit value instead of 
> total relationship count
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-5163
>                 URL: https://issues.apache.org/jira/browse/ATLAS-5163
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Aditya Gupta
>            Assignee: Aditya Gupta
>            Priority: Major
>
> *Jira Summary:* Fixes a bug in Relationship Search where the {{approxCount}} 
> field was incorrectly calculated based on the requested {{limit}} value, 
> rather than the actual total number of relationships found.
> Relationship Search API was supposed to tell you the *total number of related 
> entities* (the {{{}approxCount{}}}), even if you only asked for a small set 
> of results on one page (using the {{limit}} parameter).
> *The problem was* that the system would often lie about the total count. 
> Instead of giving you the true total (say, 30), it would just give you the 
> value you set for the {{{}limit{}}}.
> h3. Consider Total Realtionship = 30(hive_table_db)
> h3. Example of the Bug (Total is 30)
>  * If you searched and set the page {{limit}} to {*}5{*}, the API incorrectly 
> reported the total count ({{{}approxCount{}}}) as {*}5{*}, even though there 
> were actually 30 relationships.
>  * If you set the page {{limit}} to {*}29{*}, the API reported the total 
> count as {*}29{*}.
> h3. Example After the Fix (Total is 30)
>  * Regardless of whether you set the page {{limit}} to {*}1{*}, {*}10{*}, or 
> {*}35{*}, the API now correctly and consistently reports the total number of 
> relationships ({{{}approxCount{}}}) as {*}30{*}.



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

Reply via email to