Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why is EventHub enqueued_time of type `Optional[datetime.datetime]`?
See original GitHub issueI’m using EventHubConsumerClient and when reading on_event, enqueued_time is a requirement for our system to use timestamp state and manage progress.
Does the IotHub always return event objects with an enqueued_time?
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
EventData.EnqueuedTime Property - Microsoft Learn
DateTimeOffset. This value is read-only and will only be populated for events that have been read from Event Hubs. The default value when...
Read more >Source code for azure.eventhub._common - NET
:param body: The data to send in a single message. body can be type of str or ... def enqueued_time(self): # type: ()...
Read more >Can a date and time be specified when sending data to Azure ...
A possible solution would be to write the Event Hub data to an Azure SQL server or blob storage for long term storage....
Read more >Azure Event Hubs | Databricks on AWS
To connect to your EventHubs, an EntityPath must be present. ... The position can be an enqueued time, offset, sequence number, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
thanks, appreciate the quick response.
Hi @deeTEEcee. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “
/unresolve” to remove the “issue-addressed” label and continue the conversation.