[KUDU-782] Range predicates on key prefixes don't work via client

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Private Beta
• Component/s: client, tserver
• Target Version/s: Feature Complete
• Assignee: Jean-Daniel Cryans
• Reporter: Todd Lipcon
• Created: 19/May/15 16:02
• Updated: 06/Aug/15 17:19
• Resolved: 06/Aug/15 17:19

Description

If I set up a composite primary key (as in the TPCH table), and I set a range predicate only on a prefix of that key, then I end up getting the following error back from the server:
F0519 14:02:45.307723 21286 rpc_line_item_dao.cc:158] Check failed: _s.ok() Bad status: Invalid argument: Invalid scan start key: Error decoding composite key component 'l_linenumber': key too short