Automate Bitbucket Data Replication to Azure Data Lake

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Bitbucket data into your Azure Data Lake instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Azure Data Lake as a Replication Destination

Using CData Sync, you can replicate Bitbucket data to Azure Data Lake. To add a replication destination, navigate to the Connections tab.

1. Click Add Connection.
2. Select Azure Data Lake as a destination.

3. Enter the necessary connection properties. To connect to Azure Data Lake, set the following properties, depending on your version of Azure Data Lake Storage:

   Azure Data Lake Storage Gen1

   • Generation: Must be set to 1.
   • Account: The name of the Azure Data Lake Store account.
   • Path: The path to store the replicated file (the root directory by default).
   • TenantId: The tenant ID.
   • OAuthClientId: The application ID for the Azure Directory web application (see the CData Sync Help for more information).
   • OAuthClientSecret: The key generated for the Azure Directory web application (see the CData Sync Help for more information).

   Azure Data Lake Storage Gen2

   • Generation: Must be set to 2.
   • Access Key: The access key used to authenticate (see the CData Sync Help for more information).
   • Account: The name of the Azure Data Lake Store account.
   • FileSystem: The file systems used for this account.
   • Path: The path to store the replicated file (the root directory by default).
4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Configure the Bitbucket Connection

You can configure a connection to Bitbucket from the Connections tab. To add a connection to your Bitbucket account, navigate to the Connections tab.

1. Click Add Connection.
2. Select a source (Bitbucket).
3. Configure the connection properties.
   
   

   For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.

   Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:

   • Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
   • Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.

   Authenticating to Bitbucket

   Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.

   Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

   Creating a custom OAuth application

   From your Bitbucket account:

   1. Go to Settings (the gear icon) and select Workspace Settings.
   2. In the Apps and Features section, select OAuth Consumers.
   3. Click Add Consumer.
   4. Enter a name and description for your custom application.
   5. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
   6. If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
   7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
   8. To save the new custom application, click Save.
   9. After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.
4. Click Connect to ensure that the connection is configured properly.
5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Bitbucket data to PostgreSQL.