You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While I was debugging the data pipeline, I noticed subscription testing was hooked up but there was no data provided. This means that the testing fixture was half-implemented. For now, I have disabled subscription as part of "reducing the scope -> getting to stable -> expanding scope".
As part of stabilizing the build and keeping it stable, we need to make sure the fixture and tests are working and covering subscription functionality as expected.
Please address subscriptions properly after getting duckdb build sorted out.
DoD:
Following along with the rest of ETL test data - Create sample data for multiple days of subscriptions..
Hook up sample data and table to fixture
Update fixture tests and verifications
Make sure that gql, etl, and other subscription tests are using fixtures
idiom-bytes
changed the title
[Lake][Test] Hookup subscription sample data into fixture + update tests
[Lake][Test] Implement subscription fixture + test data
May 23, 2024
idiom-bytes
changed the title
[Lake][Test] Implement subscription fixture + test data
[Lake][Test] Re-enable subscription table + create fixture + test data
May 28, 2024
Describe the bug
While I was debugging the data pipeline, I noticed subscription testing was hooked up but there was no data provided. This means that the testing fixture was half-implemented. For now, I have disabled subscription as part of "reducing the scope -> getting to stable -> expanding scope".
As part of stabilizing the build and keeping it stable, we need to make sure the fixture and tests are working and covering subscription functionality as expected.
Please address subscriptions properly after getting duckdb build sorted out.
DoD:
Issues referencing this one
The text was updated successfully, but these errors were encountered: