巢式查询会传回奇怪的结果。 elasticsearch

Question

This is my client code:

settings

var defaultSettings = new ConnectionSettings(
    uri: new System.Uri("http://localhost:9200")
);

defaultSettings.SetJsonSerializerSettingsModifier(s => {
    s.ReferenceLoopHandling = ReferenceLoopHandling.Ignore;
});

defaultSettings.SetConnectionStatusHandler(c => {
    if(!c.Success) throw new Exception(c.ToString());
});

defaultSettings.SetDefaultIndex("projects");

executing code

public ActionResult Search(String searchTerm) {
    var result = this.searchClient.Search<ProjectIndexModel>(
        descriptor: new SearchDescriptor<ProjectIndexModel>().Index("projects").AllTypes().Query(
            query: q => q.QueryString(qs => qs.Query(searchTerm)
        )
    ));

    // or
    /* 
    var results = this.searchClient.Search<ProjectIndexModel>(s =>
        s.Index("projects").Type("project").Query(q => 
            q.Term(f => f.ProblemDefinition, searchTerm) || 
            q.Term(f => f.Name, searchTerm) ||
            q.Term(f => f.SuggestedSolution, searchTerm) ||
            q.Term(f => f.Initiator, searchTerm)
        )
    );        
    */

    return Json(result.Documents.ToList());
}

Indexing is launched at application start:

foreach(var project in this.dbContext.Projects) {
    var indexModel = Mapper.Map<ProjectIndexModel>(project);
    searchClient.Index(indexModel, "projects", "project", indexModel.Id.ToString());
}

Indexes are present in database (that's not quite the same as I have now, but the schema stayed the same).

what have I tried :

Controller action returns (default) 10 hits of 11 documents. It's like searching is ignored entirely, without visible errors.

Fiddler gave positive result (1 hit) both for {host:9200}/_search and {host:9200}/projects/project/_search POST requests with query:

{
    "query": {
        "query_string": {
            "query": "original"
        }
    }
}

What's the problem?

Answer 1

Problem was not in NEST . After exploring the results.ConnectionStatus.ToString() , which showed a hit as Fiddler did, I found that problem was in my client code. I overlooked that I was sending POST without {searchTerm: $scope.searchTerm} specified:

$http({
    url: '/projects/search',
    method: "POST",
    data: { searchTerm: $scope.searchTerm }
})
.success(function(data, status, headers, config) {
    $scope.projects = data.documents;
}).error(function(data, status, headers, config) {
    console.log('error: ' + data);
});