feat: Use Qdrant FastEmbed as local embedding provider

[leehuwuj]

Summary by CodeRabbit

• New Features

  • Introduced Qdrant FastEmbed as the new local embedding provider.

• Improvements

  • Updated dependency management to support "groq" case with specific versions of llama-index-embeddings-fastembed and llama-index-llms-groq.

• Bug Fixes

  • Modified initialization functions to use FastEmbedEmbedding instead of HuggingFaceEmbedding for improved embedding model usage.

• Chores

  • Updated .gitignore to exclude .mypy_cache/.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4f21f2b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-llama	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This update integrates Qdrant FastEmbed as the local embedding provider, modifies dependency management, and adapts initialization functions to use FastEmbed. Specifically, dependencies for the "groq" case are updated, ignoring .mypy_cache/ in .gitignore, and altering initialization methods in settings.py to utilize init_fastembed.

Changes

Files	Change Summary
.changeset/happy-emus-attend.md	Introduced Qdrant FastEmbed as the local embedding provider.
.gitignore	Added exclusion for .mypy_cache/ in the Python section.
helpers/python.ts	Updated getAdditionalDependencies to include llama-index-embeddings-fastembed and llama-index-llms-groq.
templates/components/settings/python/settings.py	Modified init_groq and init_anthropic to use init_fastembed for setting Settings.embed_model.

Poem

In the land where code does thrive,
New embeddings come alive,
FastEmbed now takes its place,
In settings, finds its embrace.
Dependencies align in cheer,
Code flows smooth without a fear.
🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3b57bdc and 4f21f2b.

Files selected for processing (4)

• .changeset/happy-emus-attend.md (1 hunks)
• .gitignore (1 hunks)
• helpers/python.ts (1 hunks)
• templates/components/settings/python/settings.py (3 hunks)

Files skipped from review due to trivial changes (1)

• .gitignore

Additional comments not posted (5)

.changeset/happy-emus-attend.md (1)

1-5: Documentation changes are clear and concise.

The documentation accurately describes the use of Qdrant FastEmbed as the local embedding provider.

templates/components/settings/python/settings.py (2)

146-147: Verify the impact of using FastEmbed instead of HuggingFaceEmbedding.

The change in embedding provider might have implications on the downstream tasks. Ensure that FastEmbed is compatible with all use cases previously handled by HuggingFaceEmbedding.

---

130-131: Verify the impact of using FastEmbed instead of HuggingFaceEmbedding.

The change in embedding provider might have implications on the downstream tasks. Ensure that FastEmbed is compatible with all use cases previously handled by HuggingFaceEmbedding.

Verification successful

---

Verification successful: FastEmbed properly integrated

The FastEmbedEmbedding has been correctly integrated in place of HuggingFaceEmbedding throughout the codebase. No breaking changes are observed.

• templates/components/settings/python/settings.py demonstrates proper usage of FastEmbedEmbedding.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the impact of using FastEmbed instead of HuggingFaceEmbedding.

# Test: Search for usage of HuggingFaceEmbedding. Expect: No breaking changes.
rg --type python -A 5 $'HuggingFaceEmbedding'

Length of output: 75

---

Script:

#!/bin/bash
# Description: Verify the impact of using FastEmbed instead of HuggingFaceEmbedding.

# Test: Search for usage of HuggingFaceEmbedding. Expect: No breaking changes.
rg --glob '*.py' -A 5 'HuggingFaceEmbedding'

Length of output: 44

---

Script:

#!/bin/bash
# Description: Verify the integration and usage of FastEmbed.

# Test: Search for usage of FastEmbed. Expect: Proper integration and usage.
rg --glob '*.py' -A 5 'FastEmbed'

Length of output: 1985

helpers/python.ts (2)

156-165: Dependencies for "groq" case look good.

The dependencies llama-index-llms-groq and llama-index-embeddings-fastembed are correctly added.

---

172-173: Dependencies for "anthropic" case look good.

The dependency llama-index-embeddings-fastembed is correctly added.