When collecting attributes to populate attributes_metadata almost ALL attributes were fetched creating a lot of data to be transferred to ElasticSearch. I changed the the logic so only the attributes that have is_visible AND is_visible_on_front set will be collected.
I assume this was intent from the beginning.
Probably we can even get rid of the is_visible check and only fetch attributes based on is_visible_on_front.
I think an attribute will never have is_visible == 0 and is_visible_on_front == 1 at the same time?!
What do you think @afirlejczyk @doliwa-divante ?
closes #383
When collecting attributes to populate
attributes_metadataalmost ALL attributes were fetched creating a lot of data to be transferred to ElasticSearch. I changed the the logic so only the attributes that haveis_visibleANDis_visible_on_frontset will be collected. I assume this was intent from the beginning.Probably we can even get rid of the
is_visiblecheck and only fetch attributes based onis_visible_on_front. I think an attribute will never haveis_visible == 0andis_visible_on_front == 1at the same time?! What do you think @afirlejczyk @doliwa-divante ?