[
https://issues.apache.org/jira/browse/AMBARI-13057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-13057:
-------------------------------
Description:
Every invocation of MessageFormat.format() should use a number specifier:
{0,number,#} where a long is used to build queries.
This issue can occur with any Ambari DB when the cluster has 1000+ components.
Therefore, there is a high risk of this problem occurring on a cluster with
200+ hosts (which translates to 1000+ components, assuming 5 components per
host).
was:
Every invocation of MessageFormat.format() should use a number specifier:
{0,number,#} where a long is used to build queries.
This issue can occur with any Ambari DB when the cluster has 1000+ components.
Therefore, there is a high risk of this problem occurring on a cluster with >
200+ hosts (which translates to 1000+ components, assuming 5 components per
host).
> UpgradeCatalogs should use integer specifiers
> ---------------------------------------------
>
> Key: AMBARI-13057
> URL: https://issues.apache.org/jira/browse/AMBARI-13057
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-13057.patch
>
>
> Every invocation of MessageFormat.format() should use a number specifier:
> {0,number,#} where a long is used to build queries.
> This issue can occur with any Ambari DB when the cluster has 1000+
> components. Therefore, there is a high risk of this problem occurring on a
> cluster with 200+ hosts (which translates to 1000+ components, assuming 5
> components per host).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
