Re:Show HN: How we leapfrogged traditional vector based RAG ...
by PhilippGille on Friday July 19, 2024 @02:49AM
(#41002613)
It's still RAG, just the R in RAG is not vector-based anymore, no?
[ Parent
| on HN ]
Re:Show HN: How we leapfrogged traditional vector based RAG ...
by zbyforgotp on Friday July 19, 2024 @03:56AM
(#41003119)
What you describe sounds like Agetic RAG https://zzbbyy.substack.com/p/agentic-rag
Re:Show HN: How we leapfrogged traditional vector based RAG ...
by janalsncm on Friday July 19, 2024 @04:22AM
(#41003434)
> The traditional way to do RAG is to find information relevant to a query - and then incorporate it into the LLM prompt together with the question we want it to answer.
Technically this is incorrect. The original RAG paper used a seq2seq generator (BART) and involved two methods: RAG sequence and RAG token.
RAG sequence used the same fixed documents and appended them to the input query (note, this is different from a decoder-only model). RAG token generates each token based on a different document.
I only nitpick this because if someone is going to invent new fancy-sounding variants of RAG they should at least get the basics right.
Re:Show HN: How we leapfrogged traditional vector based RAG ...
by zbyforgotp on Sunday July 21, 2024 @02:50AM
(#41023037)
Traditional does not equate original. The original technique was never used widely and cannot be called the traditional way.
Re:Show HN: How we leapfrogged traditional vector based RAG ...
by koliber on Friday July 19, 2024 @04:28PM
(#41010797)
You’re right. Many people ppl e take a mental shortcut and assume that RAG is a vector DB search. Any kind of retrieval is retrieval. You can do keyword search. You can do a PageRank like query. You can sort content by date and send the most recent items to the LLM. It’s all retrieval. That is the R on Retrieval Augmented Generation.