[ACCUMULO-2217] fall back to reliable compression settings on failure

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.4, 1.5.0
• Assignee: Unassigned
• Reporter: Adam Fuchs
• Created: 17/Jan/14 19:00
• Updated: 04/Apr/14 04:49

Description

Bad compression configuration keeps tables online:

createtable test
config -t test -s table.file.compression.type=snappy
flush
droptable test

The flush results in an unsatisfied link error when Snappy is not properly configured. This keeps the tablet online. Dropping the table when the tablet is stuck online puts a FATE operation in the queue, which backs everything up.

Can we fall back to something that is in the java code base (i.e. gz) in the event of failures to load other compression code?