feat(trends): use hogql for legacy insight trends api

[thmsobrmlr]

Problem

We want to use HogQL queries for computing the legacy insight API endpoints. We use /query everywhere in our codebase, but the endpoints can still be called by customers.

Changes

Changes computation of the trends(-like) endpoint to HogQL.

How did you test this code?

CI run

and calling

http://localhost:8000/api/projects/1/insights/trend
http://localhost:8000/api/projects/1/insights/trend?query_method=legacy

with payload

{
  "events": [
    {
      "id": "$pageview",
      "math": "total",
      "type": "events",
      "order": 0
    }
  ],
  "date_from": "-4w",
  "interval": "month"
}

[thmsobrmlr]

I just couldn't get this test to work. During debugging I found that raw_sessions isn't populated in tests, but using a different method to create the events or passing in a valid uuid7 for the session id all didn't work. I couldn't find additional steps in other tests.

Running a session histogram breakdown locally works, e.g.

{
  "events": [
    {
      "id": "$pageview",
      "math": "total",
      "type": "events",
      "order": 0
    }
  ],
  "date_from": "-7d",
  "breakdown": "$session_duration",
  "breakdown_type": "session",
  "breakdown_histogram_bin_count": 2
}

[anirudhpillai]

Where do customers call this endpoint from and does this have the same rate limit as /query?
As CALCULATE_BLOCKING_ALWAYS gives them a way around async processing.

[thmsobrmlr]

They call https://us.posthog.com/api/projects/:team_id/insights/trend/, and yes this allows bypassing async processing and always has (legacy endpoint didn't have async processing).

I think we'll eventually bug them to use the new /query api, but this allows us to get rid of legacy code while giving them a longer grace period.

Current usage can be seen on this dashboard https://us.posthog.com/project/2/dashboard/289911 e.g. the funnels endpoint is only used by one customer.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ CHQueryErrorTimeoutExceeded: DB::Exception: Timeout exceeded: elapsed 109.69949917 seconds, maximum: 60. Stack trace: /api/projects/{parent_lookup_team_id}/insights/... View Issue
• ‼️ CHQueryErrorIllegalTypeOfArgument: DB::Exception: Illegal type Float64 of argument of function notILike: While processing (team_id =... /api/projects/{parent_lookup_team_id}/insights/... View Issue
• ‼️ IndexError: list index out of range /api/projects/{parent_lookup_team_id}/insights/... View Issue
• ‼️ ValidationError: 6 validation errors for EventsNode /api/projects/{parent_lookup_team_id}/insights/... View Issue
• ‼️ AssertionError /api/projects/{parent_lookup_team_id}/insights/... View Issue

_{Did you find this useful? React with a 👍 or 👎}