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

As a plugin developer, I want to archive my historical plugin's data without having to re-process all other plugins as well #5392

Closed
quba opened this issue Jun 30, 2014 · 4 comments
Labels
c: Performance For when we could improve the performance / speed of Matomo. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.

Comments

@quba
Copy link
Contributor

quba commented Jun 30, 2014

I wonder if it could be possible to archive one specified plug-in.

Example scenario, when such feature would be useful:
-running high-traffic instance using Piwik,
-install new plug-in that is using daily archiving,
-archive all historical data.

Currently it's only possible by dropping archives for all plug-ins. It's an overkill in most cases.
Keywords: archiving

@quba quba added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab mattab removed the P: normal label Aug 3, 2014
@mattab mattab modified the milestones: Mid term, Piwik 2.6.0 Aug 4, 2014
@mattab mattab changed the title Feature request: archive one plugin As a plugin developer, I want to archive my historical plugin's data without having to re-process all other plugins as well Aug 4, 2014
@mattab
Copy link
Member

mattab commented Aug 4, 2014

  • maybe a new parameter --archive-plugins to core:archive to specify which plugins we should restrict archiving for.

@mattab mattab modified the milestones: Piwik 2.8.0, Piwik 2.7.0 Sep 2, 2014
@mattab mattab added Major c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. labels Sep 2, 2014
@mattab mattab modified the milestones: Piwik 2.9.0, Piwik 2.8.0 Oct 8, 2014
@mattab mattab modified the milestones: Piwik 2.9.0, Piwik 2.10.0 Oct 23, 2014
@mattab
Copy link
Member

mattab commented Nov 13, 2014

@quba is this still high priority issue?

@quba
Copy link
Contributor Author

quba commented Nov 13, 2014

It isn't that important. It is a "good to have" feature but not a "must have".

@mattab mattab modified the milestones: Mid term, Piwik 2.10.0 Nov 13, 2014
@mattab mattab modified the milestones: Mid term, Long term Dec 5, 2016
@mattab
Copy link
Member

mattab commented Aug 25, 2017

see #11974

@mattab mattab closed this as completed Aug 25, 2017
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Aug 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Performance For when we could improve the performance / speed of Matomo. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

2 participants