New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

WARNING: Version 5.x has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Conventions Type name inference »
Elastic Docs ›Elasticsearch.Net and NEST: the .NET clients [5.x] ›NEST - High level client ›Conventions

Index name inference

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Index name inference

edit

Many endpoints within the Elasticsearch API expect to receive one or more index names as part of the request, in order to know what index/indices a request should operate on.

NEST has a number of ways in which the index name(s) can be specified

Default Index name on Connection Settings

edit

A default index name can be specified on ConnectionSettings using .DefaultIndex(). This is the default index name to use when no other index name can be resolved for a request

var settings = new ConnectionSettings()
    .DefaultIndex("defaultindex");
var resolver = new IndexNameResolver(settings);
var index = resolver.Resolve<Project>();
index.Should().Be("defaultindex");

Mapping an Index name for a .NET type

edit

A index name can be mapped for CLR types using .MapDefaultTypeIndices() on ConnectionSettings.

var settings = new ConnectionSettings()
    .MapDefaultTypeIndices(m => m
        .Add(typeof(Project), "projects")
    );
var resolver = new IndexNameResolver(settings);
var index = resolver.Resolve<Project>();
index.Should().Be("projects");

.InferMappingFor<T>() can also be used to specify the index name, as well as be used to specify the type name and POCO property that should be used as the id for the document

var settings = new ConnectionSettings()
    .InferMappingFor<Project>(m => m
        .IndexName("projects")
    );
var resolver = new IndexNameResolver(settings);
var index = resolver.Resolve<Project>();
index.Should().Be("projects");

An index name for a POCO provided using .MapDefaultTypeIndices() or .InferMappingFor<T>() will take precedence over the default index name set on ConnectionSettings. This way, the client can be configured with a default index to use if no index is specified, and a specific index to use for different POCO types.

var settings = new ConnectionSettings()
    .DefaultIndex("defaultindex")
    .MapDefaultTypeIndices(m => m
        .Add(typeof(Project), "projects")
    );
var resolver = new IndexNameResolver(settings);
var index = resolver.Resolve<Project>();
index.Should().Be("projects");

Explicitly specifying Index name on the request

edit

For API calls that expect an index name, the index name can be explicitly provided on the request

var client = TestClient.Default;
var response = client.Search<Project>(s => s.Index("some-other-index")); 
var requestUri = response.ApiCall.Uri;

requestUri.Should().NotBeNull();
requestUri.LocalPath.Should().StartWith("/some-other-index/");

Provide the index name on the request

When an index name is provided on a request, it will take precedence over the default index name and any index name specified for the POCO type using .MapDefaultTypeIndices() or .InferMappingFor<T>()

var client = new ElasticClient(new AlwaysInMemoryConnectionSettings()
    .DefaultIndex("defaultindex")
    .InferMappingFor<Project>(m => m
        .IndexName("projects")
    ));

var response = client.Search<Project>(s => s.Index("some-other-index")); 

response.ApiCall.Uri.Should().NotBeNull();
response.ApiCall.Uri.LocalPath.Should().StartWith("/some-other-index/");

Provide the index name on the request

In summary, the order of precedence for determining the index name for a request is

  1. Index name specified on the request
  2. Index name specified for the generic type parameter in the request using .MapDefaultTypeIndices() or .InferMappingFor<T>()
  3. Default index name specified on ConnectionSettings
« Conventions Type name inference »