[ESRCH-37] Introduce a mixin to make sure data is ingested in ES Created: 15/Oct/20 Updated: 26/Jul/21 |
|
| Status: | Accepted |
| Project: | External Enterprise Search |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
Scenario - Difficult to know if a document is sync or note Idea of solution/improvement - In the runtime, we want to make sure that we have ingested all the data in ES. In additional, we also want to make sure we don't send any unnecessary load to ES e.g. already ingested data shouldn't be sent to ES. Hence, we would like to introduce a mixin to make sure the data has been sent to ES prior to any modification
AC
|