ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Bukatovic (JIRA)" <>
Subject [jira] [Commented] (AMBARI-5181) HCFS Component for Ambari JIRAs
Date Wed, 07 Jan 2015 09:47:34 GMT


Martin Bukatovic commented on AMBARI-5181:

[~vijikarthi] You are right, hcfs JIRAs may be related to various components, eg. AMBARI-8658
is clearly a stack related, while there are issues related to multiple components as well:
eg. AMBARI-8468. On the other hand, there are issues without component (eg. AMBARI-8505) as
it's not immediatelly clear which is the right one (from the reporter perspective).

And since I needed some easy way to track hcfs related issues, I created [hcfs label|]
some time ago. What do you think about this approach? The downside is that me and [~dahorak]
are the only ones currently using it so far.

> HCFS Component for Ambari JIRAs
> -------------------------------
>                 Key: AMBARI-5181
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>            Reporter: jay vyas
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> Lets create an "HCFS" component for ambari JIRAs... ! ((( Ping [~erinaboyd] is this what
your thought is ? This was originally your idea, thanks for mentioning it ! )))
> Now that Ambari is HCFS Compliant (i.e. see,
it would be great if we were able to document and file bugs specific to HCFS related support
.. for example: 
> - if there was a bug associated with installing a file system plugin
> - if an HCFS ambari module breaks or causes ambari deployment to fail
> - if an HCFS is somehow not compliant with HDFS specific semantics in how ambari sets
up the file system... see BIGTOP-1200 / BIGTOP-952 as an how management tools "should" (or
at least "could") be doing HCFS provisioning :)  
> So, lets create an HCFS component where we can track any file system plugin and setup
related issues. 

This message was sent by Atlassian JIRA

View raw message