Skip to content

Conversation

@leigaol
Copy link
Contributor

@leigaol leigaol commented Oct 1, 2024

Problem

Current LSP start is coupled with vector index creation, this should be decoupled. We will be having new releases in the LSP to build some other indexes for everyone very soon ( not computation expensive as vector index), therefore we need to start LSP by default. The vector indexing, as a computational expensive index, will be only enabled if opt-in.

Solution

Decouple LSP from vector index creation; start LSP by default


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@leigaol leigaol requested review from a team as code owners October 1, 2024 15:55
@leigaol leigaol requested a review from Will-ShaoHua October 1, 2024 15:55
@github-actions
Copy link

github-actions bot commented Oct 1, 2024

This pull request modifies code in src/ but no tests were added/updated. Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@nkomonen-amazon nkomonen-amazon merged commit 562128a into aws:master Oct 10, 2024
9 of 10 checks passed
@Will-ShaoHua Will-ShaoHua changed the title feat(amazonq): Decouple LSP from vector index creation; start LSP by default config(amazonq): Decouple LSP from vector index creation; start LSP by default Oct 17, 2024
@Will-ShaoHua Will-ShaoHua changed the title config(amazonq): Decouple LSP from vector index creation; start LSP by default feat(amazonq): Decouple LSP from vector index creation; start LSP by default Oct 17, 2024
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 this pull request may close these issues.

3 participants