Failed to serialize the response body for content type 'application/json' for ISearchResponse<T>

[rentianhua]

I have founded a MVC5 webapi project, and set a http api to get request from ES using NEST then return response. like below

Event though, i attempt to return response.Highlights , it is still failed to serialize.

Do you have any way to handle the serialize problem?

[rentianhua]

[RoutePrefix("api/webapi")]
    public class WebAPIController : ApiController
    {
        [HttpPost]
        [Route("PatentSearch")]
        public object PatentSearch(IPCriteria criteria)
        {
            IEsService service = new EsService();
            var response = service.SearchIPEntities(criteria);

            return response;
        }
    }

[mcboman]

Had a serialization problem my self. One where a value could be either a string[] or a string. The way I resolved it was by create 2 props. One as a string and another as a string[]. You could try to set the exception field as type of Object instead of the current type.

[russcam]

@rentianhua, do you have

1. The POCO structure that you are using and the query (in NEST) that you are doing
2. a sample json response from Elasticsearch for the query

Without these things, it's difficult to investigate. If you could provide these things, I may be able to help further.

[russcam]

@rentianhua Is this the same issue as #2168? Returning documents with highlights where documents may have the same id?

[rentianhua]

i think they may same. Now i use low_type api to workaround.

[russcam]

@rentianhua Thanks for reporting back. Because .Highlights is just a helpful extension (although not helpful in this case 😄 ) for getting all highlights from all hits, you can do enumerate over to get all the highlights without needing to use the low level API. Something like

var response = client.Search<Page>(s => s.MatchAll());

foreach (var hit in response.HitsMetaData.Hits)
{
    var highlights = hit.Highlights;
    // do something with highlights
}

I'm going to close this issue as it's related to #2168; feel free to reopen if that's not the case

[rentianhua]

Thanks. i will try later 😄