Micro second and nano second precision on stored in custom timestamp field

[ShivaniSK]

Hi @alex-karpovich
We currently have data in below format where timestamp is having microseconds / nanoseconds data.

<style> </style>

timestamp	symbol	price
2024-10-10T08:20:23.632832Z	ABC	1
2024-10-10T08:20:23.632913Z	ABC	2
2024-10-10T08:20:23.633106Z	ABC	1

On executing below query over the data

select LAST{} (price) as priceAgg, LAST{} (timestamp) as timestampOriginal   
            from market_trades OVER TIME(1ms) 
            WHERE timestamp BETWEEN '2024-10-10 08:20:23.632'd and '2024-10-10 08:20:23.633'd 
and symbol == 'ABC' AND price is NOT NULL

Expected output:

<style> </style>

timestamp	price	timestampOriginal
2024-10-10T08:20:23.633Z	2	2024-10-10T08:20:23.632913Z
2024-10-10T08:20:23.634Z	1	2024-10-10T08:20:23.633106Z

Actual Output:

<style> </style>

timestamp	price	timestampOriginal
2024-10-10T08:20:23.633Z	2	2024-10-10T08:20:23.632Z
2024-10-10T08:20:23.634Z	1	2024-10-10T08:20:23.633Z

As can be seen, the "timestampOriginal" column is not giving the complete microsecond level time. Its giving data only upto milliseconds.

Can you please help us out.
We want to have the original precision of timestamp, even when we are performing aggregations.

Regards,
Shivani

[alex-karpovich]

please share schema of the stream

[ShivaniSK]

Hi @alex-karpovich ,
The timestamps mentioned above looks like "2024-10-10T08:20:23.632832Z" 10/10/2024 08:20:23.632832 AM on the timebase webadmin.

the market_trades has below columns
-> timestamp is the TimeBase internal field
-> symbol is Timebase internal field
-> price is FLOAT DECIMAL64

[alex-karpovich]

Please use temp workaround

select LAST{} (price) as priceAgg, LAST{} (timestampNs) as timestampOriginal   
            from market_trades OVER TIME(1ms) 
            WHERE timestamp BETWEEN '2024-10-10 08:20:23.632'd and '2024-10-10 08:20:23.633'd 
and symbol == 'ABC' AND price is NOT NULL

in next version it will be fixed