The use case for the initial load of records assumes that you are loading records into an empty data domain 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 ingestChanges operation with addRecords, specifying one or more record elements.
<attribute name="pKey" type="mdex:string">pKeyValue</attribute>where pKey is the name of the primary-key attribute (such as partID) and pKeyValue is the value of the primary key for the record that you are adding (such as P775).
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.endeca.com/MDEX/ingest/2/0" xmlns:ns1="http://www.endeca.com/MDEX/XQuery/2009/09"> <soapenv:Header/> <soapenv:Body> <ns:ingestChanges> <ns:addRecords> <ns:record> <ns1:attribute name="mdex-property_Key" type="mdex:string">partID</ns1:attribute> <ns1:attribute name="mdex-property_DisplayName" type="mdex:string">Part ID</ns1:attribute> <ns1:attribute name="mdex-property_Type" type="mdex:string">mdex:string</ns1:attribute> <ns1:attribute name="mdex-property_Language" type="mdex:string">en</ns1:attribute> <ns1:attribute name="mdex-property_IsSingleAssign" type="mdex:boolean">false</ns1:attribute> <ns1:attribute name="mdex-property_IsUnique" type="mdex:boolean">true</ns1:attribute> <ns1:attribute name="mdex-property_IsTextSearchable" type="mdex:boolean">false</ns1:attribute> <ns1:attribute name="mdex-property_TextSearchAllowsWildcards" type="mdex:boolean"> false</ns1:attribute> <ns1:attribute name="mdex-property_IsPropertyValueSearchable" type="mdex:boolean"> true</ns1:attribute> <ns1:attribute name="system-navigation_Select" type="mdex:string">single</ns1:attribute> <ns1:attribute name="system-navigation_Sorting" type="mdex:string">lexical</ns1:attribute> <ns1:attribute name="system-navigation_ShowRecordCounts" type="mdex:boolean">true</ns1:attribute> <ns1:attribute name="system-property_GroupMembership" type="mdex:string"> system_properties</ns1:attribute> </ns:record> <ns:record> <ns1:attribute name="partID" type="mdex:string">P789</ns1:attribute> <ns1:attribute name="modelNum" type="mdex:int">2562</ns1:attribute> <ns1:attribute name="location" type="mdex:geocode">42.365615 -71.075647</ns1:attribute> </ns:record> </ns:addRecords> </ns:ingestChanges></soapenv:Body></soapenv:Envelope>
The request first creates the partID primary-key attribute, and then adds one new record to the data domain with the primary key partID=P789. The request also creates two standard attributes (modelNum and location), because they do not exist in the data domain.
To load records into an empty data domain:
The request is typically created and managed by a ETL client.
<ingest:ingestChangesResponse xmlns:ingest="http://www.endeca.com/MDEX/ingest/2/0"> <ingest:numPropertiesCreated>2</ingest:numPropertiesCreated> <ingest:numRecordsAffected>1</ingest:numRecordsAffected> <ingest:numRecordsDeleted>0</ingest:numRecordsDeleted> </ingest:ingestChangesResponse>