Update search because it can now be instantiated#1170
Merged
Conversation
mmattel
force-pushed
the
search_can_now_be_instantinated
branch
from
e17fabc to
7c67e2a
Compare
jvillafanez
reviewed
Jun 17, 2025
| NOTE: Both metadata and content extractions are stored as indexes via the search service. Keep in mind that indexing requires adequate storage capacity, and this requirement will grow over time. To prevent the index from filling up the file system and rendering Infinite Scale unusable, it should reside on its own file system. | ||
|
|
||
| You can change the path to where search maintains its data in case the filesystem gets close to full and you need to relocate the data. Stop the service, move the data, reconfigure the path in the environment variable and restart the service. | ||
| In case the file system gets close to full and you need to relocate {service_name} data, you can change the path to where {service_name} maintains its index data. |
Member
There was a problem hiding this comment.
I'm pretty sure you'll need to copy the index data into the new location. Just changing the location will break things because oCIS won't find the index data.
It's mentioned below... maybe it's better to link to where the actual info is
Contributor
Author
There was a problem hiding this comment.
There is an own section about this, see Reloacting the Index. This is also part of the table of contents.
This here should only tell that it is possible.
| * The embedded `basic` configuration provides metadata extraction which is always on. | ||
| * The `tika` configuration, which _additionally_ provides content extraction, if installed and configured. | ||
| * The embedded `basic` configuration provides metadata extraction which is always on. This includes all data that _describes_ the file like `Name`, `Size`, `MimeType`, `Tags` and `Mtime`. | ||
| * The `tika` configuration, which _additionally_ provides content extraction, if installed and configured. This includes all data that _relates to content_ of the file like `words`, `geo data`, `exif data` etc. |
Member
There was a problem hiding this comment.
Can we extract exif data and geo data with the ocis_full example? I guess tika can be configured to extract the data, but I'm not sure if oCIS is prepared to handle it. If we don't have instructions to set it up, I'd rather skip this part.
Contributor
Author
There was a problem hiding this comment.
Good point.
I think that this is two fold:
- The data is extracted and stored in the bleve index, this comes from tika and it does (should do) it without extra config. I have not heard any negative reponses that if tika is on, an image is saved, that ocis logs an error. The question is, can we e.g. prove it that data is present in the index.
- How to access the data from the UI. We are using KQL, at least a subset of it, see the search in the dev docs
With ocis_full on hetzer, such a test could be done...
kobergj
requested changes
Jun 20, 2025
Co-authored-by: kobergj <juliankoberg@googlemail.com>
kobergj
approved these changes
Jun 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #1135 (Allow scaling of the search service)
Documents around
searchare updated to match the new functionality of the search service.No backport, it is part of the upcoming 7.2
Rendered locally, looks good.