[KUDU-852] Defining scan projections should have a better API

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Private Beta
• Component/s: api, client
• Target Version/s: Feature Complete
• Code Review: http://gerrit.sjc.cloudera.com:8080/#/c/7138/
• Assignee: Todd Lipcon
• Reporter: David Alves
• Created: 10/Jul/15 16:13
• Updated: 13/Jul/15 23:18
• Resolved: 13/Jul/15 23:18

Description

Defining scan projections on the cilent is currently messy. For instance the scan projection allows to define any order of columns, including key columns, as long as the number of key columns is set to 0, otherwise the key columns must come first.

Since the client already fetches the table schema anyway we should just have a simple api that takes column names in whichever order instead of having to pass a full blown schema.