Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[connector-builder] Child Stream only returns records from the first page of the parent stream when using pagination #40573

Closed
argylepayments opened this issue Jun 27, 2024 · 2 comments

Comments

@argylepayments
Copy link

Topic

Parent Stream Pagination

Relevant information

I have setup a no code connector that has a stream that is using a parent stream. The child stream only returns the first page of records. It does not go through all the pages of the parent stream.

@zoloogg
Copy link

zoloogg commented Jul 3, 2024

Same. Example configuration:

Parent pagination

type: DefaultPaginator
page_token_option:
  type: RequestOption
  inject_into: request_parameter
  field_name: start
pagination_strategy:
  type: CursorPagination
  cursor_value: '{{ response.get("next", {}) }}'
  stop_condition: '{{ not response.get("next", {}) }}'

Child config

- type: SubstreamPartitionRouter
  parent_stream_configs:
    - type: ParentStreamConfig
      parent_key: ID
      request_option:
        type: RequestOption
        field_name: id
        inject_into: request_parameter
      partition_field: parent_id
      stream:
        $ref: '#/definitions/streams/deals'

@marcosmarxm marcosmarxm changed the title No Code Connector builder Child Stream only returns records from the first page of the parent stream when using pagination [connector-builder] Child Stream only returns records from the first page of the parent stream when using pagination Jul 8, 2024
@natikgadzhi
Copy link
Contributor

@zoloogg we're tracking this in #40734 — closing this, but we're going to wrap it up and ship later this week!

@natikgadzhi natikgadzhi added the duplicate This issue or pull request already exists label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants