Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-1390 Underscore separated field name is required in one context dash separated in another Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1390 Underscore separated field name is required in one context dash separated in another Change By: Ryan Senior Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1390 Underscore separated field name is required in one context dash separated in another Change By: Steve Barlow Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1390 Underscore separated field name is required in one context dash separated in another Change By: Ryan Senior Sprint: PuppetDB 2015-04-22 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title
Michal Ruzicka updated an issue
PuppetDB / PDB-1390
Underscore separated field name is required in one context dash separated in another
Change By:
Michal Ruzicka
Depending on context (on other parameters specified in a PDB request) PuppetDB sometimes requires an underscore separated field name other times a dash separated field name in the {{query}} parameter. See the following example queries and the corresponding responses returned by PuppetDB:* underscore separated field name - {{report_receive_time}} - required but dash separated name - {{report-receive-time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:24:21 GMTContent-Length: 369Server: Jetty(9.2.10.v20150310)'report-receive-time' is not a queryable object for events, known queryable objects are ["certname","configuration_version","containing_class","containment_path","environment","file","latest_report?","line","message","new_value","old_value","property","report","report_receive_time","resource_title","resource_type","run_end_time","run_start_time","status","timestamp"]{code}* underscore separated field name - {{report_receive_time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:26:40 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 5, "noops" : 1, "skips" : 2, "total" : 6}{code}* dash separated name - {{report-receive-time}} - required but underscore separated field name - {{report_receive_time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:31:04 GMTContent-Length: 76Server: Jetty(9.2.10.v20150310)< operator does not support object 'report_receive_time' for resource events{code}* dash separated name - {{report-receive-time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:31:59 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 2, "noops" : 1, "skips" : 0, "total" : 4}{code}Additional info:* apparently the difference is the use of the {{distinct_*}} parameters: when they are specified then the dash separated field name is required, otherwise the underscore separated fiel
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title
Michal Ruzicka updated an issue
PuppetDB / PDB-1390
Underscore separated field name is required in one context dash separated in another
Change By:
Michal Ruzicka
Depending on context (on other parameters specified in a PDB request) PuppetDB sometimes requires an underscore separated field name other times a dash separated field name in the {{query}} parameter. See the following example queries and the corresponding responses returned by PuppetDB:* underscore separated field name - {{report_receive_time}} - required but dash separated name - {{report-receive-time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:24:21 GMTContent-Length: 369Server: Jetty(9.2.10.v20150310)'report-receive-time' is not a queryable object for events, known queryable objects are ["certname","configuration_version","containing_class","containment_path","environment","file","latest_report?","line","message","new_value","old_value","property","report","report_receive_time","resource_title","resource_type","run_end_time","run_start_time","status","timestamp"]{code}* underscore separated field name - {{report_receive_time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:26:40 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 5, "noops" : 1, "skips" : 2, "total" : 6}{code}* dash separated name - {{report-receive-time}} - required but underscore separated field name - {{report_receive_time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:31:04 GMTContent-Length: 76Server: Jetty(9.2.10.v20150310)< operator does not support object 'report_receive_time' for resource events{code}* dash separated name - {{report-receive-time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:31:59 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 2, "noops" : 1, "skips" : 0, "total" : 4}{code}Additional notes info :* apparently the difference is the use of the {{distinct_*}} parameters: when they are specified then the dash separated field name is required, otherwise the underscore separ
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title
Michal Ruzicka updated an issue
PuppetDB / PDB-1390
Underscore separated field name is required in one context dash separated in another
Change By:
Michal Ruzicka
Depending on context (on other parameters specified in a PDB request) PuppetDB sometimes requires an underscore separated field name other times a dash separated field name in the {{query}} parameter. See the following example queries and the corresponding responses returned by PuppetDB:* underscore separated field name - {{report_receive_time}} - required but dash separated name - {{report-receive-time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:24:21 GMTContent-Length: 369Server: Jetty(9.2.10.v20150310)'report-receive-time' is not a queryable object for events, known queryable objects are ["certname","configuration_version","containing_class","containment_path","environment","file","latest_report?","line","message","new_value","old_value","property","report","report_receive_time","resource_title","resource_type","run_end_time","run_start_time","status","timestamp"]{code}* underscore separated field name - {{report_receive_time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:26:40 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 5, "noops" : 1, "skips" : 2, "total" : 6}{code}* dash separated name - {{report-receive-time}} - required but underscore separated field name - {{report_receive_time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:31:04 GMTContent-Length: 76Server: Jetty(9.2.10.v20150310)< operator does not support object 'report_receive_time' for resource events{code}* dash separated name - {{report-receive-time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:31:59 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 2, "noops" : 1, "skips" : 0, "total" : 4}{code}Additional notes : * apparently the difference is the use of the {{distinct_*}} parameters: when they are specified then the dash separated field name is required, otherwise the underscore separated f
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title
Michal Ruzicka updated an issue
PuppetDB / PDB-1390
Underscore separated field name is required in one context dash separated in another
Change By:
Michal Ruzicka
Depending on context (on other parameters specified in a PDB request) PuppetDB sometimes requires an underscore separated field name other times a dash separated filed field name in the {{query}} parameter. See the following example queries and the corresponding responses returned by PuppetDB:* underscore separated filed field name - {{report_receive_time}} - required but dash separated name - {{report-receive-time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:24:21 GMTContent-Length: 369Server: Jetty(9.2.10.v20150310)'report-receive-time' is not a queryable object for events, known queryable objects are ["certname","configuration_version","containing_class","containment_path","environment","file","latest_report?","line","message","new_value","old_value","property","report","report_receive_time","resource_title","resource_type","run_end_time","run_start_time","status","timestamp"]{code}* underscore separated filed field name - {{report_receive_time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:26:40 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 5, "noops" : 1, "skips" : 2, "total" : 6}{code}* dash separated name - {{report-receive-time}} - required but underscore separated filed field name - {{report_receive_time}} - specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report_receive_time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad RequestDate: Fri, 03 Apr 2015 23:31:04 GMTContent-Length: 76Server: Jetty(9.2.10.v20150310)< operator does not support object 'report_receive_time' for resource events{code}* dash separated name - {{report-receive-time}} - required and specified{code}curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'distinct_resources=true' --data-urlencode 'distinct_start_time=2015-04-02T21:48:24Z' --data-urlencode 'distinct_end_time=2015-04-03T21:48:24Z' --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 200 OKDate: Fri, 03 Apr 2015 23:31:59 GMTContent-Type: application/json; charset=utf-8Content-Length: 84Server: Jetty(9.2.10.v20150310){ "successes" : 1, "failures" : 2, "noops" : 1, "skips" : 0, "total" : 4}{code}Additional notes* apparently the difference is the use of the {{distinct_*}} parameters: when they are specified then the dash separated field name is required, oth
Jira (PDB-1390) Underscore separated field name is required in one context dash separated in another
Title: Message Title Michal Ruzicka created an issue PuppetDB / PDB-1390 Underscore separated field name is required in one context dash separated in another Issue Type: Bug Assignee: Unassigned Created: 2015/04/03 4:43 PM Priority: Major Reporter: Michal Ruzicka Depending on context (on other parameters specified in a PDB request) PuppetDB sometimes requires an underscore separated field name other times a dash separated filed name in the query parameter. See the following example queries and the corresponding responses returned by PuppetDB: underscore separated filed name - report_receive_time - required but dash separated name - report-receive-time - specified curl -i -gG http://localhost:8080/v4/aggregate-event-counts --data-urlencode 'query=["<","report-receive-time","2015-04-03T21:48:24Z"]' --data-urlencode 'summarize_by=containing_class' HTTP/1.1 400 Bad Request
