<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Guide on Parquet</title><link>https://alamb.github.io/parquet-site/docs/contribution-guidelines/</link><description>Recent content in Developer Guide on Parquet</description><generator>Hugo</generator><language>en</language><atom:link href="https://alamb.github.io/parquet-site/docs/contribution-guidelines/index.xml" rel="self" type="application/rss+xml"/><item><title>Sub-Projects</title><link>https://alamb.github.io/parquet-site/docs/contribution-guidelines/sub-projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alamb.github.io/parquet-site/docs/contribution-guidelines/sub-projects/</guid><description>&lt;p&gt;The &lt;a href="https://github.com/apache/parquet-format"&gt;parquet-format&lt;/a&gt; project contains format specifications and Thrift definitions of metadata required to properly read Parquet files.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://github.com/apache/parquet-java"&gt;parquet-java&lt;/a&gt; project is a Java library to read and write Parquet files. It consists of multiple sub-modules, which implement the core components of reading and writing a nested, column-oriented data stream, to and from the Parquet format, along with Hadoop Input/Output Formats, Pig loaders, and other Java-based utilities for interacting with Parquet.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://arrow.apache.org/docs/cpp/parquet.html"&gt;parquet-cpp&lt;/a&gt; project is a C++ library to read-write Parquet files. It is part of the &lt;a href="https://arrow.apache.org/"&gt;Apache Arrow&lt;/a&gt; C++ implementation, with bindings to Python, R, Ruby and C/GLib.&lt;/p&gt;</description></item><item><title>Building Parquet</title><link>https://alamb.github.io/parquet-site/docs/contribution-guidelines/building/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alamb.github.io/parquet-site/docs/contribution-guidelines/building/</guid><description>&lt;p&gt;Building
Java resources can be build using &lt;code&gt;mvn package&lt;/code&gt;. The current stable version should always be available from Maven Central.&lt;/p&gt;
&lt;p&gt;C++ thrift resources can be generated via make.&lt;/p&gt;
&lt;p&gt;Thrift can be also code-genned into any other thrift-supported language.&lt;/p&gt;</description></item><item><title>Contributing to Parquet-Java</title><link>https://alamb.github.io/parquet-site/docs/contribution-guidelines/contributing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alamb.github.io/parquet-site/docs/contribution-guidelines/contributing/</guid><description>&lt;h2 id="pull-requests"&gt;Pull Requests&lt;/h2&gt;
&lt;p&gt;We prefer to receive contributions in the form of GitHub pull requests. Please send pull requests against the &lt;a href="https://github.com/apache/parquet-java"&gt;github.com/apache/parquet-java&lt;/a&gt; repository. If you’ve previously forked Parquet from its old location, you will need to add a remote or update your origin remote to &lt;a href="https://github.com/apache/parquet-java.git"&gt;https://github.com/apache/parquet-java.git&lt;/a&gt;. Here are a few tips to get your contribution in:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Break your work into small, single-purpose patches if possible. It’s much harder to merge in a large change with a lot of disjoint features.&lt;/li&gt;
&lt;li&gt;Create an Issue on the &lt;a href="https://github.com/apache/parquet-java/issues"&gt;Parquet-Java issues&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Submit the patch as a GitHub pull request against the master branch. For a tutorial, see the GitHub guides on forking a repo and sending a pull request. Prefix your pull request name with the Issue &lt;code&gt;GH-2935&lt;/code&gt;: (ex: &lt;a href="https://github.com/apache/parquet-java/pull/2951"&gt;https://github.com/apache/parquet-java/pull/2951&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Make sure that your code passes the unit tests. You can run the tests with &lt;code&gt;mvn test&lt;/code&gt; in the root directory.&lt;/li&gt;
&lt;li&gt;Add new unit tests for your code.&lt;/li&gt;
&lt;li&gt;All Pull Requests are tested automatically on &lt;a href="https://github.com/apache/parquet-java/actions"&gt;GitHub Actions&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you’d like to report a bug but don’t have time to fix it, you can still &lt;a href="https://github.com/apache/parquet-java/issues"&gt;raise an issue&lt;/a&gt;, or email the mailing list (&lt;a href="mailto:dev@parquet.apache.org"&gt;dev@parquet.apache.org&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>Releasing Parquet-Java</title><link>https://alamb.github.io/parquet-site/docs/contribution-guidelines/releasing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alamb.github.io/parquet-site/docs/contribution-guidelines/releasing/</guid><description>&lt;h3 id="setup"&gt;Setup&lt;/h3&gt;
&lt;p&gt;N.B. The mechanics of releasing parquet-format is the same (e.g. setting up keys, branching, votes, etc)&lt;/p&gt;
&lt;p&gt;You will need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;PGP code signing keys, published in &lt;a href="https://downloads.apache.org/parquet/KEYS"&gt;KEYS&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Permission to stage artifacts in &lt;a href="https://repository.apache.org/"&gt;Nexus&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Make sure you have permission to deploy Parquet artifacts to Nexus by pushing a snapshot:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"&gt;&lt;code class="language-sh" data-lang="sh"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;mvn deploy
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you have problems, read the &lt;a href="https://www.apache.org/dev/publishing-maven-artifacts.html"&gt;publishing Maven artifacts documentation&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="release-process"&gt;Release process&lt;/h3&gt;
&lt;p&gt;Parquet uses the maven-release-plugin to tag a release and push binary artifacts to staging in Nexus. Once maven completes the release, the official source tarball is built from the tag.&lt;/p&gt;</description></item></channel></rss>