-
Notifications
You must be signed in to change notification settings - Fork 236
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
HTTP client API all-in-one [3/3] #1398
HTTP client API all-in-one [3/3] #1398
Conversation
6348791
to
3948210
Compare
A two month worth of commits by @hmmr and @lehoff, squashed. The odd change in riak_kv_qry_worker (preserving lists for records in the return value of query) goes with the list_to_tuple conversion now happening in riak_kv_ts_api. Native lists from riak_kv_qry:submit are immediately consumable by mochijson2:encode, and this is the form we would like to have the query results in wm_timeseries_query.
3948210
to
bf62ab8
Compare
@@ -292,10 +292,8 @@ prepare_final_results2(#riak_sel_clause_v1{col_return_types = ColTypes, | |||
|
|||
prepare_final_results_test() -> | |||
Rows = [[12, <<"windy">>], [13, <<"windy">>]], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be tuples then? I'll test and find out...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
list_to_tuple
now happens in riak_kv_ts_svc
, right before the records are delivered to the PB/TTB code and further to the client. This is so in order to avoid converting tuples back to lists in riak_kv_wm_timeseries_query
, where lists are required for converting the data to json.
Which is why we still have native records-as-lists here.
…client_api_allinone
A two month worth of commits by @hmmr and @lehoff, squashed. The odd change in riak_kv_qry_worker (preserving lists for records in the return value of query) goes with the list_to_tuple conversion now happening in riak_kv_ts_api. Native lists from riak_kv_qry:submit are immediately consumable by mochijson2:encode, and this is the form we would like to have the query results in wm_timeseries_query.
…client_api_allinone
bf62ab8
to
1912a98
Compare
…asho/riak_kv into feature-az+th-http_client_api_allinone
{ReqId, {error, timeout}} -> | ||
{mochijson2:encode({struct, [{error, timeout}]}), done}; | ||
_Weird -> | ||
%% @todo: should we log this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a good idea. Might be useful to see if bad requests are being sent.
received from riak_kv_keys_fsm
👍 94db162 |
@borshop merge |
This is Part 3/3 of #1382 broken up and reassembled into new commits.
Requires (includes) #1396, #1397 (with basho/riak_pb#190 (RIAK-2492)).
A two month worth of commits by @hmmr and @lehoff, squashed.
The odd change in riak_kv_qry_worker (preserving lists for records in the return value of query) goes with the list_to_tuple conversion now happening in riak_kv_ts_api. Native lists from riak_kv_qry:submit are immediately consumable by mochijson2:encode, and this is the form we would like to have the query results in wm_timeseries_query.