PARQUET-2274: Remove Yetus

[Fokko]

I don't think this is used anywhere anymore.

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-2274
  • 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:

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"

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]

LGTM though I am not familiar with this tool.

cc @gszadovszky

[gszadovszky]

We started to use this to mark somehow the public classes/methods that did not ment to be public for the API users but only because of our current module layout. Since we are on java8 we do not have anything else to mark them. But because we do not have any tools running on the API (not even talking about the client side) it does not really make sense to have these annotations. Maybe it would worth some comments as replacements of the annotations but I am not sure they would be checked before used.

[shangxinli]

Yeah, adding some comments could help although sometimes people ignore it. But some of them are already used by other tool like the columnIndex one.

[shangxinli]

@Fokko Do you think you can add some comment and we merge this PR in?

[Fokko]

@shangxinli Sorry for the long wait, I've added the comments 👍

[wgtmac]

@sekikn Do you have any comment?

[sekikn]

No, I agree with replacing audience annotations with appropriate comments for now, since we don't have a tool for enforcing restriction based on the annotations, as mentioned by @gszadovszky.

[Fokko]

Thank you @sekikn for confirming. I'll move this forward.