Update next be a complete string url

[hamza-56]

PROD-4266

Update next be a complete string url (like v1) rather than a list in /api/v2/search/all

[DawoudSheraz]

how is has_next calculated here?

[hamza-56]

SearchAfterPagination extends PageNumberPagination from django_elasticsearch_dsl_drf.pagination
PageNumberPagination extends pagination.PageNumberPagination from rest_framework

ref: https://github.com/barseghyanartur/django-elasticsearch-dsl-drf/blob/master/src/django_elasticsearch_dsl_drf/pagination.py

[DawoudSheraz]

Yes but that does not answer how it will fit in with SearchAfter pagination where the next is determined from sort values.

[hamza-56]

def has_next(self):
    return self.number < self.paginator.num_pages

The has_next method checks if there are additional pages available by comparing the current page number (self.number) with the total number of pages (self.paginator.num_pages).

num_pages: Calculates the total number of pages based on the total count of objects (self.count), adjusted for orphans, and divided by per_page. It uses ceil to ensure partial pages are counted as full pages.
count: Determines the total number of objects. If the dataset has a callable count method (e.g., a QuerySet in Django), it uses that for efficiency. Otherwise, it defaults to the length of the object list.

References:

1. https://github.com/django/django/blob/main/django/core/paginator.py#L205
2. https://github.com/django/django/blob/main/django/core/paginator.py#L114

The current implementation does not include anything that should break the has_next calculation for search_after pagination in Elasticsearch