Jira (PDB-4199) Puppet query - Issue with contents of arrays and type

Erik Hansen (JIRA)

unread,

Nov 28, 2018, 5:06:02 PM11/28/18

to puppe...@googlegroups.com

Erik Hansen created an issue

PuppetDB /

PDB-4199

Puppet query - Issue with contents of arrays and type

Issue Type:	Bug
Assignee:	Unassigned
Created:	2018/11/28 2:05 PM
Labels:	maintenance
Priority:	Normal
Reporter:	Erik Hansen

There seems to be an issue with the contents of Arrays and interpreting the type when processing a query. For instance this query worked in 2016.4.13:

curl -X POST -H 'Content-Type:application/json' http://localhost:8080/pdb/query/v4/nodes -d '{"query": ["in", ["fact", "uptime_seconds"], ["array",["20000.0","150.0", "300000"]]]}'

However in 2018.1.4 it returns an error:

"All values in array must be the same type."

The example comes from documentation here:

https://puppet.com/docs/puppetdb/6.0/api/query/v4/ast.html#array

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Erik Hansen (JIRA)

unread,

Nov 28, 2018, 5:33:03 PM11/28/18

to puppe...@googlegroups.com

Erik Hansen updated an issue

PuppetDB /

PDB-4199

Puppet query - Issue with contents of arrays and type

Change By:	Erik Hansen
Priority:	Normal Major

Add Comment

Austin Blatt (JIRA)

unread,

Jan 22, 2019, 1:20:04 PM1/22/19

to puppe...@googlegroups.com

Austin Blatt assigned an issue to Austin Blatt

PuppetDB /

PDB-4199

Puppet query - Issue with contents of arrays and type

Change By:	Austin Blatt
Assignee:	Austin Blatt

Add Comment

Austin Blatt (JIRA)

unread,

Jan 22, 2019, 1:49:03 PM1/22/19

to puppe...@googlegroups.com

Austin Blatt updated an issue

PuppetDB /

PDB-4199

Puppet query - Issue with contents of arrays and type

Change By:	Austin Blatt
Release Notes Summary:	Previously PuppetDB threw the error 'All values in array must be the same type' when querying using the in operator with an array of fact values for any array that did not have just one element. Now PuppetDB won't error on an array of fact values unless there's an actual type mismatch among the values.
Release Notes:	Bug Fix