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

source-mixpanel-native: runTransactions: readMessage: Killed #2165

Open
jonwihl opened this issue Nov 22, 2024 · 1 comment · Fixed by #2170
Open

source-mixpanel-native: runTransactions: readMessage: Killed #2165

jonwihl opened this issue Nov 22, 2024 · 1 comment · Fixed by #2170
Assignees

Comments

@jonwihl
Copy link
Contributor

jonwihl commented Nov 22, 2024

No description provided.

@Alex-Bair
Copy link
Contributor

Alex-Bair commented Dec 13, 2024

Reopening because the previous PR did not fix the OOM issues. I have a clearer idea of what the problem is now though. Previously, I assumed that all user profiles returned in cohort_members would have the same/similar shape and size, and a single page_size would work across each cohort when retrieving its members. However, this is not true. Some user profiles are huge and getting a lot of these larger profiles in a single page is OOM-ing the connector.

The only workable path forward I can think of right now is to make cohort_members actually incremental, somehow. I think a possible cursor field is $last_seen, but that needs verified.

Edit: Per this Mixpanel doc, it does sound like $last_seen could be a good cursor field since Mixpanel refers to it as an "Updated at" field.

@Alex-Bair Alex-Bair reopened this Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants