Temporary disabling facet and column update

HFCDev

Hi, 

  This is something that has occured that I would want to do in the module I'm building with distributed agents, but I think this would apply to any batch data migration (OI, OTIC, other) where a large number of objects are being created, and category attributes are heavily involved in the mix.  

  Given that any update of category attributes (applying them, updating them, upgrading them) would signal a change in any facets or custom columns based on them, a large data migration might could cause a huge load on the Distributed Agents framework. Is there a way of deferring facet/column update jobs until after a migration or mass update has completed?

-Hugh

Kyle_Swidrovich

Hi Hugh,

 

Not in current product, however, we’re working on scheduling features right now that would ship in an update for Content Server.

 

I’d like to get a session together to bounce ideas off the community for feedback to see if the scheduling features we’re working on will meet the needs of our admins and partners. We’re aiming for the first week of April.

 

Kyle