Filter
Top Products
HCERR_OOM
HCERR_INVALID_NVR
HCERR_ILLEGAL_ARGUMENT
Storing Data and Metadata
The following functions are dened to store data and metadata and to enforce indexing of
metadata where 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 value in the returned system record (hc_system_record_t) indicates
whether this record was successfully inserted in the query engine at the time of store, and is
hence available for query. Objects that were not inserted into the query engine at time of store
are called store index exceptions. Until they are resolved, store index exceptions may or may not
show up in the result sets of queries that match the store. A store index exception is resolved
once the metadata for that object has been successfully inserted into the query engine, after
which the object will denitely 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
exception under program control. Store index exceptions will also be resolved automatically
(eventually) by ongoing system healing.
hc_store_both_ez
Stores a 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
This function stores both object data and metadata and returns a system_record descriptor.
The status from this operation can be reclaimed using “hc_session_get_status” on page 55.
SynchronousCAPI Functions
Chapter3 • SunStorageTek 5800SystemCClient API 87