39

This question was puzzling me for quite a while.

Why is the improvement bugfix introduced in Magento 1.13.x.x called partial re-indexing not covering "Product Attributes" and "Tags Aggregation Data" indexers? Why do these two have to be re-indexed manually?

To my opinion EAV index is one of the most critical. Not having a partial re-indexing for it means that after each sale (and some people have them) the index is invalidated which means the layered navigation is not valid anymore which results in inconsistent data display and loss of sales.

Am I missing something obvious?

Update:

So here is the description of this bug. Once the sale is made and product goes out of stock the layered navigation reflects the changes for products attributes only for simple products but not for configurables (have not tested bundles and grouped).

So let's assume in your catalog you have a configurable product like t-shirt available in different sizes and "Size" attribute is "Filterable (with results)". Then in a layered navigation of appropriate category or search results you will have the sizes section where all available sizes are listed. If after one of the sales, a particular size goes out of stock you would expect it to disappear from layered navigation. This doesn't happen unless you refresh attributes index and flush blocks cache.

This bug is really critical. It's a two way threat. First, the end customer who sees his size in a layered navigation and then sees that it is actually not available will leave your shop in frustration. Even worse thing is once the product is back in stock it will not be visible in layered navigation, so the end customer will not be able to purchase it. So it's hard to underestimate the amount of revenue losses.

Improve this question
16
  • 5
    We run out of time to implement those two and they were not critical from the performance standpoint which was the main driving factor for the changes. If you see inconsistent data can you report to support? Maybe there is a patch for that.
    – Piotr Kaminski
    Jul 18, 2014 at 17:38
  • 2
    @PiotrKaminski this is sad but you can safely post it as an answer as it of course explains everything.
    – user487772
    Jul 18, 2014 at 20:26
  • 2
    I'm voting to close this question as off-topic because it's about EE
    – Sander Mangel ♦
    Sep 4, 2015 at 8:56
  • 4
    Woah. EE is a perfectly valid version of Magento with a lot of developers (as evidenced by the number of votes this thing has).
    – Luke Rodgers
    Sep 4, 2015 at 9:36
  • 2
    "I'm voting to close this question as off-topic because it's about EE" - Not cool
    – Paras Sood
    Sep 4, 2015 at 12:50

1 Answer 1

Reset to default
5

To not let this question hang at the top of the unanswered queue forever, here's the official answer to "WHY" again:

We run out of time to implement those two and they were not critical from the performance standpoint which was the main driving factor for the changes. If you see inconsistent data can you report to support? Maybe there is a patch for that.

– Piotr Kaminski Jul 18 '14 at 17:38

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.