Hi there, I'm not quite sure which schema design would be better and hoping someone could help:
(1) Measurement = PageViews Tags = OrganisationId=XYZ, PageId=123 Values = BrowserAgent=Chrome, URL=test.com Measurement = Clicks Tags = OrganisationId=XYZ, PageId=123 Values = BrowserAgent=Chrome, URL=test.com or (2) Measurement = XYZ (OrganisationID) Tags = PageId=123, Event=PageView Values = BrowserAgent=Chrome, URL=test.com Measurement = XYZ (OrganisationID) Tags = PageId=123, Event=Click Values = BrowserAgent=Chrome, URL=test.com or (3) Measurement = XYZ-123 (OrganisationId-PageId) Tags = Event=PageView Values = BrowserAgent=Chrome, URL=test.com Measurement = XYZ-123 (OrganisationId-PageId) Tags = Event=Click Values = BrowserAgent=Chrome, URL=test.com This would be a used in a multi-tenant environment where each customer (organisation) has their own data. Does the use of a orgid-pageid measurement help the underlying database? IE, with SQL having a table name as the OrgId-PageId would restrict the indexing storage/speed to just that of that scope, however I'm not sure it would be the same with InfluxDB as perhaps indexes are based on series (which includes measurement and tags). So then in theory it would be much of a muchness - no performance gain by segmenting data? Ryan -- 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/0100a133-7b23-4d29-aa7a-33e2666991d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
