You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Want to use fscrawler for more complex processing before indexing to ES
Describe the solution you'd like
Now the "pipeline" is hardcoded in Java
find new file -> OCR/parse with tika -> index in ES
Rather, provide an ProcessingPipeline plugin that users can replace with their own implementation MyCustomPipeline. This pipeline plugin woud have a simple interface and provide a default impl which works exactly like todays hardcoded:
Is your feature request related to a problem? Please describe.
Want to use fscrawler for more complex processing before indexing to ES
Describe the solution you'd like
Now the "pipeline" is hardcoded in Java
Rather, provide an
ProcessingPipeline
plugin that users can replace with their own implementationMyCustomPipeline
. This pipeline plugin woud have a simple interface and provide a default impl which works exactly like todays hardcoded:However, users can provide their custom processing logic
Describe alternatives you've considered
Just forking the project, or build something from scratch
The text was updated successfully, but these errors were encountered: