Count gives "Could not parse server exception"

[tonywiredin]

Hi

Using NEST 1.0 and Elastisearch 1.3.2, using count is not working.

The request URL is correct (e.g. http://localhost:9200/_count) but no matter what I try and count, the outcome is always the same:
Elasticsearch.Net.IResponseWithRequestInformation.RequestInformation {StatusCode: 400,
Method: POST,
Url: http://localhost:9200/_count,
Request: {},
Response:
ExceptionMessage: Could not parse server exception
StackTrace: } Elasticsearch.Net.IElasticsearchResponse {Elasticsearch.Net.ElasticsearchResponse<Nest.CountResponse>}

I'm extremely new to elasticsearch and NEST (as in, today's my first day) so I'm sure I'm making a newbie mistake

Thanks

[Mpdreamz]

Hi @tonywiredin mind pasting the code that results in this error?

[tonywiredin]

I think I found the problem.

I downloaded the NEST source code, and debugged the call to Count, and I discovered that in elasticsearch-net-develop\src\Nest\DSL\CountDescriptor.cs the HttpMethod is ALWAYS set to POST (

internal static class CountPathInfo
{
public static void Update(ElasticsearchPathInfo pathInfo, ICountRequest request)
{
var source = request.RequestParameters.GetQueryStringValue("source");
pathInfo.HttpMethod = !source.IsNullOrEmpty()
? PathInfoHttpMethod.GET
: PathInfoHttpMethod.POST;

        pathInfo.HttpMethod = PathInfoHttpMethod.POST;
    }
}

Changing that last line to .GET fixes my problem and I get the correct count

My code to do the count is as simple as it gets:

        var node = new Uri("http://localhost:9200");

        var settings = new ConnectionSettings(
            node,
            defaultIndex: "superfirec"
        );
        var client = new ElasticClient(settings);
        var recordCount = client.Count();

[gmarz]

@tonywiredin really good find, thank you! I just pushed the above fix. In addition to that last line being totally wrong, we were also checking the source param (request body), and doing a GET if it was present, otherwise a POST. It should be the other way around.

[tonywiredin]

Thanks for the incredibly fast turnaround :-)