Modeling Guide for SAP Data Hub

CSV Ingest2 via Disk

The data generator generates a series of messages, each consisting of one or more csv records. Each message is passed to the preingestor, which creates a message with record objects. Finally, this message is passed to the ingestor, which stores the records in the vora disk engine and emits the commit token associated with each message.

The table definition is derived from the avro schema configured at the preingestor, which is given as:
{ "name": "sample_demo_deep_record", "type": "record", "fields": [ {"name": "idx", "type": "int"}, {"name": "code", "type": "string"}, {"name": "magnitude", "type": "double"}, {"name": "name", "type": "string"}, {"name": "coordinates", "type": "record", "fields": [ {"name": "latitude", "type": "double"}, {"name": "longtitude", "type": "double"}]}, {"name": "ts", "type": "long", "logicalType": "timestamp-millis"}, {"name": "status", "type": "boolean"}] }
The corresponding csv line should represent e fields with the values representing the following field values:
The datagenerator operator will transmit a mesage whose body consists of one or more such lines:
4284,9ar6S,6538.984505939649,f4I4XgsW7Te66n7EVLjFilM8,77.44481090477504,154.91779649284774,2018-05-07 2:17:42.849,true 5068,CKqKW,5027.427239619433,o9DdLXkUH,54.209264596298,54.42583528731214,2018-05-07 2:17:42.849,false 5783,7spVh,1238.6340364821854,WZzhhg3Oape8MVtTEnLvB,-42.23289035504596,-46.40615837430687,2018-05-07 2:17:42.850,false ...


You need a running SAP Vora instance.

Configure and Run the Graph

Follow the steps below to run the example from the Data Pipeline UI:
  1. In the left panel, select the Graphs tab and navigate to com/sap/demo/vora/ingestion/csv_ingestion_example2_disk.
  2. Check the configuration of the ingestor node: dsn.
  3. In the tool bar, select Run (play button).
  4. The Status panel indicates if the graph is running.
  5. Use the context menu Open UI of the Wiretap node to open the wiretap.
  6. The wiretap opens and you see the commit tokens.
  7. Stop the graph and change the generator's batchSize and run the graph again.