Details

    • Type: Improvement
    • Status: Patch Available
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: deployment, general
    • Labels:
    • Environment:

      AWS AMI Linux environment / RPM Deployment / EMR Environment.

      Description

      I've worked on a Blog post for AWS about building Bigtop applications for EMR.
      https://blogs.aws.amazon.com/bigdata/post/TxNJ6YS4X6S59U/Building-and-Deploying-Custom-Applications-with-Apache-Bigtop-and-Amazon-EMR
      As the example application I've used Elasticsearch 1.6, which currently is not part of the Bigtop repository.
      I would like to contribute back Elasticsearch 1.6 for Bigtop.

        Issue Links

          Activity

          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user hvivani opened a pull request:

          https://github.com/apache/bigtop/pull/138

          BIGTOP-2517: Elasticsearch 1.6 for Bigtop

          You can merge this pull request into a Git repository by running:

          $ git pull https://github.com/hvivani/bigtop BIGTOP-2517

          Alternatively you can review and apply these changes as the patch at:

          https://github.com/apache/bigtop/pull/138.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 #138


          commit cd33e95b2582b0aaca920622073611f9b79edd65
          Author: Hernan Vivani <hernan@vivani.com.ar>
          Date: 2016-08-11T14:59:37Z

          BIGTOP-2517: Elasticsearch 1.6 for Bigtop


          Show
          githubbot ASF GitHub Bot added a comment - GitHub user hvivani opened a pull request: https://github.com/apache/bigtop/pull/138 BIGTOP-2517 : Elasticsearch 1.6 for Bigtop You can merge this pull request into a Git repository by running: $ git pull https://github.com/hvivani/bigtop BIGTOP-2517 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/138.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 #138 commit cd33e95b2582b0aaca920622073611f9b79edd65 Author: Hernan Vivani <hernan@vivani.com.ar> Date: 2016-08-11T14:59:37Z BIGTOP-2517 : Elasticsearch 1.6 for Bigtop
          Show
          hvivani Hernan Vivani added a comment - https://github.com/apache/bigtop/pull/138.patch
          Hide
          evans_ye Evans Ye added a comment -

          The patch and blog looks really great. Thanks Hernan Vivani.
          While what you provided are good. I think at this point we does not have enough knowledge in Elasticsearch yet.
          If you're ok to be a maintainer of this component.
          Then we can find a way to work with you and get the patch in.
          How do you think?

          Show
          evans_ye Evans Ye added a comment - The patch and blog looks really great. Thanks Hernan Vivani . While what you provided are good. I think at this point we does not have enough knowledge in Elasticsearch yet. If you're ok to be a maintainer of this component. Then we can find a way to work with you and get the patch in. How do you think?
          Hide
          hvivani Hernan Vivani added a comment -

          Hello Evans,
          Yes, I'll be more than glad to help here. Do you want me to update the maintainers file with my information ?

          Show
          hvivani Hernan Vivani added a comment - Hello Evans, Yes, I'll be more than glad to help here. Do you want me to update the maintainers file with my information ?
          Hide
          hvivani Hernan Vivani added a comment -

          Created https://github.com/apache/bigtop/pull/183 to add hernan vivani as maintainer for elasticsearch.

          Show
          hvivani Hernan Vivani added a comment - Created https://github.com/apache/bigtop/pull/183 to add hernan vivani as maintainer for elasticsearch.
          Hide
          evans_ye Evans Ye added a comment -

          Hernan Vivani that would be awesome!
          We can add you into maintainer list first, and then get back to the business of ES inclusion.
          From what I can see, version 1.6 is quite outdated. ES itself seems to have a huge bump of version just like firefox.
          Any chance to bump the version up-to-date while rebasing the patch?

          OTOH, please create another JIRA to host your PR-183.
          That way every changes has been tracked.
          Thanks.

          Show
          evans_ye Evans Ye added a comment - Hernan Vivani that would be awesome! We can add you into maintainer list first, and then get back to the business of ES inclusion. From what I can see, version 1.6 is quite outdated. ES itself seems to have a huge bump of version just like firefox. Any chance to bump the version up-to-date while rebasing the patch? OTOH, please create another JIRA to host your PR-183. That way every changes has been tracked. Thanks.
          Hide
          hvivani Hernan Vivani added a comment -

          Hi Evans,
          As per your comments, I've created https://issues.apache.org/jira/browse/BIGTOP-2694 for the maintainer request, and closed PR-183.
          I think we can add ES 1.6 as initial version and will start the work to create an ES 2.x version and then ES 5.x version.
          Thank you guys for the opportunity!

          Show
          hvivani Hernan Vivani added a comment - Hi Evans, As per your comments, I've created https://issues.apache.org/jira/browse/BIGTOP-2694 for the maintainer request, and closed PR-183. I think we can add ES 1.6 as initial version and will start the work to create an ES 2.x version and then ES 5.x version. Thank you guys for the opportunity!
          Hide
          evans_ye Evans Ye added a comment -

          Actually I'm very unfamiliar with ES, but it seems that 1.6 is quite old (released 09 June 2015).
          I think we'd be better to include newest, or at least newer/popular version of ES.
          FYI, we're close to the release of Bigtop 1.2, hence inclusion of a new component with old version looks pretty strange.
          Are you ok to bump the version up?

          Show
          evans_ye Evans Ye added a comment - Actually I'm very unfamiliar with ES, but it seems that 1.6 is quite old (released 09 June 2015). I think we'd be better to include newest, or at least newer/popular version of ES. FYI, we're close to the release of Bigtop 1.2, hence inclusion of a new component with old version looks pretty strange. Are you ok to bump the version up?
          Hide
          hvivani Hernan Vivani added a comment -

          Hello Evans,
          There are many structural changes between 1.x, 2.x and 5.x. Depending on the prod environment and the cost of migration, we have still users running on 1.x, others working on 2.x and finally new ones (or the ones that migrated all the structure) to ES 5.x.
          Yes, I'll work to bump the version up. Will create another Jira for that version.

          Show
          hvivani Hernan Vivani added a comment - Hello Evans, There are many structural changes between 1.x, 2.x and 5.x. Depending on the prod environment and the cost of migration, we have still users running on 1.x, others working on 2.x and finally new ones (or the ones that migrated all the structure) to ES 5.x. Yes, I'll work to bump the version up. Will create another Jira for that version.
          Hide
          evans_ye Evans Ye added a comment -

          Hernan Vivani I personally would love to see a newer version of ES being included in Bigtop. That's much more reasonable for an addition of new component. Sorry for being late on paying attention to this JIRA. Please ping me directly if you get any progress on this.

          Show
          evans_ye Evans Ye added a comment - Hernan Vivani I personally would love to see a newer version of ES being included in Bigtop. That's much more reasonable for an addition of new component. Sorry for being late on paying attention to this JIRA. Please ping me directly if you get any progress on this.
          Hide
          hvivani Hernan Vivani added a comment -

          Hello Evans,
          Sorry for the delay here.
          I started the work on it but got sidetracked with other issues and I couldn't advance to much yet. The structure is pretty different so I'm working recreating the SPEC and will need to perform some proper tests to see if everything works properly.
          I'll keep you posted.

          Show
          hvivani Hernan Vivani added a comment - Hello Evans, Sorry for the delay here. I started the work on it but got sidetracked with other issues and I couldn't advance to much yet. The structure is pretty different so I'm working recreating the SPEC and will need to perform some proper tests to see if everything works properly. I'll keep you posted.
          Hide
          evans_ye Evans Ye added a comment -

          Hernan Vivani anything we can help?

          Show
          evans_ye Evans Ye added a comment - Hernan Vivani anything we can help?

            People

            • Assignee:
              Unassigned
              Reporter:
              hvivani Hernan Vivani
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 168h
                168h
                Remaining:
                Remaining Estimate - 168h
                168h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Development