Is this your first time deploying Airbyte?: Yes
OS Version / Instance: EC2 t2.large
Deployment: Docker
Airbyte Version: 0.36.4 alpha
Source name/version: Zendesk Support
Destination name/version: Redshift
Step: sync (full-refresh overwrite, incremental)
Description:
I had a similar issue and it was solved by the PR. Thank you @alafanechere !
When I sync ticket_metrics
I can only fetch a subset of all the data and I am missing lots of rows even though my set up is as below:
What I noticed is that there is no tickets which were closed in 2021 and earlier, also updated_at
is mostly 2022-MM-DD
This is the view I have in Zendesk for 2021
logs-853.txt (33.3 KB)
Hi @jablonskijakub , adding some additional context for airbyte team when they look into this.
I recently created a fix for the user
stream, but i imagine the ticket_metric
stream suffers the same issue. Linking the PR as the description there links a few zendesk support issues:
airbytehq:master
← danieldiamond:danieldiamond/fix-zendesk-support-user-limit
opened 02:51AM - 19 Apr 22 UTC
## What
Fix https://github.com/airbytehq/airbyte/issues/11895
Fix https://gith… ub.com/airbytehq/airbyte/issues/12059
Fix https://github.com/airbytehq/airbyte/issues/11899 (for user stream only!)
Fix https://github.com/airbytehq/airbyte/issues/12060 (TBC)
## How
Add `SourceZendeskUserExportStream` similar to ticket and ticket comment streams
## Recommended reading order
1. `x.java`
2. `y.python`
## 🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
## Pre-merge Checklist
Expand the relevant checklist and delete the others.
<details><summary><strong>New Connector</strong></summary>
### Community member or Airbyter
- [ ] **Community member?** Grant edit access to maintainers ([instructions](https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork#enabling-repository-maintainer-permissions-on-existing-pull-requests))
- [ ] Secrets in the connector's spec are annotated with `airbyte_secret`
- [ ] Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run `./gradlew :airbyte-integrations:connectors:<name>:integrationTest`.
- [ ] Code reviews completed
- [ ] Documentation updated
- [ ] Connector's `README.md`
- [ ] Connector's `bootstrap.md`. See [description and examples](https://docs.google.com/document/d/1ypdgmwmEHWv-TrO4_YOQ7pAJGVrMp5BOkEVh831N260/edit?usp=sharing)
- [ ] `docs/SUMMARY.md`
- [ ] `docs/integrations/<source or destination>/<name>.md` including changelog. See changelog [example](https://docs.airbyte.io/integrations/sources/stripe#changelog)
- [ ] `docs/integrations/README.md`
- [ ] `airbyte-integrations/builds.md`
- [ ] PR name follows [PR naming conventions](https://docs.airbyte.io/contributing-to-airbyte/updating-documentation#issues-and-pull-requests)
### Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
- [ ] Create a non-forked branch based on this PR and test the below items on it
- [ ] Build is successful
- [ ] If new credentials are required for use in CI, add them to GSM. [Instructions](https://docs.airbyte.io/connector-development#using-credentials-in-ci).
- [ ] [`/test connector=connectors/<name>` command](https://docs.airbyte.io/connector-development#updating-an-existing-connector) is passing
- [ ] New Connector version released on Dockerhub by running the `/publish` command described [here](https://docs.airbyte.io/connector-development#updating-an-existing-connector)
- [ ] After the connector is published, connector added to connector index as described [here](https://docs.airbyte.io/connector-development#publishing-a-connector)
- [ ] Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described [here](https://docs.airbyte.io/connector-development#publishing-a-connector)
</details>
<details><summary><strong>Updating a connector</strong></summary>
### Community member or Airbyter
- [x] Grant edit access to maintainers ([instructions](https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork#enabling-repository-maintainer-permissions-on-existing-pull-requests))
- [x] Secrets in the connector's spec are annotated with `airbyte_secret`
- [ ] Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run `./gradlew :airbyte-integrations:connectors:<name>:integrationTest`.
- [ ] Code reviews completed
- [ ] Documentation updated
- [x] Connector's `README.md`
- [ ] Connector's `bootstrap.md`. See [description and examples](https://docs.google.com/document/d/1ypdgmwmEHWv-TrO4_YOQ7pAJGVrMp5BOkEVh831N260/edit?usp=sharing)
- [x] Changelog updated in `docs/integrations/<source or destination>/<name>.md` including changelog. See changelog [example](https://docs.airbyte.io/integrations/sources/stripe#changelog)
- [x] PR name follows [PR naming conventions](https://docs.airbyte.io/contributing-to-airbyte/updating-documentation#issues-and-pull-requests)
### Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
- [ ] Create a non-forked branch based on this PR and test the below items on it
- [ ] Build is successful
- [ ] If new credentials are required for use in CI, add them to GSM. [Instructions](https://docs.airbyte.io/connector-development#using-credentials-in-ci).
- [ ] [`/test connector=connectors/<name>` command](https://docs.airbyte.io/connector-development#updating-an-existing-connector) is passing
- [ ] New Connector version released on Dockerhub and connector version bumped by running the `/publish` command described [here](https://docs.airbyte.io/connector-development#updating-an-existing-connector)
</details>
<details><summary><strong>Connector Generator</strong></summary>
- [ ] Issue acceptance criteria met
- [ ] PR name follows [PR naming conventions](https://docs.airbyte.io/contributing-to-airbyte/updating-documentation#issues-and-pull-requests)
- [ ] If adding a new generator, add it to the [list of scaffold modules being tested](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connector-templates/generator/build.gradle#L41)
- [ ] The generator test modules (all connectors with `-scaffold` in their name) have been updated with the latest scaffold by running `./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates` then checking in your changes
- [ ] Documentation which references the generator is updated as needed
</details>
## Tests
<details><summary><strong>Unit</strong></summary>
*Put your unit tests output here.*
</details>
<details><summary><strong>Integration</strong></summary>
*Put your integration tests output here.*
</details>
<details><summary><strong>Acceptance</strong></summary>
*Put your acceptance tests output here.*
</details>
1 Like
Hey could you create a github issue around this and link it here?
Thanks @danieldiamond a lot!
@harshith here’s the created GitHub issue
opened 07:16AM - 21 Jun 22 UTC
type/bug
community
needs-triage
team/use
autoteam
## Environment
- **Airbyte version**: 0.36.4 alpha
- **OS Version / Instance*… *: AWS EC2
- **Deployment**: Docker
- **Source Connector and version**: Zendesk Support 0.2.10
- **Destination Connector and version**: Postgres via S3
- **Step where error happened**: Sync job
## Current Behavior
When I sync `ticket_metrics` I can only fetch a subset of all the data and I am missing lots of rows even though my set up is as below:
<img width="727" alt="image" src="https://user-images.githubusercontent.com/88671308/174739486-8a92b809-500b-435e-be36-3f329e567ca3.png">
What I noticed is that there is no tickets which were closed in 2021 and earlier, also `updated_at` is mostly 2022-MM-DD
<img width="392" alt="image" src="https://user-images.githubusercontent.com/88671308/174739555-55c797dc-4803-42ad-b6a1-3ff96067d7a6.png">
This is the view I have in Zendesk for 2021
<img width="674" alt="image" src="https://user-images.githubusercontent.com/88671308/174739608-14fe52a5-67ed-4e3c-983f-a1ffbbc3fcce.png">
## Expected Behaviour
It is possible to sync all `ticket_metrics`
##Logs
[logs-853.txt](https://github.com/airbytehq/airbyte/files/8946640/logs-853.txt)
## Are you willing to submit a PR?
No
Got it thanks. We can continue discussion over the issue
1 Like
Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.