Hi Airbyte team. We recently migrated to v0.40.28 ...
# replication-troubleshooting
l
Hi Airbyte team. We recently migrated to v0.40.28 and when the sync jobs of some of our connections run, they don't save a state (even though they complete successfully). That's not good on our end and because of that, we're running full refresh every round, instead of only getting incremental updates. Any idea what might be wrong?
n
Hi! Could you please give me bit more info: 1. Airbyte version 2. Connector versions 3. Any sync logs
l
Hi. Sure. Here are the details: 1. Airbyte version: 0.40.28 2. Connector versions: intercom 0.1.24, and custom versions of amplitude and hubspot (they used to work before upgrading). 3. Any sync logs: Here are some:
We found a way to make it work. We updated our custom connector's
source
class to overwrite this
AbstractSource
method:
Copy code
@property
    def per_stream_state_enabled(self) -> bool:
        return False
l
we’ve noticed this issue in our cluster too, airbyte ver 0.40.27 the shopify connector is not saving state
n
Great to hear that you've figured it out, Luis!
l
Is it possible to configure that property via source definition? Also, could you provide details exactly on what it is used for?
l
I think the effect of this property to return False would be to yield airbyte legacy state. which is not ideal.
l
Right, but all our connection states have always been of type legacy. I'm not sure if there's any plan to automatically migrate them to something more recent
l
My understanding is that any new connectors will only support the new
STREAM
state but I’ll let the airbyte folks shed some light on this topic
thanks 1