Partial paths returned from User Paths
Open
Nobody has claimed this yet.
bug
feature/insights
feature/paths
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug description
- When a "Maximum number of paths" is set, this just adds a
LIMIT nclause to the underlying SQL query. The query returns a list ofA => Bsteps - which means a path with 3 steps (e.g.A => B => C) requires 2 rows of data (A => BandB => C). - Because of this, we can lose the latter steps of some paths with the
LIMITclause - Most of the time, this is unnoticeable, but when you also have "Ends at" turned on, you get some odd results with paths ending at the wrong URL
How to reproduce
- View this support ticket
Thank you for your bug report – we love squashing them!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the User Paths implementation and find the underlying SQL query where the maximum number of paths becomes a LIMIT clause. Reproduce the behavior using the linked support ticket, especially with “Ends at” enabled. Done means limited results retain complete paths and do not end at the wrong URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- analytics, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100