Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add support for preconditions

未关闭
#80 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
go, sql
领域
databases

调研方向

No files, tests, or entry points are named in the issue. Start by resolving how precondition queries should be expressed and whether a false result is a no-op or a failure; done means the agreed behavior is implemented for SQL Runner playbooks and verified for both described use cases.

由索引模型根据 Issue 内容生成。

描述

Use case 1

Imagine that:

  • You have a process landing new data in Redshift roughly every 40-60 minutes
  • You want to kick off a SQL Runner playbook as soon as the new data has arrived
  • The playbook has a non-trivial runlength whether or not there is new data
  • You want the playbook to complete as soon as possible
Use case 2

Imagine that:

  • You want to upgrade a Redshift table by adding some columns
  • You only want to perform the upgrade if the table is v0.5.0 and the table is empty
Solution

We could add a new feature to SQL Runner: playbook preconditions: for the playbook steps to be executed, all of the precondition queries must return TRUE. If any of them return FALSE, then the playbook doesn't run (a "no-op", or possibly a "failure").

Open question: whether it's a bit fiddly constructing the preconditions SQL queries to return TRUE/FALSE - it might be easier to add a syntax to compare the resultset with what's expected.

主要语言
Go
星标
81
派生
15
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

snowplow/sql-runner 的其他 Issue

查看 snowplow/sql-runner 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。