Flowman follows the "Everything-is-Code" approach. Therefore the development of all data flows takes place in a text editor of your choice. Since all Flowman entities like relations, mappings, targets and jobs are specified as simple declarative YAML files, any editor which supports YAML will work fine.
The execution of the Flowman project is performed with a powerful command line tools. These can be directly installed on your Linux machine and other OSes are well supported with pre-built Docker images.
In addition to the main tool for batch execution, Flowman also provides an interactive shell for development purpose which allows inspection of all entities and intermediate results.
All that Flowman needs are the YAML files of your project. This supports a simple deployment process to different staging environments (dev, test, prod) by transfering the project files to the corresponding systems.
By using environment and/or profiles, you can easily provide the details of each environment like dataabse server names etc.
Test and document your project and your data by annotating mappings or relations with descriptions and with quality checks. Both can be done either on the entity level (mapping or relation) or even on the column level.
Flowman then easily generates a full blown documentation of your project, that will not only include your description, but also the results of all specified test cases. This minimizes friction between your assumption on the data and the reality.
Flowman follows the "Everything-is-Code" approach. Therefore the development of all data flows takes place in a text editor of your choice. Since all Flowman entities like relations, mappings, targets and jobs are specified as simple declarative YAML files, any editor which supports YAML will work fine.
Flowman follows the "Everything-is-Code" approach. Therefore the development of all data flows takes place in a text editor of your choice. Since all Flowman entities like relations, mappings, targets and jobs are specified as simple declarative YAML files, any editor which supports YAML will work fine.
The execution of the Flowman project is performed with a powerful command line tools. These can be directly installed on your Linux machine and other OSes are well supported with pre-built Docker images.
In addition to the main tool for batch execution, Flowman also provides an interactive shell for development purpose which allows inspection of all entities and intermediate results.
All that Flowman needs are the YAML files of your project. This supports a simple deployment process to different staging environments (dev, test, prod) by transfering the project files to the corresponding systems.
By using environment and/or profiles, you can easily provide the details of each environment like dataabse server names etc.
Test and document your project and your data by annotating mappings or relations with descriptions and with quality checks. Both can be done either on the entity level (mapping or relation) or even on the column level.
Flowman then easily generates a full blown documentation of your project, that will not only include your description, but also the results of all specified test cases. This minimizes friction between your assumption on the data and the reality.
Flowman follows the "Everything-is-Code" approach. Therefore the development of all data flows takes place in a text editor of your choice. Since all Flowman entities like relations, mappings, targets and jobs are specified as simple declarative YAML files, any editor which supports YAML will work fine.
© dimajix - Dr. Kaya Kupferschmidt | Freiherr-vom-Stein Straße 3, 60323 Frankfurt, Germany | +49 69 71588909 | info@dimajix.de | www.dimajix.de
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |