Closed akohlbecker closed 5 months ago
I'm not sure what behavior you are expecting here. I had a quick look at your docker comose and could not find a database initialization step anywhere. Just based on the log snippet, it's also not quite clear if you interacted with cineast in any way that would cause it to query an uninitialized database. Could you elaborate on what you were trying to do?
In the wiki (https://github.com/vitrivr/cineast/wiki/Environment-Setup & https://github.com/vitrivr/cottontaildb/wiki ) I did not find anything on initializing a db, therefore I was assuming that cineast has a default configuration that allow it to connect cottontaildb in order to initialize a DB in case it is missing.
Well, the features based on which retrieval is performed need to come from somewhere. Generally, cineast extracts them and stores them in cottontaildb. Since the features to be used are configurable, the relevant database initialization happens only when the features are used for extraction. See https://github.com/vitrivr/cineast/wiki/Extracting-Features#extracting-directly-to-cottontail-db.
Thanks a lot! That answers two of the questions I scratch my head about.
Ok great. If you have any further questions, please don't hesitate to reach out through the Discussions tab.
This seems to be a regression of #255.
To reproduce clone https://github.com/akohlbecker/vitrivr-docker-compose
and start the vitrivr stack with docker compose:
conttontaildb startup fails with: