Hey all! If I have a current integration and is scheduled using Airflow (via Meltano), is it possible to adjust the endpoints being collected? Example: • I currently have a Klaviyo to Redshift integration scheduled through Airflow and running on an hourly basis • The integration is still working on a long run to extract data from the start_date I set. (Klaviyo has a ton of data so takes some time to catch up) • I want to add additional endpoints/streams to be collected without disturbing the current integration. (Let's say I'm extracting data from Clicks, Received, and Bounce endpoints. Can I add Subscribe and Unsubscribe endpoints). If this is possible, what is the best way to make these changes?

@gunnar Does the tap already support these additional streams? If so, running

meltano select tap-klaviyo subscribe

and

meltano select tap-klaviyo unsubscribe

to add the new streams to the

select

list in

meltano.yml

should have them be included in the next run. Then, these endpoints/streams will be replicated in full since there is no incremental state yet, while the other streams will pick up where they left off in the initial run that's currently running

@douwe_maan I do have to make some small adjustments to the code. The default tap doesn't have the schemas setup, but all I would need to do is copy in some .json files and adjust 1 reference in the tap-klaviyo init.py . I have already tested this out in a separate meltano project so I know it works. I just don't want to break an existing integration by making these slight adjustments while in the middle of a run.

@gunnar It shouldn't affect the current run, and I'd expect the tap to handle state from the old run correctly after the changes you're making, so that it's do a full refresh of the new streams but not the old