-
Notifications
You must be signed in to change notification settings - Fork 143
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
multi-property option to analyze properties seperately #318
Comments
Yes, the events from each of those properties will each have a unique |
Thanks! But does that mean that we still first combine the datasets from both properties? I am using the bigquery connection and if i create the base table the query costs will be a lot higher if i first combine the tables and after that select different streaming ids to seperate them |
It's up to you if you'd like 3 separate projects for 3 properties or 1 larger project with 3 properties. You can either process and analyze them independently or jointly. In either case, all data is partitioned on date, so you can limit costs by including date filters. Hopefully that helps. |
I suspect it would also help save cost if the base table creation in |
@DVDH-000 It's currently clustered on I'm pretty certain that config setting can be overridden in the project yaml. And if anyone wants to run some empirical tests to demonstrate which is more performant under various scenarios, by all means :) |
We can select multiple properties like this:
And it then combines the dataset into one (with combined_property_data()). I need a way to analyze them seperately in the same project. Is there a workaround for this? Thanks in advance!
The text was updated successfully, but these errors were encountered: