-
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
RRE rre-report:report produces no results #103
Comments
Theoretically the |
@risdenk I've banged my head on |
curl 'http://localhost:8983/solr/ecommerce/select?q=laptop' works anonymously just fine from the terminal and as a URL in Safari, so I don't think the RRE problem is actually due to authentication alone. On further inspection, RRE supported SOLR version is 8.3.0 (ref rre/pom.xml, https://github.com/SeaseLtd/rated-ranking-evaluator/wiki/Supported%20Versions), while the SOLR version in the container is 9.0.0 (ref solr/Dockerfile). While none of the major changes (https://github.com/apache/solr/blob/main/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc) to the security section look like they broke RRE, it is a possibility. None of the changes between 8.3.0 and 8.11.0 look to be the culprit. Backing out of the SOLR 9.0 changes might verify that the problem is due to SOLR version number. |
So, for fun I ran:
The -X enables debugging, and it appears looking at the HTTP traffic (yeah, looking at traffic now) that we do get results back!
So the WARN I see at the end:
makes me wonder if we don't have permissions for RRE, in Docker, to write out the data? |
Closing as we removed RRE. |
RRE -
No evaluation data has been generated - no reports will be produced.
katas/000_setting_up_chorus.md
andkatas/001_optimize_a_query.md
both have a section on using RRE to evaluate search results, but it looks to fail silently. Issue #92 I think shows a symptom of this failure as wellthis doesn't seem to change even if the evaluation is run in the same
docker-compose run
:The same error occurs even though RRE looks like it ran correctly in the evaluate stage.
Potentially relates to SeaseLtd/rated-ranking-evaluator#140
The text was updated successfully, but these errors were encountered: