[ https://jira.jboss.org/jira/browse/TEIID-908?page=com.atlassian.jira.plug... ] John Doyle commented on TEIID-908: ---------------------------------- The DTP APIs for this pass the plan around as a String, and I need to provide at minimum a parser to convert the string to a tree of nodes for the view they supply. Either text or xml would work for me. A PlanNode type of return would be ideal, but the intent is to stick to JDBC and core java classes with no dependency on our classes. I don't know how you could expose a PlanNode type of return with that limitation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/TEIID-908?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-908: -------------------------------------- To be a little more concrete about possible implementations: assuming that you still want to use the PlanNode API one possibility given access to the statement object: PlanNode plan = statement.unwrap(com.metamatrix.jdbc.api.Statement.class).getPlanDescription(); which allows you to safely get to our api without casting. Another option would be ... statement.executeQuery("select .... option showplan"); ... statement.executeQuery("showplan [text|xml]"); which would create a resultset containing a single column/row with either the text or the SQL/XML representation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/TEIID-908?page=com.atlassian.jira.plug... ] John Doyle commented on TEIID-908: ---------------------------------- I'll look into Steve's suggestions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-908?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-908: ------------------------------------- So does PlanNode plan = statement.unwrap(org.teiid.jdbc.TeiidStatement.class).getPlanDescription(); meet your needs, or would it be better to get the results as XML directly so that there is no dependency on the org.teiid.client.plan.PlanNode class? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-908?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-908: ------------------------------------- What seems best is to add SHOW statement handling into the driver, just like the SET statement it is handled on the client side. Proposed usage: SHOW PLAN returns a resultset with a clob column PLAN_TEXT, an xml column PLAN_XML, and a clob column DEBUG_LOG with a row containing these values from the previously executed query. SHOW ANNOTATIONS returns a resultset with string columns CATEGORY, PRIORITY, ANNOTATION, RESOLUTION and a row for each annotation on the previously executed query. SHOW <property> - the inverse of SET, shows the property value for the given property. we could consider PLAN, ANNOTATIONS, and ALL to be reserved property keys. returns a resultset with a single string column with a name matching the property key. SHOW ALL returns a resultset with a NAME string column and a VALUE string column with a row entry for every property value -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-908?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-908. --------------------------------- Resolution: Done added the show logic as described and updated the docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira