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
LPS-120741 Reindexing new article versions in a publication effects production #1233
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-120741 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#4162 |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#94913 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#3685 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#3685 |
CC @arboliveira this doesn't fully cover the undo case but the current design expects the search index to be fully backed by the database. We don't have a system in place where the search index for production can fully diverge within a publication. At some point I'll try to come up with a system that uses search index independently from the DB for change tracking which could resolve that case. Do you see a better way?