This issue was previously titled "Other caches besides DuckDB are incorrectly showing 0 record counts" - but it appears that was a user error on my side. I was not aware that source-faker supported incremental sync, and it was actually generating 0 records when I re-loaded to the same cache as I had loaded to previously.
This is a relatively small bug, which sprung up after our major refactor. See the PR for more info:
This issue was previously titled "Other caches besides DuckDB are incorrectly showing
0record counts" - but it appears that was a user error on my side. I was not aware thatsource-fakersupported incremental sync, and it was actually generating 0 records when I re-loaded to the same cache as I had loaded to previously.