This website uses cookies to ensure you get the best experience.
Learn more.
A retrieval pipeline embeds 3,000-token passages with an encoder whose input limit is 512 tokens. Important details near passage ends are missing from search. What is the best first fix?
Published
- Split passages into meaningful units that fit the encoder limit and re-embed them.
- Lower the retrieval timeout to discard more candidates.
- Rename the stored vector column.
- Increase only the answer generator's output length.
Comments — 0
Sign in to comment