The tag must be unique across all configurations per type. There can be only one core-site/version1, hdfs-site/version1 etc. You can make it anything you wish: core-site/1.0.0, hdfs-site/x.y.z.
When you create a configuration tag and assign it to a cluster, that one becomes the "current version." You can see that when you request: GET /api/v1/clusters/c1?fields=Clusters/desired_configs Thanks, Nate On 6/20/14 2:23 AM, 赵全超 wrote: > > > Hi, > > In ambari , when api client want to create a configuration file , it > need to provide a tag eg,”version1”. > > I want to know What are the rules to generate the tag in the ambari-web? > When a user want to get configuration file , how he know tag value? > > I think users does not care how many versions in ambari-server, more > concerned with latest version , > > So, maintain a version not more simple? > > > > ZhaoQuanchao > > > > China,Beijing > > > > > > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
