- .NET Clients: other versions:
- Introduction
- Breaking changes
- API Conventions
- Elasticsearch.Net - Low level client
- NEST - High level client
- Troubleshooting
- Search
- Query DSL
- Full text queries
- Term level queries
- Exists Query Usage
- Fuzzy Date Query Usage
- Fuzzy Numeric Query Usage
- Fuzzy Query Usage
- Ids Query Usage
- Prefix Query Usage
- Date Range Query Usage
- Long Range Query Usage
- Numeric Range Query Usage
- Term Range Query Usage
- Regexp Query Usage
- Term Query Usage
- Terms List Query Usage
- Terms Lookup Query Usage
- Terms Query Usage
- Terms Set Query Usage
- Type Query Usage
- Wildcard Query Usage
- Compound queries
- Joining queries
- Geo queries
- Geo Bounding Box Query Usage
- Geo Distance Query Usage
- Geo Polygon Query Usage
- Geo Shape Circle Query Usage
- Geo Shape Envelope Query Usage
- Geo Shape Geometry Collection Query Usage
- Geo Shape Indexed Shape Query Usage
- Geo Shape Line String Query Usage
- Geo Shape Multi Line String Query Usage
- Geo Shape Multi Point Query Usage
- Geo Shape Multi Polygon Query Usage
- Geo Shape Point Query Usage
- Geo Shape Polygon Query Usage
- Specialized queries
- Span queries
- NEST specific queries
- Aggregations
- Metric Aggregations
- Average Aggregation Usage
- Cardinality Aggregation Usage
- Extended Stats Aggregation Usage
- Geo Bounds Aggregation Usage
- Geo Centroid Aggregation Usage
- Max Aggregation Usage
- Median Absolute Deviation Aggregation Usage
- Min Aggregation Usage
- Percentile Ranks Aggregation Usage
- Percentiles Aggregation Usage
- Scripted Metric Aggregation Usage
- Stats Aggregation Usage
- Sum Aggregation Usage
- Top Hits Aggregation Usage
- Value Count Aggregation Usage
- Weighted Average Aggregation Usage
- Bucket Aggregations
- Adjacency Matrix Usage
- Auto Date Histogram Aggregation Usage
- Children Aggregation Usage
- Composite Aggregation Usage
- Date Histogram Aggregation Usage
- Date Range Aggregation Usage
- Filter Aggregation Usage
- Filters Aggregation Usage
- Geo Distance Aggregation Usage
- Geo Hash Grid Aggregation Usage
- Global Aggregation Usage
- Histogram Aggregation Usage
- Ip Range Aggregation Usage
- Missing Aggregation Usage
- Nested Aggregation Usage
- Parent Aggregation Usage
- Range Aggregation Usage
- Reverse Nested Aggregation Usage
- Sampler Aggregation Usage
- Significant Terms Aggregation Usage
- Significant Text Aggregation Usage
- Terms Aggregation Usage
- Pipeline Aggregations
- Average Bucket Aggregation Usage
- Bucket Script Aggregation Usage
- Bucket Selector Aggregation Usage
- Bucket Sort Aggregation Usage
- Cumulative Sum Aggregation Usage
- Derivative Aggregation Usage
- Extended Stats Bucket Aggregation Usage
- Max Bucket Aggregation Usage
- Min Bucket Aggregation Usage
- Moving Average Ewma Aggregation Usage
- Moving Average Holt Linear Aggregation Usage
- Moving Average Holt Winters Aggregation Usage
- Moving Average Linear Aggregation Usage
- Moving Average Simple Aggregation Usage
- Moving Function Aggregation Usage
- Percentiles Bucket Aggregation Usage
- Serial Differencing Aggregation Usage
- Stats Bucket Aggregation Usage
- Sum Bucket Aggregation Usage
- Matrix Aggregations
- Metric Aggregations
NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.
Type and Relation names inference
editType and Relation names inference
editType names are resolved in NEST by default, by lowercasing the CLR type name
var settings = new ConnectionSettings(); var resolver = new TypeNameResolver(settings); var type = resolver.Resolve<Project>(); type.Should().Be("project");
Applying a type name with ElasticsearchTypeAttribute
editA type name can be applied for a CLR type, using the Name property on ElasticsearchTypeAttribute
[ElasticsearchType(Name = "attributed_project")] public class AttributedProject { } var settings = new ConnectionSettings(); var resolver = new TypeNameResolver(settings); var type = resolver.Resolve<AttributedProject>(); type.Should().Be("attributed_project");
Applying a type name with DataContractAttribute
editSimilarly to ElasticsearchTypeAttribute
, a type name can be applied for a
CLR type, using the Name property on System.Runtime.Serialization.DataContractAttribute
[DataContract(Name = "data_contract_project")] public class DataContractProject { } var settings = new ConnectionSettings(); var resolver = new TypeNameResolver(settings); var type = resolver.Resolve<DataContractProject>(); type.Should().Be("data_contract_project");
Default type name
editWith Elasticsearch 6.x, you can only have a single type per index and in the long run types will be
phased out entirely.
The need to tag types is no longer necessary, so in many cases it makes sense to use a single fixed type,
like doc
var settings = new ConnectionSettings().DefaultTypeName("doc"); var resolver = new TypeNameResolver(settings); var type = resolver.Resolve<Project>(); type.Should().Be("doc");
With such a setting in place, all CLR types will resolve to doc
as the type name to use in Elasticsearch.
Override type name inferrer
editYou can provide a delegate to override the default type name inferrer for types
var settings = new ConnectionSettings() .DefaultTypeNameInferrer(t=>t.Name.ToLower() + "-suffix"); var resolver = new TypeNameResolver(settings); var type = resolver.Resolve<Project>(); type.Should().Be("project-suffix");
Relation names
editPrior to Elasticsearch 6.x you could have multiple types per index. They acted as a discrimatory column but were often confused with tables. The fact that the mapping API’s treated them as seperate entities did not help.
The general guideline has always been to use a single type per index. Starting from 6.x this is also enforced. Some features still need to store multiple types in a single index such as Parent/Child join relations.
Both Parent
and Child
will need to have resolve to the same typename to be indexed into the same index.
Therefore in 6.x we need a different type that translates a CLR type to a join relation. This can be configured seperately
using .RelationName()
var settings = new ConnectionSettings() .DefaultMappingFor<CommitActivity>(m => m .IndexName("projects-and-commits") .TypeName("doc") .RelationName("commits") ) .DefaultMappingFor<Project>(m => m .IndexName("projects-and-commits") .TypeName("doc") .RelationName("projects") ); var resolver = new RelationNameResolver(settings); var relation = resolver.Resolve<Project>(); relation.Should().Be("projects"); relation = resolver.Resolve<CommitActivity>(); relation.Should().Be("commits");
RelationName
uses the DefaultTypeNameInferrer
to translate CLR types to a string representation.
Explicit TypeName
configuration does not affect how the default relation for the CLR type
is represented though
var settings = new ConnectionSettings() .DefaultMappingFor<Project>(m => m .IndexName("projects-and-commits") .TypeName("doc") ); var resolver = new RelationNameResolver(settings); var relation = resolver.Resolve<Project>(); relation.Should().Be("project");
On this page