For those that have used Airbyte for some time, ho...
# replication-troubleshooting
j
For those that have used Airbyte for some time, how happy are you with the ‘non-happy path’ experience? By that I mean when you have to troubleshoot things, having to reset syncs or backfill, etc. I’m concerned by what appears to be a ‘start it and it’s always perfect’ interface. Inside a source with multiple streams, I don’t see any methods to: • Reset a single stream • For incremental streams backfill from YYYY-MM-DD to current or restart from a specific id • see ingest metrics, write to the airbyte filesystem, write to destination metrics. Bottleneck identification in non-error scenario details • Any way to handle a non conforming piece of data. Like if a source returned garbage in an API call that didn’t map correctly a way to define how to handle or manually handle that resource
a
Hi Jon-- these are all great points of feedback. Specifically, resetting a single stream is something we're actively working on. Would you be open to providing feedback on some designs when we get further along in the approach? The other topics you mention are also great points of feedback and I'll route them to the appropriate teams.
j
Yeah I’d be happy to take a look
m
@[DEPRECATED] Marcos Marx Reset a single stream, is this feature already available? Or is there any work around without having to reset stream for all tables in a connection?