[feature request] Support month and year as duration unit

ghost commented 9 years ago

For example:

1M for 1 month
1y for 1 year

Its useful for me when i want to query the data last month and year...

pauldix commented 6 years ago

This will be included as part of our new query engine, Flux. This would be something added to the window function in the new language.

Unfortunately, handling this in our existing query engine would be very difficult. Addressing many long standing query feature requests are exactly why we set out to create a new query engine and language with it.

Wolfgang1966 commented 6 years ago

Dear Paul, that's great news!

Thank you very much!

kylethebaker commented 6 years ago

@pauldix That sounds promising, do you have an example of what an Flux query will look like for doing doing a month-to-date aggregate for every month in a year? For example, selecting the sum of some value between the 1st and 15th day of the month, grouped by month and year?

Tux12Fun commented 6 years ago

+1

Would like to see this for a business case, and for a private case.

patrickcat commented 6 years ago

+1

Scott-St commented 6 years ago

+1

patrickvallet commented 6 years ago

Hi, It will be available in future 1.5 version then? Many thanks Regards

Pirx99 commented 6 years ago

would be really great for me to get 'month' supported soon!

HoshangCharania commented 6 years ago

Any update on this issue?

mkontula commented 6 years ago

Since it comes up as an additional layer beside actual db there's no way of getting your shard durations nor CQ's to run with calendar intervals. This will probably make some enterprisish customers look elsewhere. Perhaps you should consider renaming the product Fixed-Interval-Timeseries-DB. Would reflect the reality way better. Also state on your product description: We are a timeseries db, but we don't understand anything about calendars.

mr-varga commented 6 years ago

+1

idobarash commented 6 years ago

+1

kukudemajia commented 6 years ago

+1

dlanza1 commented 6 years ago

+1

marine1988 commented 6 years ago

+1

migsk commented 6 years ago

+1

yihaozhadan commented 6 years ago

+1

Pirx99 commented 6 years ago

After waiting too long for this important feature I now moved to a different DB. Sorry guys but without it you can't call it "time-series DB".

gsemet commented 6 years ago

We also moved to prometheus.

cicciopizza commented 6 years ago

we are also doing tests to migrate on prometheus... shame because it was a good project...

Pirx99 commented 6 years ago

I moved to PostgreSQL

scmod commented 6 years ago

+1 from a large amount of data in timeunit of second, I have to draw the minutely, quarterly, half-hourly, hourly, daily, weekly, monthly or even yearly k-line chart, so I think group by month or year is really powerful to do these things

TheEggi commented 6 years ago

Any update on this one?

scmod commented 6 years ago

Any update on this one?

currently not...

aigr commented 6 years ago

+1

eraelpeha commented 6 years ago

+1

decaillet commented 6 years ago

+1

samreaves commented 6 years ago

+1

douglasg14b commented 6 years ago

Would very much like to see this as a feature. It's not really possible to create any sort of month-by-month view in grafana for InfluxDB sources..... Unless the month is manually added as a tag.

timhallinflux commented 6 years ago

Re-iterating @pauldix comment from above: This will be included as part of our new query engine, Flux. This would be something added to the window function in the new language.

Unfortunately, handling this in our existing query engine would be very difficult. Addressing many long standing query feature requests are exactly why we set out to create a new query engine and language with it.

This won't appear in the Flux 0.7 technical preview forthcoming -- but it is very much on our radar to include for GA of Flux.