You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we use PIT search instead of scroll search in opensearch connector?
It is mentioned that PIT search is preferred when deep pagination is done: Point in Time (PIT) with search_after is the preferred pagination method in OpenSearch, especially for deep pagination. It bypasses the limitations of all other methods because it operates on a dataset that is frozen in time, it is not bound to a query, and it supports consistent pagination going forward and backward. https://opensearch.org/docs/latest/search-plugins/searching-data/paginate/
It is mentioned to use PIT in elastic discussion also: https://discuss.elastic.co/t/sliced-scroll-with-sort/284874
It would be nice to have a feature to enable search using PIT to gain performance benefits when searching on huge datasets.
The text was updated successfully, but these errors were encountered:
hashhar
changed the title
Can we use PIT search instead of scroll search in opensearch connector?
Use point-in-time (PIT) search instead of scroll search in OpenSearch connector
Feb 26, 2024
Can we use PIT search instead of scroll search in opensearch connector?
It is mentioned that PIT search is preferred when deep pagination is done:
Point in Time (PIT) with search_after is the preferred pagination method in OpenSearch, especially for deep pagination. It bypasses the limitations of all other methods because it operates on a dataset that is frozen in time, it is not bound to a query, and it supports consistent pagination going forward and backward.
https://opensearch.org/docs/latest/search-plugins/searching-data/paginate/
It is mentioned to use PIT in elastic discussion also: https://discuss.elastic.co/t/sliced-scroll-with-sort/284874
It would be nice to have a feature to enable search using PIT to gain performance benefits when searching on huge datasets.
The text was updated successfully, but these errors were encountered: