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

split docs instead of truncating on tokenizer max_input_tokens #253

Open
K-Schubert opened this issue Jul 2, 2024 · 0 comments
Open

split docs instead of truncating on tokenizer max_input_tokens #253

K-Schubert opened this issue Jul 2, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@K-Schubert
Copy link
Collaborator

Description

Currently, a call to an embedding model will truncate the input text to embed according to the embedding model max_input_tokens if the number of tokens of the input text exceeds this limit.

It would be better to split the text and embed each chunk separately (and keep track of chunk IDs and relationship to one another) to avoid losing data.

@K-Schubert K-Schubert added this to the MVP2 milestone Jul 2, 2024
@K-Schubert K-Schubert self-assigned this Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant