Thursday 10 July 2014 2:59:16 pm



I moved the discussion on query optimizer to new feature request:

It is a good feature request, but I don't believe it solves the issue Donat has here, as it is more about languages and amount of data returned for the matching content objects, so making Donat's reported issue be about that:

Note that the last one will need changes to API most likely, so will need some design work before we can jump on it, maybe something to tackle during summer camp in separate workshops.

Modified on Thursday 10 July 2014 3:24:08 pm by André R

Thursday 10 July 2014 10:17:10 am

Thanks Gaetano and André for your comments.

Regarding the problems with subtree limitations, Felix Woldt has commented the JIRA issue presenting a simple but highly effective query optimisation.

Regarding the features and use of SearchService, Petar Španja has written a great article: Fetching content in eZ Publish 5 using Search service. Highly recommended!

Thursday 10 July 2014 10:12:26 am

It is possible to optimize the sql query to remove all unused policies for the current search.

See the following jira comment which descripes a solution for ezp4 which removes all (mostly all) policies which has no impact to the search

I think such an algorihm can improve ezp5 sql queries a lot.

You must be logged in to post messages in this topic!