feat: Remove exportEvents #18682
Merged
feat: Remove exportEvents #18682
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tiina303
force-pushed
the
nuke-export-events
branch
from
1173864 to
5bf1dd2
Compare
|
Size Change: 0 B Total Size: 1.99 MB ℹ️ View Unchanged
|
tiina303
force-pushed
the
nuke-export-events
branch
2 times, most recently
from
da29ebf to
c69e91f
Compare
|
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
tiina303
force-pushed
the
nuke-export-events
branch
from
c69e91f to
1ed7987
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
All export events apps have been either moved to batch exports or onEvent apps, this means we can remove the related code.
User communication please see: https://posthog.slack.com/archives/C01FHN8DNN6/p1700503323428169
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?
verified no usage in clouds
select * from posthog_pluginsourcefile where source like '%exportEvents%'