Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema change on bans table #21

Open
cgilj opened this issue Mar 3, 2020 · 0 comments
Open

Schema change on bans table #21

cgilj opened this issue Mar 3, 2020 · 0 comments

Comments

@cgilj
Copy link

cgilj commented Mar 3, 2020

While trying to run an extraction, the job failed in the following way

Error persisting data to Stitch: 400: {'error': 'Record 0 for table bans did not conform to schema:\n#: #: no subschema matched out of the total 2 subschemas\n#: expected: null, found: JSONObject\n#: extraneous key [created_at] is not permitted\n'}

Checking the error message and Zendesk Chat API, seems that there's a new field created_at on bans table which does not exists on the current schema.

Zendesk Chat API Docs

Screenshot from 2020-03-03 13-36-15

Current tap schema

https://github.com/singer-io/tap-zendesk-chat/blob/master/tap_zendesk_chat/schemas/bans.json

I believe we would need to add something like

"created_at": {
      "type": [
        "null",
        "string"
      ],
      "format": "date-time"
    },

Please let me know if this sounds accurate and if I can open a Pull Request myself to fix the issue. Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant