About Quandl connector
Etlworks Quandl connector allows the fastest and easiest way to connect to real-time Quandl API data. The connector works just like any other database connector.
Etlworks partnered with CData to provide access to Quandl API using industry-standard JDBC protocol. Read about CData Quandl JDBC connector.
When to use Quandl connector
Use this connector to create Flows that extract data from Quandl API.
Enable Quandl connector for your Etlworks Integrator account. Contact
email@example.com to enable the connector.
Create a Connection
Here's how you can create a Connection in two easy steps:
Step 1. In the
Connections window, click
+, and type in
Step 2. Enter Connection parameters:
API Key: enter Quand API Key. Read how to obtain Quandl API Key.
Other parameters to specify the Connection string options. Read about available Connection string options.
Work with Quandl API
Quandl Data Model
The connector models Quandl Databases as relational Databases; Quandl Datasets are modeled as relational views.
After specifying a DatabaseCode, you can access a Dataset in the Database by querying the view of the same name. The view definitions are dynamically retrieved. When you connect, the driver gets the list of tables and the metadata for the tables by calling the appropriate Web services. Your queries can then pick up changes to the remote data.
This chapter provides more information about the behavior of the Database and Dataset Views, as well as the stored procedures of the driver. It also includes sample tables from the WIKI Dataset; the actual data model will be dynamically obtained based on the DatabaseCode you specify. Quandl Datasets all support several common filters in the WHERE clause. See Using Filters for more information.
Read about the data model.
Stored procedures are available to complement the data available from the Data Model. It may be necessary to update data available from a view using a stored procedure because the data does not provide for direct, table-like, two-way updates. In these situations, the retrieval of the data is done using the appropriate view or table, while the update is done by calling a stored procedure. Stored procedures take a list of parameters and return back a dataset that contains the collection of tuples that constitute the response.
Read about available stored procedures in the data model.
To call stored procure from the SQL Flow or Before/After SQL, use
EXEC sp_name params=value. Example:
EXECUTE my_proc @second = 2, @first = 1, @third = 3;
Read about SQL Compliance.
Extract data from Quandl API
Extracting data from Quandl is similar to extracting data from the relational database.
Here's how you can do this:
Step 1. Create Quandl Connection which will be used as a source (
Step 3. Create a Flow where the
source is a database and the destination is a Connection created in step 2, for example, a relational database.
Step 4. Add a new source-to-destination transformation.
Step 5. Select the Quandl Connection created in step 1 as a source Connection and select the data object you are extracting data from.
Step 6. Select
TO Connection, Format (if needed), and object (for example database table) to load data into.
Step 7. Click
MAPPING and optionally, enter
Source query (you don't need a query if you are extracting data from the Quandl data object unconditionally).
Step 8. Optionally, define the per-field Mapping.
Step 9. Add more transformations if needed.
Browse data in Quandl
You must have Quandl Connection to browse objects and run SQL queries.
Use the Etlworks Explorer to browse data and metadata in Quandl as well as execute
SELECT queries against the Quandl Connection.