Skip to content

Extract Protocol Buffers interface from KV#138

Merged
rzezeski merged 1 commit into
masterfrom
sdc-pbc-extract
Jun 5, 2012
Merged

Extract Protocol Buffers interface from KV#138
rzezeski merged 1 commit into
masterfrom
sdc-pbc-extract

Conversation

@seancribbs

Copy link
Copy Markdown
Contributor

This is part of a series of pull-requests to extract the Protocol Buffers interface from riak_kv and make it available to all applications in an unobtrusive manner.

Related: basho/riak_kv#321

This specific pull-request adjusts app.config to move settings into the new riak_api, enables R15B01 support, and temporarily points the riak_kv dependency at the branch that includes the refactoring.

The Java and Python clients test suites should pass against this refactoring. Ruby and Erlang clients test suites fail because they directly modify the server or its configuration. Manual testing and benchmarking is encouraged.

Comment thread rebar.config Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a reminder to make sure this get set back to master before merge.

@kellymclaughlin

Copy link
Copy Markdown
Contributor

These changes look good to me, +1.

@rzezeski

Copy link
Copy Markdown
Contributor

I wonder about the app.config changes. From my understanding when a user upgrades the pkg installers will keep the old app.config. This means that riak_api will revert to defaults if user doesn't migrate PB config from riak_core to riak_api. This poses a problem if said user has modified their PB settings (especially IP/Port).

@kellymclaughlin

Copy link
Copy Markdown
Contributor

The other problem is that if they simply use the old version of the config then riak fails to start at all with ugly errors. I made a comment about more helpful error messages in that regard on the riak_kv pr. In the interest of backward compatibility maybe riak_api should also check for the existence of the properties in the riak_core section and use those in the absence of riak_api properties in addition to some friendly lager reminders to upgrade the code. Then a couple of versions from now we can take out the riak_core check.

@rzezeski

Copy link
Copy Markdown
Contributor

I agree. I'm going to fix riak_api to do just that. I feel in the future we'll need a better story than "make sure you go into all your app configs and change this stuff or things will break in the future."

@rzezeski

Copy link
Copy Markdown
Contributor

Hopefully this fixes the upgrade path, need to test still.

basho/riak_api#1

@rzezeski

rzezeski commented Jun 1, 2012

Copy link
Copy Markdown
Contributor

The recent riak_api additions fix the upgrade path and allow PB to function with old configs.

+1 to merge.

@rzezeski
rzezeski merged commit 487dcc2 into master Jun 5, 2012
hmmr pushed a commit that referenced this pull request Nov 8, 2016
@martincox
martincox deleted the sdc-pbc-extract branch February 22, 2019 21:10
martincox pushed a commit that referenced this pull request Jan 28, 2022
martincox pushed a commit that referenced this pull request Jan 31, 2022
…tion

Tweak python build to work with either Python 2 or 3

Reviewed-by: lukebakken
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants