Proposal:
By adding a getter for the timestamp a developer can get more control on handling data points.
E.g. on handling the storing and retry of points in case of an not reachable InfluxDB.
Current behavior:
getter does not exists and value is private / class is final so there is no nice way to access the value
Desired behavior:
Calling point.getTime() to get the Timestamp
Alternatives considered:
Not declaring the Point class as final would allow to extend the Point class
Use case:
In my case collect values from a number of APIs into Points on Android. Points are can either go live to the InfluxDB and/or be cached into a local DB to be send when the connection to the DB is possible. Using the Timestamp to identify the points would be very helpful.
Proposal:
By adding a getter for the timestamp a developer can get more control on handling data points.
E.g. on handling the storing and retry of points in case of an not reachable InfluxDB.
Current behavior:
getter does not exists and value is private / class is final so there is no nice way to access the value
Desired behavior:
Calling point.getTime() to get the Timestamp
Alternatives considered:
Not declaring the Point class as final would allow to extend the Point class
Use case:
In my case collect values from a number of APIs into Points on Android. Points are can either go live to the InfluxDB and/or be cached into a local DB to be send when the connection to the DB is possible. Using the Timestamp to identify the points would be very helpful.