code: public void updateCatalog(String diffCmds, CatalogContext context, boolean isReplay,
              boolean requireCatalogDiffCmdsApplyToEE, boolean requiresNewExportGeneration)
      {
          // note this will never require snapshot isolation because the MPI has no snapshot funtionality
          m_executionSite.updateCatalog(diffCmds, context, false, true, Long.MIN_VALUE, Long.MIN_VALUE, Long.MIN_VALUE,
                  isReplay, requireCatalogDiffCmdsApplyToEE, requiresNewExportGeneration);
          m_scheduler.updateCatalog(diffCmds, context);
      }
docs: Update the MPI's Site's catalog.  Unlike the SPI, this is not going to
  run from the same Site's thread; this is actually going to run from some
  other local SPI's Site thread.  Since the MPI's site thread is going to
  be blocked running the EveryPartitionTask for the catalog update, this
  is currently safe with no locking.  And yes, I'm a horrible person.