Bug #30350 time field in ndb_logevent struct retreived by ndb_logevent_get_next() always 0
Submitted: 10 Aug 2007 8:34 Modified: 20 Aug 2007 9:09
Reporter: Hartmut Holzgraefe Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: NDB API Severity:S3 (Non-critical)
Version:mysql-5.1 OS:Linux
Assigned to: CPU Architecture:Any
Tags: 5.0, 5.1
Triage: Triaged: D3 (Medium)

[10 Aug 2007 8:34] Hartmut Holzgraefe
Description:
unless i'm doing something completely wrong the log_event.time field is never filled with any data and so just 0 which makes it completely meaningless

How to repeat:
see attached test program that sends an "ALL DUMP 1000" to the cluster and prints the results, the Time: output is always 0

Suggested fix:
fill the time field with real values
[10 Aug 2007 8:37] Hartmut Holzgraefe
test program

Attachment: mgm_dump1000-0.2.tar.gz (application/x-gunzip, text), 299.51 KiB.

[9 Jan 2009 18:25] Magnus BlÄudd
The time field is send from ndb_mgmd and set to 0 in mgmsrv/Services.cpp