feat: move problem engagement MVs #93
Conversation
|
Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
openedx-webhooks
added
the
open-source-contribution
Ian2012
force-pushed
the
cag/mv-blocks
branch
2 times, most recently
from
704a6d3
to
c8360f2
Compare
Ian2012
changed the title
|
This seems ok to me, once |
Ian2012
force-pushed
the
cag/mv-blocks
branch
2 times, most recently
from
3a6813a
to
e539789
Compare
Ian2012
force-pushed
the
cag/problem-performance
branch
from
71b004f
to
91c79dd
Compare
feat: move problem engagement to an mv feat: move problem engagement to an mv feat: move problem engagement to an mv feat: move problem engagement to an mv feat: add subsection block id to items per subsection feat: add subsection block id to items per subsection fix: use section_id for section problem engagement fix: use section_id for section problem engagement fix: use section_id for section problem engagement fix: use section_id for section problem engagement fix: use section_id for section problem engagement
|
@Ian2012 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
Description
This PR moves the problem engagement to an MV. A testing model called
fact_problem_engagement_v2has been created to compare the old model to the new one.In the new model, records with empty
section_subsection_nameare skipped.Author concerns
The data in the new MVs will only be updated once a new problem event is triggered