Skip to content
This repository was archived by the owner on Jan 20, 2026. It is now read-only.

Commit 219493b

Browse files
actor_id issue polishing
1 parent a82a55e commit 219493b

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
# dbt_zendesk_source v0.16.0 or v0.16.0-a2
2-
- Handle `actor_id` in `ticket_chat_event` sometimes having inconsistent formatting - either just the ID or `agent:#######`.
1+
# dbt_zendesk_source v0.16.0-a2
2+
- Handles `actor_id` in `ticket_chat_event` having inconsistent formatting, so that we can safely cast it as a bigint. Typically, `actor_id` just contains the ID, but it may also look like `agent:<#######>`. ([PR #63](https://github.com/fivetran/dbt_zendesk_source/pull/63))
33

44
# dbt_zendesk_source v0.16.0-a1
55

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Include the following zendesk_source package version in your `packages.yml` file
4545
```yaml
4646
packages:
4747
- package: fivetran/zendesk_source
48-
version: 0.16.0-a1
48+
version: 0.16.0-a2
4949
```
5050
### Step 3: Define database and schema variables
5151
#### Option A: Single connection

docs/catalog.json

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

docs/manifest.json

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)