[GRIFFIN-345] Support cross-version compilation for Scala and Spark dependencies

**What changes were proposed in this pull request?**

_This PR affects only the measure module._

In newer environments specially clouds, Griffin measure module may face compatibility issues due the old Scala and Spark versions. To remedy this following topics are covered in this ticket,

- Cross-compilation across scala major versions (2.11, 2.12)
- Update Spark Version (2.4+)
- Create maven profiles to build different scala and spark versions
- Changes to build strategy

This process is also done is apache spark to build for different versions of Scala and Hadoop.

**Does this PR introduce any user-facing change?**

**How was this patch tested?**
Via maven build process.

Closes #589 from chitralverma/cross-version-build.

Authored-by: chitralverma <chitralverma@gmail.com>
Signed-off-by: chitralverma <chitralverma@gmail.com>
37 files changed
tree: 61afa11b313cd867f2d2cf69c4e8b7b6e0e05526
  1. griffin-doc/
  2. measure/
  3. service/
  4. ui/
  5. .gitignore
  6. .scalafmt.conf
  7. .travis.yml
  9. KEYS
  11. merge_pr.py
  12. NOTICE
  13. pom.xml
  14. README.md
  15. scalastyle-config.xml

Apache Griffin

Build Status License: Apache 2.0

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.

Getting Started

Quick Start

You can try running Griffin in docker following the docker guide.

Environment for Dev

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.

Deployment at Local

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:


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.

  • Fork the project from github
  • Clone down your fork
  • Implement your feature or bug fix and commit changes
  • Push the branch up to your fork
  • Send a pull request to Apache Griffin master branch