-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
List the series available in a database #99
Comments
👍 |
2 similar comments
👍 |
👍 |
This should be implemented in the query language so clients won't need to be updated to hit a new HTTP endpoint.
or maybe
? |
I would prefer the former. Distinguishes a time serie db a little more from a relational one :]. |
|
I think list is more natural, but I used show because that's what SQL uses. But maybe it's ok to deviate? |
Nice ! |
The response should look like the following:
the columns and points can be omitted. |
fix #99. Return a separate time series
Has the last commit been reverted? It's still the old format...
|
That looks like the correct format to me. What were you expecting? |
From 2a7c7d5f14b60755e33b87aa98c7ffb74b3473b3:
I was expecting [{"name":"demo","columns":[],"points":[]},
{"name":"demo2","columns":[],"points":[]},
{"name":"demo3","columns":[],"points":[]} |
This ticket should be reopened. |
No description provided.
The text was updated successfully, but these errors were encountered: