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

chore(data-warehouse): add data warehouse type to experiment trend goal #21053

Closed
wants to merge 4 commits into from

Conversation

EDsCODE
Copy link
Member

@EDsCODE EDsCODE commented Mar 20, 2024

Problem

  • data warehouse in trend goal not supported right now

Changes

  • add support

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

@EDsCODE EDsCODE marked this pull request as draft March 20, 2024 15:53
Copy link
Contributor

github-actions bot commented Mar 20, 2024

Size Change: 0 B

Total Size: 824 kB

ℹ️ View Unchanged
Filename Size
frontend/dist/toolbar.js 824 kB

compressed-size-action

@EDsCODE EDsCODE marked this pull request as ready for review March 21, 2024 19:01
@EDsCODE EDsCODE enabled auto-merge (squash) March 22, 2024 21:56
@@ -131,6 +135,15 @@ export function ExperimentInsightCreator({ insightProps }: { insightProps: Insig
TaxonomicFilterGroupType.Elements,
TaxonomicFilterGroupType.HogQLExpression,
]}
actionsTaxonomicGroupTypes={
Copy link
Collaborator

Choose a reason for hiding this comment

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

the backend feeds into the old trends query runner class, will that handle dataWarehouse actions? Basically this line: https://github.com/PostHog/posthog/blob/master/ee/clickhouse/queries/experiments/trend_experiment_result.py#L225 unsure if this automagically supports these new types.

Not sure if you've tried running an experiment locally yet. We'll also add a breakdown by feature flag to the metric, so I imagine this table needs to have the flag properties as well? Unless its a funnel with the first event coming from non-data warehouse (which will automatically populate it) - but I assume that still requires a personID column in the warehouse to match the right persons?

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh hmm, if the backend depends on old trends query runner, this won't work yet

@neilkakkar neilkakkar disabled auto-merge March 22, 2024 22:04
@EDsCODE EDsCODE marked this pull request as draft March 22, 2024 22:21
@posthog-bot
Copy link
Contributor

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

@EDsCODE EDsCODE removed the stale label Apr 2, 2024
@posthog-bot
Copy link
Contributor

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

@posthog-bot
Copy link
Contributor

This PR was closed due to lack of activity. Feel free to reopen if it's still relevant.

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

Successfully merging this pull request may close these issues.

4 participants