The search indexer returns a mysql error

After hitting the button "Re-Index Basic (Content Lists)" I get this error and the index table is empty:

21900 / 21900 items You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'END WHERE item_id IN ()' at line 1 SQL=UPDATE ___flexicontent_items_ext SET search_index = CASE item_id END WHERE item_id IN () [180.26 secs] , INDEXING FINISHED. You may close this window

How would I correct this error?

Cheers

Hello,

backup , update to r1742a and send me a PM with super admin login

i see that you have 21,000 items ?

I updated and sent you the credentials.

Yes, I have 21900 items (which are only dummies right now but will be real data soon).

The Advanced Indexer is doing okay, but the Basic one gives that error.

cheers

PS: the indexer displays the time taken to index, that time is highly incorrect, it definitely does not count seconds

Hello

the indexer does count seconds,
seconds of execution time

if indexer run via a single run and not via multiple AJAX calls the it would take that amount of time to complete,

e.g. it would take 180 seconds, but with multiple AJAX calls you may end up spending 400 more seconds in network delay to send AJAX request + get AJAX response + some small time to indexer display inside the browser

About error, the very last AJAX run of indexer, runs with ZERO items because you have exactly 21900 items a check needs to be added for this

Thanks for the explanation. Where do I switch the indexer to not use AJAX and therefore be faster?

Hello,

no just maybe we will add a parameter to configure a larger step,

and also add a descriptions about seconds to denote what it is

ah, ok. yes, larger steps would definitely speed up the index process from what I can tell looking at the seconds going by very slowly.

Cheers

Hello

re-index speed
for re-indexing your 21,000 is not slow at all,

-- when you index real items with "different content", it will be 5x-10x times slower than now

1. but still this would be considered fast !
2. the Joomla smart-index is re-index multiple times more slow and maybe for 20,000 articles it will not finish unless you have a server with a lot of memory and CPU power

Just the 20 items per step (AJAX call) wastes some time in
send request - receive response
- in this case for execution time 0.1 seconds , e.g. 0.5 seconds are wasted sending and receiving the server response

-- but for normal data 0.1 seconds of execution time will be 2 or 5 or 10 seconds

thus with real data you will spend
5 seconds indexing 20 items and
0.5 seconds communicating with server(request/response)

Ah, thanks for the insight, very helpful! 2 Questions arise now:

1. Will only the index process be affected time wise when using real data or will the Advanced FC Search in the front end be slower as well? And if so what can I do to speed up the search? I reduced the amount of filters already to 5.

2. I will use the Advanced FC Search in the front end (or maybe the Basic Search too, to have a quick search as well). Do I need to run the basic indexer or the advanced indexer or both? I read www.flexicontent.org/documentation/faq/i...l?fontstyle=f-larger , but Im still not sure how to handle the search correctly.

Cheers

Hello

1. Filter creation on large site is slow because:
it also does "item counting", we have option to disable "item counting", but currently this is broken so do not try to disable it yet
(we are fixing it)

2. Hello, in search view menu item, you have a description,
you can use basic search index which is faster, but in this case you cannot limit text-search to only search specific fields , e.g. if you use basic search index you cannot limit text search to use only TITLE field or only DESCRIPTION field