The Lyftron Provider for Google Drive offers the most natural way to access Google Drive 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 Google Drive data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Google Drive 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.
- Comprehensive Delta load mechanism.
- Real-time access to Google Drive.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Google Drive, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Follow the steps below to authenticate with Google Drive and obtain the OAuthVerifier connection property:
- Click the following link to open the Google Drive OAuth endpoint in your browser.
- Log in and grant permissions to the provider. You are then redirected to the callback URL, which contains the verifier code.
- Save the value of the verifier code. You will set this in the OAuthVerifier connection property.
On the headless machine, set the following connection properties to obtain the OAuth authentication values.
- OAuthVerifier: Set this to the verifier code.
- InitiateOAuth: Set this to REFRESH.
- OAuthSettingsLocation: Set this to persist the encrypted OAuth authentication values to the specified file.
After the OAuth settings file is generated, set the following properties to connect to data:
- OAuthSettingsLocation: Set this to the file containing the encrypted OAuth authentication values. Make sure this file gives read and write permissions to the provider to enable the automatic refreshing of the access token.
- InitiateOAuth: Set this to REFRESH.
For more detailed information on service and user account connectivity click Google Drive Advanced Settings
Establishing a Connection with Lyftron's Quickstart Steps
Create your Google Drive 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 Google Drive 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 Google Drive connection with Lyftron.InitiateOAuth=GETANDREFRESH;OAuthClientId=[OAuthClientId]; OAuthClientSecret=[ServerName]; OAuthAccessToken=[User]; OAuthAccessTokenSecret=[Password];
|Connection Name||Enter your connection details||Required|
|InitiateOAuth||your Google Drive GETANDREFRESH||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
The provider models the data in Google Drive into a list of tables that can be queried using standard SQL statements.
Generally, querying Google Drive tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns.
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard. To find out more about tables and stored procedures, please navigate to their corresponding entries in this help document.
|Files||Tables||Create, update, delete, and query the files and folders contained in a user's Google Drive.|
|Permissions||Tables||Create, update, delete, and query permissions for resources in a user's Google Drive.|
|TeamDrives||Tables||Create, delete, and query the available TeamDrives for a specific user.|
|Docs||Views||Query the Google Docs contained in a user's Google Drive.|
|Folders||Views||Query the folders contained in a user's Google Drive.|
|Photos||Views||Query the photos contained in a user's Google Drive.|
|Sheets||Views||Query the Google Sheets contained in a user's Google Drive.|
|Videos||Views||Query the Google Videos contained in a user's Google Drive.|