search

TWCable / grabbit

Grabbit - Fast Content Sync tool for AEM/CQ
Apache License 2.0
125 stars 64 forks source link

Overly aggressive exclusion filter #208

Closed bsaylor closed 6 years ago

bsaylor commented 6 years ago

The exclusion feature which allows a node and its children to be excluded fro the sync is being overly aggressive and excluding similar sibling nodes by mistake. See the example below for specifics.

Example paths: /content/someContent/2015/1/otherContent /content/someContent/2015/2/otherContent /content/someContent/2015/11/otherContent /content/someContent/2015/12/otherContent

Example job

"pathConfigurations": [
   "path": /content/someContent/2015",
   "excludePaths": [
      "1"
   ]
]

Results This is intended to sync the content under /content/someContent/2015 and it should exclude /content/someContent/2015/1/ and its children. However what happens is that it does exclude the "1" node, but also the "11" and "12" nodes. This occurs when the name of an excluded node is also the prefix for a sibling node.

What version of AEM are you running? AEM 6.1

What version of Grabbit are you using? Grabbit 7.1.2

How do you produce the issue? Perform a sync and exclude a node that would be the prefix for a sibling node. For example exclude the node "other" and the sibling node "otherContent" will also be excluded.

Does the issue occur consistently? Yes

Any additional details?