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.

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

Webapp API Endpoint to Serve Indexing Instructions #626

Closed
CarsonDavis opened this issue Feb 22, 2024 · 0 comments · Fixed by #627
Closed

Webapp API Endpoint to Serve Indexing Instructions #626

CarsonDavis opened this issue Feb 22, 2024 · 0 comments · Fixed by #627
Assignees

Comments

@CarsonDavis
Copy link
Collaborator

CarsonDavis commented Feb 22, 2024

Description

When sinequa gets an incoming batch of items to index, it will ping this endpoint to see which collections it should be indexing.

Implementation Considerations

There are many different ways we could implement this.

  • premade parallel jobs have already been created. the webapp checks the sinequa api to see which ones haven't run, and initiates running
  • premade json indexers exist. webapp checks to see which ones don't have any content. passes back the first one it sees with no content
  • Webapp has a to-be-indexed backlog. Each collection carries information about whether it has been indexed on a server and whether it is ready to be indexed on that server. filtering collections on their metadata tells you the indexing desires of the webapp

Deliverable

No response

Dependencies

depends on

@CarsonDavis CarsonDavis self-assigned this Feb 22, 2024
@CarsonDavis CarsonDavis linked a pull request Feb 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant