After you have an Ascend Read Connection set up, then you continue to set up the Read Connector in your dataflow.
In Figure 1 above:
- Name (required): The name to identify this connector with.
- Description (optional): Description of what data this connector will read.
You can either manually provide Table Name(required), Schema name(optional) and Replication Strategy(optional) or click on Browse and Select Data: this button allows to explore resource and locate assets to ingest. This will give you access to the Vertica Server database in a modal dialog (Figure 3 and 4 below), where you can navigate to the desired table to be imported. Select the table you want to ingest and press Select.
NOTE: Replication Strategy allows to create an identical copy of your primary database or synchronize changes between multiple databases, and maintain data consistency and integrity. For information about replication strategies, please refer to our Database Reading Strategies documentation.
Once you click on the GENERATE SCHEMA button, the parser will create a schema and a data preview will be populated as in the Figure 5 below.
- Add schema column: Add a custom column to the generated schema
Update the status of the read connector by marking it either Running to mark it active or Paused to pause the connector from running.
The refresh schedule specifies how often Ascend checks the data location to see if there's new data. Ascend will automatically kick off the corresponding big data jobs once new or updated data is discovered.
When resources are constrained, Processing Priority will be used to determine which components to schedule first.
Higher priority numbers are scheduled before lower ones. Increasing the priority on a component also causes all its upstream components to be prioritized higher. Negative priorities can be used to postpone work until excess capacity becomes available.
Updated 10 days ago