[GitHub] bigtop issue #146: Update Solr to 4.10.4
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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] bigtop pull request #146: BIGTOP-2538: Update Solr to 4.10.4
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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (BIGTOP-2538) Bump version of Solr to 4.10.4
Andrew Kuchling created BIGTOP-2538: --- Summary: Bump version of Solr to 4.10.4 Key: BIGTOP-2538 URL: https://issues.apache.org/jira/browse/BIGTOP-2538 Project: Bigtop Issue Type: Task Components: solr Affects Versions: 1.1.0 Reporter: Andrew Kuchling Priority: Minor Fix For: 1.2.0 Updating Solr from 4.9.0 to 4.10.4 will hopefully be a trivial upgrade. While it's still far behind the current versions of 5.5.3 and 6.2, Solr 4.10.4 does fix some significant known issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] bigtop pull request #146: Update Solr to 4.10.4
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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 Date: 2016-09-19T15:39:04Z Clarify instructions; *-yum target doesn't seem to exist commit e013f03949197341cad950b72766b489b3e375d5 Author: Andrew Kuchling 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: need a mentor to contribute few patches
I guess you're looking to start these jobs here... https://ci.bigtop.apache.org/view/ppc64le/ IIRC you need to run them in this sequence: - puppet - toolchain - deploy (which doesn't seem to exist for PPC platform yet, but could be easily added to the Docker-Deploy job). Does it answer your question? Cos On Wed, Sep 21, 2016 at 06:42AM, MrAsanjar . wrote: > Sorry for the incomplete email... > Also, I am surprised that we don't have similar issues with ARM? How are we > building zeppelin and tez for ARM architecture? > > On Wed, Sep 21, 2016 at 6:37 AM, MrAsanjar . wrote: > > > Hi Cos, > > Sorry for a late reply, on the road again :) > > I have a ppc64le specific patch (https://issues.apache.org/ > > jira/browse/BIGTOP-2535) that should result in a new ubuntu-16.04-ppc64le > > slave docker image. I was not sure what else is required from my side. I > > have two other patches dependent on this patch to contribute. > > Also, I am superi > > > > On Thu, Sep 15, 2016 at 10:36 PM, Konstantin Boudnik > > wrote: > > > >> What seems to be incorrect in the page? > >> > >> Cos > >> > >> On Thu, Sep 15, 2016 at 08:58PM, MrAsanjar . wrote: > >> > Hi guys, > >> > I have few patches that I would like to contribute, however not sure if > >> > instruction > >> > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute > >> is up > >> > to date. I would very much appreciate any help or guidance you are able > >> to > >> > provide. > >> > Cheers > >> > > > >
Re: need a mentor to contribute few patches
Sorry for the incomplete email... Also, I am surprised that we don't have similar issues with ARM? How are we building zeppelin and tez for ARM architecture? On Wed, Sep 21, 2016 at 6:37 AM, MrAsanjar . wrote: > Hi Cos, > Sorry for a late reply, on the road again :) > I have a ppc64le specific patch (https://issues.apache.org/ > jira/browse/BIGTOP-2535) that should result in a new ubuntu-16.04-ppc64le > slave docker image. I was not sure what else is required from my side. I > have two other patches dependent on this patch to contribute. > Also, I am superi > > On Thu, Sep 15, 2016 at 10:36 PM, Konstantin Boudnik > wrote: > >> What seems to be incorrect in the page? >> >> Cos >> >> On Thu, Sep 15, 2016 at 08:58PM, MrAsanjar . wrote: >> > Hi guys, >> > I have few patches that I would like to contribute, however not sure if >> > instruction >> > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute >> is up >> > to date. I would very much appreciate any help or guidance you are able >> to >> > provide. >> > Cheers >> > >
Re: need a mentor to contribute few patches
Hi Cos, Sorry for a late reply, on the road again :) I have a ppc64le specific patch ( https://issues.apache.org/jira/browse/BIGTOP-2535) that should result in a new ubuntu-16.04-ppc64le slave docker image. I was not sure what else is required from my side. I have two other patches dependent on this patch to contribute. Also, I am superi On Thu, Sep 15, 2016 at 10:36 PM, Konstantin Boudnik wrote: > What seems to be incorrect in the page? > > Cos > > On Thu, Sep 15, 2016 at 08:58PM, MrAsanjar . wrote: > > Hi guys, > > I have few patches that I would like to contribute, however not sure if > > instruction > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute is > up > > to date. I would very much appreciate any help or guidance you are able > to > > provide. > > Cheers >
