HCERR_OOM
HCERR_INVALID_NVR
HCERR_ILLEGAL_ARGUMENT
StoringData and Metadata
Thefollowing functions are dened to store data and metadata and to enforce indexing of
metadatawhere necessary:
■“hc_store_both_ez”on page 87
■“hc_store_metadata_ez”on page 88
■“hc_check_indexed_ez”on page 89
Note– The is_indexed valuein the returned system record (hc_system_record_t) indicates
whetherthis record was successfully inserted in the query engine at the time of store, and is
henceavailable for query. Objects that were not inserted into the query engine at time of store
arecalled store index exceptions. Until they are resolved, store index exceptions may or may not
showup in the result sets of queries that match the store. A store index exception is resolved
oncethe metadata for that object has been successfully inserted into the query engine, after
whichthe object will denitely show up in the result sets of queries that match the store. The
“hc_check_indexed_ez”on page 89 method may be used to attempt to resolve a store index
exceptionunder program control. Store index exceptions will also be resolved automatically
(eventually)by ongoing system healing.
hc_store_both_ez
Storesa metadata record and associated data.
Synopsis
hcerr_t hc_store_both_ez (hc_session_t *session,
*data_source_reader,
void *cookie,
hc_nvr_t *nvr,
hc_system_record_t *system_record);
Description
Thisfunction stores both object data and metadata and returns a system_record descriptor.
Thestatus from this operation can be reclaimed using “hc_session_get_status” on page 55.
SynchronousCAPI Functions
Chapter3 • Sun StorageTek5800 System C Client API 87