| commit | cad4530023c0c00b1311fd02a80946c16d343d73 | [log] [tgz] |
|---|---|---|
| author | Joseph Koshakow <jkosh44@users.noreply.github.com> | Mon Mar 09 18:17:52 2020 -0400 |
| committer | GitHub <noreply@github.com> | Mon Mar 09 18:17:52 2020 -0400 |
| tree | f2ccf98f079f3f2a2788400ca988590123bbe939 | |
| parent | f2cf203fb2901769c2c6035af11a4310af8ac19a [diff] |
Remove stack traces from Integration Test logs (#1091) Expected errors during integartion tests were logging large stack traces. This caused people to think there were errors in the tests when there weren't and was ugly to look at. The majority of the stack traces were coming from org.apache.fluo.core.oracle.OracleClient and org.apache.fluo.core.shaded.thrift.ProcessFunction. Setting these loggers to FATAL prevents these stack traces from being logged.
Apache Fluo is a distributed processing system that lets users make incremental updates to large data sets. With Apache Fluo, users can set up workflows that execute cross node transactions when data changes. These workflows enable users to continuously join new data into large existing data sets without reprocessing all data. Apache Fluo is built on Apache Accumulo. Check out the Fluo project website for news and general information.