Hi all, I’m running into an issue setting up a con...
# ask-community-for-troubleshooting
b
Hi all, I’m running into an issue setting up a connection using Mixpanel. While I can create a Source ok, it appears that fetching the schema causes an error, because some of the
default_cursor_field
values are unexpectedly `null`:
Copy code
2022-10-06 21:38:31 INFO i.a.v.j.JsonSchemaValidator(test):71 - JSON schema validation failed.
errors: $.catalog.streams[4].default_cursor_field: null found, array expected, $.catalog.streams[5].default_cursor_field: null found, array expected
Log4j2Appender says: JSON schema validation failed.
errors: $.catalog.streams[4].default_cursor_field: null found, array expected, $.catalog.streams[5].default_cursor_field: null found, array expected
(more info in thread)
✍️ 1
The returned schema entry in question:
Copy code
{
  "name": "engage",
  "json_schema": {
    "$schema": "<http://json-schema.org/draft-07/schema#>",
    "type": "object",
    "properties": {
        ...
    },
    "additionalProperties": false
  },
  "supported_sync_modes": [
    "full_refresh",
    "incremental"
  ],
  "source_defined_cursor": false,
  "default_cursor_field": null,
  "source_defined_primary_key": [
    [
      "distinct_id"
    ]
  ]
}
I initially set up using the “Project Secret” option, switching to a Service Account didn’t fix unfortunately
I’m using connector version
0.1.27
, will try downgrading to
0.1.25
since this looks like it might be related:
0.1.26 2022-09-28 17304 Migrate to per-stream states.
Looks like
0.1.25
ends up hitting the same issue
Seems like the two fields which don’t have cursors are
engage
and
cohort_members
u
@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2632 to ensure timely resolution!
m
b
great, thank you!
@Marcos Marx (Airbyte) For what it’s worth, it looks like
cohort_members
might also. have a
null
cursor field
Copy code
{
    "name": "cohort_members",
    "json_schema": {
        "$schema": "<http://json-schema.org/draft-07/schema#>",
        "type": "object",
        "properties": {
    ...
        },
        "additionalProperties": false
    },
    "supported_sync_modes": [
        "full_refresh",
        "incremental"
    ],
    "source_defined_cursor": false,
    "default_cursor_field": null,
    "source_defined_primary_key": [
        [
        "distinct_id"
        ]
    ]
}
The new connector version has fixed this issue for me. Thanks for the fast fix!