![]() ![]() ![]() It uses the search query to retrieve the list of entity IDs that match the query, loads those entities, and returns them. When you query a Search API index it retrieves the indexed data, but it doesn't just return those values. It tracks entities that it may index and pushes data from those entities, as configured, into the search index. The Search API module works differently in a typical Drupal installation. The GraphQL Search API module performs the same way – you're pushing your GraphQL query to Drupal, but it is returning the raw results from your search index. Querying directly from the search index means your consumer now must understand two different schemas or fetch the individual resources itself. The problem with this approach is that your index query results match the data existing in your search index, not what is represented in Drupal. Before diving into the module, I want to explore the problem space it aims to solve.Ĭurrently, consumers in a decoupled Drupal architecture would need to query the search index directly or access it through a proxy like ContentaJS. ![]() I'm happy to introduce a new module created in my research and development time at Centarro. The JSON:API Search API integration module enables decoupled Drupal architectures to use the Search API module to query indexed data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |