<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body bgcolor="#FFFFFF" text="#000000">
And it's actually not just optimizePredicates() that could prompt a
cardinality SQL statement on the actor thread. It can happen with
SegmentBuilder.toConstrainedColumns() as well. <br>
<br>
<br>
<div class="moz-cite-prefix">On 11/08/2013 11:41 AM, Luc Boudreau
wrote:<br>
</div>
<blockquote cite="mid:CAKTEAx-yBWG5GutFpK0kjZ_UyQy+xo42_7sj4A0h4EO8OeC0gg@mail.gmail.com" type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Nov 8, 2013 at 11:16 AM, Matt
Campbell <span dir="ltr"><<a moz-do-not-send="true" href="mailto:mcampbell@pentaho.com" target="_blank">mcampbell@pentaho.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Thread
(b) blocks waiting on the connection held by (a)</blockquote>
</div>
<br>
To me that's the core of the problem. The actor thread should
not run SQL statements; ever. But as we have realized while
browsing the code, moving the optimization phase isn't
trivial.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Still thinking about this...</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>