SearchResults<T> doesn't implement trait serde::Serialize

[ZelCloud]

Description Not sure if this is a bug or a feature request.

SearchResults<T> doesn't seem to have the serde serialize trait, this prevents passing the results to something like actix httpresponse json.

code block

#[macro_use]
extern crate diesel;

extern crate env_logger;

use std::env;

use actix_cors::Cors;
use actix_web::{
    delete, get, middleware, patch, post,
    web::{self, Data},
    App, HttpRequest, HttpResponse, HttpServer,
};

use serde::{Deserialize, Serialize};
use serde_json::Result;

use chrono::{DateTime, Utc};

use meilisearch_sdk::client::*;

#[derive(Debug, Serialize, Deserialize)]
pub struct Posting {
    pub id: uuid::Uuid,
    pub title: String,
    pub link: String,
    pub rating: i32,
    pub summary: Option<String>,
    pub updated_at: DateTime<Utc>,
    pub created_at: DateTime<Utc>,
}

#[get("/search-test")]
async fn get_r_search_test(
    req: HttpRequest,
    meili_client: web::Data<meilisearch_sdk::client::Client>,
) -> Result<HttpResponse> {
    let results = meili_client
        .index("movies")
        .search()
        .with_query("Apple")
        .execute::<crate::models::Posting>()
        .await
        .unwrap();

    println!("{:?}", results);

	// ERROR LINE
    Ok(HttpResponse::Ok().json(results))
}

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    dotenvy::dotenv().ok();

    let meilisearch_url = env::var("MEILISEARCH_URL").expect("Meilisearch URL env not found");
    let meilisearch_master_key = env::var("MEILISEARCH_MASTER_KEY").expect("Meilisearch master API key env not found");
    let meilisearch_client = Client::new(&meilisearch_url, Some(meilisearch_master_key));

    std::env::set_var("RUST_LOG", "actix_web=info");
    env_logger::init();

    HttpServer::new(move || {
        App::new()
            .app_data(Data::new(meilisearch_client.clone()))
            .wrap(middleware::Logger::default())
            .wrap(Cors::permissive())
            .service(web::scope("/api/v1").service(get_r_search_test))
    })
    .bind("127.0.0.1:9004")?
    .run()
    .await
}

Expected behavior SearchResults<T> will have the serde serialize trait.

Current behavior HttpResponse::Ok().json(results) ---- ^^^^^^^ the trait _::_serde::Serialize is not implemented for SearchResults<Posting>

Screenshots or Logs N/A

Environment (please complete the following information):

• OS: Windows 10 x64
• Meilisearch version: 1.3.3
• meilisearch-rust version: 0.24.1

[moy2010]

This is not a bug. When you search with Meilisearch's client it will return the SearchResults wrapper around whatever document model you are using for your documents (in this case, you are using crate::models::Posting).

SearchResults is just the response object with the details for the search result (i.e. how many hits or results were returned, in what page you are in case that you are using pagination, etc.) and it's obviously not meant to be exposed to the user, hence why I guess it doesn't implement Serialize. It's the API telling you that you are doing something wrong.

In your case, I would just extract the hits from it and send the response to the consumer of the /search-test endpoint.

[taufik-nurhidayat]

What is the solutions for this case?

[CommanderStorm]

What is the solutions for this case?

The solution is entirely dependent on what you WANT the API to return.

Example:

• do you want the formatted or unformatted result?
• do you want where the search matches
• do you want to expose other statistics (facets, paging, ...)?

I would say that adding your own struct for these return types is better. Rationale: You will get notified earlier (via compilation errors) of any changes you will need to migrate around.

[Tails]

Running into the same thing, trying to return the query result as Json in a Rocket server. I also had expected the result structs to implement Serialize when T supports it, since the data in the results is pretty harmless to be exposed to the client.

[WillKirkmanM]

Here's a workaround for now, by defining a new struct that mirrors the search results, then mapping SearchResult<CombinedItem> to a Vector of Combined Items and then finally construct a serializable structure.

(CombinedItem is my data structure, similar to the author's Posting) Using Actix:

#[derive(Serialize)]
struct SerializableSearchResults {
    hits: Vec<CombinedItem>,
}

#[get("/search")]
pub async fn search(query: web::Query<SearchQuery>) -> HttpResponse {
    let client = Client::new("http://localhost:7700", None::<&str>).unwrap();
    let index = client.index("library");

    let search_results: SearchResults<CombinedItem> = index.search()
        .with_query(&query.query)
        .execute()
        .await
        .unwrap();

    let hits: Vec<CombinedItem> = search_results.hits.into_iter().map(|result| result.result).collect();

    let serializable_results = SerializableSearchResults {
        hits,
    };

    HttpResponse::Ok().json(serializable_results)
}

[Mubelotix]

This was indeed never planned. We might accept PRs that implement Serialize on our structs as long as they don't increase the complexity of the codebase though (like #668), feel free to send one