Wednesday, March 9, 2016

How Endeca Assembler Query works?

Find out the Assembler query flow and corresponding response below till Endeca 11.2: 1. A query is sent to Endeca MDEX to get  suppleme... thumbnail 1 summary
Find out the Assembler query flow and corresponding response below till Endeca 11.2:

1. A query is sent to Endeca MDEX to get supplemental objects and other objects like the thesaurus, keyword redirect etc.This response is entry point for second query to resolve all content collection, keyword redirects, did you mean, spelling correction and thesaurus expansion.

    Query below from dgraph request log
    /graph?node=0&profiles=site.<<site_name>>&offset=0&nbins=0&irversion=652

Note :  11.2 does not return supplement objects


2. Fire an actual query based on navigation state using response from step 1 or search term and get the following kinds of data:
  • Dimensions and properties( Refinements/facets) 
  • Record (Erec Object)
  • Breadcrumbs ( Descriptor Refinement)
As per above flow, Minimum two queries are required to render the page. The number of queries can be more if other cartridges like Horizontal Record Spotlight with different navigation state is selected. First query does not return any records and this is very lightweight query but this may get heavy response object due to supplemental objects.

Note :- Navigation state can be changed from cartridge handler and this may lead to fire another query to Endeca. 

No comments

Post a Comment

Text Widget