Describe the bug
This is basically one of the issues I called out in #1855:
When I run datasource new and exit the process at any point (e.g. ctrl+c), I still get a block for the credentials in config_variables.yml. However great_expectations.yml doesn't have the datasource entry. I would expect any kind of failure in the datasource creation process to not leave any artifacts.
WeDataSphere is a financial level one-stop open-source suitcase for big data platforms. Currently the source code of Scriptis and Linkis has already been released to the open-source community. WeDataSphere, Big Data Made Easy!
Qualitis is a one-stop data quality management platform that supports quality verification, notification, and management for various datasource. It is used to solve various data quality problems caused by data processing. https://github.com/WeBankFinTech/Qualitis
NBi is a testing framework (add-on to NUnit) for Business Intelligence and Data Access. The main goal of this framework is to let users create tests with a declarative approach based on an Xml syntax. By the means of NBi, you don't need to develop C# or Java code to specify your tests! Either, you don't need Visual Studio or Eclipse to compile your test suite. Just create an Xml file and let the framework interpret it and play your tests. The framework is designed as an add-on of NUnit but with the possibility to port it easily to other testing frameworks.
Jumbune, an open source BigData APM & Data Quality Management Platform for Data Clouds. Enterprise feature offering is available at http://jumbune.com. More details of open source offering are at,
e.g. sqlalchemy.exc.IdentifierError: Identifier 'quality_check_airport_report_next_interval_SNN_daily_unique_quality_check' exceeds maximum length of 63 characters
Describe the bug
This is basically one of the issues I called out in #1855:
When I run
datasource newand exit the process at any point (e.g. ctrl+c), I still get a block for the credentials in config_variables.yml. However great_expectations.yml doesn't have the datasource entry. I would expect any kind of failure in the datasource creation process to not leave any artifacts.**To Re