Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Additional query parameter to specify duration #65

Open
dschowta opened this issue Apr 28, 2020 · 3 comments
Open

Additional query parameter to specify duration #65

dschowta opened this issue Apr 28, 2020 · 3 comments
Assignees
Labels
nice to have A low priority enhancement

Comments

@dschowta
Copy link
Member

In order to query for a relateive time, it is better to support duration like field in HDS query.
e.g. /data/sensor1/reading?$duration=1h will fetch the data of last 1 hour.

@dschowta dschowta self-assigned this Apr 28, 2020
@dschowta dschowta added the enhancement New feature or request label Apr 28, 2020
@farshidtz
Copy link
Member

I think this is redundant. The client can simply provide start and end times to get the equivalent and more consistent results.

@dschowta
Copy link
Member Author

dschowta commented Jul 3, 2020

If I remember it right, it was for the BIMERR project requirement, where the BIF data fetcher needed this functionality. The fetcher presumably could not calculate the absolute times.

@farshidtz
Copy link
Member

farshidtz commented Jul 3, 2020

Right, we wanted to set the URL in their UI for cron-based retrieval. They had no parameter injection support for the URL.

@farshidtz farshidtz added nice to have A low priority enhancement and removed enhancement New feature or request labels Jul 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
nice to have A low priority enhancement
Projects
None yet
Development

No branches or pull requests

2 participants