Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27F9010ED0 for ; Tue, 5 Nov 2013 14:45:44 +0000 (UTC) Received: (qmail 3409 invoked by uid 500); 5 Nov 2013 14:45:37 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 3278 invoked by uid 500); 5 Nov 2013 14:45:30 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 3224 invoked by uid 99); 5 Nov 2013 14:45:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 14:45:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [213.199.154.189] (HELO db8outboundpool.messaging.microsoft.com) (213.199.154.189) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 14:45:15 +0000 Received: from mail25-db8-R.bigfish.com (10.174.8.238) by DB8EHSOBE015.bigfish.com (10.174.4.78) with Microsoft SMTP Server id 14.1.225.22; Tue, 5 Nov 2013 14:44:55 +0000 Received: from mail25-db8 (localhost [127.0.0.1]) by mail25-db8-R.bigfish.com (Postfix) with ESMTP id 22E4C1240313 for ; Tue, 5 Nov 2013 14:44:55 +0000 (UTC) X-Forefront-Antispam-Report: CIP:143.239.1.23;KIP:(null);UIP:(null);IPV:NLI;H:mail3.ucc.ie;RD:mail3.ucc.ie;EFVD:NLI X-SpamScore: 0 X-BigFish: VPS0(zz4015Izz1f42h2148h208ch1ee6h1de0h1d18h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1de097hz2dh2a8h6f5h839h947hd24he40he5bhf0ahfa3h1288h12a5h12a9h12bdh137ah13b6h1441h1473h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1b0ah2222h1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1ff5h209eh2216h223bi1155h) Received: from mail25-db8 (localhost.localdomain [127.0.0.1]) by mail25-db8 (MessageSwitch) id 1383662692798080_3949; Tue, 5 Nov 2013 14:44:52 +0000 (UTC) Received: from DB8EHSMHS012.bigfish.com (unknown [10.174.8.244]) by mail25-db8.bigfish.com (Postfix) with ESMTP id BF601F4004C for ; Tue, 5 Nov 2013 14:44:52 +0000 (UTC) Received: from mail3.ucc.ie (143.239.1.23) by DB8EHSMHS012.bigfish.com (10.174.4.22) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 5 Nov 2013 14:44:48 +0000 Received: from 4c.ucc.ie (4c.ucc.ie [143.239.201.140]) by mail3.ucc.ie (8.14.4/8.14.4) with ESMTP id rA5EimXt030158 for ; Tue, 5 Nov 2013 14:44:48 GMT Received: from 4c.ucc.ie (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by 4c.ucc.ie (Postfix) with ESMTPS id 5F732316001 for ; Tue, 5 Nov 2013 14:44:48 +0000 (GMT) Received: (from apache@localhost) by 4c.ucc.ie (8.14.3/8.14.3/Submit) id rA5EimsX013818; Tue, 5 Nov 2013 14:44:48 GMT X-Authentication-Warning: 4c.ucc.ie: apache set sender to pdavern@localhost using -f Received: from 86.45.102.220 (SquirrelMail authenticated user pdavern) by 4c.ucc.ie with HTTP; Tue, 5 Nov 2013 14:44:48 -0000 Message-ID: Date: Tue, 5 Nov 2013 14:44:48 +0000 Subject: Execution tree metadata From: Paul Davern To: User-Agent: SquirrelMail/1.4.19-2.fc10 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-OriginatorOrg: 4c.ucc.ie X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-Virus-Checked: Checked by ClamAV on apache.org Hello I am looking at =93monitoring/tracing=94 the resultset execution tree to observe the tuples/records as they propagate up the tree - specifically the calls to getNextRowCore() in BulkTableScanResultSet, NestedLoopJoinResultSet, etc. For aggregations I am looking at using the SortObserver type interface. There does not appear to be much in the way of metadata available (at least I have not found it) in the execution tree? I am traversing the AST tree after bind/generate to pick up some of the metadata. This is easy enough when a column is directly associated with a base table, but, is getting hacky otherwise. Is there a better solution? Putting something in during the generate phase looks like a daunting task! I realise I can use the toXML/childrenToXML interface to walk the execution tree, but there does not appear to be much in the way of metadata here. I suppose what I am asking is, is there a direct link from the=20 org.apache.derby.impl.sql.execute.ResultSet hierarchy back to the org.apache.derby.impl.sql.compile.ResultSetNode hierarchy? Thanks, Paul.