Summary
User encounters an issue where subsequent full refresh syncs return zero records after an initial successful sync following a Jira source upgrade. The user suspects a version mismatch between the connector and the Airbyte platform.
Question
Hey all, we recently upgraded our jira source from 1.x (can’t recall, but maybe <http://1.2.to|1.2.2) to> 3.3.0-rc.3. We’re running airbyte-platform with a helm chart version of 0.49.20 (airbyte version 0.50.33). It seems like a number of streams with a sync mode of full refresh return zero records after an initial sync (after a reset) that returns all of the records correctly. My first thought is that there’s a version mismatch between platform and this connector, but how can I determine if that’s the case? It seems strange to me that a full refresh sync would differ between the initial sync and subsequent syncs, so I’m guessing it has something to do with that. Admittedly, our airbyte platform version is far behind the latest, but I want to avoid doing a shotgun upgrade and potentially revert the jira source for the short term to minimize the fallout. I attached an example of syncs to show what I mean. In this case, all streams are set to do a full refresh so returning zero records results in an empty result set for the destination.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.