Jira (PDB-5547) Support scheduling GC pieces independently
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5547 Support scheduling GC pieces independently Change By: Austin Blatt Epic Link: PE-34842 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.470477.1664997398000.1737.1687300560032%40Atlassian.JIRA.
Jira (PDB-5552) Improve the removal of old reports partitions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5552 Improve the removal of old reports partitions Change By: Austin Blatt Fix Version/s: 2023.y Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472746.1666299365000.4173.1685645640336%40Atlassian.JIRA.
Jira (PDB-5599) Remove catalog resources pg_trgm index on file path
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5599 Remove catalog resources pg_trgm index on file path Change By: Austin Blatt Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481564.1676566129000.2164.1685031180051%40Atlassian.JIRA.
Jira (PDB-5599) Remove catalog resources pg_trgm index on file path
Title: Message Title
Austin Blatt commented on PDB-5599
Re: Remove catalog resources pg_trgm index on file path
This is an extraordinarily expensive index to maintain. From support in Slack regarding a customer:
Their catalog_resources_file_trgm index is 58 GB in size, which is over 33% of the total PuppetDB database size and it's been used 0 times
pg_stat_user_indexes: https://www.postgresql.org/docs/11/monitoring-stats.html#PG-STAT-ALL-INDEXES-VIEW relid | indexrelid | schemaname | relname | indexrelname | idx_scan | idx_tup_read | idx_tup_fetch -{}+{}{}{}{}{}---{}{}{}{}--{}{}--{}{}- 17540 | 18381 | public | catalog_resources | catalog_resources_file_trgm | 0 | 0 | 0
14:56 5571717074944 disk blocks have been read from that index though, so it seems like autovaccuum and autoanalyze have spent 5.5 TB in just read I/O to keep it maintained. Probably more in write. 15:08 Well, hopefully 5.5 TB if postgres means 1 kB file system blocks by "disk blocks". If it's counting 8 kB Postgres pages, then that's 44 TB in read 15:28 Postgres slack confirms it's counting the 8 kB database pages
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
--
You received this message because you are subscribed to the Go
Jira (PDB-5632) Accommodate statement timeouts (opt-out, etc.) in sync
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5632 Accommodate statement timeouts (opt-out, etc.) in sync Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484717.1682107165000.12157.1683738240340%40Atlassian.JIRA.
Jira (PDB-5632) Accommodate statement timeouts (opt-out, etc.) in sync
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5632 Accommodate statement timeouts (opt-out, etc.) in sync Change By: Austin Blatt Fix Version/s: PDB 8.0.1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484717.1682107165000.12156.1683738240293%40Atlassian.JIRA.
Jira (PDB-5642) Slow PQL parsing does not always log
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5642 Slow PQL parsing does not always log Change By: Austin Blatt Affects Version/s: PDB 7.11.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485143.1683047013000.10199.1683047640027%40Atlassian.JIRA.
Jira (PDB-5642) Slow PQL parsing does not always log
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5642 Slow PQL parsing does not always log Issue Type: Bug Assignee: Austin Blatt Created: 2023/05/02 10:03 AM Priority: Normal Reporter: Austin Blatt It was put behind the log-queries configuration option, but it should always warn users when they have slow PQL. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5616) Draft release notes (Puppet Platform 7.24.0)
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5616 Draft release notes (Puppet Platform 7.24.0) Change By: Austin Blatt Fix Version/s: PDB n/a Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483611.1679700064000.7584.1682112000104%40Atlassian.JIRA.
Jira (PDB-5485) Move to github actions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5485 Move to github actions Change By: Austin Blatt Fix Version/s: PDB n/a Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444744.1650904924000.7583.168211241%40Atlassian.JIRA.
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Change By: Austin Blatt Assignee: Rob Browning Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484458.1681765167000.7309.1682035620026%40Atlassian.JIRA.
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Austin Blatt assigned an issue to Rob Browning PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Change By: Austin Blatt Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.484458.1681765167000.6449.1681837920022%40Atlassian.JIRA.
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Change By: Austin Blatt Problem: On RedHat-based OSes, PuppetDB fails to start after upgrading from Platform 7 to Platform 8. EZBake controls which java we run with by setting JAVA_BIN to /usr/bin/java in our service defaults. On Debian and Redhat (at least), this is actually a symlink to java controlled by update-alternatives and alternatives respectively. RedHat's Java 8 package still has a higher alternatives priority than Java 11, so even though our PuppetDB 8 packages install java 11, the symlink at /usr/bin/java is not updated and we continue trying to use java 8. This breaks because HikariCP was updated to a version that does not run on java 8 anymore. It is also possible that we would hit this on Debian-based OSes on any installation where an admin has manually selected java 8. This does not affect PE because the hard-coded path in EZBake is to pe-java and not a java managed by update-alternatives.Option 1: Guide users through the problem manually with documentation. On RedHat, they could be instructed to install java 11 and select it as the preferred java. Con: module upgrades will not work without manual intervention.Option 2: We can use the output of the alternatives cli tools to "sniff" out available java versions and select one that will work for us even if the user has an incompatible java selected as the default java. In this case we would remove EZBake's hard-coded JAVA_BIN setting, but allow users to override the sniffing by setting JAVA_BIN themselves (this will also maintain their ability to use a java that is not registered with the alternatives programs.Open questions: SLES? Add Comment
Jira (PDB-5630) RHEL Platform 7 to Platform 8 upgrade failure
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5630 RHEL Platform 7 to Platform 8 upgrade failure Issue Type: Bug Assignee: Unassigned Created: 2023/04/17 1:59 PM Priority: Normal Reporter: Austin Blatt Problem: On RedHat-based OSes, PuppetDB fails to start after upgrading from Platform 7 to Platform 8. EZBake controls which java we run with by setting JAVA_BIN to /usr/bin/java in our service defaults. On Debian and Redhat (at least), this is actually a symlink to java controlled by update-alternatives and alternatives respectively. RedHat's Java 8 package still has a higher alternatives priority than Java 11, so even though our PuppetDB 8 packages install java 11, the symlink at /usr/bin/java is not updated and we continue trying to use java 8. This breaks because HikariCP was updated to a version that does not run on java 8 anymore. It is also possible that we would hit this on Debian-based OSes on any installation where an admin has manually selected java 8. Add Comment
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4937 Add a default statement timeout to user queries Change By: Austin Blatt Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.375530.1603302604000.4877.1681323060197%40Atlassian.JIRA.
Jira (PDB-5611) Remove legacy fact usage from PuppetDB module
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5611 Remove legacy fact usage from PuppetDB module Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482931.1678895661000.4505.1681251060247%40Atlassian.JIRA.
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt Sprint: Skeletor 04/12/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3302.1680725460020%40Atlassian.JIRA.
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt The puppetdb acceptance tests on PR are failing and have been for quite some time [https://jenkins-enterprise new HikariCP version requires Java 11+ . delivery.puppetlabs.net/job/enterprise_puppetdb_integration-system-puppetdb_pr-main/] The issue appears to be related to [https://github.com/puppetlabs/puppetdb/pull/3791] a pr which unpinned Many of the hikari library PuppetDB packages still depend on Java 8, but they should depend on Java 11 or Java 17 . Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3298.16807254
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3299.1680725400104%40Atlassian.JIRA.
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3301.1680725400196%40Atlassian.JIRA.
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3300.1680725400148%40Atlassian.JIRA.
Jira (PDB-5622) PuppetDB 8 package need java 11+
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5622 PuppetDB 8 package need java 11+ Change By: Austin Blatt Summary: Puppetdb acceptance test failures PuppetDB 8 package need java 11+ Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483790.1680130559000.3297.1680725220020%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt commented on PDB-5613 Re: Drop PSON or at least don't call it by default PR is here https://github.com/puppetlabs/puppetdb/pull/3772 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.3022.1679596860020%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Austin Blatt Sprint: Skeletor 03/29/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.3020.1679596800030%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt commented on PDB-5613 Re: Drop PSON or at least don't call it by default Pulling this into the current sprint because PuppetDB rspec and integration tests started failing due to the removal of to_pson. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.3021.1679596800077%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.3019.1679596740097%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Austin Blatt Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.3018.1679596740033%40Atlassian.JIRA.
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Austin Blatt Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.2967.1679589300024%40Atlassian.JIRA.
Jira (PDB-5582) Remove metrics/v1 references
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5582 Remove metrics/v1 references Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.2717.1679516700023%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 Please take these results very loosely, they were produced on a laptop. Migration results running migrations 81 and 82 0 reports - 81ms 6,720 reports - 135ms 35,500 reports - 185ms 67,200 reports - 188ms There is some impact in migration time when more data is added, but it may even tail off as you get more data in a partition. Even if we ignore the final run with 67k nodes, extrapolating from the first three data points linearly puts 67.2 million reports (100k nodes with a run interval of 30 minutes and a history of 14 days) at 172 seconds — or just under 3 minutes. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480704.1675468795000.2715.1679516400029%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 Noticed a 2 index difference between the new and old version. Partitions have a primary key, which is expected, but there also appears to be a duplicate index being created (at least by the migration). This was run against an brand new postgres 15.2, where the bug was supposed to have been fixed. "reports_20230318z_encode_producer_timestamp_idx" UNIQUE, btree (encode(hash, 'hex'::text), producer_timestamp) "reports_hash_expr_idx_20230318z" UNIQUE, btree (encode(hash, 'hex'::text)) the id index is also not removed in the migration, but does not continue into a newly created partition. "idx_reports_id_20230318z" UNIQUE, btree (id) These issues go away for new partitions, so I don't know how big of an issue they are. Add Comment
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Austin Blatt Epic Link: PE- 34946 34738 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483168.1679088965000.2184.1679431260090%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5589 Investigate pdb upgrade times with migration 81/82 Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480704.1675468795000.1109.1678913880205%40Atlassian.JIRA.
Jira (PDB-5612) Update PuppetDB acceptance tests for Platform 8
Title: Message Title Austin Blatt moved an issue PuppetDB / PDB-5612 Update PuppetDB acceptance tests for Platform 8 Change By: Austin Blatt Key: PE PDB - 35623 5612 Issue Type: Improvement Task Project: Puppet Enterprise [Internal] PuppetDB Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482934.1678896009000.824.1678896060032%40Atlassian.JIRA.
Jira (PDB-5611) Remove legacy fact usage from PuppetDB module
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5611 Remove legacy fact usage from PuppetDB module Change By: Austin Blatt Epic Link: PE-34738 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482931.1678895661000.822.1678895880023%40Atlassian.JIRA.
Jira (PDB-5611) Remove legacy fact usage from PuppetDB module
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5611 Remove legacy fact usage from PuppetDB module Issue Type: Improvement Assignee: Unassigned Created: 2023/03/15 8:54 AM Priority: Normal Reporter: Austin Blatt The FOSS PuppetDB module, which is used in our internal testing for PuppetDB and Puppetserver, uses legacy facts which are being removed from Puppet 8. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5610) pg_dump with -j flag can conflict with PuppetDB report garbage collection
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5610 pg_dump with -j flag can conflict with PuppetDB report garbage collection Issue Type: Bug Assignee: Austin Blatt Created: 2023/03/15 8:40 AM Priority: Normal Reporter: Austin Blatt FOSS PuppetDB instances running against PG <14 will still perform a default hourly GC that gets an access exclusive lock on reports and would conflict with pg_dump Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 I'm not too worried about time to upgrade PE (famous last words...). I think all our operations are "move" operations, the alter table commands all look to be commands that are not table rewriting. But checking indexes and query performance after the upgrade would be good. I do not know if we still have the data around for Locust, but running all those queries would be a good start. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.480704.1675468795000.809.1678894560073%40Atlassian.JIRA.
Jira (PDB-5582) Remove metrics/v1 references
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5582 Remove metrics/v1 references Change By: Austin Blatt Summary: Remove /rework/redirect metrics/v1 references Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.4293.1678398180022%40Atlassian.JIRA.
Jira (PDB-5605) Remove 6.x pipelines
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5605 Remove 6.x pipelines Change By: Austin Blatt Sprint: Skeletor 03/15/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482178.1677865919000.4290.1678398060025%40Atlassian.JIRA.
Jira (PDB-5582) Remove/rework/redirect metrics/v1 references
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5582 Remove/rework/redirect metrics/v1 references Change By: Austin Blatt Remove references to metrics v1.There are some example curl commands that need to be updated.The list of useful metrics provided in the v1 docs should be moved to the v2 docs. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.4289.167839826%40Atlassian.JIRA.
Jira (PDB-5582) Remove/rework/redirect metrics/v1 references
Title: Message Title Austin Blatt assigned an issue to Unassigned PuppetDB / PDB-5582 Remove/rework/redirect metrics/v1 references Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.4288.1678397880025%40Atlassian.JIRA.
Jira (PDB-5582) Remove/rework/redirect metrics/v1 references
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5582 Remove/rework/redirect metrics/v1 references Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479640.1674756239000.4287.1678397340247%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Release Notes Summary: Improved speed of queries that filter based on giant arrays. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3916.1678302240073%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3914.1678302180072%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt commented on PDB-3171 Re: query compilation is very slow for queries with giant arrays Same set of old failures on main, so I'll say that's "good enough". Unfortunately, due to the state of internal CI, that's likely the best we can get right now. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3912.1678302120024%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Fix Version/s: PDB 7.12.2 Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3909.1678302000247%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt commented on PDB-3171 Re: query compilation is very slow for queries with giant arrays Promoted into main as 2023.1.0-rc1-92-g7108a7f, tests look green except some ones that have been persistently red for weeks. Promoted into 2021.7.x as 2021.7.3-rc1-77-g6c56868, waiting to see results of pe-integration tests, which are still running Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3854.1678294440024%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt commented on PDB-3171 Re: query compilation is very slow for queries with giant arrays This has successfully promoted to 2021.7 and main. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.3695.1678243860018%40Atlassian.JIRA.
Jira (PDB-5592) Generating catalog data
Title: Message Title Austin Blatt commented on PDB-5592 Re: Generating catalog data I think I was likely just thinking we need a way to control the output size, and for this first pass we can just focus on one. Since the PR has function args for for number of resources, and their sizes I think it's ok if total catalog size is an "output" rather than a specific configurable variable. I had totally forgotten about the "contains" edge... that's likely to be the dominant edge size I'll spin up a PE to check. I was thinking of depth as, there might be a difference between 9 edges as "resources 2 through 10 require resource 1" vs. 9 edges as "resource 1 thru 10 all require the previous resource". If contains is the dominant edge size, and there's no way to query for "depth", then it may only be edge number that matters and the other types are (at least for now) unnecessary. I am not that familiar with how defined types are modeled in Puppet, but there's no version of a defined type in PuppetDB afaik, so it is likely a Class (I think...). Type and Title are likely the two most important "sizes" since they are indexed together, so yeah the length of a defined type's namespace could be important to model. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481307.1676309101000.3300.1678142820023%40Atlassian.JIRA.
Jira (PDB-5605) Remove 6.x pipelines
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5605 Remove 6.x pipelines Issue Type: Task Assignee: Austin Blatt Created: 2023/03/03 9:51 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482178.1677865919000.2969.16778
Jira (PDB-5598) SPIKE - Test if Patroni can increase the number of queries we can support
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5598 SPIKE - Test if Patroni can increase the number of queries we can support Change By: Austin Blatt Epic Link: PE-35436 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481563.1676566083000.2788.1677793560021%40Atlassian.JIRA.
Jira (PDB-5601) Jetty threadpool can be exhausted by commands stuck behind concurrent-writes semaphore
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5601 Jetty threadpool can be exhausted by commands stuck behind concurrent-writes semaphore Change By: Austin Blatt Epic Link: PE-35436 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481652.1676576795000.2787.1677793500097%40Atlassian.JIRA.
Jira (PDB-5597) Cancellable queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5597 Cancellable queries Change By: Austin Blatt Epic Link: PE-35436 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481562.1676566046000.2786.1677793500044%40Atlassian.JIRA.
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4937
Add a default statement timeout to user queries
Change By:
Austin Blatt
Remaining questions* What is the default statement timeout for a query? 1min, 5min, 10min?JDBC does _not_ respect Thread interrupts so we could implement this by tracking running jdbc queries and calling JDBC's Statement.cancel() method.Alternatively, and likely preferably, we can use statement timeouts to abort a query after a set time. Either by using setQueryTimeout (or setQueryTimeoutMs), and allow pgjdbc to handle things from there (see https://github.com/pgjdbc/pgjdbc/blob/5c78edb1412467636f996416ad37118f651db86e/pgjdbc/src/test/java/org/postgresql/test/jdbc2/StatementTest.java#L737-L762 for an example).Or, we can set explicit statement timeouts in the SQL if the above does not work{code} puppetdb-> SET statement_timeout TO 1 I puppetdb-> ;SET I puppetdb=> select pg_sleep(2);ERROR: canceling statement due to statement timeout{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-4937) Add a default statement timeout to user queries
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4937
Add a default statement timeout to user queries
Change By:
Austin Blatt
Remaining questions* What is the default statement timeout for a query? 1min, 5min, 10min? JDBC does _not_ respect Thread interrupts so we could implement this by tracking running jdbc queries and calling JDBC's Statement.cancel() method.Alternatively, and likely preferably, we can use statement timeouts to abort a query after a set time. Either by using setQueryTimeout (or setQueryTimeoutMs), and allow pgjdbc to handle things from there (see https://github.com/pgjdbc/pgjdbc/blob/5c78edb1412467636f996416ad37118f651db86e/pgjdbc/src/test/java/org/postgresql/test/jdbc2/StatementTest.java#L737-L762 for an example).Or, we can set explicit statement timeouts in the SQL if the above does not work{code}SET statement_timeout TO 1 I puppetdb-> ;SET I puppetdb=> select pg_sleep(2);ERROR: canceling statement due to statement timeout{code}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt assigned an issue to Nick Lewis PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Assignee: Rob Browning Nick Lewis Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.2366.1677697260031%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.2368.1677697320076%40Atlassian.JIRA.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Austin Blatt Team: PuppetDB Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.159741.1478279255000.2365.1677697200144%40Atlassian.JIRA.
Jira (PDB-5594) SPIKE - can we use clojure/data.generators
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5594 SPIKE - can we use clojure/data.generators Change By: Austin Blatt Fix Version/s: PDB n/a Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481309.1676309254000.1750.1677615720084%40Atlassian.JIRA.
Jira (PDB-5594) SPIKE - can we use clojure/data.generators
Title: Message Title Austin Blatt commented on PDB-5594 Re: SPIKE - can we use clojure/data.generators I think the simplicity of generating the catalog with some helper functions look good. It gives us flexibility over structuring the content of each field. I agree that the test check output looks too random, and given the simplicity of the example where we generate things ourselves it's probably not worth trying to cajole that library into producing the output we want. My thinking was that this tool doesn't need any level of reproducibility. Benchmark can load example commands from json sample data. By default it uses some that are checked in to the puppetdb repo https://github.com/puppetlabs/puppetdb/tree/main/resources/puppetlabs/puppetdb/benchmark/samples so I was envisioning running these generators to create sample files and then the tests could re-use those sample files until we feel the need to change some variable of the generated data. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481309.1676309254000.1748.1677615600020%40Atlassian.JIRA.
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5553 Remove foreign keys from report partitions Change By: Austin Blatt Fix Version/s: PDB 7.12.2 Fix Version/s: PDB 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.1565.1677606600020%40Atlassian.JIRA.
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5553 Remove foreign keys from report partitions Change By: Austin Blatt Release Notes: Not Needed Release Notes Summary: This has little user-facing effect, the improvement to partition management is probably better documented in the release note for switching to declarative partitioning. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.1562.1677606360020%40Atlassian.JIRA.
Jira (PDB-5602) Transient test failure in benchmark tests
Title: Message Title Austin Blatt commented on PDB-5602 Re: Transient test failure in benchmark tests My assumption is that the MacOS runners are slowing down to the point where it doesn't finish in the proper time-frame. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481880.1677267977000.1054.1677269280018%40Atlassian.JIRA.
Jira (PDB-5602) Transient test failure in benchmark tests
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5602 Transient test failure in benchmark tests Issue Type: Bug Assignee: Unassigned Created: 2023/02/24 11:46 AM Priority: Normal Reporter: Austin Blatt I've now seen this failure twice. Both times in our core+ext tests running on MacOS in Github. main / o (macos-10.15, core+ext/openjdk11/pg-11) (pull_request) 2023-02-24T19:18:54.7827060Z lein test :only puppetlabs.puppetdb.cli.benchmark-test/benchmark-runs-at-correct-rate 2023-02-24T19:18:54.7839610Z 2023-02-24T19:18:54.7840350Z FAIL in (benchmark-runs-at-correct-rate) (benchmark_test.clj:205) 2023-02-24T19:18:54.7840660Z expected: (<= 2.1 elapsed 3.9) 2023-02-24T19:18:54.7840880Z actual: (not (<= 2.1 3.946 3.9))
Jira (PDB-5603) Transient test failure in benchmark tests
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5603 Transient test failure in benchmark tests Issue Type: Bug Assignee: Unassigned Created: 2023/02/24 11:46 AM Priority: Normal Reporter: Austin Blatt I've now seen this failure twice. Both times in our core+ext tests running on MacOS in Github. main / o (macos-10.15, core+ext/openjdk11/pg-11) (pull_request) 2023-02-24T19:18:54.7827060Z lein test :only puppetlabs.puppetdb.cli.benchmark-test/benchmark-runs-at-correct-rate 2023-02-24T19:18:54.7839610Z 2023-02-24T19:18:54.7840350Z FAIL in (benchmark-runs-at-correct-rate) (benchmark_test.clj:205) 2023-02-24T19:18:54.7840660Z expected: (<= 2.1 elapsed 3.9) 2023-02-24T19:18:54.7840880Z actual: (not (<= 2.1 3.946 3.9))
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Austin Blatt commented on PDB-5553 Re: Remove foreign keys from report partitions added tests, this is ready for merge now Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.325.1676997540021%40Atlassian.JIRA.
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Austin Blatt commented on PDB-5553 Re: Remove foreign keys from report partitions I verified that removing the foreign key resulted in purging nodes failing to remove the reports. I pushed a fix for that issue, but it still needs a test as none of our existing ones failed. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.156.1676679900023%40Atlassian.JIRA.
Jira (PDB-5598) SPIKE - Test if Patroni can increase the number of queries we can support
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5598 SPIKE - Test if Patroni can increase the number of queries we can support Change By: Austin Blatt If we need to scale queries, adding read-only mirrors of our primary postgres may help reduce contention. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481563.1676566083000.11073.1676578920028%40Atlassian.JIRA.
Jira (PDB-5598) SPIKE - Test if Patroni can increase the number of queries we can support
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5598 SPIKE - Test if Patroni can increase the number of queries we can support Change By: Austin Blatt Summary: SPIKE - Test if Patroni can increase the number of queries we can support Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481563.1676566083000.11070.1676578200073%40Atlassian.JIRA.
Jira (PDB-5597) Cancellable queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5597 Cancellable queries Change By: Austin Blatt In order to provide a more "interactive" experience, the console will send queries as a user types. But once they type something else and the console sends an updated query, it will never use the previous result. Providing a way for the console to cancel an existing query would be beneficial.This could possibly be done by ensuring that a closed jetty connection cancels its query (similar to the spike ticket PDB-5600) Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481562.1676566046000.11068.1676578140029%40Atlassian.JIRA.
Jira (PDB-5596) Audit index usage
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5596 Audit index usage Change By: Austin Blatt Our indexes have accumulated over time, and some may not be necessary anymore. In addition to our own reasoning, and checking the git history for why they were added, we can get index usage statistics out Postgres from data gathered by PE support scripts to see which indexes are used most at customer sites. We should be sure to get scripts from multiple customers because their usage of PuppetDB may differ. Create tickets to remove any indexes we no longer need Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481561.1676566009000.11066.1676578020032%40Atlassia
Jira (PDB-5596) Audit index usage
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5596 Audit index usage Change By: Austin Blatt Our indexes have accumulated over time, and some may not be necessary anymore. In addition to our own reasoning, and checking the git history for why they were added, we can get index usage statistics out Postgres from data gathered by PE support scripts to see which indexes are used most at customer sites. We should be sure to get scripts from multiple customers because their usage of PuppetDB may differ.Create tickets to remove any indexes we no longer need /want Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481561.1676566009000.11067.1676578020082%40Atl
Jira (PDB-5596) Audit index usage
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5596 Audit index usage Change By: Austin Blatt Our indexes have accumulated over time, and some may not be necessary anymore. In addition to our own reasoning, and checking the git history for why they were added, we can get index usage statistics out Postgres from data gathered by PE support scripts to see which indexes are used most at customer sites. We should be sure to get scripts from multiple customers because their usage of PuppetDB may differ. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481561.1676566009000.11065.1676577960034%40Atlassian.JIRA.
Jira (PDB-5601) Jetty threadpool can be exhausted by commands stuck behind concurrent-writes semaphore
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5601 Jetty threadpool can be exhausted by commands stuck behind concurrent-writes semaphore Issue Type: Bug Assignee: Unassigned Created: 2023/02/16 11:46 AM Priority: Normal Reporter: Austin Blatt QoS filter Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5600) SPIKE - What happens to the database query if we lose the jetty connection
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5600 SPIKE - What happens to the database query if we lose the jetty connection Issue Type: Task Assignee: Unassigned Created: 2023/02/16 8:51 AM Priority: Normal Reporter: Austin Blatt Various PuppetDB clients (such as the console) use timeouts to cancel queries that take too long. That will close the jetty connection, but what happens to the PG connection and the running query? We would want that connection and the query operation to terminate as well. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5599) Remove catalog resources pg_trgm index on file path
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5599 Remove catalog resources pg_trgm index on file path Issue Type: Improvement Assignee: Unassigned Created: 2023/02/16 8:48 AM Priority: Normal Reporter: Austin Blatt CD4PE is no longer using this index (it was added for their queries) Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5598) SPIKE - Patroni
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5598 SPIKE - Patroni Issue Type: New Feature Assignee: Unassigned Created: 2023/02/16 8:48 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481563.1676566083000.10942.1676
Jira (PDB-5597) Cancellable queries
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5597 Cancellable queries Issue Type: New Feature Assignee: Unassigned Created: 2023/02/16 8:47 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481562.1676566046000.10941.
Jira (PDB-5596) Audit index usage
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5596 Audit index usage Issue Type: Task Assignee: Unassigned Created: 2023/02/16 8:46 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481561.1676566009000.10940.167656602
Jira (PDB-5595) Test PuppetDB Scaling
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5595 Test PuppetDB Scaling Issue Type: Epic Assignee: Unassigned Created: 2023/02/15 2:26 PM Priority: Normal Reporter: Austin Blatt Using the testing data generated in PDB-5590 (as well as benchmark, something to submit repeated queries to puppetdb, and p[erhaps the scale testing code written by Deepak & Noah) test PuppetDB to identify where our limitations are. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Austin Blatt commented on PDB-5553 Re: Remove foreign keys from report partitions Migration and its test are ready for review, I am investigating if the purge nodes GC operation needs modification as a result. I will also add a test if that is the case, given no tests are currently failing. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.10803.1676495880089%40Atlassian.JIRA.
Jira (PDB-5594) SPIKE - can we use clojure/data.generators
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5594 SPIKE - can we use clojure/data.generators Issue Type: Task Assignee: Unassigned Created: 2023/02/13 9:27 AM Priority: Normal Reporter: Austin Blatt The existing tool in Clojure that I know of is https://github.com/clojure/data.generators/ but I do not have any experience with it. Can we use it to generate data that matches the command wireformats that we need? Should we? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5592) Generating catalog data
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5592 Generating catalog data Issue Type: New Feature Assignee: Unassigned Created: 2023/02/13 9:25 AM Priority: Normal Reporter: Austin Blatt Number of classes (correlates to "source files" in a control-repo) Number of resources Number of resources Size of title string (this is indexed for queries, so its size is important) Total size of Catalog "Depth" of ordering edge DAG Add Comment
Jira (PDB-5593) Generating report data
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5593 Generating report data Issue Type: New Feature Assignee: Unassigned Created: 2023/02/13 9:25 AM Priority: Normal Reporter: Austin Blatt Events per report Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5591) Generating factset data examples
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5591 Generating factset data examples Issue Type: New Feature Assignee: Unassigned Created: 2023/02/13 9:24 AM Priority: Normal Reporter: Austin Blatt Should probably include the default facts, because they'll always be present, and are generally pretty static. Due to trigram indexes on fact paths, we should not use random data for that. Lorem ipsum text, or similar? Some parameters that immediately come to mind Number of facts depth of facts total data size of facts Add Comment
Jira (PDB-5590) Generating scale testing data
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5590 Generating scale testing data Issue Type: Epic Assignee: Unassigned Created: 2023/02/13 9:22 AM Priority: Normal Reporter: Austin Blatt For an actual scale test we can use the existing benchmark tool to submit arbitrary numbers of commands to a PDB. But that operates by reading a set of "example" commands and making minor modifications to them over time. The existing data was generated on an employees laptop years ago and is not representative of "real data" - but we don't know what is. In order to test PuppetDB at scale, we need better data. Current data examples are very sparse - generated on an employees laptop many years ago with very little total data - or from a customer but very old. Why do we need to write code to generate it as opposed to just create it once? We don't know what data structure is "representative" of customers use case, and it likely isn't one single structure. I think we have about 1000 customers, so we probably have 1001 different use profiles. By write code to generate it from a set of parameters, we can change our data set as we move forward in time. Out of scope, but we could even instrument the same metrics in PE and potentially use that to replicate issues a customer is seeing without having to ask them to run things on our behalf to diagnose issues. Add Comment
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title Austin Blatt commented on PDB-5215 Re: Diagnose and fix pdb SIGHUP handling We need to write a CHANGELOG entry for this and then do a TK release. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408847.1627498028000.8522.1675814580020%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Fix Version/s: PDB n/a Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.5939.1675117800060%40Atlassian.JIRA.
Jira (PDB-5560) Update PuppetDB terminus for Puppet 8/Ruby 3
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5560 Update PuppetDB terminus for Puppet 8/Ruby 3 Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474929.1668708016000.5888.1675108440029%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Sprint: Skeletor 02/01/2023 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.3717.1674597600074%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.3715.1674597420035%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.3716.1674597420098%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Summary: Github PR pipeline doesn't report after first acceptance test job Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479496.1674513484000.3568.1674579540023%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after first job
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-5581
Github PR pipeline doesn't report after first job
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/01/23 2:38 PM
Priority:
Normal
Reporter:
Austin Blatt
Our github PR pipelines involved 3 jobs, the init job, the ezbake job, and the acceptance tests. The PR job reports immediately after ezbake finishes It looks like we fall into use-case 2 on https://github.com/puppetlabs/ci-job-configs/blob/main/doc/pipelines/pr.md
2. Upstream / downstream interconnected jobs
and are hitting the documented con
By default it only calls one job, and returns the status of that one job, while your pipeline may have many more ...
and the solution is
This can be worked around by adding the macro 'set-github-pr-status-{p_pr_enabled}' to all the jobs in the pipeline
Add Comment
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Fix Version/s: PDB 7.12.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477993.1672942656000.71234.1673366940109%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Affects Version/s: PDB 7.12.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477993.1672942656000.71233.1673366940059%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Fix Version/s: PDB 7.12.1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477993.1672942656000.71235.1673366940157%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Release Notes Summary: Fix issue where queries ordering by a fact value failed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477993.1672942656000.69984.1672943760260%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.477993.1672942656000.69977.1672943580089%40Atlassian.JIRA.
