Vespa CLI 8.586.25

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa CLI 8.583.10

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa CLI 8.579.17

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa CLI 8.578.22

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa Language Server 2.4.7

The Language-server for Vespa schemas

Use the jar file to integrate the language server into your favorite editor.

For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.

Schema Language Server in Neovim

Requirements

Requires Java 17 or newer.

Optional: lspconfig plugin for nvim.

Installation

Download schema-language-server-jar-with-dependencies.jar.

Using lspconfig

The language server is registered at lspconfig as vespa_ls. If you have lspconfig installed, all that needs to
be done is to enable the language server.

Register .sd, .profile and .yql as filetypes (in init.lua):

vim.filetype.add {
  extension = {
    profile = 'sd',
    sd = 'sd',
    yql = 'yql'
  }
}

Create a config for schema language server (in init.lua):

vim.lsp.config('vespa_ls', {
    cmd = { 'java', '-jar', '/path/to/vespa-language-server_X.X.X.jar' },
    -- on_attach = ...
})

vim.lsp.enable('vespa_ls')

Manual Installation

If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.

What's New

• Support for multiple inheritance of match-features.
• Fixed formatting bugs.

Vespa Language Server 2.4.6

The Language-server for Vespa schemas

Use the jar file to integrate the language server into your favorite editor.

For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.

Schema Language Server in Neovim

Requirements

Requires Java 17 or newer.

Optional: lspconfig plugin for nvim.

Installation

Download schema-language-server-jar-with-dependencies.jar.

Using lspconfig

The language server is registered at lspconfig as vespa_ls. If you have lspconfig installed, all that needs to
be done is to enable the language server.

Register .sd, .profile and .yql as filetypes (in init.lua):

vim.filetype.add {
  extension = {
    profile = 'sd',
    sd = 'sd',
    yql = 'yql'
  }
}

Create a config for schema language server (in init.lua):

vim.lsp.config('vespa_ls', {
    cmd = { 'java', '-jar', '/path/to/vespa-language-server_X.X.X.jar' },
    -- on_attach = ...
})

vim.lsp.enable('vespa_ls')

Manual Installation

If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.

What's New

• Add some missing rank feature properties.
• Fixed minor bugs.

Vespa CLI 8.562.17

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa Language Server 2.4.4

The Language-server for Vespa schemas

Use the jar file to integrate the language server into your favorite editor.

For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.

Schema Language Server in Neovim

Requirements

Requires Java 17 or newer.

Optional: lspconfig plugin for nvim.

Installation

Download schema-language-server-jar-with-dependencies.jar.

Using lspconfig

The language server is registered at lspconfig as vespa_ls. If you have lspconfig installed, all that needs to
be done is to enable the language server.

Register .sd, .profile and .yql as filetypes (in init.lua):

vim.filetype.add {
  extension = {
    profile = 'sd',
    sd = 'sd',
    yql = 'yql'
  }
}

Create a config for schema language server (in init.lua):

vim.lsp.config('vespa_ls', {
    cmd = { 'java', '-jar', '/path/to/vespa-language-server_X.X.X.jar' },
    -- on_attach = ...
})

vim.lsp.enable('vespa_ls')

Manual Installation

If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.

What's New

• Add some missing rank feature properties.
• Fixed minor bugs.

Vespa CLI 8.556.6

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.

Vespa CLI 8.553.3

The command-line tool for Vespa.ai.

Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.

See Vespa documentation and getting started with Vespa
CLI.

Run make to build and test - make sure to use go 1.18 or higher.