Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/az/remove dead code because legacy gossip is false #734

Closed

Conversation

hmmr
Copy link
Contributor

@hmmr hmmr commented May 3, 2015

In response to comment by @jonmeredith in basho/riak_kv#1104 "Also could do with a PR to clean up riak_core sometime", here's an attempt to carefully excise code that has become dead due to legacy_gossip and related functions being stubbed to 'false'.

hmmr added 6 commits May 1, 2015 22:41
Note that riak_core_gossip_legacy.erl is gone (after cleanup, there
are no references to this module remaining in the entire riak/deps
tree).
For some reason, dialyzer fails to use exported behaviour_info/1 and
goes on to emit warnings in riak_kv.  But it works fine with callback
specs expressly provided.
There are three modules in riak_kv implementing this behaviour:
riak_kv_{buckets,keys,index}_fsm.  The wirst two are good, but the
"index" one has process_results/2 deprecated (L191 has this comment:
"Legacy, unsorted 2i, should remove?"), instead exporting process_result/3,
which is not a legislated callback of that behaviour.

A quick resolution to this, somewhat nitpicky, issue would be to just let
riak_kv_index_fsm not implement this behaviour.  Hereby I'm soliciting
more informative suggestions -- or we could just let it be, along with a
corresponding entry in riak_kv/dialyzer.ignore-warnings, and wait for a
more sweeping change to flush this tiny piece of impropriety.
…d-code-because-legacy_gossip-is-false

# Conflicts:
#	dialyzer.ignore-warnings
@hmmr
Copy link
Contributor Author

hmmr commented May 5, 2015

With the merge of 'fix/az/assorted-dialyzer-issues', dialyzer.ignored-warnings shrinks to 0. However, please look at c5a0a7b.

@hmmr hmmr self-assigned this May 7, 2015
@hmmr
Copy link
Contributor Author

hmmr commented May 13, 2015

Looks like this wheel has been invented already: #541.

@hmmr
Copy link
Contributor Author

hmmr commented May 17, 2015

I have rebased #541 and created a new PR for it (#737 (RIAK-1799)).

Going to close this PR and delete the branch.

@hmmr hmmr closed this May 19, 2015
@hmmr hmmr deleted the fix/az/remove-dead-code-because-legacy_gossip-is-false branch May 19, 2015 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant