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 ne nomme aucun fichier, test ou point d’entrée. Commencez par retracer la manière dont les schémas de Hive MetaStore et les Thrift SerDes sont gérés, puis examinez l’intégration de parquet-thrift et elephant-bird ; le travail est considéré comme terminé lorsqu’une table parquet Hive peut obtenir son schéma à partir d’un Thrift IDL et rester utilisable dans Hive, Pig et Native MR.

Rédigé par le modèle d'indexation à partir du texte de l'issue.