-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-2991] [SPIKE] Investigate minimal-snowplow-tracker #8409
Comments
I bumped into a issue with minimal showplow after installing The guide is a little bit inaccurate because it does not say that you need to install
This happens because I propose to update contract of |
I believe it is public: https://github.com/dbt-labs/snowplow-python-tracker |
Do you happen to have any news here? The issue with Meltano persists, I created an issue in their Github: Should I invest my time to work around it in Meltano, or do you plan to solve it here in the near future? |
We don't have a timeline for working on this ticket yet @jaceksan |
Edgar created a pull request which is already under review and IMO it relates to this issue (if it even does not fix it?): |
Why not just release a version 0.1.0 of minimal-snowplow-tracker, and install it to |
That'd be ideal, but it'd still require changes in dbt to update the imports. |
Housekeeping
Short description
minimal-snowplow-tracker
is used indbt-core
for anonymous usage tracking. It is an internally managed fork of snowplow-python-tracker. Currently it is 100+ commits behind and only officially supports up to Python 3.7.Acceptance criteria
Explore if there are performance hits for switching from our fork (
minimal-snowplow-tracker
) to the Snowplow maintained project (snowplow-python-tracker
).Impact to Adapters
None
Context
If there is a performance hit from using the full package maintained by Snowplow, we should look into rolling this code into the code codebase. Will need to verify if any other internal projects are depending on this project.
The
minimal-snowplow-tracker
project is considered acritical project
by PyPI meaning it's in the top 1% of downloads on PyPI. I'm guessing that's because it's a dependency of core which is also acritical project
. When we remove the project we should not remove it from PyPI for 6+ months to ensure we don't accidentally break other projects.The text was updated successfully, but these errors were encountered: