-
Notifications
You must be signed in to change notification settings - Fork 32
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
Again about reindexing #269
Comments
To be able to debug the ES queries generated by this app, I'd recommend to set your loglevel to Unfortunately the debug logging is currently broken, that's why you might need to adjust the following code a bit to be able to actually see the query body: try {
$serializedParams = var_export($query['params'], true);
$this->logger->debug('Searching ES: ' . $serializedParams);
$result = $client->search($query['params']);
} (Will try to bring in a PR to fix the debug logging within the next days). After that, analyze the JSON query which is sent to ES and now written to your NC log. Most likely it will contain a "share_names" : {
"user0" : "GroupA/Applications/Ivanova.docx",
"user6" : "GroupA/Applications/Ivanova.docx",
"user3" : "",
}, A ES document is only visible to his That would be a hint that your index process ended with errors. In that case please reindex your documents end inspect your Nextcloud logfile while leaving the |
Out of curiosity: https://github.com/nextcloud/fulltextsearch_elasticsearch#compatibility says the app is ONLY compatible with ES 7? OP has used a container with ES 8.6.1 -- please somebody clarify if this CAN even work? |
Docs are outdated. If you have a look at the |
Thanks for the clarification. As always, the real information is buried in the sources. Wouldn't it be a nice gesture to the admin who wants to install this app for his users: let him know upfront that this app is compatible with a distinct ElasticSearch version? (in Nextcloud admin panel -> apps -> fulltextsearch_elasticsearch -> details)? |
Now I'm fully on track: NC on 26.0.4, ES on 8.6.1. And it seems the same result as described here: everything is fully indexed (index rebuilt with zero errors), but the query for files does not yield results. In particular:
Shall I open a new issue for this (the difference is: there are no groupfolders involved) or which info do you need to track this down? |
Reading your observations, I understand that the issue is hiding somewhere deeper. |
I have decided to open #277 for this problem. It seems too different from this issue which is about indexing. |
Hi! I am asking for help. Almost a week after moving from server installed elasticsearch to the dockerised I am struggling to make the full text search working on my instance:
Reindexing done with the following commands:
Searching with curl in index "my-index" for the word "Ivanova" (our member) gives (user data are stripped and scratched):
Next, I search for Ivanova on behind of a user0
The documents are stored in the groupfolder, which is accessible to
user0
,user1
,user2
,user3
,user10
, but that's what I see when searching with the help of NC fulltextsearch app:Obviously, users in webUI cannot see the proper output.
Would you be so kind to explain, why it is not working as expected? What should I do to make it working? Thanks!
The text was updated successfully, but these errors were encountered: