Consider the following derived metric, namespace.derived, which is defined as namespace.metric * 2
There are 2 dependencies: namespace.metric and namespace (where namespace is speculatively a dependency because of the rsplit code to accommodate the case where it's a dimension node)
Now DJ will check if any of these dependencies is unsatisfied
If namespace.metric is NOT part of the deployment:
namespace.metric -> found it in external system, satisfied
namespace -> is the start of namespace.metric, satisfied
If namespace.metric is part of the deployment:
namespace.metric -> satisfied
namespace -> unsatisfied (but DJ is wrong)
So we have a bug where namespace is wrongly declared an unsatisfied dependency
Consider the following derived metric,
namespace.derived, which is defined asnamespace.metric * 2There are 2 dependencies:
namespace.metricandnamespace(wherenamespaceis speculatively a dependency because of thersplitcode to accommodate the case where it's a dimension node)Now DJ will check if any of these dependencies is unsatisfied
If
namespace.metricis NOT part of the deployment:namespace.metric-> found it in external system, satisfiednamespace-> is the start ofnamespace.metric, satisfiedIf
namespace.metricis part of the deployment:namespace.metric-> satisfiednamespace-> unsatisfied (but DJ is wrong)So we have a bug where
namespaceis wrongly declared an unsatisfied dependency