a little more searching went a long way: https://groups.google.com/d/msg/influxdb/YZ_ZcJjfabM/4XWbKMbLAwAJ
for visitors from the future, cardinality refers to combinations *used* rather than combinations *possible* On Tuesday, August 9, 2016 at 5:12:28 PM UTC-4, Sam Hatchett wrote: > > I've searched for an answer to this specific question, but turned up > nothing specific. > > Is series cardinality affected by actual use, or by combinatorial math > alone? > > For example: > > metric,asset_id=abc,geohash=gbsuv7ztq > metric,asset_id=xyz,geohash=gbsuv7ztr > > ... in this schema, a series will have been generated by some asset > (important information), and that asset will have a location associated > with it. But, the location of each asset will be unique to that asset > alone. Asset 'abc' will never be located somewhere else and therefore will > only ever have that one geohash. This is relational data, of course, which > I am trying to shoehorn into a time-series database - but only for the sake > of getting data plotted in Grafana's new WorldMap panel. > > Any clarification of cardinality in this situation would be helpful. I'm > expecting to have ~200k assets (and therefore ~200k geohashes) at maximum. > Alternatively, if anyone has more experience with geohashing for grafana or > can point me to resources, I'd be very grateful. > -- 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/17554139-2929-4b00-8f0b-80c20e2c76a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
