The use case for the initial load of records assumes that you are loading records into an empty data store that has been created in the Oracle Endeca Server.
The initial data load is performed via one or more invocations of the Data Ingest Web Service ingestRecords operation specifying one or more mdex:record elements.
<ingest:ingestRecords xmlns:ingest="http://www.endeca.com/MDEX/ingest/1/0" xmlns:mdex="http://www.endeca.com/MDEX/XQuery/2009/09"> <ingest:primaryKeys> <ingest:primaryKey name="partID"/> <ingest:primaryKey name="supplierID"/> </ingest:primaryKeys> <ingest:addAssignments> <mdex:record> <partID type="mdex:string">P123</partID> <modelNum type="mdex:int">2562</modelNum> </mdex:record> <mdex:record> <supplierID type="mdex:string">S456</supplierID> <location type="mdex:geocode">42.365615 -71.075647</location> </mdex:record> </ingest:addAssignments> </ingest:ingestRecords>
The request first creates the partID and supplierID primary-key attributes, and then adds two new records to the data store. The primary key of the first record is partID=P123 while supplierID=S456 is the primary key of the second record. The request also creates two standard attributes (modelNum and location) because they do not exist in the data store.
To load records into an empty data store:
<ingest:ingestRecordsResponse xmlns:ingest="http://www.endeca.com/MDEX/ingest/1/0"> <ingest:numPropertiesCreated>4</ingest:numPropertiesCreated> <ingest:numRecordsAffected>2</ingest:numRecordsAffected> <ingest:numRecordsDeleted>0</ingest:numRecordsDeleted> </ingest:ingestRecordsResponse>