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
So for HTML files i got this running. But whats about PDF Files and other documents? They still have there content in the content field and don't have any content MetaField. I was unable to find a "CopyContentToMetaField" config. Or is there a posibility to overwrite the content with the DOM Tagger (or any other config)? The current behavior is that the content for PDF files and other documents which is commited to CloudSearch is empty.
The text was updated successfully, but these errors were encountered:
There is already a feature request to for a DOMTransformer that would do what you are after: Norconex/importer#62.
In the meantime, you have a few options. If you want to modify the content rather than store in a new field, you can use the ReplaceTransformer to perform search & replace using regular expressions. You can also look at using a combination of StripBeforeTransformer and StripAfterTransformer. All would need to be set up as pre-parse handlers.
To copy the content to a metadata field, you can use TextPatternTagger, in a similar way (untested):
Hi,
currently i have the situation that i want to only have the "main" content parsed in an html document. Like this:
But this does not overwrite the content. It only sets a content MetaField.
If i want to upload this i have to configure my CloudSearch commiter to use this MetaField als content.
So for HTML files i got this running. But whats about PDF Files and other documents? They still have there content in the content field and don't have any content MetaField. I was unable to find a "CopyContentToMetaField" config. Or is there a posibility to overwrite the content with the DOM Tagger (or any other config)? The current behavior is that the content for PDF files and other documents which is commited to CloudSearch is empty.
The text was updated successfully, but these errors were encountered: