XML sitemaps for large sites

[skttl (Søren Kottal)]

@mistyn8

but that I need to worry about a query such as give me a filtered set of content nodes, not getting me all my nodes and having to work out an approach in order to make sure I get them all..

Thats just how Lucene works

[mistyn8 (Mike Chambers)]

I think I’ve lost the plot somewhere here.. but are we saying that
Umbraco-CMS/src/Umbraco.Core/EmbeddedResources/Snippets/SiteMap.cshtml at release-15.2.3 · umbraco/Umbraco-CMS

Isn’t a good approach as it requests each and every node and fills the new hybridcache, but because we are actually traversing we do get all our content..

But if we did something like
Model?.Content.Root(PublishedContentCache, DocumentNavigationQueryService).Descendents.Where(x=>x.CustomProp == "something") we might not get the results we are expecting as the PublishedContentCache doesn’t necessarily hold all our published nodes?

Hence why we are reverting to Lucene to do deep nested searches (or some repositry cache pattern)??

Sorry if I’ve belabouring the point here, but wanted to understand.

[skttl (Søren Kottal)]

@mistyn8

But if we did something like
Model?.Content.Root(PublishedContentCache, DocumentNavigationQueryService).Descendents.Where(x=>x.CustomProp == "something") we might not get the results we are expecting as the PublishedContentCache doesn’t necessarily hold all our published nodes?

I don’t know anything about that approach, but my gut feeling says, that if you need to know anything about properties on a node, then they need to be in the cache. I guess the above, will fill the cache with all descendant nodes, but not sure.