Skip to content

Conversation

@tkaemming
Copy link
Contributor

This was an oversight as part of GH-5317, and wasn't caught in tests because the test suite didn't actually run the tests against multiple databases. The easiest way to test this (other than depending on the tests to have the correct behavior) is to cross-reference the routing logic in the other mutation commands and make sure it's consistent.

vnodes=64,
enable_frequency_sketches=True,
hosts={
i - 6: {'db': i} for i in xrange(6, 9)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

All other tests typically run on db 9 so I just picked some arbitrary numbers around there

Copy link
Contributor

Choose a reason for hiding this comment

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

arbitrary numbers

🤔

Copy link
Contributor

@LewisJEllis LewisJEllis left a comment

Choose a reason for hiding this comment

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

LGTM

)

def tearDown(self):
with self.db.cluster.fanout('all') as client:
Copy link
Contributor

@LewisJEllis LewisJEllis May 25, 2017

Choose a reason for hiding this comment

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

I guess docs say it's the same exact thing, but can we do

with self.db.cluster.all() as client:

here? Or do we prefer having "fanout" in there to hint at what's going on?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No specific reason to prefer one over the other, I just went with the one that I remembered exists. I changed it to .all because it seems more reliable to use a method here.

@tkaemming tkaemming merged commit 33a75e7 into master May 25, 2017
@tkaemming tkaemming deleted the fix-tsdb-deletions branch May 25, 2017 18:34
@github-actions github-actions bot locked and limited conversation to collaborators Dec 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants