PARQUET-2419: Reduce noisy logging when running test suite

[amousavigourabi]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Parquet Jira issues and references
  them in the PR title. For example, "PARQUET-1234: My Parquet PR"
  • https://issues.apache.org/jira/browse/PARQUET-2419
  • In case you are adding a dependency, check if the license complies with
    the ASF 3rd Party License Policy.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:
• Only introduces changes to CI/CD workflows

Commits

• My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines
  from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Style

• My contribution adheres to the code style guidelines and Spotless passes.
  • To apply the necessary changes, run mvn spotless:apply -Pvector-plugins

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain Javadoc that explain what it does

[wgtmac]

Why enable it by default? BTW, do the surefire.xx arguments actually work locally?

[amousavigourabi]

Generally, when you run mvn test you do not need the immense amount of low level logs provided now. It makes more sense for them to be opt-in. As for the other question, luckily these settings do work locally.

[wgtmac]

cc @Fokko

[wgtmac]

What about keeping the ci-test profile to be verbose as is, and add a new compact one which is activated by default?

[amousavigourabi]

As of now our output is verbose by default, with the ci-test profile being more compact. I tried looking into enabling ci-test by default, but when a profile is activeByDefault, it gets deactivated whenever another profile becomes active. The problem then is that parquet-mr has a few profiles that get activated automatically depending on the environment Maven is run in, so we cannot rely on it in that way. Because of this, the PR gets rid of the slimmed down ci-test profile and replaces it with a verbose one, such that the (currently default) verbose output becomes opt-in, with the more lean output just being the default setting.

[wgtmac]

Sounds good to me.

@gszadovszky @shangxinli Do you have different opinions?

[Fokko]

I think verbose-test is a better name than ci-test

[Fokko]

Lookg good, thanks @amousavigourabi for working on this 👍

[Fokko]

I think verbose-test is a better name than ci-test