[
https://issues.apache.org/jira/browse/AMBARI-19528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reopened AMBARI-19528:
----------------------------------------
[~nitiraj.rathore] Could you please avoid moving around imports unnecessarily?
Wrong import order causes build failure on {{trunk}}. Thanks.
{noformat}
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @ ambari-server ---
[INFO] Starting audit...
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/view/RemoteAmbariCluster.java:28:
Wrong order for 'org.apache.ambari.server.configuration.Configuration' import.
[ImportOrder]
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/view/RemoteAmbariCluster.java:35:
Wrong order for 'java.io.IOException' import. [ImportOrder]
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/view/ClusterImpl.java:22:
Wrong order for 'org.apache.ambari.server.state.Config' import. [ImportOrder]
[ERROR]
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/java/org/apache/ambari/server/view/ClusterImpl.java:26:
Wrong order for 'java.util.ArrayList' import. [ImportOrder]
Audit done.
{noformat}
> Ambari views : Adding new FileSystem support to views should work without
> code changes
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-19528
> URL: https://issues.apache.org/jira/browse/AMBARI-19528
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.4.0
> Reporter: Nitiraj Singh Rathore
> Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-19528_branch-2.5.patch
>
>
> Right now when new file-system support has to be added to views, we need to
> add code to include several more key value pairs into the conf to make it
> work.
> Usually these key value pairs are file-system class names, secret key and
> access key.
> following 2 changes are proposed.
> 1. load the complete core-site and hdfs-site into the conf for creating
> filesystem. This will load any secret key, access key configured. It will
> also load any other necessary parameters.
> 2. Create a new view setting's parameter per view which will have semi colon
> separated key=value pairs that needs to be loaded into conf for connecting to
> the filesystem. This will cover any extra parameters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
