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 of "object" data type in time series param (MEGH-5404) #307

Open
CescG opened this issue Mar 31, 2024 · 1 comment
Open

support of "object" data type in time series param (MEGH-5404) #307

CescG opened this issue Mar 31, 2024 · 1 comment

Comments

@CescG
Copy link

CescG commented Mar 31, 2024

Is your feature request related to a problem?

I'm trying to provide a complex time series, with a lot of different values per each timestamp. it would be nice to use the "object" data type instead to be forced to use a lot of params or encapsulate all of them in a "string" data type

Describe the solution you'd like.

Time series param support of object data type

Describe alternatives you've considered.

No response

Additional context.

No response

@github-actions github-actions bot changed the title support of "object" data type in time series param support of "object" data type in time series param (MEGH-5404) Mar 31, 2024
@shahpiyushv
Copy link
Collaborator

Object data type is hard to support in the cloud backend for time series data since there's no easy way for it to know the object model and parse accordingly. If the issue is about not being able to report multiple params against same timestamp since timestamp is added internally, you can construct your own JSON as per the specs here and then publish to the time series MQTT topic.

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