Bug: extended person properties do not respect table data type for filters

Open
#44,520 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
data, frontend

Research direction

Start by tracing how insight filters are built for extended person properties coming from a DW join. Reproduce the issue by joining persons on an int column, then check whether the resulting insight exposes the usual integer filter options. Done means the filter choices respect the table data type.

Written by the indexing model from the issue text.

Description

bug team/product-analytics
Bug Description

Bug description

extended person properties do not respect table data type for filters e.g. int does not have the usual filters

How to reproduce

  1. Create a DW join to persons on an int column
  2. Try and use that in an insight and the filter options for ints are not available

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/46361 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/49389)

Debug info
Kind: support

Target area: analytics

Report event: http://go/ticketByUUID/0e1f7f5d-4ded-4513-b7ef-f12bf0ed7c72

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019b922b-e93d-7c2d-a725-0829811038cf?t=602

Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019b922b-e93d-7c2d-a725-0829811038cf%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D

Location: https://eu.posthog.com/project/26904/insights/y6Fg5fpc/edit

Persons-on-events mode for project: person_id_override_properties_on_events
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.