You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by akuchling <gi...@git.apache.org> on 2016/09/21 18:26:56 UTC
[GitHub] bigtop pull request #146: Update Solr to 4.10.4
GitHub user akuchling opened a pull request:
https://github.com/apache/bigtop/pull/146
Update Solr to 4.10.4
I tried bumping the version of Solr to the last 4.10 release and running the 'gradlew' build script to build RPM packages. That build process worked fine, and the resulting solr-4.10.4 packages at least install on our CentOS machines and start up as expected.
I don't know if my employer will decide to try this with 5.5.x or 6.x. I expect that version bump would be more complicated because of Solr's switch from using Tomcat to Jetty, but haven't tried it yet. For those versions, we might just install Solr directly from a .tgz without using Bigtop's re-packaging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/akuchling/bigtop akuchling-solr-410
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/146.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #146
----
commit dd165df9c9efe95b61162edbca0210b25520d21b
Author: Andrew Kuchling <am...@amk.ca>
Date: 2016-09-19T15:39:04Z
Clarify instructions; *-yum target doesn't seem to exist
commit e013f03949197341cad950b72766b489b3e375d5
Author: Andrew Kuchling <am...@amk.ca>
Date: 2016-09-19T17:23:28Z
Bump Solr version to 4.10.4
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bigtop pull request #146: Update Solr to 4.10.4
Posted by c0s <gi...@git.apache.org>.
Github user c0s commented on a diff in the pull request:
https://github.com/apache/bigtop/pull/146#discussion_r79902357
--- Diff: bigtop-deploy/vm/vagrant-puppet-vm/README.md ---
@@ -56,13 +56,18 @@ num_instances: 5
5) Test on local built packages is available by:
-first, build up local yum repo
--- End diff --
The sequence of the YUM build has changed indeed after some recent refactorings. Now it is
- ./gradlew componentname-pkg
- ./gradlew yum|apt
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bigtop pull request #146: BIGTOP-2538: Update Solr to 4.10.4
Posted by akuchling <gi...@git.apache.org>.
Github user akuchling commented on a diff in the pull request:
https://github.com/apache/bigtop/pull/146#discussion_r79908155
--- Diff: bigtop-deploy/vm/vagrant-puppet-vm/README.md ---
@@ -56,13 +56,18 @@ num_instances: 5
5) Test on local built packages is available by:
-first, build up local yum repo
--- End diff --
Thanks! Done -- I removed the README changes and filed a Jira issue for the version bump, BIGTOP-2538.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] bigtop issue #146: Update Solr to 4.10.4
Posted by c0s <gi...@git.apache.org>.
Github user c0s commented on the issue:
https://github.com/apache/bigtop/pull/146
it has been committed - you can close the PR now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---