Developer forum

+1 :-)

Hi

The point of having 2 indexes is that the frontend index do not update all the time.The problem is that we have customers that may have 10+ PIM editors making changes all day long. On every change the index needs to run an update for the backend to reflect the changes and update e.g. queries and dashboards.

For the frontend the idea is to keep it stable, fast and always on. updating the index potentially every minute is an issue for consistency and performance. So for the frontend, a scheduled update once or twice a day is a better solution.

If you for some reason want the frontend index to always update, which we think can cause problems, you just go back to run on one index - then there is no purpose of having 2.

Or do I miss somehting?

BR Nicolai

Hello Nicolai,

- just wonder, if none of the +10 PIM editors ever have asked why changes aren't available in the frontend until the day after, since they have customers awaiting the update?

Importjobs offers a configuration of which indexs should be updated on completion, so we can choose to have full update on backend index and partial update on frontend index. Are there any issues with this?

Br. Michael Knudsen

They seem to have a fine understanding of the concepts - being able to work with data and handle their product enrichments in the backend, and then updates will reach the frontend on schedules.

For small product catalogs instant updates are not a big issue - but for larger ones, it can be a real issue. So it is about keeping the frontend stable and snappy - and 100s of updates of the index each hour will affect the stability... In the perfect world, the index would update instantly with no complications.

So I would say it depends on the setup - amount of pim editors, the amount of updates and the amount of products. 

The setup in Swift is made so we can take larger setups into consideration and do a setup that fits the specific installation.

You could run index updates every 15 minutes or even more often if that is super important for your customer.

Or - you can go away from 2 indexes and just use 1 and get the updates on save. But it can cause some unwanted side-affects in some setups.

We are constantly looking at the features of the index - and we are trying to make the index updates more snappy than now.

BR Nicolai

Hi Nicolai,

I understand your reasons behind the limitation, but your point is valid only for large projects.
For smaller projects where the team is small, requiring additional changes just to make the products available in the front-end just adds frustration.
I also understand that I can just use a single index, but in some cases, even for smaller projects it makes sense to have separate indexes.
Just leave the decision to us (the consultant), and we can decide the scenario and the setup.
Since we have the option to run multiple uindexes after the import, I just figured it may not be that complicated to add it also in the Shop settings (and possibly the User section).
It's not that we cannot live without this option or that we cannot find workarounds. It's just about making our lives (possibly) easier.
Thank you,
Adrian
 

I get it.

We did this to avoid a problem we have seen many times - adding this feature would get us back to square one... :)