atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <>
Subject [jira] [Updated] (ATLAS-347) Atlas search APIs should allow pagination of results
Date Tue, 05 Jul 2016 10:54:11 GMT


Shwetha G S updated ATLAS-347:
    Attachment: ATLAS-347.patch

1. orderby doesn't require fully qualified field name anymore. For example,  'hive_table orderby
name' resolves name to
2. Added limit and offset to search by DSL API.
3. DSL query adds API's limit and offset to the specified DSL query. For eaxmple, 'hive_table
orderby name' maps to 'hive_table orderby name limit 100 offset 0'. 'hive_table orderby name
limit 200 offset 10' maps to 'hive_table orderby name limit 100 offset 10'. 100 and 0 are
API's limit and offset respectively here
4. orderby was using case insensitive search. Changed it to case sensitive search as the query
fails if the orderby property is not set
5. All existing tests work

1. Add more tests 
2. Add limit and offset for full text search. I don't think the index search that we do supports
pagination. May have to filter results on atlas server

> Atlas search APIs should allow pagination of results
> ----------------------------------------------------
>                 Key: ATLAS-347
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Hemanth Yamijala
>            Assignee: Shwetha G S
>            Priority: Critical
>         Attachments: ATLAS-347.patch
> Currently, we can search for all entities of type like a hive table or hive column (query
string is hive_table or hive_column). The API returns all results at one shot in this case.
With a sufficiently large number of entities, this would be a huge list and a lot of data
flowing from server to UI. To scale this better, we should have a way of specifying to get
a page of results at a time in the API.

This message was sent by Atlassian JIRA

View raw message