- Más nuevo
- Más votos
- Más comentarios
Hi James, I am Victor from the Timestream PM team, we would love to learn more about your issue, would you please file a customer support ticket so we can follow up from there?
Thanks
Victor
Hi James, unfortunately Timestream as a service only supports seconds offset from Epoch. Are you planning to do time series analysis going all the way back to late 1800s?
Hi Victor, we are yes, we are using it to store historical and current prices for gold and other precious metals..
Oh ok, I get it. Even when you could use multi-measure records since it provides support for having a timestamp as a measure, by doing so you will miss on most of the benefits of indexing on the time column offered by Timestream. Sadly there is not much we can do at this time, but if you file a customer support ticket we will be able to track it and reach out to you in the future if some work around becomes available. My apologies for not being able to help you at this time and thank you for reaching out.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
Hi Victor, actually I think I worked around this original issue, my fault as I hadn't noticed an error.. But it has lead to another related problem, very similar. When adding data from pre 1970 (epoch), the data is rejected, even if we try and add a time with a minus value, for example adding the time with value:
-2169358250000 (Thu Apr 04 1901 16:29:10)
We're trying to add historical (and live) precious metal prices to timestream..