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

Schema changes will take place in Piwik 3.0.0 (for tables log_visit, log_link_visit_action, log_action) #6953

Closed
mattab opened this issue Jan 8, 2015 · 7 comments
Labels
c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jan 8, 2015

The goal of this issue is to ensure that in Piwik 2.11.0, Piwik 2.12.0, Piwik 2.13.0 and maybe Piwik 2.14.0 we do not introduce any major schema change impacting log_visit or log_link_visit_action.

In the meantime we will research a solution for the database to handle such schema changes in a more manageable way. Maybe Mariadb + TokuDB will solve this.

@mattab mattab added Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. labels Jan 8, 2015
@mattab mattab added this to the Piwik 2.11.0 milestone Jan 8, 2015
@mattab mattab modified the milestones: Piwik 2.11.0, Piwik 2.12.0 Feb 8, 2015
@mattab
Copy link
Member Author

mattab commented Feb 8, 2015

See this comment which links to percona article: #6759 (comment)

@mattab mattab changed the title No schema change allowed on log_visit nor log_link_visit_actions tables No schema change allowed on log_visit nor log_link_visit_actions nor log_action tables Feb 26, 2015
@mattab mattab modified the milestones: Piwik 2.12.0, Piwik 2.13.0 Mar 11, 2015
@mattab mattab modified the milestones: Piwik 2.14.0, Piwik 2.13.0 Apr 22, 2015
@mattab
Copy link
Member Author

mattab commented Apr 22, 2015

This issue still applies to 2.14.0 - but it is planned that in Piwik 3.0.0 we will be able to issue schema changes again (to be confirmed!)

@tsteur
Copy link
Member

tsteur commented Jun 9, 2015

Can we close this issue? I find it kinda useless and annoying seeing this all the time and it pollutes the milestone.

@mattab mattab modified the milestones: 2.15.0, 2.14.0 Jun 9, 2015
@mattab
Copy link
Member Author

mattab commented Jun 9, 2015

@tsteur Moved to 2.15.0. We will be able to add schema changes in Piwik 3.0.0. I'd prefer to leave it opened while it's active to make this policy clear since it can be counter intuitive (eg. if new team members join)

@tsteur
Copy link
Member

tsteur commented Jun 9, 2015

I doubt they would directly make big changes to that and if so, we can still mention that if something potentially needs that ;) Also unlikely that someone would see it in the next milestone then

@mattab mattab modified the milestones: 3.0.0-b1, 2.14.x Jul 30, 2015
@mattab
Copy link
Member Author

mattab commented Jul 30, 2015

Starting in 3.0.0 beta cycle, we can make database schema changes! 🚀 it feels good after 7 months to close this issue.

@mattab mattab closed this as completed Jul 30, 2015
@mattab mattab changed the title No schema change allowed on log_visit nor log_link_visit_actions nor log_action tables Schema changes will take place in Piwik 3.0.0 (for tables log_visit, log_link_visit_action, log_action) Jul 30, 2015
@mattab
Copy link
Member Author

mattab commented Sep 27, 2016

There will be many schema changes in Piwik 3.0.0.

@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Oct 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants