Skip to content

Conversation

@lyrixx
Copy link
Member

@lyrixx lyrixx commented Dec 15, 2025

Q A
Bug fix? no
New feature? yes
Docs? yes
Issues Fix #997, fix #875
License MIT

@chr-hertel
Copy link
Member

Thanks for kicking off the next round - we're now here, right?

image

we're stacking quite some integration concepts onto each other from architecture point of view - it's not easy to grasp the difference from Ingester and Indexer - especially for me that term is connected to ETL/ELT, but load and transform are part of Indexer. but that's me maybe.

and we're keeping flaws like that sources state in the Ingester now.


compared to
image

I missed to catch up on your arguments in #997, but will create a sketch PR tho.

@lyrixx
Copy link
Member Author

lyrixx commented Dec 16, 2025

wahoo, the diagrams are cool 👏🏼

t's not easy to grasp the difference from Ingester and Indexer - especially for me that term is connected to ETL/ELT, but load and transform are part of Indexer. but that's me maybe.

I don't know, for me it's clear. But I'm biased since I partially built it 😁
I could rename Ingester to Etl to make it clearer

Anyway, we must have something to index (fileter, transform, vectorize, store) documents. I don't need the loader thing, since data are coming in real time from RabbitMQ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature New feature Status: Needs Review Store Issues & PRs about the AI Store component

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Store] Indexer is nice, but hard to use directly

3 participants