Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FEATURE] Add "suggest" to SearchResponse
See original GitHub issueIt looks like the SearchResponse is missing serialization for a suggestion response yet, e.g. https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters.html#querying
Issue Analytics
- State:
- Created 6 months ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Extract the Source data from Elastic Search Suggest ...
I am using the Completition suggester for an auto complete App in Java, I was able to extract the suggest text from the...
Read more >Deserialization of suggest responses not working #57297
I am trying to create unit tests for classes that use the java high level rest client. To make this easier I am...
Read more >SearchResponse as JSON - Elasticsearch
I'm looking for a way to get the SearchResponse as JSON, ... We will add this as an out-of-the-box feature of the Java...
Read more >Completion suggester in java API - Elasticsearch
I am trying to integrate the autocompletion feature by following the article ... DEFAULT); Suggest suggest = searchResponse.
Read more >Elasticsearch Highlighting with Kotlin | by Manserpatrice
No. The SearchResponse of the search function does not contain highlighting. This means that we have to do it ourselves.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for raising this @svenhartmann. The suggesters property had some issues with code-gen and is on a list for me to revisit. I’ll keep this issue open to track that progress. For the second item, I’ll need to investigate. That might be an issue with the spec.
From what I see, the real issue is the JSON produced from ES. Fix that and a lot of the client code on many platforms becomes much easier to code, maintain, and performs better. Basically a lot of band-aiding going on with client code. I pretty sure another approach I have in mind would work with current JSON, result in easier to code to maintain and faster, but I need more coffee.