Jira (PDB-3278) Recieved time should be left as an object for the CommandRef

[Ryan Senior (JIRA)]

Ryan Senior created an issue

PuppetDB / PDB-3278 Recieved time should be left as an object for the CommandRef Issue Type: Task Assignee: Unassigned Created: 2017/01/26 6:39 AM Labels: maintenance Priority: Normal Reporter: Ryan Senior Switch the queue code to leave the received timestamp as an object, rather than converting it to a string before enqueueing it in the channel. A recent change added another timestamp field to the header (producer timestamp) and having the timestamp as a string was bad for that field as it can't be compared with other timestamps unless it's re-parsed. Now the CommandRef is inconsistent in that it has one string timestamp (received) and one object timestamp (producer). Having received as an object is more useful, consistent and is probably more efficient. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Ryan Senior (JIRA)]

Ryan Senior updated an issue

PuppetDB / PDB-3278 Recieved time should be left as an object for the CommandRef

Change By: Ryan Senior Sprint: Hopper

Add Comment

[Ryan Senior (JIRA)]

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3278 Recieved time should be left as an object for the CommandRef

Change By: Russell Mull Sprint: Hopper

Add Comment

[Zachary Kent (Jira)]

Zachary Kent updated an issue

PuppetDB / PDB-3278 Recieved time should be left as an object for the CommandRef

Change By: Zachary Kent Labels: maintenance needs-investigation

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)