did you have a memory issue ?
do you have records with the same filename and date
or is the date always unique for a given filename ?
If you have duplicate values there , the timestamp is not useless
because it will prevent your duplicate records to be overwritten.
If you don’t have duplicates , you could parse the file so that the date becomes the timestamp ,
I have still not “memory issues”, but I am just trying to optimize memory consuming of InfluxDB.
To answer your question:
do you have records with the same filename and date --> NO
or is the date always unique for a given filename ? --> YES
BUT date is not unique, so it can’t be the timestamp, this were my first try indeed.
But what is the unique key for your data when it’s not the time and not the filename? What are the metrics you’re going to keep and retrieve? You can use the date to construct the timestamp for InfluxDB and use the filename to build the series. That way you could say retrieve the number of files with timestamp in Feb 28, or whatever.
My suggestion is to convert your date to a timestamp, like for midnight on that date. You build metrics like this to write
data,file= obs=1
It’s a bit artificial since you don’t really have anything to measure and don’t really have time series (with multiple observations per series over time). Would be different if you were dealing with size= for example, and wanted to report the amount of date by month or so.
If this is all you need, then a generic NoSQL database like mongodb would be a more obvious choice.