Export Data

Mammoth allows data to be exported from a View to various Databases and Cloud services. This can be done in one of the two ways.

  1. Export as part of the pipeline
  2. Quick Export
  3. Live Link [1]

Export as part of the pipeline

When an export is added through the add task menu, the export becomes part of the pipeline. This means that the export is performed every time there is update to the original dataset.

Automatic export is configured in the following manner.

  1. Click ADD TASK button in the menu-bar
  2. Go to EXPORT section
  3. Choose the export you want to add.
  4. Fill the export form & set configuration.
  5. Click VALIDATE and APPLY

Options

From the pipeline, one can perform the following actions by accessing the menu on any of the export items.

  1. Run now - allows user to initiate export manually.
  2. Unlink - removes the export from the pipeline
  3. Edit - allows changes to export confirmation.

Quick Export

Quick exports are one time exports of the data view, without adding an item in the pipeline. This can be done any time manually.

To perform a quick export of the data view do the following -

  1. Click EXPORT button in the status bar to open an export dialog
  2. Select the export option
  3. Fill the export form & set configuration.
  4. Depending on the export option click DOWNLOAD or SEND or APPLY
  5. A notification will appear in the notification section, that gives updates on the status of the export action.

Export as stored vs as seen

Data is not always as it appears on the grid in the data view. This is because the data can be formatted which does not affect the underlying data. The following options are allowed when performing exports wherever it is appropriate.

  • Export as Stored: The formatting done on the data is not considered when doing exports.
  • Export as Seen: The formatting done on the data is not considered when doing exports. The data is formatted and the target of the export might have text columns whereas whenever the formatted can not be exported as numeric or date.

Supported Exports

Currently following exports are supported

  • Push to Databases & Cloud
    • MySQL
    • PostgreSQL
    • Elasticsearch
    • Power Bi
  • Download as CSV
  • Send via E-mail
  • Save as Dataset

Look at the following table to get a comprehensive overview of the supported exports

Table 20 Supported Exports
Action Add to pipeline Quick Export Export as seen Export as stored
Export to MySQL ✔︎ ✔︎
Export to PostgreSQL ✔︎ ✔︎
Export to Elasticsearch ✔︎ ✔︎ ✔︎
Export to Power Bi ✔︎ ✔︎ ✔︎
Download as CSV ✔︎
Send via Email
Save as Dataset

Export to MySQL | PostgreSQL

With Mammoth the data view can be exported to MySQL or PostgreSQL table in a database residing on a remote server. Exporting data view to MySQL or PostgreSQL can be performed via Quick Export as well as Add to Pipeline.

For Export to MySQL or PostgreSQL action user needs to provide the following -

  1. Host - the remote host where MySQL resides
  2. Port - to connect when communicating with remote host
  3. User
  4. Password
  5. Database name
  6. Table name

Running this export will create a table on the remote database that already exists and populate it with the contents of data view.

Note

  1. Except table name, the other requirements are mandatory. If table name is not provided, it will be auto-generated and visible in the notification corresponding to the action.
  2. If a table is present in the database with same name as table name mentioned in the export action, then the existing table would be deleted and a new table will get created with that name.
  3. The username provider should have sufficient privileges.

Export to Elasticsearch

With Mammoth the data view can be exported to Elasticsearch on a remote server. Exporting data view to Elasticsearch can be performed via Quick Export as well as Add to Pipeline.

For Export to Elasticsearch action user needs to provide the following -

  1. Host - the remote host on which elasticsearch is running
  2. Port - to connect when communicating with remote host
  3. User
  4. Password
  5. Index name

Additionally user has to set the following:-

  1. Batch Size - This the no. of rows from data view that get exported in a single POST request
  2. Connect via - type of connection allowed on remote host HTTP | HTTPS

Running this action will create an index on Elasticsearch with type as mammoth and for each row a document will be created with an id auto-generated by Elasticsearch.

Note

  1. If an index with name as mentioned in action is already present in the elasticsearch, it is removed and a new index is created with that name.
  2. Currently Elasticsearch version 5 and above are supported

Export to Power Bi

With Mammoth the data view can be exported to Power Bi cloud service. Exporting data view to Power Bi can be performed via Quick Export as well as Add to Pipeline.

For Export to Power Bi action user needs to provide the following -

  1. User - Power BI account id
  2. Password
  3. Client id - application id of a native application registered with Power Bi
  4. Dataset name
  5. Table name

Running this action will create a dataset on your Power BI workspace

Note

  1. Changing schema of the dataset is not allowed in Power Bi.
  2. In a given dataset there can be only one table in Power Bi

Download as CSV

With Mammoth the data view can be exported to a csv file. Exporting data view to a csv can be performed via Quick Export only

This is the default export option for Quick Export.

Running this action will generate a csv file which can then be downloaded by clicking the DOWNLOAD button in notification corresponding to the action.

Note

  1. The download link is valid for 1 hour

Send via E-mail

With Mammoth the data view can exported via email. This action can be performed as Quick Export only.

This requires users to enter -

  1. Recipients
  2. Subject of E-mail
  3. Message

Running this action will send an E-mail to the recipient(s) containing a link in the body of email. Clicking that link will download a csv file generated corresponding to the view.

Note

  1. Except message other fields in the export dialog are mandatory
  2. To send E-mail to multiple recipients, add comma after the email address of each recipient
[1]Beta.