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

Support for more complex value types #4

Open
mitar opened this issue Mar 19, 2014 · 1 comment
Open

Support for more complex value types #4

mitar opened this issue Mar 19, 2014 · 1 comment

Comments

@mitar
Copy link

mitar commented Mar 19, 2014

Currently only doubles are allowed as value types. It would be great if you could pass in Python longs or even dicts.

@stevedh
Copy link
Owner

stevedh commented Apr 10, 2014

I think once you get into that you might be better off using postgres with the hstore or json column types; they're probably going to be way more optimized than what we're doing. Although there might be interesting opportunities for compression given the time-series format!

I'd be down for adding strings though; I think that could come in handy for stuff like logging and a few people have asked for it. It does probably do funny things to the bucketing approach that is really why the compression works in the first place so it's not completely trivial; although you could do a trivial implementation using the protobufs.

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

No branches or pull requests

2 participants