Repository navigation
Migrate Shopify Streams from REST API to GraphQL API - #201
Conversation
…tafields_customers and metafields_orders
4be5461 to
fc706be
Compare
fc706be to
71619f3
Compare
* graphql implementataion for custoemrs, events and locations stream * Use graphql endpoint for orders * add the queries in the respective stream class * Update the logic for inventory levels stream * Optimize inventory levels logic * update transactions and order_refunds logic * Initial commit for abandoned checkouts and collections streams * Remove reference for the collects and custom collections * optimize the order_refunds and transactions stream logic * partial logic for collections * update locations query * add collections streams changes and separate out metafields as individual streams * remove gql query file * remove gql query file reference and include the query in the code * fix abandoned checkouts logic * format the code * remove metafields reference from init file * update checkout schema * fix typo * set the default page size to 250 * make pylint happy and format the code * upgrade python packages * fix circleci pylint issues * modify variable name in collections stream * optimize get query params method * move the graphql base code to the base file * removed reference to the gql_base file * fix the pylint * optimize the source code * update unit test cases * update exception in unit test * Refactor the code - 1. Use the single query for inventiry levels to fetch the child object as well. 2. Add Sortkey in the products query 3. Update query names for the respective metafields * move date_window_size to the parent class * make pylint happy * make pylint happy * Make metafields related stream, order_refunds and transactions stream as pseudo incremental * make pylint happy * the similar scencario is tested in the integration test, so we can skip this test. * Update Integration Tests for GraphQL Migration (#205) * make initial base file changes * add individual meta streams * update all fields integration test * update locations replication key in test suite * remove old references of the stream * avoid testing on the events stream * reduce the default page size for metafields * update state file in the bookmarks * include events in the expected streams * fix interrupt sync * update foreign key for transactions table
|
Hey guys - StitchData customer here. It looks like the GraphQL rewrite omitted the These two issues have broken our reporting pipelines and made us unable to really use StitchData for our usecase. Is this GraphQL rewrite still a work-in-progress? Feels like a lot was missed here and StitchData won't let us roll back or use the old version. At the very least, the new GraphQL-based API call should have all the same data. Should I submit a GitHub issue for this, or is it something we need to ask StitchData support about? |
Description of change
This PR migrates several streams in tap-shopify from the REST API to the GraphQL API, improving performance and efficiency. Additionally, some stream changes were made to better align with Shopify’s data structure.
Changes & Updates
Migrated Streams (REST → GraphQL)
Metafields Stream Refactoring
Removed: metafields (generic metafields stream)
Introduced New Streams:
Collections Stream Refactoring
Removed: collects and custom_collections
Introduced New Stream: collections (consolidated collection stream)
QA steps
Risks
Rollback steps
AI generated code
https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code