-
Notifications
You must be signed in to change notification settings - Fork 607
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
Asset Ingestor | Add include section #1644
Comments
I think it sounds fantastic, we just need to make sure to update the docs so people understand it and also change the defaults so the behavior still works the same if they leave the values unchanged. I like the way you're going about this. Admittedly when I wrote the exclude stuff it's because my sample size was small -- about 30 gb of vacation and family photos. 😄 Obviously you're working with a much larger sample size to validate the requirements of this one. |
HI @badvision, What solution is more suitable from your point of view?
|
Change existing fields I think. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stale, do not close it, please |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello @badvision PR is created: #1978 |
* #1644 Name FIlter implementation
* Adobe-Consulting-Services/acs-aem-commons#1644 updating Asset Ingestor docs * Adobe-Consulting-Services/acs-aem-commons#1644 updating Url Asset Import Docs * Adobe-Consulting-Services/acs-aem-commons#1644 updating S3 Asset Ingestor * providing narrow images
Currently user is able to exclude some specific folders, files, extensions that would be ignored during assets import:
![image](https://user-images.githubusercontent.com/23450886/50337388-04db0400-0522-11e9-87b3-3cd49891a419.png)
What if user is not able to analyze source content because it is too large? It is much better to provide what user wants to import.
In our case we have large filesystem with different content : video, text files and etc. We need to iterate over all file system and import only images. In this case I want to configure specific extensions to be migrated.
I guess it would be useful to have include configuration for files, folder and extensions.
I see two possible options:
For the second option we could rename Exclude section to the Filter section and use the following processing logic:
Also exclude logic should have priority over include logic
What do you think?
The text was updated successfully, but these errors were encountered: