feat(hogql): Put retention actor appearances in columns

[webjunkie]

Problem

The result of the retention actors query is hard to understand.

Changes

• put booleans of the returns as columns
• we can let the SQL query do that
• anyone can now filter from frontend or export this way conveniently

How did you test this code?

• click in frontend

[webjunkie]

@mariusandra how can I make these HogQL dialogs understand the columns?

[github-actions]

Size Change: 0 B

Total Size: 2 MB

ℹ️ View Unchanged

Filename	Size
frontend/dist/toolbar.js	2 MB

_{compressed-size-action}

[posthog-bot]

📸 UI snapshots have been updated

4 snapshot changes in total. 0 added, 4 modified, 0 deleted:

• chromium: 0 added, 4 modified, 0 deleted (diff for shard 1, diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[mariusandra]

@mariusandra how can I make these HogQL dialogs understand the columns?

Oh, hmm. Those dialogs are currently hardcoded to assume we're selecting from an "events" or "persons" table. There's a hogQLTable var we pass into the taxonomicFilterLogic via the <TaxonomicFilter /> tag.

This then gets passed to the HogQLMetadata query. We then put this table in a random ast.SelectQuery together with the parsed column, and hope for the best. We need to make the other fields available in scope at parsing time for this to work.

The solution is likely to replace the hogQLTable field with a hogQLBase, which would then be a query node, either {kind:'HogQLQuery', query: 'select * from events'}, or a InsightActorsQuery, or normally just an empty EventsQuery.

[posthog-bot]

📸 UI snapshots have been updated

2 snapshot changes in total. 0 added, 2 modified, 0 deleted:

• chromium: 0 added, 2 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 1)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

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.

[webjunkie]

I realized that interval is the term for the rows already in the general retention result... and then you select one interval to get the appearances/returns... so the columns there should probably be named something else 🤔
I will address that.

[mariusandra]

LGTM 👍. I'll have a think about the column editing. Not blocking for here though.