-
Notifications
You must be signed in to change notification settings - Fork 34
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
WikibaseCirrusSearch doesn't seem to be working with the Docker files shown as examples #383
Comments
examples
examples
In this Github Gist , you can find the output of executing
For the record, this is the output of
|
@rdrg109 statements are not indexed by default. Make sure that it's also mounted into the jobrunner since that container is doing the actual indexing. (see https://github.com/wmde/wikibase-release-pipeline/pull/390/files) |
The context
I'm running Wikibase in Docker locally for experimentation purposes. I'm using the files from the
main
branch as of the time of this writing (permalink to commit). Namely, the files shown below.example/docker-compose-extra.yml
example/docker-compose.yml
example/extra-install.sh
example/jobrunner-entrypoint.sh
example/template.env
I've run the following command to start Docker
and this is the state of the containers
The problem
If I search
insource:"has been"
, the pageMain Page
is the only result shown, because it contains the sentenceMediaWiki has been installed.
. However, if I searchhaswbstatement:*
, no result is shown and the messageThere were no results matching the query.
is shown even though I have Wikibase items that have statements.This is the URL that was shown in the top of my web browser after I pressed the button
Search
(see screenshot below).Additional information
I found this issue (archive) published in the Gitlab instance (https://gitlab.opensourceecology.de). A user mentioned that
haswbstatement:*
showed 0 results, which is the same problem that I'm describing here. @lucaswerkmeister shared a link which, apparently, implied that the issue had been solved. I tried visiting the same endpoint in my instance and this was the result. I'm including it below just in case it helps to find the root cause of this issue.Here's the output shown above pretty-printed.
Personal thoughts
I think the problem here is the extension
WikibaseCirrusSearch
. I'd appreciate anyone could help me to find the root cause of this issue. If you need more information of my system, please let me know.The text was updated successfully, but these errors were encountered: