Ingesting Nulab Backlog Data Into Snowflake Tables: Part I

This tutorial has four parts in total:

I wanted to backup Backlog data onto Snowflake tables. But there was not easy backup options, so I created one and wanted to share it with you.

In this tutorial we will extract data from Backlog and ingest it into Snowflake tables using Snowflake Stored Procedures.

Backlog:: a project management software developed by a Japanese company Nulab, Inc.
Snowflake:: a data storage platform.

Existing Options

It is almost always good idea to use existing tools and solutions. In other words, there is no need to reinvent the wheel. So, before trying to implement my custom solution, I wanted to explore the landscape in search of existing solutions.

Backlog only offers REST API and Web Hook endpoints, no integration or other features. As for Snowflake, although it offers variety of connection options: Snowflake OpenFlow, Snowflake connectors, Snowflake Ecosystem All, Snowflake Ecosystem ETL, unfortunately as of January 2026, there is no native Backlog connector.

There are no first-party (native) connection options, how about third-party options?
I could find some paid third-party solutions such as cdata and workato, but couldn’t find any open-source tools.

If there is no existing open-source solution available, we can build our custom solution.

Note:
There is an awesome ETL & ELT tool called Airbyte. Although it doesn’t have a Backlog connecter, building Airbyte connectors is very easy. A challenging part is deploying Airbyte requires kubernetes cluster.

Custom Solution

There are many ways to create our custom solution. The best approach is context dependent. Your requirements might be different from mine. I will introduce some of the available options, based on your own needs/requirements, you can implement one. Below I will list the interfaces provided by Snowflake and Backlog and their capabilities.

Backlog

Backlog exposes both REST API and Web hook endpoints.

If you want to get notified as soon as some actions happen in Backlog, You should use Web hooks. In my case, however I just want to backup Backlog data to a Snowflake table. Using Backlog Rest API and calling it a few times a day suffices my requirements.

Snowflake

REST API

Although Snowflake has REST API, it does not support inserting data into tables.

Native Programmatic Interfaces

Native Programmatic Interfaces are programming language specific SDKs (Software development Kit libraries) to connect to Snowflake. Nodejs, SQLAlchemy, and Python sdks are some of the available Native Programmatic Interfaces. Check out API Reference for details.

Native Programmatic Interfaces fit the bigger, more complex applications better. As an example, let’s assume we are building a python web application that has many features and functionalities. The Application takes inputs from users, perform certain calculations, communicates with other servers etc.

At some point the application needs to get data from or record data onto Snowflake tables. For this task, we can use Snowflake Native Programmatic Interface such as Python SDK. Application connects to Snowflake using snowflake provided python library to authenticate, and execute necessary queries.

In my case, I only need to record fetched data onto a Snowflake table. No other functionality is needed. Native Programmatic Interfaces are overkill for such a simple requirement.

Stored procedures

Snowflake Stored Procedures are custom procedures created by users. Stored procedures are similar to functions (with some differences). Stored procedures can be written in SQL, Java, JavaScript, Python or Scala. Stored procedures are run within Snowflake (controlled cloud environment).

Snowflake has User-defined functions as well. User defined functions are similar to stored procedures but not the same. User defined functions should be deterministic, and always return a value. While, Stored Procedures don’t have to return a value, and they are most commonly used for administrative tasks such as DDL and DML.

I will talk about Stored Procedures more in the second part of these series.

What to Use and Where To Run

We have a few options to create our custom solutions. Based on which mix of the options we use, we can run our custom solution in cloud providers such as AWS, GitHub, or within Snowflake.

Option 1: [Backlog webhook + Snowflake Native Programmatic Interfaces] runs on AWS lambda functions.
Whenever new event occurs in the Backlog, Backlog webhook calls lambda function, lambda function records data on Snowflake table immediately using Native Programmatic Interfaces.

Option 2: [Backlog REST API + Snowflake Native Programmatic Interfaces] runs on GitHub Actions.
A script executed by GitHub Actions calls Backlog Rest API periodically (e.g. every two hours), and records all the events of Backlog that happened since its last run onto Snowflake using Native Programmatic Interfaces.

Option 3: [Snowflake Stored Procedures + Backlog REST API] runs on Snowflake.
Snowflake Tasks executes Snowflake Stored Procedure periodically. Stored Procedure calls Backlog REST API and records the fetched data onto Snowflake table.

Choose option No 2, if you prioritize easy version controlling, deployment, code review and modifications to code. Choose Snowflake Stored Procedures option if you want to confine and control code, roles, permissions and secrets in one place.

Note: If you choose Snowflake Stored Procedures option, there will be a friction in code deployment and updates.

In this tutorial, we will go with Snowflake Stored Procedures option. For implementation details, proceed to the part two.

Comments

Introduction to SQLFluff: How to make your SQL code clean and error-free

Image by Jake Aldridge from Pixabay You know oftentimes, the cause of runtime or compile errors and hours of debugging agony is all due to simply a missing semicolon. Have you ever had such experience? If you had, you are not alone. There are two ways to avoid these unfortunate situations: either become a perfect developer who never makes mistakes, or use helpful tools such as linters that can catch these errors early on. I am nowhere near being a perfect developer who never makes a mistake. In fact, I'm probably the opposite of a perfect developer, so even if I wanted to, I wouldn’t be able to teach you how to become a perfect developer. But what I can teach you is using linters. A Wikipedia defines a linter as a "static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs." If you're not convinced yet on using linters, consider this scenario: in a large project with multiple members, different people tend to ...

How To Use KeePassXC Cli

There are similarly named programs: KeePass, KeePassX and KeePassXC (many of which are each others’ forks). Program Condition KeePass primarily for Windows. KeePassX no longer actively maintained. KeePassXC actively maintained and runs natively on Linux, macOS and Windows . Note: GUI version of the KeePassXC has more features than cli version. GUI version has variety of shortcuts as well. Regarding how to use GUI version of the KeePassXC, visit Getting Started Guide . Below features are available only in GUI version. Setting “Name” and “Description” fields of passwords database. Nesting Groups. Creating entry attributes ( open issue ). Adding Timed One-Time Passwords (TOTP). Adding entry with the same title as existing entry. KeePassXC stores all the passwords in passwords database. A passwords database (hereafter referred to as database) is an (encrypted) binary file. It can have any or no extension, but the .kdbx extension is commonly used. The ...

Git squash merge explained

There are many ways to integrate changes in git: regular / normal git merge, git squash merge, git rebase etc. This article explains git squash merge by comparing it to regular merge. Let’s use below example: In the repository with default main branch, after two commits, a new feature branch is created. Some work happened in feature branch. feature branch now has 2 commits that it shares with main branch, and three exclusive commits (exists only in feature branch). In the meantime, others worked on main branch and added two new commits (exists only in main branch). git log output of the main branch: c72d4a9 ( HEAD - > main ) fourth commit on main 2c3dd61 third commit on main 0c2eec3 second commit on main 9b968e8 first commit on main git log output of the feature branch: 786650f ( HEAD - > feature ) third commit on feature 21cbaf1 second commit on feature 677bc7f first commit on feature 0c2eec3 second commit on main 9b968e8 first commit on mai...

例を使ってSnowflakeストアドプロシージャを学びましょう

Image by Gerd Altmann from Pixabay データベースの操作において、反復的なタスクや複雑なロジックの実行は、時間と労力を要する作業になりがちです。Snowflakeストアドプロシージャは、こうした課題を解決するための強力な機能であり、SQLクエリを拡張して、より効率的かつ安全なデータ処理を実現します。本稿では、Snowflakeストアドプロシージャの基本的な概念から、JavaScript、Python、そしてSnowflake Scripting (SQL)といった複数のプログラミング言語を使った作成方法、さらにはセキュリティ対策まで、実践的な知識を提供します。小売業におけるキャンペーン管理を例に、県名に応じてキャンペーン情報と割引率を一括更新するストアドプロシージャを実装します。ストアドプロシージャと言うのはストアドプロシージャを関数の一つ種類と考えてもいいです。ストアドプロシージャを記述して、 SQL を実行する手続き型コードでシステムを拡張できます。ストアドプロシージャを作成すると、何度でも再利用できます。値を明示的に返すことが許可されていますが、必須ではないです。ストアドプロシージャを実行するロールの権限だけではなく、プロシージャを所有するロールの権限でも実行出来ます。サポートされている言語: Java JavaScript Python Scala Snowflake Scripting (SQL) ストアドプロシージャの形： CREATE OR REPLACE PROCEDURE プロシージャ名(arguments argumentsのタイプ) RETURNS レターんタイプ LANGUAGE 言語 -- (例:python, JavaScript等) -- RUNTIME_VERSION = '3.8' (言語がpython, java, scalaなら必要 ) -- PACKAGES = ('snowflake-snowpark-python') (言語がpython, java, scalaなら必要 ) -- HANDLER = 'run' (言語がpython, java, scalaなら必要 ) EXECUTE AS ...

Snowflake Load History vs Copy History: 7 differences

Image by Icons8_team from Pixabay Tracking data loads in Snowflake is crucial to maintaining data health and performance. Load History and Copy History are features that provide valuable information about past data loads. Understanding these features can help you efficiently troubleshoot, audit, and analyze performance. You might be wondering why two functions exist to achieve the same goal, what are the differences, which one I am supposed to use and when? In this article we will provide you with all the answers. So, let's learn what are the differences and when to use which! Load History vs Copy History: 7 differences Differences 1 and 2: views vs table function and Account Usage vs information Schema Here things get little confusing, bare with me, there are two Load History views, a view that belongs to Information Schema and a view that belongs to Account Usage schema . As for Copy History, there are Copy History table function of Information schema and a Copy H...

WinMerge のセットアップと使う方

WinMerge は、Windows 用のオープンソースの差分およびマージツールです。WinMerge は、フォルダーとファイルの両方を比較し、違いを理解して扱いやすい視覚的なテキスト形式で表示します。この記事でWinMerge のセットアップと使う方を教えます。 source: https://winmerge.org WinMerge をダウンロード WinMerge のウェブサイトに行って、「WinMerge-2.16.44-x64-Setup.exe」ボタンを押し、WinMerge 2.16 をダウンロードしてください。 WinMerge をインストールダウンロードされたソフトウェアをクリックし、ポップアップ画面で「Next」を押してください「Languages」部分をスクロールダウンし、「Japanese menus and dialogs」を選択し、「Next」ボタンを押してくださいターミナル等からも WinMerge をアクセス出来ようにする為に「Add WinMerge folder to your system path」オプションを選択し、希望によって他のオプション選択してください「Enable Explorer context menu Integration」オプションを選択したら、フォルダ／ファイルを右キリックし、コンテクストメニューから WinMerge を開くようになります。「Install」ボタンを押し、「Next」ボタンを押し、その後、「Finish」ボタンを押してください言語を日本語にするもし WinMerge の言語が日本語じゃなくて、英語なら、「Edit」タブから「Options」を押してください。ポップアップ画面で右側の下にある「Languages」と言うドロップダウンメニューから日本語を選択し、「OK」ボタンを押してください WinMerge を使う方「ファイル」タッブから「開く」を押し参照ボタンを押し、比較したいフォルダ・ファイルを指定比較したいフォルダを指定する方法: ポップアップ画面から対象のフォルダーを選択し、「Open」を押してくだい何も選択しないで、「Open」を押してくだい右側下にある「比較」ボタンを押し ...

From Generic to Genius: Fine-tuning LLMs for Superior Accuracy in Snowflake

TL;DR: Cortex Fine-tuning is a fully managed service that lets you fine-tune popular LLMs using your data, all within Snowflake. While large language models (LLMs) are revolutionizing various fields, their "out-of-the-box" capabilities might not always align perfectly with your specific needs. This is where the power of fine-tuning comes into play. As it will be explained in this article, this feature empowers you to take a base LLM and customize it to excel in your particular domain. Here's the brief summary of why you might want to leverage Snowflake's fine-tuning capabilities: Unlocking Domain Expertise : Pre-trained LLMs are trained on massive, general datasets. Fine-tuning allows you to build upon this foundation and train the LLM further using data specific to your field, such as legal documents, medical records, or financial data. This empowers the LLM to understand complex terminology and patterns unique to your domain, leading to more accurate a...

脱初心者！ Git ワークフローを理解して開発効率アップ

Git – チーム開発に必須のバージョン管理システムですが、その真価を発揮するにはワークフローの理解が欠かせません。色々な人は Git の使い方を良く知っていますが、Git を仕事やワークフローに統合する方法を余り良く知らない人もいます。本記事では、Git をワークフローに組み込むことで、開発プロセスがどのように効率化され、チーム全体のパフォーマンスが向上するのかを解説します。Centralized Workflow から Forking Workflow まで、代表的な 9 つのワークフローの特徴を分かりやすく紹介します。それぞれのメリット・デメリット、そして最適なユースケースを理解することで、あなたのプロジェクトに最適なワークフローを選択し、開発をスムーズに進めましょう！ Centralized Workflow Feature branching/GitHub Flow Trunk Based Flow Git Feature Flow Git Flow Enhanced Git Flow One Flow GitLab Flow Forking Workflow 分かりやすくするために、同じコンセプトを説明するに一つ以上の図を使った場合があります。 Centralized Workflow 説明：集中化ワークフローではプロジェクトにおけるすべての変更の単一の入力箇所として中央リポジトリを使用します。デフォルトの開発用ブランチは main と呼ばれ、すべての変更がこのブランチにコミットされます。集中化ワークフローでは main 以外のブランチは不要です。チームメンバー全員がひとつのブランチで作業し、変更を直接中央リポジトリにプッシュします。メリット： SVN のような集中型バージョン管理システムから移行する小規模チームに最適。デメリット：お互いのコードが邪魔になり (お互いの変更を上書きするように)、プロダクション環境にバグをい入れる可能性が高くて、複数のメンバいるチームでこのフローを使いにくい。地図： graph TD; A[Central Repository] -->|Clone| B1[Developer A's Local Repo] A --...

Streamline Your Workflow: Send Snowflake Alerts to Slack

Do you know integrating Snowflake and Slack can make your life as a data engineer much easier? Here's why: Real-time error catching and debugging : Instead of constantly checking logs for errors, you can set up Snowflake to automatically ping you in a Slack channel when something goes wrong. This is like having a dedicated assistant who watches for errors in your code and immediately lets you know so you can fix them faster. This is achieved through the use of webhooks, which are essentially automated HTTP requests that Snowflake sends to Slack when triggered by an event. Keep everyone in the loop : Slack integration also means you can keep your entire team informed about the status of data pipelines and other processes. You can configure Snowflake to send notifications to a shared channel whenever a pipeline completes, fails, or encounters an issue. This keeps everyone on the same page and avoids unnecessary status update meetings. This integration turns Slack ...

SQLFluff入門：SQLコードをクリーンかつエラーフリーに

コードを書いた後に実行したとき、エラーが発生するとイライラします。さらに厄介なのは、そのエラーの原因が分からないときです。また、複数のメンバーがいる大規模なプロジェクトでは、メンバーごとにコードの書き方が異なる傾向があり、その結果、コードレビューが難しくなり、ソースコードに不整合が生じます。コードを実行する前にエラーを検出できた方が良いと思いませんか？さらに、チームメンバー全員が同じフォーマットでコードを書けば、もっと効率的になるでしょう。 SQLFluffと言うツールがこの全ての事を実現させます。 SQLFluffは何でしょう？ SQLFluffは、SQLファイル用の最も人気のあるリンターです。構文エラーを検出すると、そのエラーが発生した行番号や位置、エラーの原因が表示されます。SQLFluffはエラーの検出だけでなく、SQLコードのフォーマットや構文エラーの修正も可能です。PostgreSQL、MySQL、Google BigQuery、Snowflakeなど、複数の SQL 言語をサポートしています。つまり、SQLコードを実行する前に構文エラーを検出・修正できるので、非常に役立ち、重要な作業に集中することができます。また、SQLFluffは非常に設定が簡単で、コンマの位置、文字の大文字小文字、インデントなどのルールを簡単に設定できます。エンジニアは自分のパソコンにSQLFluffをインストールし、SQLFluffを利用してコードのエラーを検出・修正した後にGitにコミットし、GitLabやGitHubなどにプッシュすることをお勧めします。全てのドキュメントはこちらにあります : Docs 。インストール SQLFluff は以下のようにインストールできます VSCode エクステンションプリコミットフックコマンドラインツール CI/CDパイプラインツール SQLFluffをコマンドラインツールとして設定し、実行してくださいのが一番簡単です。また、この記事でプレコミットフックとしての使い方も説明します。 SQLFluffをコマンドラインツールとしてインストール注意点： SQLFluffをインストールするにはPythonとpip (またはpoetryやpipenvなどのパッケージマネージャ)が必要です。この...

Cherry Peeked

Search This Blog