TEPHRA-310 Add OWASP dependency check, and update the flagged direct dependencies

add check (activated with -Powasp-dependency-check)
update logback to 1.2.0
update thrift to 0.9.3-1

Closes #104
1 file changed
tree: 8a32b00d7d07713c6877f284e18cf54a8007c947
  1. bin/
  2. conf/
  3. docs/
  4. src/
  5. tephra-api/
  6. tephra-core/
  7. tephra-core-shaded/
  8. tephra-distribution/
  9. tephra-examples/
  10. tephra-hbase-compat-0.96/
  11. tephra-hbase-compat-0.98/
  12. tephra-hbase-compat-1.0/
  13. tephra-hbase-compat-1.0-cdh/
  14. tephra-hbase-compat-1.1-base/
  15. tephra-hbase-compat-1.3/
  16. tephra-hbase-compat-1.4/
  17. tephra-hbase-compat-2.0-base/
  18. tephra-hbase-compat-2.3/
  19. .gitignore
  20. .travis.yml
  21. checkstyle.xml
  22. DISCLAIMER
  23. KEYS
  24. LICENSE
  25. NOTICE
  26. pom.xml
  27. README.md
  28. suppressions.xml
README.md

What is Apache Tephra (TM)

Apache Tephra provides globally consistent transactions on top of distributed data stores such as Apache HBase. While HBase provides strong consistency with row- or region-level ACID operations, it sacrifices cross-region and cross-table consistency in favor of scalability. This trade-off requires application developers to handle the complexity of ensuring consistency when their modifications span region boundaries. By providing support for global transactions that span regions, tables, or multiple RPCs, Tephra simplifies application development on top of HBase, without a significant impact on performance or scalability for many workloads.

Tephra is used by the Apache Phoenix as well to add cross-row and cross-table transaction support with full ACID semantics.

Please refer to the Getting Started guide to start using Apache Tephra.

Building

You can build Tephra directly from the latest source code:

  git clone https://git-wip-us.apache.org/repos/asf/incubator-tephra.git
  cd incubator-tephra
  mvn clean package