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

Question about content_cluster_name argument in delete_all_docs method #469

Closed
louisoutin opened this issue Feb 16, 2023 · 5 comments
Closed

Comments

@louisoutin
Copy link

Hello,
In the doc reference API, the class classvespa.application.Vespa has a method delete_all_docs with an argument called content_cluster_name. I'm not sure how to know what's my cluster name since when initializing the Application Package or when feeding the data, there is no such argument. I've checked the code and the vespa server doc, but I didn't find answers. Would be nice to have more information/examples about this content_cluster_name argument.
Thanks

@kkraune
Copy link
Member

kkraune commented Feb 16, 2023

off the bat, I think it is the same as the schema name, so you can try that. will update documentation regardless. thanks for reporting!

@louisoutin
Copy link
Author

Will try that, thanks

@kkraune
Copy link
Member

kkraune commented Feb 16, 2023

I was almost right, it seems:

https://github.com/vespa-engine/pyvespa/blob/master/vespa/templates/services.xml#L20

<content id="{{ application_name }}_content" version="1.0">

need to document this ...

@kkraune
Copy link
Member

kkraune commented Feb 16, 2023

https://pyvespa.readthedocs.io/en/latest/deploy-docker.html#Learn-Vespa-by-looking-at-underlying-config-files then look at the generated services.xml - that will have to content cluster id

@louisoutin
Copy link
Author

Great! thanks!

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