(parquet-java) branch dependabot/maven/net.openhft-zero-allocation-hashing-0.27ea1 updated (48db9c3de -> 7fe1ab80c)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/net.openhft-zero-allocation-hashing-0.27ea1
in repository https://gitbox.apache.org/repos/asf/parquet-java.git


    omit 48db9c3de Bump net.openhft:zero-allocation-hashing from 0.27ea0 to 0.27ea1
     add 33426a682 Bump org.codehaus.mojo:exec-maven-plugin from 3.5.0 to 3.6.3 (#3440)
     add e8d1a553b Bump org.apache.parquet:parquet-pig from 1.15.0 to 1.15.2 (#3420)
     add 51ea6100b Bump commons-logging:commons-logging from 1.3.5 to 1.3.6 (#3418)
     add c1b6aa35c Bump com.google.re2j:re2j from 1.7 to 1.8 (#3433)
     add 7fe1ab80c Bump net.openhft:zero-allocation-hashing from 0.27ea0 to 0.27ea1

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (48db9c3de)
            \
             N -- N -- N   refs/heads/dependabot/maven/net.openhft-zero-allocation-hashing-0.27ea1 (7fe1ab80c)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 parquet-cli/pom.xml    | 2 +-
 parquet-thrift/pom.xml | 4 ++--
 pom.xml                | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)