3

I have a very basic setup, in which I never get any output if I use the TIMESTAMP BY statement.

I have a stream analytics job which is reading from Event Hub and writing to the table storage.

The query is the following:

SELECT
    * 
INTO
    MyOutput
FROM
    MyInput TIMESTAMP BY myDateTime;

If the query uses timestamp statement, I never get any output events. I do see incoming events in the monitoring, there are no errors neither in monitoring nor in the maintenance logs. I am pretty sure that the source data has the right column in the right format.

If I remove the timestamp statement, then everything is working fine. The reason why I need the timestamp statement in the first place is because I need to write a number of queries in the same job, writing various aggregations to different outputs. And if I use timestamp in one query, I am required to use it in all other queries itself.

Am I doing something wrong? Perhaps SELECT * does not play well with TIMESTAMP BY? I just did not find any documentation explaining that...

4

1 回答 1

2

{"myDateTime":"2015-08-02T10:59:02.0000000Z", "EventEnqueuedUtcTime":"2015-08-07T10:59:07.6980000Z"}

延迟容忍窗口：00.00:00:05

您的所有事件都被视为迟到，因为 myDateTime 比 EventEnqueuedUtcTime 早 5 天。您能否尝试发送 myDateTime 为 UTC 且为“现在”的新事件，以便它在几秒钟内匹配？

另外，当您开始工作时，您选择的工作开始日期时间是什么？你能确保在 myDateTime 值之前选择一个日期吗？你可以先试试这个。

于 2015-08-07T13:18:33.340 回答