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

List the series available in a database #99

Closed
hvt opened this issue Dec 4, 2013 · 13 comments
Closed

List the series available in a database #99

hvt opened this issue Dec 4, 2013 · 13 comments

Comments

@hvt
Copy link

hvt commented Dec 4, 2013

No description provided.

@auxesis
Copy link
Contributor

auxesis commented Dec 5, 2013

👍

2 similar comments
@FGRibreau
Copy link

👍

@bs-github
Copy link

👍

@pauldix
Copy link
Member

pauldix commented Dec 10, 2013

This should be implemented in the query language so clients won't need to be updated to hit a new HTTP endpoint.

show series;

or maybe

show tables;

?

@hvt
Copy link
Author

hvt commented Dec 10, 2013

I would prefer the former. Distinguishes a time serie db a little more from a relational one :].

@FGRibreau
Copy link

list seems to feel more natural to me (but english is not my native language):

list series;

@pauldix
Copy link
Member

pauldix commented Dec 10, 2013

I think list is more natural, but I used show because that's what SQL uses. But maybe it's ok to deviate?

@ghost ghost assigned jvshahid Dec 17, 2013
@FGRibreau
Copy link

Nice !

jvshahid added a commit that referenced this issue Dec 19, 2013
@jvshahid
Copy link
Contributor

jvshahid commented Jan 2, 2014

The response should look like the following:

[{"name": "series_name", columns: [], points: []}]

the columns and points can be omitted.

@jvshahid jvshahid reopened this Jan 2, 2014
pauldix added a commit that referenced this issue Jan 6, 2014
fix #99. Return a separate time series
jvshahid pushed a commit that referenced this issue Aug 12, 2014
@jonashaag
Copy link

Has the last commit been reverted? It's still the old format...

$ curl "http://XXX:8086/db/demo/series?q=list%20series&u=XXX&p=XXX"
[{"name":"list_series_result","columns":["time","name"],"points":[[0,"demo"],[0,"demo2"],[0,"demo3"]]}]

$ influxdb -v
InfluxDB v0.8.5 (git: 9485e99) (leveldb: 1.15)

@pauldix
Copy link
Member

pauldix commented Nov 14, 2014

That looks like the correct format to me. What were you expecting?

@jonashaag
Copy link

From 2a7c7d5f14b60755e33b87aa98c7ffb74b3473b3:

Previously we returned a single time series with the name "names" that
had one point per time series with the column "name" set to the time
series name. This patch changes the behavior of the server to return a
single time series with no points for each time series in the given db.

I was expecting

[{"name":"demo","columns":[],"points":[]},
 {"name":"demo2","columns":[],"points":[]},
 {"name":"demo3","columns":[],"points":[]}

@jonashaag
Copy link

This ticket should be reopened.

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

7 participants