| commit | 7f718d3c2c73e4a0fd87afbea4e9165d56e4258c | [log] [tgz] |
|---|---|---|
| author | chitralverma <chitralverma@gmail.com> | Wed Dec 25 10:39:11 2019 +0800 |
| committer | wankunde <wankunde@163.com> | Wed Dec 25 10:39:11 2019 +0800 |
| tree | f8b62ff5563bb7f1d7d51ec85a488b7f99453681 | |
| parent | ed47c2b2232e07adea0a8919786ce835a15f2191 [diff] |
[GRIFFIN-312] Code Style Standardization **What changes were proposed in this pull request?** This PR targets the following, - fix the various warnings during build and in source code, - perform code formatting as per a standard style, - fix scalastyle integration Using the [code format from spark code style can be automatically imposed on measure module. Link: https://github.com/apache/spark/blob/master/dev/.scalafmt.conf Since ScalaStyle targets scala source code only, it should be a part of the measure module only. Current misconfiguration is also suppressing the formatting errors Scalafmt is used for code formatting. **Does this PR introduce any user-facing change?** No **How was this patch tested?** Griffin test suite. Author: chitralverma <chitralverma@gmail.com> Closes #560 from chitralverma/code-style-standardization.
The data quality (DQ) is a key criteria for many data consumers like IoT, machine learning etc., however, there is no standard agreement on how to determine “good” data. Apache Griffin is a model-driven data quality service platform where you can examine your data on-demand. It provides a standard process to define data quality measures, executions and reports, allowing those examinations across multiple data systems. When you don't trust your data, or concern that poorly controlled data can negatively impact critical decision, you can utilize Apache Griffin to ensure data quality.
You can try running Griffin in docker following the docker guide.
Follow Apache Griffin Development Environment Build Guide to set up development environment.
If you want to contribute codes to Griffin, please follow Apache Griffin Development Code Style Config Guide to keep consistent code style.
If you want to deploy Griffin in your local environment, please follow Apache Griffin Deployment Guide.
For more information about Griffin, please visit our website at: griffin home page.
You can contact us via email:
You can also subscribe the latest information by sending a email to subscribe dev-list and subscribe user-list. You can also subscribe the latest information by sending a email to subscribe dev-list and user-list:
dev-subscribe@griffin.apache.org users-subscribe@griffin.apache.org
You can access our issues on JIRA page
See How to Contribute for details on how to contribute code, documentation, etc.
Here's the most direct way to contribute your work merged into Apache Griffin.
