[
https://issues.apache.org/jira/browse/DERBY-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669100#action_12669100
]
Kathey Marsden commented on DERBY-3819:
---------------------------------------
I started looking at using optimizer directives to get the desired behavior but
the approach worries me. What is the value of forcing a hash join just to make
sure our check for a hash join passes? Seems a reasonable test for
DERBY-PROPERTIES but I don't know that it tests predicate pushdown behavior.
Perhaps I am way off and it is another directive that I should be using besides
joinStrategy. Any thoughts on this would be greatly appreciated.
> 'Expected Table Scan ResultSet for T3' in
> 'test_predicatePushdown(....PredicatePushdownTest)' since 670215 2008-06-21
> 18:01:08 MEST
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3819
> URL: https://issues.apache.org/jira/browse/DERBY-3819
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.5.0.0
> Environment: OS: Solaris 10 5/08 s10x_u5wos_10 X86 64bits - SunOS
> 5.10 Generic_127128-11 (sol)
> JVM: Sun Microsystems Inc.
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22 mixed mode 64-bit)
> Reporter: Ole Solberg
> Attachments: new_plan.txt, old_plan.txt
>
>
> 'test_predicatePushdown(org.apache.derbyTesting.functionTests.tests.lang.PredicatePushdownTest)junit.framework.AssertionFailedError:
> Expected Table Scan ResultSet for T3' since 670215 2008-06-21 18:01:08 MEST
> http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/670215.txt
> The failure is seen on SunOS 5.10 / Sun Jvm 1.6.0.
> See e.g.
> http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/sol/682186-suitesAll_diff.txt
> The test (suites.All) is run with '-XX:-UseThreadPriorities
> -XX:MaxPermSize=128M -Xmx256M -d64'.
> When run with '-XX:MaxPermSize=128M -Xmx256M' as is used for the other
> platforms in this set of tests we do not see a failure.
> The failure was also seen on Solaris Express Community Edition snv_86 X86bits
> - SunOS 5.11 snv_86 (solN+1) between 670215 and 676638.
> (Run w/ -XX:-UseThreadPriorities -XX:MaxPermSize=128M -Xmx256M -d32)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
