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
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 11 out of 12 changed files in this pull request and generated 1 comment.
Files not reviewed (1)
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-elasticsearch-e2e/src/test/resources/elasticsearch/elasticsearch_source_with_pit.conf: Language not supported
Do you have more information on PIT vs scroll? @hailin0
Here are the advantages of PIT compared with Scroll API:
Better data consistency: PIT creates a consistent data view, ensuring accurate results even when the index changes during pagination.
Lower resource consumption: It uses snapshots to save search results, only storing document changes after the write point, thus reducing memory consumption.
More flexible usage: Combined with Search After, PIT allows for more stable pagination and is less affected by the number of retrieval requests.
Do you have more information on PIT vs scroll? @hailin0
Here are the advantages of PIT compared with Scroll API:
Better data consistency: PIT creates a consistent data view, ensuring accurate results even when the index changes during pagination.
Lower resource consumption: It uses snapshots to save search results, only storing document changes after the write point, thus reducing memory consumption.
More flexible usage: Combined with Search After, PIT allows for more stable pagination and is less affected by the number of retrieval requests.
Do you have more information on PIT vs scroll? @hailin0
Here are the advantages of PIT compared with Scroll API:
Better data consistency: PIT creates a consistent data view, ensuring accurate results even when the index changes during pagination.
Lower resource consumption: It uses snapshots to save search results, only storing document changes after the write point, thus reducing memory consumption.
More flexible usage: Combined with Search After, PIT allows for more stable pagination and is less affected by the number of retrieval requests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
elasticsearch source support PIT
close #9149
Purpose of this pull request
Does this PR introduce any user-facing change?
How was this patch tested?
Check list
New License Guide
release-note.