Custom connector not working anymore after updating Airbyte version

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Debian
  • Memory / Disk: 32GB memory / 50GB disk
  • Deployment: docker-compose
  • Airbyte Version: 0.40.26
  • Source name/version: elastic-search custom connector
  • Destination name/version: bigquery
  • Step: schema discovery in webapp
  • Description:

I developped a custom source connector for Elastic Search using the Python CDK for version 0.39.42 because the standard one was not fit for my use case (needed to do incremental updates).
I created a static schema file located in the file catalog/configured_catalog.json that looks like this :

{
  "streams": [
    {
      "stream": {
        "name": "my_stream",
        "json_schema": {},
        "supported_sync_modes": [
          "full_refresh",
          "incremental"
        ],
        "source_defined_cursor": "True",
        "default_cursor_field": [
          "date"
        ]
      },
      "sync_mode": "incremental",
      "destination_sync_mode": "overwrite"
    }
]

I deployed it on Airbyte version 0.39.42 and it was working fine.
Now, we updated our Airbyte version to 0.40.26 and the connector is not working fine anymore.
The problem is located at the schema discovery step. When I go to “replication” to see my schema :

image
image1340×512 42.9 KB

I get this error message :

image
image2448×1096 268 KB

There is no error log on server side. The only error log I get is on the browser side which says (as on the screenshot) :

TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at or (CatalogSection.tsx:101:41)
    at sa (react-dom.production.min.js:157:137)
    at qa (react-dom.production.min.js:180:154)
    at Ba (react-dom.production.min.js:178:169)
    at ja (react-dom.production.min.js:177:178)
    at Gs (react-dom.production.min.js:274:126)
    at Au (react-dom.production.min.js:250:347)
    at Ou (react-dom.production.min.js:250:278)
    at Cu (react-dom.production.min.js:250:138)
ls @ react-dom.production.min.js:216
n.payload @ react-dom.production.min.js:217
ho @ react-dom.production.min.js:130
Wa @ react-dom.production.min.js:184
Gs @ react-dom.production.min.js:269
Au @ react-dom.production.min.js:250
Ou @ react-dom.production.min.js:250
Cu @ react-dom.production.min.js:250
_u @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
t.unstable_runWithPriority @ scheduler.production.min.js:18
Vi @ react-dom.production.min.js:122
Ki @ react-dom.production.min.js:123
M @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12

The local tests (check, spec, discover, read) work fine.

Is there a thing I need to modify/update in the connector Python code to get it to work with version 0.40.26 ? I am sure it is an issue with the version since it is working fine on 0.39.42. Thanks,

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Sorry I missed this topic Nahid, are you still having issues?