Skip to content
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

4158 update solr #4520

Merged
merged 45 commits into from
Apr 2, 2018
Merged

4158 update solr #4520

merged 45 commits into from
Apr 2, 2018

Conversation

matthew-a-dunlap
Copy link
Contributor

@matthew-a-dunlap matthew-a-dunlap commented Mar 16, 2018

Related Issues

Pull Request Checklist

  • Unit [tests][] completed
  • Integration [tests][]: None
  • Deployment requirements, [SQL updates][], [Solr updates][], etc.: None
  • [Documentation][docs] completed
  • Merged latest from "develop" [branch][] and resolved conflicts

matthew-a-dunlap and others added 18 commits October 23, 2017 16:25
It looks like 7.1 is not much more work, but this is the lowest bar to start with.
I am unsure if this is actually the correct approach but am committing it as this story is getting backlogged.
Dev work still needed
Discusses how to set up 7.2.1. There are still guide fixes needed around various scripts and configuration of jetty in solr
Solr 4.6.0 folder still exists at this point as I need to understand all the files inside.
Removed 4.6.0 folder
updated a script (more to come)
updated documentation
Hopefully got them all. Still untested
Fixed vagrant script, cd-ing solr install when needed #4158

Also confirmed that solr 7.2.1 works in vagrant!
Also remove comment from a solr script
I resolved conflicts in the "dev env" page after the big rewrite in pull
request #4502 for issue #4419.

doc/sphinx-guides/source/developers/dev-environment.rst
@coveralls
Copy link

coveralls commented Mar 19, 2018

Coverage Status

Coverage increased (+0.01%) to 12.921% when pulling 5f67e56 on 4158-update-solr into d317d23 on develop.

Copy link
Member

@pdurbin pdurbin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems slightly weird to me that "collection1" had to be added in so many places but from a quick look the code seems to work.

pdurbin and others added 13 commits March 22, 2018 13:00
This is an awful hack to just get Solr working at all. We were getting
AccessDeniedException when starting it. FIXME added.

The Dockerfile was also simplified to remove lines that don't seem to
serve any apparent purpose:

RUN ln -s /usr/local/solr-7.2.1/server/logs /var/log/solr
VOLUME  /usr/local/solr-7.2.1/server/solr/collection1/data
Also add more error checking to build.sh

Also track default.config used in minishift/openshift.
"Match" was showing up because the bundle key didn't exist. We are
switching away from the deprecated "JsfHelper.localize" method.
Back in 60e640b when I was playing with spelling suggestions from Solr I
changed the request handler from "/select" (the default) to "/spell". We
didn't have time to fully explore the spelling suggestions feature of
Solr during the 4.0 rewrite and the "/spell" request handler seems to be
leading to other bugs, such as not being able to search on the
"identifier" portion of a DOI (i.e. "JNIUOA") from basic search. In
short we are switching to the default request handler for Solr,
something I would have done before tagging 4.0 if I had realized I had
left the "/spell" request handler in there.
This was referenced Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants