Our customer is creating a large body of new bucketed content (using a new template) below a parent item (which is also new). In order to publish all this at once, they're leaving the parent unpublished until they're ready to reveal all of this. In the meantime, they'd like to be able to run the default bucket query on the the parent in the Content Editor to view all the new children, but when we try to do this only the parent item is returned. Is this a consequence of parent not being published, or have we missed some necessary action or setting? (May be worth noting: we've compared settings with other parents and templates - which search successfully - in the same part of the content and found nothing obvious.)
Update I may have just blundered into the problem: the index definition updates for the new content type are part of a code update which hasn't been deployed to the subject environment yet. I'll have to take direction about whether to deploy the index definition updates ahead of the rest of the code or not.
Bucket search is dependent on indexing and does not have any dependency on publishing. But based on the publishing strategy for your Content Management server, indexing can depend on your publishing. I would suggest you two options here to see the results in the content editor -
Manual Reindex - You can perform manual reindex using the control pannel or the content editor's developer tab. Where you can rebuild all the indexes or a particular index or from the developer's tab re-index the tree.
By default, Sitecore hides the Developer Tab. In order to activate the Developer Tab, you need to right-click on the Content Editor Ribbon and select the Developer option from the list. Please see the below screenshot.
You need to select the parent item and perform the re-index tree for the node.
Update the indexing strategy on CM - Since you want to see the changes on the master database without publishing you can change the indexing strategy for this. you can choose an indexing strategy based on your requirement but below are two which you can choose -
Synchronous strategy - This strategy is the index update strategy closest to real-time. It is also the most expensive strategy in terms of CPU and I/O.
Intervalasynchronous strategy - Similar to Synchronous but need to specify the frequency of the strategy trigger with the interval parameter. This strategy is triggered by a time interval and not the OnPublishEnd event. It uses the EventQueue table of the source database. The source database is specified by the database parameter of the strategy.