Nebyou

5 ms·

1.
by Nebyou 3y ago
Definitely high up on the priority list! We've actually been experimenting with this internally.
2.
by Nebyou 3y ago
This is not a simply a hosted airbyte instance. We use airbyte's connectors for its common standards and the active community behind them. That being said, our use of the project is both limited, customized, and deeply embedded under o
3.
by Nebyou 3y ago
Thanks for raising this. We share your respect for the intellectual property rights of others. We are aware of Airbyte's license structure and use connectors per its terms.
4.
by Nebyou 3y ago
We've observed that our system performs really well handling most corner cases as long as the context required can be interpolated from its inputs (either in the schemas and their descriptions or in the underlying data we sample from).
5.
by Nebyou 3y ago
Apologies, I misread your earlier question. Lume can only ascertain information from what is given directly or from what assumptions it can make with reasonable confidence. So, in this case, this will not be possible unless there is any inf
6.
by Nebyou 3y ago
This example is a full refresh, but incremental is usually the norm, especially for our supported connectors and continuous syncs. Our models can detect incremental columns. Audit timestamps (usually tables) are typically created in interme
7.
by Nebyou 3y ago
It's true that our platform can be used for the same use cases as some of those products. However, the main difference is in the customizability we offer. These products focus on and support the most common integrations and offer them
8.
by Nebyou 3y ago
Our transformations are executed in a staging database/schema before deployment. We also have versioning and backtesting capabilities. In addition, you will have complete visibility of the code we produce before and after deployment.