Roll dependencies for 1.4.2
Bump riak_kv dep to 1.4.4
Point to riak_kv 1.4 branch for now
Don't start riak_search is security is enabled
Set riak_kv dep at 1.4.4
Merge pull request #156 from basho/adt-security-holes

Don't start riak_search is security is enabled
Update riak_kv dep to 1.4.5
Update riak_kv dep to 1.4.6
Allow search to start if security is enabled, just disable its APIs

It turns out that simply not starting search if security is enabled did
not play well with the new 'riak-admin security enable' command, because
it was decoupled from node startup. Instead, simply disable the endpoint
APIs that search exposes if security is enabled, making it more friendly
to runtime changes.
Merge pull request #158 from basho/adt-security-search

Allow search to start if security is enabled, just disable its APIs
Roll riak_kv version to 1.4.7
Add deprecation notice on Riak Search startup
Rephrase deprecation notice
Merge pull request #160 from basho/feature/er/add-deprecation-message

Add deprecation notice on Riak Search startup
Bump riak_kv dep to 1.4.8
Code to skip large single terms and report them

Since a term > approx 30k can cause merge-index to be unable to compact
due to an overflow bug, we can skip the killer term and issue an error
to the logs.
Improved check to look at size of entire posting

Was originally only checking the size of Term.  A sufficiently large
combination of bucket name, key name, etc could still cause an overflow
Removed `GeneratedObject` from log message

It was just too noisy and gross.  Ended up emitting > 32000 bytes to log
when it was there which was truncated by lager.
Changed sizing method

Originally used byte_length(to byte_size(term_to_binary(...)) which
causes the binary to be generated. Per Jon Meredith, switched to
erlang:external_size(...) which does the size estimation without
generating the binary
Merge branch 'cv-skip-largeterms' into 1.4