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

Feature/support link list pagination tokens #22

Conversation

s7clarke10
Copy link
Contributor

This change introduces an additional request / response style for API's based on the hateoas api model https://en.wikipedia.org/wiki/HATEOAS - the specific implementation that this has been built and tested against is FHIR based API's https://hl7.org/fhir/http.html. More detail around this is built into the README.md.

This specific change introduces for hateoas_body request and response types:

  • Build pagination support for HATEOAS / FHIR API's
  • Incremental Replication for HATEOAS / FHIR API's
  • Introduces a start_date parameter so that if there is replication_key which is of a datetime datatype it can seed when data is replication from. The Meltano SDK has knowledge about start_dates for incremental replication.
  • Introduces a search_parameter and search_prefix which is used to identify the replication field used by the API and how the data is compared when making an incremental request from the last run position (state).
  • Updated README.md documentation for new features.

Other Changes:

  • Updates the Meltano.yml kind / data types
  • Adds a config.json.sample file for illustrating how to construct a config.json file when using the tap stand-alone for development purposes.

@s7clarke10
Copy link
Contributor Author

Closed: This logic is now incorporated in this PR - #35

@s7clarke10 s7clarke10 closed this Jul 1, 2023
@s7clarke10
Copy link
Contributor Author

Closed: This logic is now incorporated in this PR - #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant