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 Feature/Bug Hub #11008

Closed
avaidyanatha opened this issue Mar 9, 2022 · 5 comments
Closed

Source Mixpanel Feature/Bug Hub #11008

avaidyanatha opened this issue Mar 9, 2022 · 5 comments

Comments

@avaidyanatha
Copy link
Contributor

avaidyanatha commented Mar 9, 2022

The centralized hub for all feature requests and bugs associated with the Mixpanel Source has been moved to the Maintainer Github Project.

The table of issues that was previously on this issue is now deprecated but is left in the collapsed section below.

Deprecated Issue Hub

Feature Checklist

Feature Comments Related Issue(s) Related PR Claimed By Merged Bounty
Full Stream Coverage All endpoints have associated streams. ✔️ -
Incremental Sync Not currently implemented for the Engage, Annotations, Cohorts and Cohort Members streams PR @itaseskii $300
Pagination $200
Test Coverage Unit Test Files - Some testing, but more is likely required. @itaseskii $300
Sandbox Account ✔️ -
Docs Formatting This connector doc does not follow our new standard format. $50
Getting Started Guide Very stubbed currently. $100

Bug Checklist

Bug Description Other Notes Related Issue(s) Related PR Claimed By Merged Bounty
Sync failure with high volume Issue $200
Basic normalization fails with duplicate field names Issue $200
429 Status Code is not handled Issue $200
@itaseskii
Copy link
Contributor

itaseskii commented Mar 21, 2022

Hey @avaidyanatha I have done some analysis of what can and can't be done from the above requirements:

  1. Incremental Sync:
  • Engage -> Needs investigation if 'created' property is present by default, if it is custom property stream will require user-defined cursor. *might require dynamic schema creation for custom user defined properties
  • Annotations -> Date field present but connector note says 'annotation date - is the date for which annotation was added, this is not the date when annotation was added That's why stream does not support incremental sync.'
  • Cohorts -> Contains 'created' field which can be used for incremental sync
  • Cohorts Members -> Needs investigation if 'created' property is present by default, if it is custom property stream will require user-defined cursor. *might require dynamic schema creation for custom user defined properties
  1. Pagination:
  • From already present streams only Engage and Cohort Members support pagination which already have it implemented and leaves nothing to be done here
  1. Full Stream Coverage:
  • Missing: /insights, /retention (requires from to), /schemas, /pipeline, /connectors and maybe more

@itaseskii
Copy link
Contributor

Hey @avaidyanatha I would like to tackle the Incremental Sync issue next. I have already written an explanation in the comment above on how I am planning to add incremental sync for each of the streams.

@itaseskii
Copy link
Contributor

Hey @avaidyanatha I have opened a PR for the Incremental Sync issue and I would like to continue with adding full unit test coverage for the connector

@itaseskii
Copy link
Contributor

I have claimed the 429 Status Code is not handled issue

@aharelick
Copy link

Closing this issue as this will all be managed by the Maintainer Github Project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants