Akumuli icon indicating copy to clipboard operation
Akumuli copied to clipboard

What is going on ? no response on counting

Open jaffa4 opened this issue 7 years ago • 1 comments

Hi,

I do not seem to get back any data. Here is the log. 2018-05-06 10:45:24,852 Main [INFO] Parsing query: 2018-05-06 10:45:24,852 Main [INFO] { "range": { "from": "18700102T123000.000000", "to": "20200102T123010.000000" }, "aggregate": { "close": "count" } }

2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,853 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Can't open next iterator because not found 2018-05-06 10:45:24,854 Main [TRACE] Unexpected aggregate size 0 2018-05-06 10:45:24,864 http [INFO] Cursor 140499117708672 done 2018-05-06 10:45:24,864 http [INFO] Cursor 140499117708672 destroyed

The response did not return data.

jaffa4 avatar May 06 '18 11:05 jaffa4

The timestamp should be a Unix timestamp with nanosecond precision. It can be represented using the short ISO8601 format or as an integer. But despite the format used it's still a Unix timestamp. This means that the dates before Unix epoch (Jan-1 1970) can't be represented. The behavior that you've experienced is not OK, this should generate an error. I'll fix this eventually. You can use a smaller range to get the data back.

Lazin avatar May 06 '18 14:05 Lazin