[dead]
From zero to a RAG system: successes and failures
31–40 of 129 posts
Re: From zero to a RAG system: successes and failures
#32Cool work! Would be so interested in what would happen if you would put the data and you plan / features you wanted in a Claude Code instance and let it go. You did carefully thinking, but those models now also go really far and deep. Would be really interested in seeing what it comes up with. For that kind of data getting something like a Mac mini or whatever (no not with OpenClaw) would be damn interesting to see h…
But where is the fun with that?
Re: From zero to a RAG system: successes and failures
#33Odd to me that Elasticsearch isn't finding a second breath in these new ecosystems. It basically is that now, a RAG engine with model integration.
The people that survived it aren't willing to give it anymore of their breathing left
haha! it's been ok for me, but a lot of song and dance is required. the saas-version is a black box (in a bad way).
Re: From zero to a RAG system: successes and failures
#34Odd to me that Elasticsearch isn't finding a second breath in these new ecosystems. It basically is that now, a RAG engine with model integration.
It’s definitely a use case for this and would’ve saved a lot of pain IMO but also seems like it would have added confusing technology to what was a VERY Python-heavy stack that would’ve benefitted from other elements. Hardest part is always figuring out your company’s knowledge management has been dogsh!t for years so now you need to either throw most of it away or stick to the authoritative stuff somehow. Elastic pl…
ah got it! thanks for the color
Re: From zero to a RAG system: successes and failures
#35[deleted]
Re: From zero to a RAG system: successes and failures
#36[deleted]
Re: From zero to a RAG system: successes and failures
#37What would it look like to regularly react to source data changes? Seems like a big missing piece. Event based? regular cadence? Curious what people choose. Great post though.
Re: From zero to a RAG system: successes and failures
#38Thanks for an interesting read! Are you monitoring usage, and what kind of user feedback have you received? Always curious if these projects end up used because, even with the perfect tech, if the data is low quality, nobody is going to bother
Re: From zero to a RAG system: successes and failures
#39Great write-up. Thank you! I’m contemplating a similar RAG architecture for my engineering firm, but we’re dealing with roughly 20x the data volume (estimating around 9TB of project files, specs, and PDFs). I've been reading about Google's new STATIC framework (sparse matrix constrained decoding) and am really curious about the shift toward generative retrieval for massive speedups well beyond this approach. For thos…
There’s turbopuffer
Re: From zero to a RAG system: successes and failures
#40What would it look like to regularly react to source data changes? Seems like a big missing piece. Event based? regular cadence? Curious what people choose. Great post though.
Depends on the use case, ie frequency and impact of changes.
Typically you would have a reindex process, and you keep track of hashes of chunks to check if you’ve already calculated this exact block before to avoid extra costs. And then run such a reindex process pretty frequently as it’s cheap / costs nothing when there are no changes.