Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-21325

Ability to switch Quick Links to use Service URL through Knox or given proxy

    Details

    • Type: Improvement
    • Status: Patch Available
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: trunk, 2.5.2, 2.5.3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Knox has the ability to proxy Hadoop user interfaces URL. Having the ability to setup Quicklinks through Knox so instead of for example going to "Hbase Master UI" directly we can proxy through Knox for example: http://hdpjeff1.fyre.ibm.com:16010/master-status
      can be instead go through: https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status
      Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL.
      This will bring authentication to the UI access and would secure the UI access.
      Ideally this behavior can be set as secure going through proxy by default or it can be turn off to go directly by Ambari Admin.

      Changes added:
      1. Add new json properties knox_url, knox_path, supports_knox
      a. knox_url: template to be used for urls that are proxied through Knox
      b. knox_path: Knox gateway path that will be added to the proxy url.
      c. supports_knox: whether link will be redirected through Knox
      2. Add above json properties to quicklinks.json
      3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, SPARKUI services to Knox topology template.
      4. Automate protocol and port added to Knox topology file. Based on whether SSL is enabled for the services listed above, the port and protocol in params_linux.py will be updated.
      5. Update quick_view_link_view.js so that when Knox is installed and support_knox is true, quicklink url follows knox url template specified in the quicklinks.json for the service/component.

      1. AMBARI-21325-rebased.patch
        30 kB
        Balázs Bence Sári
      2. AMBARI-21325-rebased_v3.patch
        43 kB
        Balázs Bence Sári
      3. AMBARI-21325.patch
        30 kB
        Chandana Mirashi
      4. 21325_test_results.zip
        264 kB
        Chandana Mirashi

        Issue Links

          Activity

          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12876678/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-server

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11774//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12876678/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-server Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11774//console This message is automatically generated.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12877147/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-web

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11784//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12877147/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-web Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11784//console This message is automatically generated.
          Hide
          bsari Balázs Bence Sári added a comment -

          Hey Chandana Mirashi, could you please add a review board link?

          Show
          bsari Balázs Bence Sári added a comment - Hey Chandana Mirashi , could you please add a review board link?
          Hide
          cmirashi Chandana Mirashi added a comment -

          Balázs Bence Sári
          I have not yet created review board request as one of ambari-web test failed for the previous patch.

          Show
          cmirashi Chandana Mirashi added a comment - Balázs Bence Sári I have not yet created review board request as one of ambari-web test failed for the previous patch.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12878318/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The patch failed these unit tests in ambari-server ambari-web:

          org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11834//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12878318/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The patch failed these unit tests in ambari-server ambari-web: org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11834//console This message is automatically generated.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12878722/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-server

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11850//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12878722/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-server Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11850//console This message is automatically generated.
          Hide
          jeffreyr97 Jeffrey E Rodriguez added a comment -

          Hi Chandana, et all. What is the status of this AMBARI-21325 patch? Is the core test failure relevant??

          Show
          jeffreyr97 Jeffrey E Rodriguez added a comment - Hi Chandana, et all. What is the status of this AMBARI-21325 patch? Is the core test failure relevant??
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12881859/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The patch failed these unit tests in ambari-server ambari-web:

          org.apache.ambari.server.state.UpgradeHelperTest

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11997//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12881859/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The patch failed these unit tests in ambari-server ambari-web: org.apache.ambari.server.state.UpgradeHelperTest Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11997//console This message is automatically generated.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12881859/AMBARI-21325.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-server

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12015//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12881859/AMBARI-21325.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-server Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12015//console This message is automatically generated.
          Hide
          cmirashi Chandana Mirashi added a comment -

          I have attached comparable test results when creating patch. .
          trunk_*: These test reports without my changes
          21325_*: These test_reports are with my changes.

          Show
          cmirashi Chandana Mirashi added a comment - I have attached comparable test results when creating patch. . trunk_*: These test reports without my changes 21325_*: These test_reports are with my changes.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12882446/21325_test_results.zip
          against trunk revision .

          -1 patch. The patch command could not apply the patch.

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12020//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12882446/21325_test_results.zip against trunk revision . -1 patch . The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12020//console This message is automatically generated.
          Hide
          lmccay Larry McCay added a comment -

          This patch is really interesting.
          I am a bit concerned about a couple aspects of the implementation however and I think we need to consider them carefully due to backward compatibility issues if we decide that we need to evolve it.

          One thing that stands out to me is that it seems to hardcode specific topology names that it is generating for the deployment. While this may work in targeted deployments, it may not suite others as well. I have also noticed that these same topology names have bled into the service definitions that were recently added to Knox itself. The rewrite rules are actually hardcoded for specific names.

          One of the things that makes that concerning to me is that it breaks the namespace provided by topologies. In order for Knox to support multiple clusters in the same gateway instance, we use topologies to represent each cluster and the services, UIs that are to be proxied from the cluster. By introducing a hbaseui.xml, an admin looking at that topology will not easily know which cluster it belongs to. Moreover, you are limited to a single hbaseui.xml for the gateway instance. Which means that our support for proxying the HBase UI will be limited to one cluster even though Knox supports multiple clusters.

          I have been thinking about how this namespace can be preserved through a new feature in Knox that will allow for simpler UI rewrite rules and a browser redirect from a typical cluster topology like default.xml to a UI specific topology for the default cluster.

          Since I believe there is a good bit of work to get this provisioning work done properly, fix the rewrite rules in the current service definitions and add the new indirection for namespace preservation, I would suggest that we use what is here as a source to inform what ends up being done and target it in a later release.

          In the meantime, I know folks do some similar things as part of a post installation provisioning step.
          Essentially, generate the needed topologies and update the quicklinks json file to use Knox URLs instead of direct.

          Show
          lmccay Larry McCay added a comment - This patch is really interesting. I am a bit concerned about a couple aspects of the implementation however and I think we need to consider them carefully due to backward compatibility issues if we decide that we need to evolve it. One thing that stands out to me is that it seems to hardcode specific topology names that it is generating for the deployment. While this may work in targeted deployments, it may not suite others as well. I have also noticed that these same topology names have bled into the service definitions that were recently added to Knox itself. The rewrite rules are actually hardcoded for specific names. One of the things that makes that concerning to me is that it breaks the namespace provided by topologies. In order for Knox to support multiple clusters in the same gateway instance, we use topologies to represent each cluster and the services, UIs that are to be proxied from the cluster. By introducing a hbaseui.xml, an admin looking at that topology will not easily know which cluster it belongs to. Moreover, you are limited to a single hbaseui.xml for the gateway instance. Which means that our support for proxying the HBase UI will be limited to one cluster even though Knox supports multiple clusters. I have been thinking about how this namespace can be preserved through a new feature in Knox that will allow for simpler UI rewrite rules and a browser redirect from a typical cluster topology like default.xml to a UI specific topology for the default cluster. Since I believe there is a good bit of work to get this provisioning work done properly, fix the rewrite rules in the current service definitions and add the new indirection for namespace preservation, I would suggest that we use what is here as a source to inform what ends up being done and target it in a later release. In the meantime, I know folks do some similar things as part of a post installation provisioning step. Essentially, generate the needed topologies and update the quicklinks json file to use Knox URLs instead of direct.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12885609/AMBARI-21325-rebased.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-web ambari-server

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12166//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12885609/AMBARI-21325-rebased.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-web ambari-server Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12166//console This message is automatically generated.
          Hide
          bsari Balázs Bence Sári added a comment -

          Hey Chandana Mirashi,

          while testing out the patch, I noticed that not all quick links got merged correctly. I am usinng HDP 2.6 and HDFS quicklinks seem to loose their Knox attributes. Not sure yet if this is an issue of the patch or some more general issue. Did you encounter anything similar? Which HDP were you testing the patch with?

          Show
          bsari Balázs Bence Sári added a comment - Hey Chandana Mirashi , while testing out the patch, I noticed that not all quick links got merged correctly. I am usinng HDP 2.6 and HDFS quicklinks seem to loose their Knox attributes. Not sure yet if this is an issue of the patch or some more general issue. Did you encounter anything similar? Which HDP were you testing the patch with?
          Hide
          bsari Balázs Bence Sári added a comment -

          Looks like it is caused by a missing comma in HDP 2.3's HDFS quicklinks.json.

          Show
          bsari Balázs Bence Sári added a comment - Looks like it is caused by a missing comma in HDP 2.3's HDFS quicklinks.json.
          Hide
          bsari Balázs Bence Sári added a comment - - edited

          Hey Larry McCay, thanks for the insights. Looks like the default topology is baked in in Ambari, not only from quicklink perspective. Once Ambari will support customizeable topolgy name I think the topology part of knox path could be a parameter in the quicklink definition.

          Show
          bsari Balázs Bence Sári added a comment - - edited Hey Larry McCay , thanks for the insights. Looks like the default topology is baked in in Ambari, not only from quicklink perspective. Once Ambari will support customizeable topolgy name I think the topology part of knox path could be a parameter in the quicklink definition.
          Hide
          bsari Balázs Bence Sári added a comment -

          Hey Chandana Mirashi,

          I am testing this patch. Made a few changes and had to rewrite the knox paths for most of the services except HDFS. I noticed that Spark2/Jobhistory UI needs the 2.1.0 version of Knox's SPARKHISTORYUI service definition (service.xml and rewrite.xml). The Knox coming with HDP 2.6 only has the 1.4.0 version of the service definition. Which HDP/Knox version does it work with out of the box? If there is no such HDP, could you attach the steps for adding SPARKHISTORYUI 2.1.0 definition to Knox?

          cc Larry McCay

          Show
          bsari Balázs Bence Sári added a comment - Hey Chandana Mirashi , I am testing this patch. Made a few changes and had to rewrite the knox paths for most of the services except HDFS. I noticed that Spark2/Jobhistory UI needs the 2.1.0 version of Knox's SPARKHISTORYUI service definition (service.xml and rewrite.xml). The Knox coming with HDP 2.6 only has the 1.4.0 version of the service definition. Which HDP/Knox version does it work with out of the box? If there is no such HDP, could you attach the steps for adding SPARKHISTORYUI 2.1.0 definition to Knox? cc Larry McCay
          Hide
          cmirashi Chandana Mirashi added a comment -

          Hi Balázs Bence Sári Sorry missed your earlier comment. I had tested with HDP 2.6. Regarding Spark2 : It was tested as part of IOP 4.2.5 which had Spark 2 as a service.
          1. Create 2.1.0 folder under sparkhistoryui in addition to current default 1.4.1
          2. Copy Spark2 history ui service and rewrite xml to this folder
          3. In knox topology, add version under sparkhistoryui <version>2.1.0</version>

          Show
          cmirashi Chandana Mirashi added a comment - Hi Balázs Bence Sári Sorry missed your earlier comment. I had tested with HDP 2.6. Regarding Spark2 : It was tested as part of IOP 4.2.5 which had Spark 2 as a service. 1. Create 2.1.0 folder under sparkhistoryui in addition to current default 1.4.1 2. Copy Spark2 history ui service and rewrite xml to this folder 3. In knox topology, add version under sparkhistoryui <version>2.1.0</version>
          Hide
          bsari Balázs Bence Sári added a comment - - edited

          Hey Chandana,

          Thanks. I am also testing with HDP 2.6, however I had to change a few things to make it work:
          1. Change Knox path for OOZIE to gateway/default/oozie/
          2. Change Knox path for HBASE to gateway/default/hbase/webui
          3. Change Knox path for YARN to gateway/default/yarn
          4. Change Knox parh for SPARK2 to to /gateway/default/sparkhistory

          Re your solution for Spark: The <version>2.1.0</version> declaration for sparkhistory is there in the topology.xml for the original path. I could as well remove it so spark would work with the 1.4.0 version in place. In that case the quick link would work, however, clicking on any further link on the Spark UI would be broken. That's why I thought the 1.4.0 may be obsolete and 2.1.0 would be working fine. Do you know if 2.1.0 Knox service definitions for sparkhistory are any different than 1.4.0?

          Show
          bsari Balázs Bence Sári added a comment - - edited Hey Chandana, Thanks. I am also testing with HDP 2.6, however I had to change a few things to make it work: 1. Change Knox path for OOZIE to gateway/default/oozie/ 2. Change Knox path for HBASE to gateway/default/hbase/webui 3. Change Knox path for YARN to gateway/default/yarn 4. Change Knox parh for SPARK2 to to /gateway/default/sparkhistory Re your solution for Spark: The <version>2.1.0</version> declaration for sparkhistory is there in the topology.xml for the original path. I could as well remove it so spark would work with the 1.4.0 version in place. In that case the quick link would work, however, clicking on any further link on the Spark UI would be broken. That's why I thought the 1.4.0 may be obsolete and 2.1.0 would be working fine. Do you know if 2.1.0 Knox service definitions for sparkhistory are any different than 1.4.0?
          Hide
          cmirashi Chandana Mirashi added a comment - - edited

          Yes, Spark2 History UI changed some of the links and underlying structure from previous versions of Spark. Hence had to create a new version in Knox to support Spark2. Given that we already had customers on previous version, the earlier version service definitions were not replaced to account for that scenario. If everyone moves to Spark 2 then 1.4 version will be obsolete.

          Show
          cmirashi Chandana Mirashi added a comment - - edited Yes, Spark2 History UI changed some of the links and underlying structure from previous versions of Spark. Hence had to create a new version in Knox to support Spark2. Given that we already had customers on previous version, the earlier version service definitions were not replaced to account for that scenario. If everyone moves to Spark 2 then 1.4 version will be obsolete.
          Hide
          bsari Balázs Bence Sári added a comment -

          Thanks Chandana Mirashi. Re the other issues: why do you think a different Knox path works for me than for you, e.g gateway/hbaseui/hbase (your version) vs. gateway/default/hbase/webui (my version)?

          larry mccay do you think we should consider integrating Chandana Mirashi's work on Spark2 Knox integration into HDP?

          Show
          bsari Balázs Bence Sári added a comment - Thanks Chandana Mirashi . Re the other issues: why do you think a different Knox path works for me than for you, e.g gateway/hbaseui/hbase (your version) vs. gateway/default/hbase/webui (my version)? larry mccay do you think we should consider integrating Chandana Mirashi 's work on Spark2 Knox integration into HDP?
          Hide
          cmirashi Chandana Mirashi added a comment -

          Knox path depends on how topology in Knox is setup. In IOP, we had separate topology for UIs instead of adding to everything to default.xml. For ex: In addition to default.xml which had REST services, Hbase UI topology was saved in hbaseui.xml. If all the services (UI and REST) are defined default.xml then the above is as expected.

          Show
          cmirashi Chandana Mirashi added a comment - Knox path depends on how topology in Knox is setup. In IOP, we had separate topology for UIs instead of adding to everything to default.xml. For ex: In addition to default.xml which had REST services, Hbase UI topology was saved in hbaseui.xml. If all the services (UI and REST) are defined default.xml then the above is as expected.
          Hide
          bsari Balázs Bence Sári added a comment -

          Thanks again Chandana Mirashi. I will use the everything goes into default.xml approach then as this looks to be best supported by Ambari.

          Show
          bsari Balázs Bence Sári added a comment - Thanks again Chandana Mirashi . I will use the everything goes into default.xml approach then as this looks to be best supported by Ambari.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12889316/AMBARI-21325-rebased_v3.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          -1 core tests. The test build failed in ambari-server

          Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12364//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12889316/AMBARI-21325-rebased_v3.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 javac . The applied patch does not increase the total number of javac compiler warnings. -1 core tests . The test build failed in ambari-server Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12364//console This message is automatically generated.
          Hide
          bsari Balázs Bence Sári added a comment -

          Hey Chandana Mirashi, could you please attach the Knox service defitions for Spark 2.1.0?

          Show
          bsari Balázs Bence Sári added a comment - Hey Chandana Mirashi , could you please attach the Knox service defitions for Spark 2.1.0?

            People

            • Assignee:
              cmirashi Chandana Mirashi
              Reporter:
              jeffreyr97 Jeffrey E Rodriguez
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

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

                  Development