Thanks Jacopo.
I noticed that flag, but I'm not sure that will solve the problem. I
wonder if we could make the keyword indexing service call async?
Ideally, the keyword indexing implementation should be made smarter, or
more configurable, or something. Right now it seems to take a brute
for
There is a flag in the Product entity that can beused to prevent the creation
of product keywords; unfortunately the flag is ignored by the eca associated to
the features of the product (imo this is something we should fix).
Kind regards,
Jacopo
On Jan 14, 2012, at 1:59 AM, Adrian Crum wrote:
forgot to mention, that re-creating keywords, these jobs already exist.
On 01/14/2012 08:04 AM, Hans Bakker wrote:
Hi Adrian,
For a large product load we disable the seca's temporarily and after
the load enable them again...
When people enter new single products sometimes they try to find
Hi Adrian,
For a large product load we disable the seca's temporarily and after
the load enable them again...
When people enter new single products sometimes they try to find these
straight away under the current scheme is working fine
sorry do not see the madness herethe end of
I tried to find out why a data import for a bespoke (made-to-order)
manufacturer was taking WAY too long. Turns out it was keyword indexing
EECAs.
Each product has dozens of product features, and it also has a
manufacturer ID. The indexProductKeywords is called for the product,
each product f