-
Notifications
You must be signed in to change notification settings - Fork 113
fix: isp column appears to be out of order between last_seen and daily table for some products #7157
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
fix: isp column appears to be out of order between last_seen and daily table for some products #7157
Conversation
…y table for some products. Fix order of the isp column in the last_seen view
Integration report for "fix: isp column appears to be out of order between last_seen and daily table for some products. Fix order of the isp column in the last_seen view"
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a jira ticket for this issue https://mozilla-hub.atlassian.net/browse/DENG-7977 which would address the general case but moving isp
is good enough
I'd lean toward #7119 over this. |
@sean-rose , I'd be okay with that too. Except long term this means we have more points where we need to remember to make updates as columns get added to the daily table. My question here would be, what would be the risk of doing it this way? At least until we can come up with and implement a better / long term solution for this? In general, I'd argue that this specific table should only contain the client_id, sample_id, and the bit fields and nothing else. But since this is currently blocking my changes related to ToS / ToU which is high priority so my preference would be to just take the action of least friction now so that I can get that work completed. |
That makes sense, and I'm fine with you merging this to unblock downstream work, I'd just personally like to see something like #7119 be the ultimate solution. Only selectively reordering columns when a schema mismatch with incompatible column types causes an outright query error still leaves the possibility of a potentially worse outcome of this query silently doing the wrong thing if there's a mismatched column order with compatible column types and nobody noticing. |
I belatedly realized that |
fix: isp column appears to be out of order between last_seen and daily table for some products.
This change is to fix the location of the isp column in the last_seen view. Making this change as currently this results in dry run failure for focus_nightly, focus_beta and klar.
blocks: #7072