Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading from 1.0.3 to 2.0.0 fails #273

Open
2 of 6 tasks
craigpfeifer opened this issue Sep 7, 2024 · 2 comments
Open
2 of 6 tasks

Upgrading from 1.0.3 to 2.0.0 fails #273

craigpfeifer opened this issue Sep 7, 2024 · 2 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@craigpfeifer
Copy link

Description

I upgraded my verba 1.0.3 install to 2.0.0 and I cannot create a local verba instance. When I click on 'Local' I get the error:

Failed to connect to Weaviate Collection may not have been created properly.! Unexpected status code: 422, with response body: {'error': [{'message': 'class already exists: found similar class "VERBA_Config"'}]}.

How can I wipe my existing install or migrate it to 2.0.0?

Installation

  • pip install goldenverba
  • pip install from source
  • Docker installation

If you installed via pip, please specify the version: 24.2

Weaviate Deployment

  • Local Deployment
  • Docker Deployment
  • Cloud Deployment

Configuration

Reader: N/A
Chunker: N/A
Embedder: N/A
Retriever: N/A
Generator: N/A

Steps to Reproduce

  1. Install verba 1.0.3
  2. import documents , issue queries, etc.
  3. pip install verba 2.0.0
  4. restart verba
  5. access https://loaclhost:8000
  6. click on 'local'

Additional context

@craigpfeifer
Copy link
Author

One solution for embedded weaviate (nuclear option):

  1. go to local storage directory (default is here)
  2. delete all files
  3. restart verba verba restart
  4. reload https://localhost:8000
  5. click on local
  6. happy verba-ing!

@thomashacker
Copy link
Collaborator

Good catch! Same happend to me, will add some CLI commands to fix this in the future + documentation.
Thanks a lot for the issue 🚀

@thomashacker thomashacker added bug Something isn't working documentation Improvements or additions to documentation labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants