Hitachi Content Platform​

 MQE vs HCI index

  • Object Storage
  • Hitachi Content Intelligence HCI
  • Hitachi Data Ingestor HDI
Eduardo Javier Huerta Yero's profile image
Eduardo Javier Huerta Yero posted 07-30-2019 20:04

Is there a document comparing the difference between using MQE with custom metadata or using an HCI index? I realize that HCI may play a role in both cases, but in different ways. Suppose a customer wants to add and index custom metadata on some HCP objects. He could use HCI to process those files and either:

  • Create custom metadata, attach it to the objects and use MQE for searching, OR
  • Create an index in HCI and use it for searching.

Is there somewhere a comparison of features/performance of these approaches?

Thanks


#HitachiDataIngestorHDI
#HitachiContentIntelligenceHCI
Jonathan Chinitz's profile image
Jonathan Chinitz
  1. When you index CM with MQE the queries that you perform will only return the URL of the object, meaning that the CM is not stored in the index. MQE indexing of CM was designed to find URLs and nothing else.
  2. MQE has built in throttling/constraints on the number of queries you can perform to ensure that the HCP cluster is not overrun. Some customers have run into these limits under load.
  3. Obviously with HCI you can do lots more with the fields than you can with HCP. The Search application that is built in to HCP is a bit more rigid and less feature rich than the one provided with HCI.
  4. One advantage that MQE/HCP Search has is that it doesn't require any additional hardware -- it runs on the HCP nodes themselves.
Eduardo Javier Huerta Yero's profile image
Eduardo Javier Huerta Yero

Thanks Jon! This is exactly what I was looking for.