Skip to content

Commit

Permalink
Fixes for unit test failures
Browse files Browse the repository at this point in the history
  • Loading branch information
robbavey committed Nov 14, 2018
1 parent ce49ee5 commit b3570c7
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions spec/unit/outputs/elasticsearch_spec.rb
Expand Up @@ -301,7 +301,7 @@
let(:event) { LogStash::Event.new("myactionfield" => "update", "message" => "blah") }

it "should obtain specific action's params from event_action_tuple" do
expect(subject.event_action_tuple(event)[1]).to include(:_upsert)
expect(subject.event_action_tuple(event)[1]).to include(subject.upsert_key)
end
end

Expand Down Expand Up @@ -362,7 +362,7 @@
it "should not set the retry_on_conflict parameter when creating an event_action_tuple" do
allow(subject.client).to receive(:maximum_seen_major_version).and_return(maximum_seen_major_version)
action, params, event_data = subject.event_action_tuple(event)
expect(params).not_to include({:_retry_on_conflict => num_retries})
expect(params).not_to include({subject.retry_on_conflict_key => num_retries})
end
end

Expand All @@ -371,7 +371,7 @@

it "should set the retry_on_conflict parameter when creating an event_action_tuple" do
action, params, event_data = subject.event_action_tuple(event)
expect(params).to include({:_retry_on_conflict => num_retries})
expect(params).to include({subject.retry_on_conflict_key => num_retries})
end
end

Expand All @@ -380,7 +380,7 @@

it "should set the retry_on_conflict parameter when creating an event_action_tuple" do
action, params, event_data = subject.event_action_tuple(event)
expect(params).to include({:_retry_on_conflict => num_retries})
expect(params).to include({subject.retry_on_conflict_key => num_retries})
expect(action).to eq("update")
end
end
Expand Down

0 comments on commit b3570c7

Please sign in to comment.