excludePattern

We are using OD 5.6 on Solaris and trying to setup excludePattern to exclude certain types of files. We are doing directory comparison with doDeletes option so we have only put the excludePattern in the source tag under pathSpecification as follows:

<pathSpecification>
<path name="usdata/sections"/>
<filters>
<excludePattern regex=".*/.jpg$" />
<excludePattern regex=".*/.jpeg$" />
<excludePattern regex=".*/.gif$" />
<excludePattern regex=".*/.bmp$" />
</filters>
<targetRules area="/data/content/usdata">
<permissionRules group="dev" user="oduser" directory="755" file="755"/>
<comparisonRules dateDifferent="yes"/>
<transferRules doDeletes="yes"/>
</targetRules>
</pathSpecification>

We followed the example as mentioned in OD admin guide but it doesn't seems to work. Can someone provide some info on what is wrong.

Find more posts tagged with

Comments

stefanmaier

Hello,
perhaps you can try a regex like this:
regex="\.jpg$"

Regards
Stefan

Adam Stoller

I think stefan hit the nail on the head there - the patterns you used have ".*/.jpg" which means that it will match files that contain the letters "jpg" as the 2nd, 3rd, and 4th characters of a filename on any path. Whereas ".*\.jpg" means that you want to match against any file that contains a literal dot (.) followed by the letters "jpg" -- to be even better though - you should anchor the regex at the end ".*\.jpg$"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Tarun

I tried changing it to :

<excludePattern regex=".*\.jpg$" />
<excludePattern regex=".*\.jpeg$" />
<excludePattern regex=".*\.gif$" />
<excludePattern regex=".*\.bmp$" />

but it also doesn't seems to work.

According to docs "When composing your regular expressions, follow your operating system’s path separator syntax. For
example, UNIX uses “/” while Windows uses “\\”. You can specify matches for a file on both
Windows and UNIX operating systems by including [/\\] in your regular expression."

I have already tried (as written in my original pos) the following:

<excludePattern regex=".*/.jpg$" />
<excludePattern regex=".*/.jpeg$" />
<excludePattern regex=".*/.gif$" />
<excludePattern regex=".*/.bmp$" />

So do I need to change it to following to make it working?:

<excludePattern regex=".*[/\\].jpg$" />
<excludePattern regex=".*[/\\].jpeg$" />
<excludePattern regex=".*[/\\].gif$" />
<excludePattern regex=".*[/\\].bmp$" />

Adam Stoller

<font color='blue'>I tried changing it to :

<<x>excludePattern regex=".*\.jpg$" />
<<x>excludePattern regex=".*\.jpeg$" />
<<x>excludePattern regex=".*\.gif$" />
<<x>excludePattern regex=".*\.bmp$" />

but it also doesn't seems to work. </font>

Can you post a copy of the micro logfile for a deployment where the above does not work - it should.
The issue of path separators is irrelevant in terms of the patterns you are dealing with - the ".*" portion should cover both '/' and '\\' and every other character under the sun. The "\.jpg$" part simply says "match against anything that ends with ".jpg".

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Tarun

Thanks its working. There was a blank line on top of the xml file.

Though this regex doesn't take care of case. jpg and JPG should both be included. Do we need to put separate pattern for each of them?

Adam Stoller

Dang - I fogot to change my last post to HTML - so it showed up funky - well....

To make it work for either case - I think you have to do something like:

<excludePattern regex=".*\.[jJ][pP][gG]$" />
<excludePattern regex=".*\.[jJ][pP][eE][gG]$" />
<excludePattern regex=".*\.[gG][iI][fF]$" />
<excludePattern regex=".*\.[bB][mM][pP]$" />

I don't think there's anyway to specify a modifier like i to indicate that the regex should be applied case-insensitively.

Hey Todd - could you set up a FR for adding another attribute to excludePattern and includePattern elements - something like case-sensitive which woukld default to "yes" (for backwards compatibility) but could be set to "no" to make the pattern regex behave in a case-insensitive manner? I thought about adding a wider-scope 'modifiers' attribute - but frankly, I don't think any of the other modifiers are really applicable: c Do not reset search position on a failed match when /g is in effect.g Match globally, i.e., find all occurrences.i Do case-insensitive pattern matching.m Treat string as multiple lines.o Compile pattern only once.s Treat string as single line.x Use extended regular expressions.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Feature request for case insensitivity option filed: #57606

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Tarun

Thanks fish.