Kristian Aune
Kristian Aune
From one of our users: A suggestion to improve the docs would be to have a glossary for all the terms used in Vespa. I find myself using the [Kubernetes...
... to make it easier to read Vespa documentation on an e-reader / offline Vespa documentation is generated using Jekyll from .md and .html files, look into options for generating...
When deploying to Vespa Cloud, it automatically checks that nodes / services are up and have correct config, like: ```` [INFO] [06:21:23] Deployment successful. [INFO] [06:21:23] Session 2715 for tenant...
When feeding a document that does not match the selection in https://docs.vespa.ai/documentation/reference/services-content.html#document, it is silently dropped. It is correct that the document is not stored - but the fact that...
One can browse schemas using http://localhost:19071/application/v2/tenant/default/session/2/content/schemas/ (replace 2 with current session) or support reading (a) file(s). Add pretty-print and syntax highlighting. Maybe write a .sd-to-json converter, so easy to build...
Creating a grouing query string (e.g. all( group(customer) each(output(sum(price))) ) ) can be difficult with multi-level grouping, having a UI to construct the string a la the querybuilder might help....
some kind of helper tool that translates from an Elasticsearch / Solr / Lucene query to YQL / query API, possibly combined with supporting documentation in https://vespa.ai/migrating-from-elastic-search-to-vespa - this will...
The querybuilder linked from https://docs.vespa.ai/en/vespa-quick-start.html is a bit basic. Build better support for making valid YQL query strings by using a dynamic form. Split the YQL string in logically separate...
Find services.xml at http://localhost:19071/application/v2/tenant/default/session/2/content/ - from there, build a UI to navigate to the content clusters, where one can view schemas, metrics, and data In a UI, the user can...
Find content clusters and schemas using http://localhost:19071/application/v2/tenant/default/session/2/content/services.xml . Use the schema to auto-generate a form with correct types so valid JSON is generated to PUT/UPDATE/DELETE documents. Support GET to read...