-
Notifications
You must be signed in to change notification settings - Fork 714
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
Collect aggregates for fbid/hashout tables #383
Conversation
Hi @santoshbanda, can you help me review this change? Thanks! |
@santoshbanda has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Should this be visible to the public? On Tue, Nov 1, 2016 at 2:44 PM, Facebook Community Bot <
Mark Callaghan |
Also, how do you guard against referencing beyond the array when you assume On Tue, Nov 1, 2016 at 3:01 PM, MARK CALLAGHAN [email protected] wrote:
Mark Callaghan |
Hi @mdcallag , Thanks for reviewing this change! Yeah, if the column offsets get changed, the stats will be incorrect. but I think this schema change will rarely happen, if so, we can detect that from the stats, since the data must be quite different. |
yeah. That's true. It is not a good idea to do hardcoding. Since the table name is unique, only FBID table will get matched, and I think deleting column of FBID table will rarely happen, if so, mysqldump will throw some error, and then we can fix that. If you have other better suggestions, I am happy to take it. Thanks! |
I don't see where the code confirms that the offsets used to reference On Tue, Nov 1, 2016 at 3:21 PM, tinaLuofb [email protected] wrote:
Mark Callaghan |
I don't think it is a good idea to throw errors in mysqldump if some columns are removed or modified. You should handle these edge cases and ignore collecting the stats and let the mysqldump succeed. |
e2bea02
to
9efb752
Compare
@tinaLuofb updated the pull request - view changes - changes since last import |
Hi @mdcallag @santoshbanda I just updated my change to handle the edge case, let me know if there is other suggestions. Thanks for reviewing this! |
9efb752
to
767efe5
Compare
@tinaLuofb updated the pull request - view changes - changes since last import |
767efe5
to
e15eaa2
Compare
@tinaLuofb updated the pull request - view changes - changes since last import |
e15eaa2
to
6feaa46
Compare
@tinaLuofb updated the pull request - view changes - changes since last import |
Summary: Collect aggregates for fbid/hashout tables during mysqldump. This change is similar to facebook@8200e5e?diff=unified Closes facebook#383 Github Author: Ting Luo <[email protected]> Github PR Sync: {sync, type="child", parent="github", parentrepo="facebook/mysql-5.6", parentprnum="383", parentprfbid="233994987017395"} Test Plan: Imported from GitHub, without a `Test Plan:` line. Reviewers: flupps, santoshb, svcscm Reviewed By: santoshb, svcscm Subscribers: svcscm, liat, bagrawal, webscalesql-eng@ Differential Revision: https://phabricator.intern.facebook.com/D4113658 Signature: t1:4113658:1479510391:531aac0fa1814f539795db1a2abc87ba7aa96714
Summary: Collect aggregates for fbid/hashout tables during mysqldump. This change is similar to 8200e5e?diff=unified Closes #383 Reviewed By: santoshbanda Differential Revision: D4113658 Pulled By: tinaLuofb fbshipit-source-id: 9e3ebd9
Summary: Collect aggregates for fbid/hashout tables during mysqldump. This change is similar to facebook@8200e5e?diff=unified Closes facebook#383 Reviewed By: santoshbanda Differential Revision: D4113658 Pulled By: tinaLuofb fbshipit-source-id: 9e3ebd9
Collect aggregates for fbid/hashout tables during mysqldump. This change is similar to 8200e5e?diff=unified