PARQUET-2361: Reduce failure rate of unit test testParquetFileWithBlo…

[fengjiajie]

…omFilterWithFpp

Change-Id: Ic230f197b0996333a082bb05bd201963d05d862e

[INFO] Results:
[INFO] 
Error:  Failures: 
Error:    TestParquetWriter.testParquetFileWithBloomFilterWithFpp:342
[INFO]  

Multiple different PR triggered this failure:

1. Bump jmh.version from 1.21 to 1.36 #1062
2. https://github.com/apache/parquet-mr/actions/runs/5420924489/job/14680382407
3. https://github.com/apache/parquet-mr/actions/runs/6336014897
4. https://github.com/apache/parquet-mr/actions/runs/6381223319
5. https://github.com/apache/parquet-mr/actions/runs/6394826826/job/17357106390

The unit test utilizes random string generation for test data without using a fixed seed. The expectation of a unit test is that the number of false positives in the Bloom filter should match the set probability. Therefore, a simple fix is to increase the number of tests on the Bloom filter. The reason for not using a fixed seed with random numbers is to avoid making the tests effective only in specific scenarios. If it is necessary to use a fixed seed, I can also modify the PR accordingly.

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-2361: Reduce failure rate of unit test testParquetFileWithBlo…"
  • https://issues.apache.org/jira/browse/PARQUET-2361
  • 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