Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Rajasree Talla commented on PDB-2888 Re: Add flag for turning off JSONB related storage in PuppetDB Susan McNerney Did 4.1.4 get released? Is this resolved? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2888 Add flag for turning off JSONB related storage in PuppetDB Change By: Susan McNerney Fix Version/s: PDB 4.1.3 Fix Version/s: PDB 4.1.4 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Larry Copeland updated an issue PuppetDB / PDB-2888 Add flag for turning off JSONB related storage in PuppetDB Change By: Larry Copeland Attachment: Screen Shot 2016-07-15 at 11.30.19 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Andrew Roetker commented on PDB-2888 Re: Add flag for turning off JSONB related storage in PuppetDB This is something I think we'll want for the Couch Z release Susan McNerney Ryan Senior. This was a huge issue for Box and has a relatively small amount of work for us to do. This is the related to the issue from Saturday Larry Copeland Charlie Sharpsteen. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2888 Add flag for turning off JSONB related storage in PuppetDB Issue Type: Bug Assignee: Unassigned Created: 2016/07/17 11:31 PM Fix Versions: PDB 4.1.3 Priority: Normal Reporter: Andrew Roetker Customers with large catalogs currently have no way to toggle storage of expensive JSONB fields on the catalogs table related to the historical-catalogs/resource-graph features in Couch. This can lead to huge database bloat and costly decreases to command-processing performance. We should add a flag (maybe in the developers section?) or use `-1` for the historical-catalogs-limit setting to allow the user to disable storage of jsonb related fields. We should also consider how garbage collection when a user disables historical-catalogs should proceed. Add Comment