The cuc_actiontext column has been removed from the cu_changes table. Therefore it needs to be no longer used in the queries in sqoop.py in analytics/refinery.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Don't select cuc_actiontext from cu_changes for sqoop | Dreamy Jazz | analytics/refinery | master | +0 -3 |
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Dreamy_Jazz | T371099 No longer use removed cuc_actiontext column in analytics/refinery | ||
| Resolved | Feature | Dreamy_Jazz | T324907 Create separate tables for log events in CheckUser | |
| · · · |
Event Timeline
Comment Actions
Change #1057221 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[analytics/refinery@master] Don't select cuc_actiontext from cu_changes for sqoop
Comment Actions
Adding this to our Sprint board as it needs to get a look and deployment. But the change looks good, just have to alter the table and make sure the timing of all the jobs works out.
Comment Actions
this got lost in the sprint move and almost broke a bunch of stuff, but I had a nightmare about it so it's all good
Comment Actions
Change #1057221 merged by Milimetric:
[analytics/refinery@master] Don't select cuc_actiontext from cu_changes for sqoop
Comment Actions
I have deployed this so it should be picked up by the job that starts on Sep. 1st. I have not dropped the column out of the table because old data is deleted quickly anyway and it doesn't hurt the insert.