SERDE backed schema for parquet storage in Hive

As of now, for a hive table stored as parquet, the schema can only be specified in Hive MetaStore. For our use-case, it is desired that the schema be provided by Thrift SerDe rather than MetaStore. Using thrift IDL as a schema provider, allows us to maintain a consistent schema across executions engines other than Hive such as Pig and Native MR.

Additionally, for a large sparse schema, it is much easier to build thrift objects, and use parquet-thrift/elephant-bird to convert them into columns/tuples rather than constructing the whole big tuple itself.

**Reporter**: [Abhishek Agarwal](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=abhishek.agarwal) / @abhishekagarwal87
**Assignee**: [Ashish Singh](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=singhashish) / @SinghAsDev

_{**Note**: *This issue was originally created as [PARQUET-47](https://issues.apache.org/jira/browse/PARQUET-47). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

L'issue non indica file, test o punti di ingresso. Inizia tracciando come vengono gestiti gli schemi di Hive MetaStore e i Thrift SerDes, quindi esamina l'integrazione di parquet-thrift ed elephant-bird; il lavoro è completato quando una tabella parquet di Hive può ottenere il proprio schema da un Thrift IDL e rimanere utilizzabile in Hive, Pig e Native MR.

Scritto dal modello di indicizzazione a partire dal testo della issue.