Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[KW-Search] Call ES from core to index at each nodes update point #8762

Open
philipperolet opened this issue Nov 19, 2024 · 3 comments
Open

[KW-Search] Call ES from core to index at each nodes update point #8762

philipperolet opened this issue Nov 19, 2024 · 3 comments
Assignees
@philipperolet

Comments

@philipperolet
Copy link
Contributor

philipperolet commented Nov 19, 2024 •
edited
Loading

See https://www.notion.so/dust-tt/Design-doc-keyword-search-infrastructure-12228599d94180a6b19aeec0b493cb13?pvs=4#14228599d941806eb941da14b4dea447
@philipperolet philipperolet mentioned this issue Nov 19, 2024
Open
@philipperolet philipperolet changed the title [KW-Search] Call search service from core to index at each doc/table/folder update point [KW-Search] Call search service from core to index at each nodes update point Nov 19, 2024
@philipperolet
Copy link
Contributor Author

Updated: dependencies are resolved. We don't need to wait for all parent standardization and folder update / backfills to be made, since we'll make a massive ES backfill at some point (which itself will depend on all parent standardization and folder update / backfills)

@philipperolet philipperolet changed the title [KW-Search] Call search service from core to index at each nodes update point [KW-Search] Call ES from core to index at each nodes update point Dec 12, 2024
@philipperolet
Copy link
Contributor Author

At each upsert on documents / tables / folders / parents

@philipperolet philipperolet self-assigned this Dec 12, 2024
@philipperolet
Copy link
Contributor Author

Will be done in multiple PRs, starting with those indexing documents. See PR #9384 for how deploying safely is handled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philipperolet philipperolet

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@philipperolet