Skip to content
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

Multitenant DynamoDB collector should use a string for the hash key. #1232

Merged
merged 1 commit into from
Apr 6, 2016

Conversation

tomwilkie
Copy link
Contributor

And propagate errors correctly.

@paulbellamy
Copy link
Contributor

Why?

Edit: By asking why, I mean "put the answer to why in the commit message"

@paulbellamy paulbellamy assigned tomwilkie and unassigned paulbellamy Apr 6, 2016
This is because the key is of the form "<userid>-<hour bucket>", but as I was testing without a userid, I didn't notice that "-<hour bucket>" was a valid number.
@tomwilkie
Copy link
Contributor Author

@paulbellamy added the following to the commit: This is because the key is of the form "<userid>-<hour bucket>", but as I was testing without a userid, I didn't notice that "-<hour bucket>" was a valid number.

@tomwilkie tomwilkie assigned paulbellamy and unassigned tomwilkie Apr 6, 2016
@paulbellamy paulbellamy merged commit e3aa92b into master Apr 6, 2016
@paulbellamy paulbellamy deleted the dynamo-schema branch April 6, 2016 14:32
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