db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1866) Assert failure in sane mode for queries that used to work in 10.1.2.1
Date Tue, 26 Sep 2006 19:20:52 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1866?page=all ]

Mike Matrigali updated DERBY-1866:
----------------------------------


I ran  a success full set of tests against this patch against windows XP and ibm 1.4.2. jvm.
 I reviewed the changes and the extensive comments seemed to match up with what the code was
doing.  Looked like good tests were being added for the problem.  I am no optimizer expert
so I suggest at least one more reviewer before we consider moving this patch from the trunk
to 10.2 codeline.  Am committing this to the trunk to get it more testing.

If possible it would be good if anyone dependent on this change can test out the fix in the
trunk and verify it works for
them.

I committed this to the trunk:
m1_ibm142:5>svn commit

Sending        java\engine\org\apache\derby\impl\sql\compile\OptimizerImpl.java
Sending        java\testing\org\apache\derbyTesting\functionTests\master\predicatePushdown.out
Sending        java\testing\org\apache\derbyTesting\functionTests\tests\lang\predicatePushdown.sql
Transmitting file data ...
Committed revision 450155.

> Assert failure in sane mode for queries that used to work in 10.1.2.1
> ---------------------------------------------------------------------
>
>                 Key: DERBY-1866
>                 URL: http://issues.apache.org/jira/browse/DERBY-1866
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.1.3.2, 10.1.4.0, 10.2.1.5
>            Reporter: A B
>         Assigned To: A B
>             Fix For: 10.2.2.0, 10.3.0.0
>
>         Attachments: d1866_v1.patch, derby.log, repro.sql
>
>
> Derby-1777 gives a database and a small program called "ViewerInit" that prepares a bunch
of large queries involving nested subqueries, unions, and join predicates.  The actual bug
described in DERBY-1777 is an NPE, and that's what the patch for DERBY-1777 addresses.
> However, once the NPEs are fixed, some of the queries in that same program now fail with
ASSERT failures when running in SANE mode; this Jira issue is for addressing those assert
failures.
> While this does constitute a regression, I don't know yet what the root cause of the
problem is, so I hesitate to make it a 10.2 blocker--hence urgency is "Normal".  I'm still
investigating the queries to try to track down where the problem is, but all I've been able
to deduce so far is that a) the assertion occurs for a scoped predicate and thus the pushing
of join predicates into UNIONs is somehow involved, and b) in INSANE mode the query compiles
without problem and appears (based on some early and very incomplete testing) to execute without
problem.  But more investigation is required to determine if the execution/results are actually
correct, and to understand more about why the assertion is being thrown.
> I'm marking the fixin as 10.2.2.0 for now since I don't enough to make this a blocker
for 10.2.1.  Hopefully more info will be forthcoming...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message