Skip to content
This repository was archived by the owner on Jan 15, 2026. It is now read-only.

Conversation

@fivetran-reneeli
Copy link
Contributor

@fivetran-reneeli fivetran-reneeli commented Jan 29, 2025

PR Overview

This PR will address the following Issue/Feature: #28

This PR will result in the following new package version: v0.5.0-a1

Schema changes from Nov 2024

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

to be completed

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

  • dbt run –full-refresh && dbt test
  • dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

  • The appropriate issue has been linked, tagged, and properly assigned
  • All necessary documentation and version upgrades have been applied
  • docs were regenerated (unless this PR does not include any code or yml updates)
  • BuildKite integration tests are passing
  • Detailed validation steps have been provided below

Detailed Validation

Please share any and all of your validation steps:

If you had to summarize this PR in an emoji, which would it be?

💃

cast(platform_version as {{ dbt.type_string() }}) as platform_version,
cast(source_type as {{ dbt.type_string() }}) as source_type,
cast(page_type as {{ dbt.type_string() }}) as page_type,
cast(pre_order as {{ dbt.type_string() }}) as pre_order,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just fyi. would have thought this is a boolean but apple docs has it as a string.

Copy link
Collaborator

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-reneeli thanks for this PR. A few comments below following this review.

Copy link
Collaborator

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few small changes. Once these are addressed this will be ready for release review for pre-release

Copy link
Collaborator

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few final change requests before approval

README.md Outdated
packages:
- package: fivetran/apple_store_source
version: [">=0.4.0", "<0.5.0"] # we recommend using ranges to capture non-breaking changes automatically
version: 0.5.0-a1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reminder to now update this to be the new range.

sources:
- name: apple_store # This source will only be used if you are using a single apple_store source connector. If multiple sources are being unioned, their tables will be directly referenced via adapter.get_relation.
schema: "{{ var('apple_store_schema', 'itunes_connect') }}"
schema: "{{ var('apple_store_schema', 'apple_appstore') }}"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this accurate? This is actually a very important piece for Quickstart to work. The default schema must be what the default schema provided by the connector. In this case it looks like it's still itunes_connect.
image

We need to keep that default schema.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha-- reverted!

README.md Outdated
version: 0.5.0-a1
```
### Step 3: Define database and schema variables
By default, this package runs using your destination and the `apple_store` schema. If this is not where your apple_store data is (for example, if your apple_store schema is named `apple_store_fivetran`), add the following configuration to your root `dbt_project.yml` file:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's also update this based on the previous comment to state the following

Suggested change
By default, this package runs using your destination and the `apple_store` schema. If this is not where your apple_store data is (for example, if your apple_store schema is named `apple_store_fivetran`), add the following configuration to your root `dbt_project.yml` file:
By default, this package runs using your destination and your Apple Store schema (default `itunes_connect`). If this is not where your Apple Store data is (for example, if your Apple Store schema is named `apple_store_fivetran`), add the following configuration to your root `dbt_project.yml` file:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

Copy link
Collaborator

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

- Following the connector's [Nov 2024 Update](https://fivetran.com/docs/connectors/applications/apple-app-store/changelog#november2024) to sync from the [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi), we've updated this dbt package to reflect the new schema which includes the following changes:

- *Models Removed*:
- `stg_apple_store__app_store_device`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think stg_apple_store__crashes_platform_version got removed too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added to changelog!

Copy link
Contributor

@fivetran-avinash fivetran-avinash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-reneeli I think there is one changelog update you need to make.

Copy link
Contributor

@fivetran-avinash fivetran-avinash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@fivetran-reneeli fivetran-reneeli merged commit 1d8cdf1 into main Feb 20, 2025
8 checks passed
@fivetran-reneeli fivetran-reneeli deleted the nov_2024_schema branch February 20, 2025 19:01
@pestrov
Copy link

pestrov commented Apr 24, 2025

Hi team — we're updating to 0.5.0 right now, and we can't find the APP_STORE_REVIEW model in the source. Why was it bypassed in this release?

We were hoping to get access to all the tables that are in Fivetran ERD. Thanks!

https://docs.google.com/presentation/d/1mtiT--CP6i3uS213Y9LAansdJKCa75Dz5SQ84rtHIFo/edit?slide=id.g244d368397_0_1#slide=id.g244d368397_0_1

@fivetran-reneeli
Copy link
Contributor Author

Hi @pestrov! We only bring in the raw tables that we used downstream in the transformed models (which are in this downstream package here). We don't use APP_STORE_REVIEW in the transformed models. However we are always looking to expand our model offerings! If you can share how APP_STORE_REVIEW plays a role in your analytics, that would inform our prioritization of new model offerings.

We also welcome you to create a feature request here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants