You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by Matt Massie <ma...@berkeley.edu> on 2014/11/19 23:54:08 UTC

Question on 1.6.0-rc4 Maven artifacts

I’m trying to discover the git sha-1 for the 1.6.0-rc4 Maven artifacts
which were published yesterday.

When I look inside META-INF/MANIFEST.MF, I find the following

Manifest-Version: 1.0
git-SHA-1: ffee26a76c04e86eaec2b71eced258a9af100ce6
Built-By: julien
Build-Jdk: 1.7.0_12-ea
Created-By: Apache Maven 3.1.1
Archiver-Version: Plexus Archiver

but I don’t see a ffee26a76c04e86eaec2b71eced258a9af100ce6 hash in the
Apache or Github repos for Parquet.

I also looked in the commit log for commits like the following…

commit 501e8feac3fb60e794979e8445cf2ceebce94b04
Author: julien <ju...@twitter.com>
Date:   Wed Sep 10 16:44:58 2014 -0700

    [maven-release-plugin] prepare for next development iteration

commit 316b5682e52cacc1d4eb7641da3066fd7a691aed
Author: julien <ju...@twitter.com>
Date:   Wed Sep 10 16:44:54 2014 -0700

    [maven-release-plugin] prepare release parquet-1.6.0rc2

but found none for rc3 or rc4.

Is there a mechanism that I’m missing for matching artifacts to git history?

Also, I’d like to move to rc4 in order to get dictionary support for
parquet-avro in our next release of ADAM
<https://github.com/bigdatagenomics/adam>. Are there any glaring bugs that
would make you advise against moving forward?

—
Matt <http://www.linkedin.com/in/mattmassie/> Massie
<http://www.twitter.com/matt_massie>

UC, Berkeley AMPLab <https://twitter.com/amplab>
​

Re: Question on 1.6.0-rc4 Maven artifacts

Posted by Matt Massie <ma...@berkeley.edu>.
I want to answer my own question for the benefit of anyone who might read
this.

I was mistaken. The hash ffee26a76c04e86eaec2b71eced258a9af100ce6 does
exist, e.g.
https://github.com/apache/incubator-parquet-mr/commit/ffee26a76c04e86eaec2b71eced258a9af100ce6

This hash is tagged parquet-1.6.0rc4 and has a parent commit, e.g.
https://github.com/apache/incubator-parquet-mr/commit/251a495d2a72de7e892ade7f64980f51f2fcc0dd

Sorry for the mailing list noise with a non-issue.
​

--
Matt <http://www.linkedin.com/in/mattmassie/> Massie
<http://www.twitter.com/matt_massie>
UC, Berkeley AMPLab <https://twitter.com/amplab>

On Wed, Nov 19, 2014 at 2:54 PM, Matt Massie <ma...@berkeley.edu> wrote:

> I’m trying to discover the git sha-1 for the 1.6.0-rc4 Maven artifacts
> which were published yesterday.
>
> When I look inside META-INF/MANIFEST.MF, I find the following
>
> Manifest-Version: 1.0
> git-SHA-1: ffee26a76c04e86eaec2b71eced258a9af100ce6
> Built-By: julien
> Build-Jdk: 1.7.0_12-ea
> Created-By: Apache Maven 3.1.1
> Archiver-Version: Plexus Archiver
>
> but I don’t see a ffee26a76c04e86eaec2b71eced258a9af100ce6 hash in the
> Apache or Github repos for Parquet.
>
> I also looked in the commit log for commits like the following…
>
> commit 501e8feac3fb60e794979e8445cf2ceebce94b04
> Author: julien <ju...@twitter.com>
> Date:   Wed Sep 10 16:44:58 2014 -0700
>
>     [maven-release-plugin] prepare for next development iteration
>
> commit 316b5682e52cacc1d4eb7641da3066fd7a691aed
> Author: julien <ju...@twitter.com>
> Date:   Wed Sep 10 16:44:54 2014 -0700
>
>     [maven-release-plugin] prepare release parquet-1.6.0rc2
>
> but found none for rc3 or rc4.
>
> Is there a mechanism that I’m missing for matching artifacts to git
> history?
>
> Also, I’d like to move to rc4 in order to get dictionary support for
> parquet-avro in our next release of ADAM
> <https://github.com/bigdatagenomics/adam>. Are there any glaring bugs
> that would make you advise against moving forward?
>
> —
> Matt <http://www.linkedin.com/in/mattmassie/> Massie
> <http://www.twitter.com/matt_massie>
>
> UC, Berkeley AMPLab <https://twitter.com/amplab>
> ​
>