---
title: "Comment by Kartik N V J K on \"Beyond a PoC #1: Your RAG demo works. But is it production-ready ?\" | Hashnode"
description: "Hashing content plus tenant metadata into the doc ID handles retries well. A revised policy PDF hashes to a new ID, though, so as far as I can tell the old vers"
url: "https://hashnode.com/posts/beyond-a-poc-1-your-rag-demo-works-but-is-it-production-ready/6ae601272d3af9cb1bd7a4b7/comment/6ae893ae8831ba3a85b1ba9c"
---

[Discussion](https://hashnode.com/posts/beyond-a-poc-1-your-rag-demo-works-but-is-it-production-ready/6ae601272d3af9cb1bd7a4b7)

Comment [Beyond a PoC #1: Your RAG demo works. But is it production-ready ?](https://hashnode.com/posts/beyond-a-poc-1-your-rag-demo-works-but-is-it-production-ready/6ae601272d3af9cb1bd7a4b7)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Nov 2](https://hashnode.com/posts/beyond-a-poc-1-your-rag-demo-works-but-is-it-production-ready/6ae601272d3af9cb1bd7a4b7/comment/6ae893ae8831ba3a85b1ba9c)

Hashing content plus tenant metadata into the doc ID handles retries well. A revised policy PDF hashes to a new ID, though, so as far as I can tell the old version's chunks stay indexed next to the new ones. I didn't see a superseded state in the lifecycle. Is retiring old versions part of the ingestion episode?

[Mete Mertkan](https://hashnode.com/@metemertkan)

[Nov 2](https://hashnode.com/posts/beyond-a-poc-1-your-rag-demo-works-but-is-it-production-ready/6ae601272d3af9cb1bd7a4b7/comment/6ae893ae8831ba3a85b1ba9c#reply-6ae897598831ba3a85b1d728)

Exactly, i see ingestion as a strategy for retrieving it later. Let's discuss that when I publish the next episode. Thanks for your input, appreciate it