Weaviate-Embedded

Anyone have any weaviate.conf.json examples that they could share? Redact any sensitive information.

Hi @Oppie !

There is not a lot I could help you with only that info :(.

Please, let me know what issues are you facing or what you are trying to accomplish so I can help you.

Thanks!

On this page: How to run an embedded vector database in 10 lines of code | Weaviate - vector database

I get an error when I do the pytest embedded_test.py I am thinking pytest is broken or something.

[oppie@dell python]$ pytest embedded_test.py
Traceback (most recent call last):
File “/usr/bin/pytest”, line 8, in
sys.exit(console_main())
^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 190, in console_main
code = main()
^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 148, in main
config = _prepareconfig(args, plugins)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 329, in _prepareconfig
config = pluginmanager.hook.pytest_cmdline_parse(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/pluggy/_hooks.py”, line 265, in call
return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/pluggy/_manager.py”, line 80, in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/pluggy/_callers.py”, line 55, in _multicall
gen.send(outcome)
File “/usr/lib/python3.11/site-packages/_pytest/helpconfig.py”, line 103, in pytest_cmdline_parse
config: Config = outcome.get_result()
^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/pluggy/_result.py”, line 60, in get_result
raise ex[1].with_traceback(ex[2])
File “/usr/lib/python3.11/site-packages/pluggy/_callers.py”, line 39, in _multicall
res = hook_impl.function(*args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 1060, in pytest_cmdline_parse
self.parse(args)
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 1348, in parse
self._preparse(args, addopts=addopts)
File “/usr/lib/python3.11/site-packages/_pytest/config/init.py”, line 1234, in _preparse
self.known_args_namespace = self._parser.parse_known_args(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/argparsing.py”, line 157, in parse_known_args
return self.parse_known_and_unknown_args(args, namespace=namespace)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/argparsing.py”, line 171, in parse_known_and_unknown_args
optparser = self._getparser()
^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/_pytest/config/argparsing.py”, line 130, in _getparser
arggroup.add_argument(*n, **a)
File “/usr/lib64/python3.11/argparse.py”, line 1468, in add_argument
return self._add_action(action)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib64/python3.11/argparse.py”, line 1670, in _add_action
action = super(_ArgumentGroup, self)._add_action(action)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib64/python3.11/argparse.py”, line 1482, in _add_action
self._check_conflict(action)
File “/usr/lib64/python3.11/argparse.py”, line 1619, in _check_conflict
conflict_handler(action, confl_optionals)
File “/usr/lib64/python3.11/argparse.py”, line 1628, in _handle_conflict_error
raise ArgumentError(action, message % conflict_string)
argparse.ArgumentError: argument --no-cov: conflicting option string: --no-cov
[oppie@dell python]$

Yes. The stack trace doesn’t seem to touch weaviate code at any point.

If you are planning on running tests, a way of doing it is running Weaviate using docker and then do tests.

Weaviate Embedded is still experimental, so I wouldn’t use it for production, just for experiments.