[HAWQ-1177] Use profile based on file format in HCatalog integration for HiveOrc profile

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0.0-incubating
• Component/s: PXF
• Assignee: Oleksandr Diachenko
• Reporter: Oleksandr Diachenko
• Created: 28/Nov/16 23:15
• Updated: 18/Feb/17 05:26
• Resolved: 28/Dec/16 01:20

Description

When user queries Hive table using HCatalog integration feature, HAWQ uses "Hive" profile, which might be not optimal. Idea is to choose profile for each fragment, based of underlying file format. In this JIRA we should implement changes to leverage HiveORC profile.

Sub-Tasks

• Enhance Fragmenter api to return profile name: Resolved
• Call Bridge api with profile value read from Fragmenter call: Resolved