New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.

« Query String Usage Term level queries »
Elastic Docs ›Elasticsearch.Net and NEST: the .NET clients [6.x] ›Query DSL ›Full text queries

Simple Query String Usage

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

Simple Query String Usage

edit

Fluent DSL example

edit
q
.SimpleQueryString(c => c
    .Name("named_query")
    .Boost(1.1)
    .Fields(f => f.Field(p => p.Description).Field("myOtherField"))
    .Query("hello world")
    .Analyzer("standard")
    .DefaultOperator(Operator.Or)
    .Flags(SimpleQueryStringFlags.And | SimpleQueryStringFlags.Near)
    .Lenient()
    .AnalyzeWildcard()
    .MinimumShouldMatch("30%")
)

Object Initializer syntax example

edit
new SimpleQueryStringQuery
{
    Name = "named_query",
    Boost = 1.1,
    Fields = Field<Project>(p => p.Description).And("myOtherField"),
    Query = "hello world",
    Analyzer = "standard",
    DefaultOperator = Operator.Or,
    Flags = SimpleQueryStringFlags.And | SimpleQueryStringFlags.Near,
    Lenient = true,
    AnalyzeWildcard = true,
    MinimumShouldMatch = "30%"
}

Example json output.

{
  "simple_query_string": {
    "_name": "named_query",
    "boost": 1.1,
    "fields": [
      "description",
      "myOtherField"
    ],
    "query": "hello world",
    "analyzer": "standard",
    "default_operator": "or",
    "flags": "AND|NEAR",
    "lenient": true,
    "analyze_wildcard": true,
    "minimum_should_match": "30%"
  }
}
« Query String Usage Term level queries »
Was this helpful?
Feedback