Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
3.0.0-alpha1
-
None
-
Incompatible change
-
Description
Config var loop detection was originally introduced by HADOOP-6871. Due to cycle detection changes in the trunk patch for HADOOP-11506, resolution for multiple references to the same variable no longer resolved, e.g.
somekey = "${otherkey} ${otherkey}"
This loop detection business is fragile, expensive, and not in branch-2, so let's reduce it.
Attachments
Attachments
Issue Links
- is broken by
-
HADOOP-11506 Configuration variable expansion regex expensive for long values
- Closed
- supercedes
-
HADOOP-6871 When the value of a configuration key is set to its unresolved form, it causes the IllegalStateException in Configuration.get() stating that substitution depth is too large.
- Resolved