-
Notifications
You must be signed in to change notification settings - Fork 29
Closed
Description
Assume that we have run the script created in this ticket - #209
This means that, in dynamodb (and elasticsearch - yet to make changes for ES, but assume that ES and Dynamodb are in sync):
challengeId
- now contains v5 challenge Id
legacyChallengeId
- now contains the legacy challenge id.
Now, when we make an api request to submissions (anything /submissions
or /submissions/:submissionId
), we need to:
- pass the legacy challenge id under
challengeId
attribute itself - v5 challenge id under a new attribute
v5ChallengeId
. This new attribute will exist only in the response - not in dynamodb or elasticsearch.
This is to buy some time while we update all dependent services - so that the dependent services do not fail.
Similarly, when we publish any submission related message into kafka (through bus api), follow the above approach.
(Assume that, we will update the submission elasticsearch processor to correctly enter values in elasitcsearch).