With API 2.0 all requests to /search are answered with just a list of identifiers. This is not sufficient for many use cases and forces clients to perform additional HTTP requests in order to present search results to human users. In my opinion the existing /search endpoint should be extended to display all available index fields if needed. This could easily be done without breaking existing contracts, e.g. by introducing another optional request parameter that allows clients to specify what fields should come with the response or by introducing an additional content type that allows clients to ask for full records in their search requests.
Please sign in to leave a comment.