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

RFC: more generic DataPoint values #65

Open
ignatz opened this issue Jul 21, 2023 · 1 comment
Open

RFC: more generic DataPoint values #65

ignatz opened this issue Jul 21, 2023 · 1 comment

Comments

@ignatz
Copy link

ignatz commented Jul 21, 2023

Hi,

I've been toying with the idea of using tstorage for a series of location data, i.e. 3D positions (latitude, longitude, altitude) for different devices.
If I understand correctly, using tstorage I'd have to model the various serious and values belonging to the same "measurement" as something like:

[
(DataPoint(now, 42), Label("id", "device0"), Label("latitude", "")),
(DataPoint(now, 23), Label("id", "device0"), Label("longitude", "")),
...
]

Is my understanding correct? If so and it's probably a big ask, but would it be possible/make-sense to generalize the data representation to e.g. a byte array? In that case, I could store all related measures as a single point. Does the storage format currently require fixed value/data-point sizes?

Thanks!

@swithek
Copy link

swithek commented Dec 9, 2023

I also think a more generic/byte array value type would be useful. @nakabonne have you considered that? This would require a new major version to be released but it would be a very nice addition.

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