Skip to content

adding aae test for ts based on verify_aae#1259

Open
korry8911 wants to merge 2 commits intodevelopfrom
kc-ts-aae
Open

adding aae test for ts based on verify_aae#1259
korry8911 wants to merge 2 commits intodevelopfrom
kc-ts-aae

Conversation

@korry8911
Copy link
Copy Markdown
Contributor

@javajolt passes for me locally

Comment thread tests/ts_cluster_aae.erl
@@ -0,0 +1,401 @@
%% -------------------------------------------------------------------
%%
%% Copyright (c) 2013 Basho Technologies, Inc.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

2017?

Comment thread tests/ts_cluster_aae.erl
%%
%% -------------------------------------------------------------------
%% @doc Verification of Active Anti Entropy.
%% The basic guarantee of AAE is this: Even without the read repairs that will
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Maybe update the text a bit to mention that this is for time series

@hazen
Copy link
Copy Markdown

hazen commented Jan 11, 2017

@korry8911 Can you close this PR and submit a new one on develop? Thanks

@hazen hazen changed the base branch from riak_ts-develop to integration January 13, 2017 17:18
Comment thread tests/ts_cluster_aae.erl
end, PlCounts, Pl).

test_data_ts(Start, End) ->
StepSize = 1000*60*5,
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

How about a comment about what this StepSize is and why we have it?

Comment thread tests/ts_cluster_aae.erl
write_data_ts(Node, KVs, Table, _Opts) ->
[begin
O =
case ts_ops:get([Node], Table, key_ts(TS_Data_Tuple)) of
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Why are we reading the data first? In the verify_aae case they read in case the data already exists and update it instead. In TS, it is write-once and we never update values.

@hazen hazen changed the base branch from integration to develop February 3, 2017 19:33
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.

2 participants