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

Error when I run main.py #6

Open
AdeolaMercy opened this issue Nov 20, 2024 · 4 comments
Open

Error when I run main.py #6

AdeolaMercy opened this issue Nov 20, 2024 · 4 comments

Comments

@AdeolaMercy
Copy link

I get this error when I run main.py "gql.transport.exceptions.TransportQueryError: Error while fetching schema: {'message': 'maximum query depth exceeded 15 > 13', 'extensions': {'classification': 'ExecutionAborted'}} If you don't need the schema, you can try with: "fetch_schema_from_transport=False" "

I used the sample DEMO_PURPLE_CE.csv file to test but got same error.

I am importing data from an old instance of vectr to 9.4.0 instance. I am also using python3.8 to run the script.

@thebleucheese
Copy link
Collaborator

thebleucheese commented Nov 25, 2024

I get this error when I run main.py "gql.transport.exceptions.TransportQueryError: Error while fetching schema: {'message': 'maximum query depth exceeded 15 > 13', 'extensions': {'classification': 'ExecutionAborted'}} If you don't need the schema, you can try with: "fetch_schema_from_transport=False" "

I used the sample DEMO_PURPLE_CE.csv file to test but got same error.

I am importing data from an old instance of vectr to 9.4.0 instance. I am also using python3.8 to run the script.

In vectr_tools/csv_import_example/vectr_api_client.py you can change fetch_schema_from_transport to False temporarily.

Looks like a VECTR issue so we'll adjust the backend to accommodate this in an upcoming VECTR release so the schema fetch can be turned back on.

@AdeolaMercy
Copy link
Author

I did change fetch_schema_from_transport to False but the error changed to Assertion Error

@thebleucheese
Copy link
Collaborator

I did change fetch_schema_from_transport to False but the error changed to Assertion Error

What are the details of the error? They shouldn't be exactly the same anymore if it's not fetching the schema. The queries run by vectr-tools aren't more than a few levels deep.

@AdeolaMercy
Copy link
Author

If I remember correctly, The error is simply “AssertionError”. After changing schema_transport to false, there is a line of code in vectr_api_client.py that checks if client.schema is not none which ended up failing

Here is the line of code:
“assert client.schema is not None“

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants