-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can anyone explain the mapping of plone.richtext behavior? #35
Comments
Indeed, |
I found a working solution: the mappings.json need a new processor for
the search query:
|
Interesting! May you provide a PR for this? |
Yes i can, but it i think more investigation is needed. My search result have this structure:
If i search the term But "file__extracted.content*" or "text__extracted.content*" is definitly wrong, but this should be corrected in |
I have setup the opensearch container with the ingest plugin. i have setup
collective.elastic.ingest
in a python venv locally.I have setup a simple Plone 6.1 site, no multilingual, language german, no content,
collective.elastic.plone
is installed. the communication between the instances works.I use the mappings.json file from the example docker-os directory in this package.
I add a Page with:
I add a PDF File with:
Now i use a Rest Client for better debugging and send a request to http://localhost:9200/plone/_search
My search tests:
I investigate the query with term "Himbeere" (that is the plone page) i see the term "Apfel", but not as plain text, the HTML is inside the field
text__extracted.content
I investigate the query with term "grün" (that is the pdf file in my plone site) i see the term "grün" in the field
file__extracted.content
Two Problems:
Any hints @jensens or @ksuess ?
The text was updated successfully, but these errors were encountered: