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

[Fix bug] Better for local embedding models #568

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lyyf2002
Copy link

Description

This pull request adds functionality to decode chunks back to strings, enabling the use of local embedding models that only accept string inputs.

Related Issues

#451
#528

Proposed Changes

  • Decodes the encoded chunks back to strings.
  • Integrates the local embedding models with the decoded strings.

Checklist

  • I have tested these changes locally.
  • I have reviewed the code changes.
  • I have updated the documentation (if necessary).
  • I have added appropriate unit tests (if applicable).

Additional Notes

These changes ensure compatibility with local embedding models that require string inputs, enhancing the overall functionality and flexibility of the system.

When using some local embedding models, they can only use str as input instead of encoded ones. So I decode the chunks back to strs, and now we can use local embedding models.
@lyyf2002 lyyf2002 requested a review from a team as a code owner July 15, 2024 12:27
@davidliudev
Copy link

This wonderfully resolves the weight summed to zero issues. Thanks for the PR. Hope the MS team could merge this soon.

@cedarwud
Copy link

cedarwud commented Aug 1, 2024

This pr is perfectly resolve error in local query,thank you very much.
Hope this pr can be merge soon.

@bytewei
Copy link

bytewei commented Aug 7, 2024

This wonderfully resolves the weight summed to zero issues. Thanks for the PR. Hope the MS team could merge this soon.

@AlonsoGuevara
Copy link
Contributor

AlonsoGuevara commented Aug 22, 2024

Hi @lyyf2002

Thanks for your contribution!
On 0.2.2 we merged a change that should have fixed this.
Could you please try with the latest version (0.3.1)?

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.

5 participants