Remus Rusanu created CALCITE-1817:
-------------------------------------
Summary: Use of singleton CyclicMetadataException.INSTANCE hides
original exception stack trace
Key: CALCITE-1817
URL: https://issues.apache.org/jira/browse/CALCITE-1817
Project: Calcite
Issue Type: Bug
Components: core
Reporter: Remus Rusanu
Assignee: Julian Hyde
Priority: Minor
The JaninoRelMetadataProvider GeneratedMetadataHandler_XXX classes throw a
singleton CyclicMetadataException instance to signal a cycle detection. this is
for performance, as the exception is used in this context as flow control
(exception is expected and ignored by
{{RelMdColumnUniqueness.areColumnsUnique(RelSubset rel,...)}}.
But when the exception occurs in any other context (as I experienced in
CALCITE-1816) it makes debugging problematic because the reported stack is one
captured at some random initialization of the singleton in the past.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
