Overview
The Lyftron Provider for GreenPlum offers the most natural way to access GreenPlum data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing GreenPlum data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s GreenPlum data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Key Features
- Comprehensive Delta load mechanism.
- Real-time access to GreenPlum.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
Prerequisites
The user must have credentials for GreenPlum, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your GreenPlum connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click GreenPlum for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish GreenPlum connection with Lyftron.
"User=user;Password=admin;Database=dbname;Server=127.0.0.1;Port=5432"Key | Value | Field |
Connection Name | Enter your connection details | Required |
User | Your GreenPlum User | Required |
Password | Your GreenPlum Password | Required |
Database | Your GreenPlum Database Name | Required |
Server | 127.0.0.1 | Required |
Port | 5432 | Required |
Logfile** | Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx | Optional |
Verbosity** | Choose verbosity 1-5 based on the severity of debugging | Optional |
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
Hurray! Now you have successfully connected with the Lyftron GreenPlum connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.
Data Model
System Tables
gp_configuration_history
The gp_configuration_history table contains information about system changes related to fault detection and recovery operations. The fts_probe process logs data to this table, as do certain related management utilities such as gprecoverseg and gpinitsystem. For example, when you add a new segment and mirror segment to the system, records for these events are logged to gp_configuration_history.
This table is populated only on the master. This table is defined in the pg_global tablespace, meaning it is globally shared across all databases in the system.
Column | Type | References | Description |
time | timestamp with time zone | Timestamp for the event recorded. | |
dbid | smallint | gp_segment _configuration.dbid | System-assigned ID. The unique identifier of a segment (or master) instance. |
desc | text | Text description of the event. |
More information about Greenplum system tables can be found here
Advanced Settings
To view a detailed advanced settings options, go to GreenPlum Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.