-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fscrawler ignores exclusion folder for subdirectories #1974
Comments
Let me check about this one. In the meantime, an "easy" way to exclude dirs is by adding a But i'm looking into the issue. |
I think it's somewhat related to Windows path names vs linux names. |
Could you try the same operation with the following path instead? fs:
url: "G:/dokument" |
I think I found a patch for this. PR is coming ;) |
There were 2 issues here: * We are comparing a folder name like `*/foo/*` with a virtual dir name which is something like `/foo` or `/bar/foo`. It's missing the `/` at the end when it's a directory. * On windows, the exclusion for a dir named `\foo\arbets` does not match the exclusion `*/arbets/*` because of the `/` vs `\` mismatch This commit fixes this behavior. Closes #1974.
There were 2 issues here: * We are comparing a folder name like `*/foo/*` with a virtual dir name which is something like `/foo` or `/bar/foo`. It's missing the `/` at the end when it's a directory. * On windows, the exclusion for a dir named `\foo\arbets` does not match the exclusion `*/arbets/*` because of the `/` vs `\` mismatch This commit fixes this behavior. Closes #1974.
Describe the bug
Having a structure where only files in the folders named "publicerat" should be indexed. So I want to exclude other folders (arbets,original,historik,attachments). These are in multiple locations including subfolders.
In this case everything inside /arbets/, /original/, /historik/ and /attachments/ are getting indexed.
Job Settings
Logs
Expected behavior
It's expected that fscrawler will not index folders that are in exclusion path.
Versions:
The text was updated successfully, but these errors were encountered: