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

Lambda searcher: default metastore_uri breaks search #5401

Closed
psanford opened this issue Sep 9, 2024 · 1 comment · Fixed by #5403
Closed

Lambda searcher: default metastore_uri breaks search #5401

psanford opened this issue Sep 9, 2024 · 1 comment · Fixed by #5403
Assignees
Labels
bug Something isn't working

Comments

@psanford
Copy link

psanford commented Sep 9, 2024

Describe the bug

I'm setting up quickwit in lambda for the first time. I loaded some data with the indexer but when I invoked the search lambda I would get back an index not found error.

After I invoked the searcher I noticed a new file in my s3 bucket that had an unusual looking path:

s3://psanford-quickwit-search/index}#polling_interval=${QW_LAMBDA_SEARCHER_METASTORE_POLLING_INTERVAL_SECONDS:-60s/manifest.json

Note the improperly expanded variable literals.

This appeared to be coming from searcher/environment.rs.

I suspected that this might be related to my issue so I updated the code to:

metastore_uri: s3://${QW_LAMBDA_METASTORE_BUCKET}/index#polling_interval=60s

After deploying this change, the quickwit searcher lambda was able to find my index and return search results.

@psanford psanford added the bug Something isn't working label Sep 9, 2024
@rdettai rdettai self-assigned this Sep 9, 2024
@rdettai
Copy link
Contributor

rdettai commented Sep 9, 2024

The interpolation string looks right, but I also just noticed the error in our internal CI.

@rdettai rdettai linked a pull request Sep 9, 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
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants