Re: [teiid-dev] [teiid-users] query plan changes
What I'm saying for the PlanNode is to simply remove most of the helper classes.
We'll just have the PlanNode (still available off of TeiidStatement) with basic output
to xml and text.
----- Original Message -----
From: "Ramesh Reddy" <rareddy(a)redhat.com>
To: "Steven Hawkins" <shawkins(a)redhat.com>
Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org>
Sent: Tuesday, April 6, 2010 1:35:30 PM GMT -06:00 US/Canada Central
Subject: Re: [teiid-users] query plan changes
Removed users and designer lists to avoid the duplicate emails.
On Tue, 2010-04-06 at 13:47 -0400, Steven Hawkins wrote:
SET SHOWPLAN [ON|DEBUG|OFF]
SET NOEXEC [ON|OFF] - general replacement for PLANONLY, will not
execute the command if ON
+1
I do like these concise commands compare to the old ones.
I would also like to remove most of the logic surrounding the
org.teiid.client.plan.PlanNode class. The visitors, display helpers,
etc. Since we don't publish a meaningful schema for the xml form(s)
or document the property keys we might as well assume that we're the
primary consumers and forgo the flexibility.
Currently we do use this in the
AdminShell and Designer to show the
query plans. I am not sure what you suggesting as an alternative for
these tools. Also, tooling was going to use this along with DTP to show
query plans. If the concern is lack of documents or schema I am in favor
of doing that work. We can add to the JDBC client developer's guide.
Ramesh..