You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dirk Rudolph (Jira)" <ji...@apache.org> on 2021/10/15 09:38:00 UTC
[jira] [Updated] (SLING-10870) Support include/exclude paths for
Sitemap Schedulers
[ https://issues.apache.org/jira/browse/SLING-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dirk Rudolph updated SLING-10870:
---------------------------------
Description:
Currently a sitemap scheduler allows to search for sitemap roots below a given path. This is typically used to have different schedules for different repository paths like
{code}
/content/tenantA => every day
/content/tenantB => every other day
{code}
However it does not allow to define a different schedule for nested sitemaps like
{code}
/content/tenantA => every day
/content/teantnA/blog => every 4h
{code}
Additionally to defining different schedules for different names and/or generators it would also make sense to support include/exclude paths.
We should support paths and globs.
was:
Currently a sitemap scheduler allows to search for sitemap roots below a given path. This is typically used to have different schedules for different repository paths like
{code}
/content/tenantA => every day
/content/tenantB => every other day
{code}
However it does not allow to define a different schedule for nested sitemaps like
{code}
/content/tenantA => every day
/content/teantnA/blog => every 4h
{code}
Additionally to defining different schedules for different names and/or generators it would also make sense to support include/exclude paths.
> Support include/exclude paths for Sitemap Schedulers
> ----------------------------------------------------
>
> Key: SLING-10870
> URL: https://issues.apache.org/jira/browse/SLING-10870
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Dirk Rudolph
> Priority: Major
> Labels: sitemaps
>
> Currently a sitemap scheduler allows to search for sitemap roots below a given path. This is typically used to have different schedules for different repository paths like
> {code}
> /content/tenantA => every day
> /content/tenantB => every other day
> {code}
> However it does not allow to define a different schedule for nested sitemaps like
> {code}
> /content/tenantA => every day
> /content/teantnA/blog => every 4h
> {code}
> Additionally to defining different schedules for different names and/or generators it would also make sense to support include/exclude paths.
> We should support paths and globs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)