[Question]: Does it support parent-child chunking?

[andeyeluguo]

If the question is concise and probably has a short answer, asking it in community Slack

Question

Environment

• OS Version and CPU Arch(uname -a):

• OB Version(LD_LIBRARY_PATH=../lib:$LD_LIBRARY_PATH ./observer -V):

• Hardware resource(cpu core/memory size/disk hardware):

[hnwyllmm]

Theoretically, yes. Parent-child chunking is inherently an application-layer orchestration logic rather than a core feature of the database itself.In a clean architecture with a proper separation of concerns, the vector database should only be responsible for efficient storage, indexing, and retrieval (e.g., performing the vector search on child chunks and returning their metadata).The pipeline itself—including document splitting, managing the hierarchical ID mapping (via parent_id), and performing the secondary lookup to fetch the full parent context—is typically handled by the application framework (like LangChain, LlamaIndex, or custom middleware). Putting this logic in the application layer gives you much better flexibility to tune chunking strategies without coupling your business logic to a specific database engine.