Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wikimedia.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
I'm probably misreading this but it seems to contradict "Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables"
Say we we have a script that gets data from WikipediaZeroUsage_14574251, would we need to temporarily change the script to get data from WikipediaZeroUsage_14574251_15423246 for like a day and then change it back to WikipediaZeroUsage_14574251 or would that be a permanent change until another schema revision?
I'm confused.
Say we we have a script that gets data from WikipediaZeroUsage_14574251, would we need to temporarily change the script to get data from
WikipediaZeroUsage_>>14574251_15423246 for like a day and then change it back >to WikipediaZeroUsage_14574251 or would that be a permanent change until another schema revision?
Sorry it was not clear, no. You would have a union in this case.
For example:
-- renamed table, no more new records from 2017/03/23 select * from WikipediaZeroUsage_14574251_15423246
UNION
-- new data gets entered here select * from WikipediaZeroUsage_14574251
Make sense?
On Tue, Mar 21, 2017 at 12:00 PM, Mikhail Popov mpopov@wikimedia.org wrote:
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
I'm probably misreading this but it seems to contradict "Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables"
Say we we have a script that gets data from WikipediaZeroUsage_14574251, would we need to temporarily change the script to get data from WikipediaZeroUsage_14574251_15423246 for like a day and then change it back to WikipediaZeroUsage_14574251 or would that be a permanent change until another schema revision?
I'm confused.
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Yup, makes total sense. Thank you for clarifying!
On Tue, Mar 21, 2017 at 12:31 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Say we we have a script that gets data from WikipediaZeroUsage_14574251, would we need to temporarily change the script to get data from
WikipediaZeroUsage_>>14574251_15423246 for like a day and then change it back >to WikipediaZeroUsage_14574251 or would that be a permanent change until another schema revision?
Sorry it was not clear, no. You would have a union in this case.
For example:
-- renamed table, no more new records from 2017/03/23 select * from WikipediaZeroUsage_14574251_15423246
UNION
-- new data gets entered here select * from WikipediaZeroUsage_14574251
Make sense?
On Tue, Mar 21, 2017 at 12:00 PM, Mikhail Popov mpopov@wikimedia.org wrote:
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
I'm probably misreading this but it seems to contradict "Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables"
Say we we have a script that gets data from WikipediaZeroUsage_14574251, would we need to temporarily change the script to get data from WikipediaZeroUsage_14574251_15423246 for like a day and then change it back to WikipediaZeroUsage_14574251 or would that be a permanent change until another schema revision?
I'm confused.
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wikimedia.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Ok, next week it is. Let's plan for this to happen on Tuesday, March 28th.
On Tue, Mar 21, 2017 at 1:22 PM, Mikhail Popov mpopov@wikimedia.org wrote:
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wiki media.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Hi Nuria,
as part of the Reading team's offsite meeting next week we already have a session scheduled for that day which will involve various people running EventLogging queries. Could we move the outage once more, to Wednesday or later? Many thanks!
On Tue, Mar 21, 2017 at 3:22 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Ok, next week it is. Let's plan for this to happen on Tuesday, March 28th.
On Tue, Mar 21, 2017 at 1:22 PM, Mikhail Popov mpopov@wikimedia.org wrote:
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wiki media.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Yes, we can do it Wednesday.
On Wed, Mar 22, 2017 at 3:44 PM, Tilman Bayer tbayer@wikimedia.org wrote:
Hi Nuria,
as part of the Reading team's offsite meeting next week we already have a session scheduled for that day which will involve various people running EventLogging queries. Could we move the outage once more, to Wednesday or later? Many thanks!
On Tue, Mar 21, 2017 at 3:22 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Ok, next week it is. Let's plan for this to happen on Tuesday, March 28th.
On Tue, Mar 21, 2017 at 1:22 PM, Mikhail Popov mpopov@wikimedia.org wrote:
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wiki media.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Friendly remainder that this will happen within the next couple hours today.
Thanks,
Nuria
On Thu, Mar 23, 2017 at 7:47 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Yes, we can do it Wednesday.
On Wed, Mar 22, 2017 at 3:44 PM, Tilman Bayer tbayer@wikimedia.org wrote:
Hi Nuria,
as part of the Reading team's offsite meeting next week we already have a session scheduled for that day which will involve various people running EventLogging queries. Could we move the outage once more, to Wednesday or later? Many thanks!
On Tue, Mar 21, 2017 at 3:22 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Ok, next week it is. Let's plan for this to happen on Tuesday, March 28th.
On Tue, Mar 21, 2017 at 1:22 PM, Mikhail Popov mpopov@wikimedia.org wrote:
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wiki media.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
This maintenance event has finished.
Thanks,
Nuria
On Wed, Mar 29, 2017 at 8:19 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Friendly remainder that this will happen within the next couple hours today.
Thanks,
Nuria
On Thu, Mar 23, 2017 at 7:47 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Yes, we can do it Wednesday.
On Wed, Mar 22, 2017 at 3:44 PM, Tilman Bayer tbayer@wikimedia.org wrote:
Hi Nuria,
as part of the Reading team's offsite meeting next week we already have a session scheduled for that day which will involve various people running EventLogging queries. Could we move the outage once more, to Wednesday or later? Many thanks!
On Tue, Mar 21, 2017 at 3:22 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Ok, next week it is. Let's plan for this to happen on Tuesday, March 28th.
On Tue, Mar 21, 2017 at 1:22 PM, Mikhail Popov mpopov@wikimedia.org wrote:
Hiya! Also! We're turning off an A/B test this Thursday afternoon and it would make our lives easier for this renaming thing to happen next week :) please and thank you.
- Mikhail
*Imagine a world in which every single human being can freely share in the **sum of all knowledge. That's our commitment.* Donate https://donate.wikimedia.org/.
On Tue, Mar 21, 2017 at 10:57 AM, Nuria Ruiz nuria@wikimedia.org wrote:
Team:
We need to do some maintenance work to the evenlogging database that requires renaming and archiving of all tables that are currently receiving events.
Tables will be renamed from, for example: WikipediaZeroUsage_14574251 to WikipediaZeroUsage_14574251_15423246;
15423246 is the capsule schema version.
As new events are come for 'WikipediaZeroUsage' schema with schema version 14574251 the table WikipediaZeroUsage_14574251 will get recreated again, the only difference is that this new table will have different column length for varchar fields.
Details of this change are here: https://phabricator.wiki media.org/T160454
We will start our maintenance event on Thursday morning around 11 am PST time and it would last couple hours, no data loss on eventlogging will happen as part of this event.
Reportupdater queries that use eventlogging would need to be updated to select from the newly renamed tables (and we will take care of doing that) but other than those we do not think there are any other automated scripts that would need updating. Please let us know otherwise.
Also, please be so kind to let us know if this renaming is disruptive in any way. We can also do this changes at a later time next week.
Thanks,
Nuria
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics