Github user sureshsubbiah commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1688#discussion_r221489512
--- Diff: core/sql/bin/SqlciErrors.txt ---
@@ -1515,6 +1515,9 @@ $1~String1 --------------------------------
8034 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Column $0~String0 of object
$1~string1 does not have a default clause but it is missing in database. This
indicates inconsistent data.
8035 ZZZZZ 99999 ADVANCED MAJOR DBADMIN Truncation of hive table failed.
$0~String0
8036 ZZZZZ 99999 ADVANCED MINOR LOGONLY Error while creating the error
logging file or logging the error row to file $0~String0: Details :$1~String1
+8037 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Loop detected in connect by
execution.
--- End diff --
In these three messages, it would help if we could give information
specific to the instance when the error occurred. Maybe value of the prior
column(s) as the error occurred. For the case of recursion exceeding a certain
length or memory being exhausted, more details what level of recursion has been
reached or how much memory has been consumed (if that information is readily
available) would be helpful. This is an advisory suggestion, and by no means
something to be addressed soon.
I would have expected some binder errors for statements where hierarchical
constructs are not supported. It is possible though unlikely that all are
caught in the parser. For example what happens if a hierarchical function or
pseudocolumn is used a regular (non-hierarchical query)
---
