[
https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2493:
--------------------------------------
Attachment: derby-2493-aggregate.stat
derby-2493-aggregate.diff
The only part of lang/aggregate.sql that is sensitive to the Hashtable changes,
is the repro for DERBY-280. Attaching a patch (derby-2493-aggregate) which
moves that part into lang.GroupByTest. The new JUnit test case uses
assertUnorderedResultSet to avoid the problem with different row order (except
for one query which already specifies an explicit ORDER BY).
> Use unsynchronized collections in BackingStoreHashtable
> -------------------------------------------------------
>
> Key: DERBY-2493
> URL: https://issues.apache.org/jira/browse/DERBY-2493
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Knut Anders Hatlen
> Priority: Minor
> Attachments: derby-2493-aggregate.diff, derby-2493-aggregate.stat,
> derby-2493-assert.diff, derby-2493-assert.stat
>
>
> BackingStoreHashtable uses a Vector and a Hashtable, but doesn't need the
> synchronization provided by these classes (I think). Replacing them with
> ArrayList and HashMap could improve performance for some kinds of operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
