Build your first embedded data product now. Talk to our product experts for a guided demo or get your hands dirty with a free 10-day trial.
March 17, 2025
.png)
📅 Originally aired: April 2, 2025
The replay and presentation slides are available—catch up at your convenience!
Warp, our powerful data acceleration layer, syncs your dataset to our high-performance query engine. And now, we're making it even better with Delta Sync technology.
Q: The Warp Delta Sync requirement mentions using timestamp columns like "created_at", "updated_at", and "deleted_at". Are these column names mandatory, or can we use alternatives e.g. "inserted"?
A: You can use any names. What matters is that the columns are timestamps that let us determine when a row was created, updated, or deleted. If you use "inserted" instead of "created", that’s perfectly fine.
Q: Does is matter which datetime format is used?
A: The format should match other datetime columns synced to Luzmo. The format (US/EU or other) can be updated at the dataset level based on your requirements. There are no additional format specifications.
Q: I started setting up Warp Delta Sync yesterday and have noticed that datasets with over 4 million records are failing. Is this a limitation of Warp?
A: It’s not a limitation of Warp—datasets with 4 million records should work.
The first sync is always a full sync. If that initial sync failed, please reach out to our support team and we can investigate the cause.
Q: You mentioned Luzmo needs a date column to warp the dataset. Does this mean Warp won't work when using date range parameters?
A: These are actually two separate things. Warp uses timestamp columns to sync rows, but filters in your dashboards use different parameters.
If you're using other timestamp columns for filtering, it won’t affect Warp. It's perfectly fine to have separate date columns for Warp syncing and for dashboard filters—your setup can support both independently.
Q: Currently, "day" is the shortest update schedule available to me. How do I get shorter frequencies?
A: Yes, that is the default frequency for both Warp Delta and Warp Full Sync. If you need a different frequency, the best approach is to contact your Customer Success Manager or email us at cs@luzmo.com.
Q: Can we set up a webhook whenever a Delta Sync has completed?
A: We’re in the process of documenting Warp Delta Sync in our developer documentation. Once it’s published, you’ll be able to start using it. It’s coming very soon.
Q: I see that some syncs are marked as failed when there were no rows to append. Is this expected?
A: Even if there are no changes, the sync should still be marked as successful. If you see a failure in your sync history, feel free to reach out to support or let me know—we’ll investigate, as that’s not expected behavior.
If there's anything else you'd like to know, drop us an email at hello@luzmo.com.
Build your first embedded data product now. Talk to our product experts for a guided demo or get your hands dirty with a free 10-day trial.
