Unifying Elastic vector database and LLM functions for intelligent query Part 2 #453
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Found 1 changed notebook. Review the changes at https://app.gitnotebooks.com/elastic/elasticsearch-labs/pull/453 |
| "from IPython.display import Markdown, display\n", | ||
| "import requests, json\n", | ||
| "from getpass import getpass\n", | ||
| "from google.colab import userdata\n", |
There was a problem hiding this comment.
Can you mention at the top of the document that this notebook must run in a Google Colab environment?
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to topic: https://github.com/orgs/elastic/projects/1446/views/1?filterQuery=llm+function&pane=issue&itemId=107821356&issue=elastic%7Csearch-labs-elastic-co%7C1535
I wrote part one here: https://www.elastic.co/search-labs/blog/llm-functions-elasticsearch-intelligent-query
This is part 2. Uses a different dataset (homes/properties instead of hotels) with the same intelligent query pattern identified in part 1. Additional part two leverages serverless and ships with a UI for search.