Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Austin Blatt Fix Version/s: PDB 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Kenn Hussey Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Robert Roland Fix Version/s: PDB 6.0.2 Fix Version/s: PDB 5.2.7 Fix Version/s: PDB 5.1.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Robert Roland Release Notes Summary: When an invalid / malformed timestamp was passed in a PQL query, it was treated as a null, giving back an unexpected query result. The timestamp is now validated, and an error is returned to the user. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4015 Look into behavior of how pql parses datetimes Change By: Robert Roland Assignee: Robert Roland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title Austin Blatt commented on PDB-4015 Re: Look into behavior of how pql parses datetimes I believe the timestamp ending in Z is the format we get from Puppet right now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4015) Look into behavior of how pql parses datetimes
Title: Message Title
Zachary Kent created an issue
PuppetDB / PDB-4015
Look into behavior of how pql parses datetimes
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/08/21 5:12 PM
Priority:
Normal
Reporter:
Zachary Kent
It looks like the parser used for pql queries here will fail silently if unable to parse a datetime string in a pql query. This results in the query being built up getting NULL values for the params which are supposed to contain a datetime. We should figure out if this is the intended behavior or if it would make more sense to return a validation error to the person making the query. You can reproduce this issue by setting up pdb with some fake data using the benchmark command. Then make sure to restart your postgres instance with the log_statement setting set to 'all' in the postgres.conf file. Then look at the differences in output from the queries below. Invalid datetime string:
puppet-query "nodes { catalog_timestamp > '2018-08-15 21:11:21 UTC'}"
valid datetime string:
puppet-query "nodes { catalog_timestamp > '2018-08-15 21:11:21Z'}"
