Develop 2.9 #1675
Develop 2.9 #1675
Conversation
fold_heads receives a binary proxy object not a riak_object.
This reverts commit 2a41ddb.
As previously this disn't work
Start to plumb in query options, rather than generating filters - as the filter can always be generated as part of generating the object folder
Make it a bit easier to write other fold functions by generalising the validation of input options in riak_kv_mapfold_fsm
Try and make abstraction between mapfold_fsm modules clearer and add in support for segment_folder in new code style
Detcted by dialyzer
Removed the need to fully convert the object to a riak-object to extract key details (e.g. sibling count, object size and vector clock)
This supports passing check_presence from the request through to the backend
Unit test JSON decoding ... kept making mistakes
It wouldn't work - and there's no code behind it yet
This isn't yet configurable. Also tidy up logging
Helps with verifying results in test.
FoldObjects fun gets transformed based on some conditions in leveled from a 4 arity to a 3 arity function. This uses a tag to reverse that
Switch to use mas-aae-segmentfoldplus. This should use the new hashing algorithms for tictac trees, and is a pre-cursor to using accelerated segment folds
Mistake - leveled capability was removed, but was required by tictac_aae
Use version brought in from riak_core to avoid confusion
Mainly outcome from testing, some changes where I had wrong assumptions about how wrq functions worked with the path. Some docs/specs changes in the cluster aae fsm that testing showed to be needed.
With leveled backend
Mas i234 snapshottimeout
AAE Fold HTTP API
This reverts commit 447daa3.
Set Request Type in prepare.
Some changes, mainly making the ordering requirement on get core results explicit in documentation. I renamed override_nodes, as I found it confusing. I renamed head_merge/2 to merge_heads/2 since it had nothing to do with head_merge/1 and made code navigation harder. I hope that none of these are too contentious
Get FSM review changes
Develop 2.9.0 prc0
bump leveled
Update rebar.config
|
@martincox - this gets all the work on 2.9.0 into the develop-2.9 branch on riak_kv. Can you +1? |
|
This is a behemoth of a PR! Am I right in seeing that the additional features introduced here, such as HEAD requests are exposed exclusively through the HTTP API? Therefore, we should maybe raise an issue for these to be exposed through PB (if needed / required)? |
|
The only API features are the aae_fold API and the new riak_repl feature which allows an object to be touched (prompting re-replication without modification). These two features are only available via HTTP - so I'll create an issue for the PB follow-up (although I'm not sure with aae_fold if in the long run the right answer is exposure via API or access direct using riak_client). The use of HEAD request is internal only at the moment (and only changes behaviour when the backend supports the |
Re-point at basho - requires other PRs to be accepted
Merge develop-2.9 changes into main basho repo for riak_kv.
The changes include:
Changes to GET and PUT FSM (and riak_kv_vnode) to support use of HEAD capability within backends;
Integration of leveled backend;
Addition of support for kv_index_tictactree based anti-entropy;
Support for aae_folds to provide inter-cluster anti-entropy building blocks based on kv_index_tictactree;
Integration with core node worker pool and ability to queue async work based on previously snapped snapshots;
Vnode soft limit monitoring when selecting PUT co-ordinators.