Open TanGentleman opened 4 months ago
Also, it seems like the collection name for the DB/manifest is one of the very reasonable things to have friction on for a RAG workflow. Labeling the bucket of sources (plus rag metadata) with something descriptive is pretty vital. I should set reasonable defaults though.
I'm gonna go ahead and call this a bug, just because unintended behavior is likely to be commonplace.
The config_override and CLI flags work correctly assuming the collection_name is correct. However, many times you want to configure new inputs or params and mistakenly leave the same collection name. It adds friction, but I want to ensure that I don't keep accidentally loading collections when I want to make new ones.