[
https://issues.jboss.org/browse/TEIID-1632?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1632:
---------------------------------------
At this point given our usage of implicit cursoring, a procedure language level
enhancement would be most appropriate. Having a procedure or log function would cause the
implicit return cursor to be set from that statement.
So we would have something like:
OUTPUT LOG [level] [context] message
The OUTPUT reserved word would be needed to disambiguate the parsing. level could be
integral, or the Log4j level mnemonics, or the jre Level mnemonics. it would default to
the appropriate debug level. Context would be a string and default to
org.teiid.PROCESSOR
We could make the message expression evaluation contingent upon whether the log will
actually be recorded. But we'd probably also have to add a boolean system function
for more complicated scenarios:
IF (isLoggable(level, context))
BEGIN
//complex concat of message
OUTPUT LOG ....
END
The logs would then be delivered to the underlying log4j logging system.
Any thoughts?
Provide something like an ECHO statement in the procedure language
that can assist a user in debugging their procedure logic
-----------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1632
URL:
https://issues.jboss.org/browse/TEIID-1632
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Provide something like an ECHO statement in the procedure language that can assist a user
in debugging their procedure logic
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira