As long as you only have hundreds or low thousands of users it should be okay. Each database incurs a fixed filesystem and RAM cost, but they aren't very high.
On Tue, Sep 6, 2016 at 8:49 PM, Mathias Herberts <[email protected] > wrote: > Thanks, the 'database per user' approach seems indeed the most appropriate. > > On Tuesday, September 6, 2016 at 11:44:30 PM UTC+2, Sean Beckett wrote: >> >> Retention policies are enforced based on the timestamp of the point, not >> when the point was written. There is no way in the system to drop data >> based on write time. Presumably you could give each user their own >> database, or databases, and when the time limit has expired, simply DROP >> DATABASE. >> >> On Tue, Sep 6, 2016 at 3:29 PM, Mathias Herberts <[email protected]> >> wrote: >> >>> I was wondering if RPs only took into consideration the timestamps of >>> the datapoints or if they could be configured to consider the time at which >>> the data was inserted into the db. >>> >>> My question is to understand how RPs should be enforced for users who >>> want to insert large historical datasets covering several years but should >>> not be allowed to keep the data they uploaded past a certain amount of time. >>> >>> If RPs are not the way to go, how could this be done? >>> >>> -- >>> Remember to include the InfluxDB version number with all issue reports >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "InfluxDB" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/influxdb. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/influxdb/d11bb8f6-facc-4bf1-b67d-54c9b45718c3%40googlegroups.com >>> <https://groups.google.com/d/msgid/influxdb/d11bb8f6-facc-4bf1-b67d-54c9b45718c3%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Sean Beckett >> Director of Support and Professional Services >> InfluxDB >> > -- > Remember to include the InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/b261ad0d-4f05-4b06-8c26-5e785f3203d3%40googlegroups.com > <https://groups.google.com/d/msgid/influxdb/b261ad0d-4f05-4b06-8c26-5e785f3203d3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvPmE43UqnQzt5_puYvCMZPGcBvf8qX7bi7au_5gY4OPEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
