You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (Created) (JIRA)" <ji...@apache.org> on 2012/04/09 14:59:19 UTC
[jira] [Created] (DERBY-5687) Back out the concurrency improvements
for identity columns introduced by derby-4437
Back out the concurrency improvements for identity columns introduced by derby-4437
-----------------------------------------------------------------------------------
Key: DERBY-5687
URL: https://issues.apache.org/jira/browse/DERBY-5687
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.9.0.0
Reporter: Rick Hillegas
DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DERBY-5687) Back out the concurrency
improvements for identity columns introduced by derby-4437
Posted by "Kristian Waagan (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan reassigned DERBY-5687:
--------------------------------------
Assignee: Rick Hillegas
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5687) Back out the concurrency improvements
for identity columns introduced by derby-4437
Posted by "Rick Hillegas (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5687:
---------------------------------
Attachment: derby-5687-02-aa-publicAPI.diff
Attaching derby-5687-02-aa-publicAPI.diff. This patch adjusts the javadoc for SequencePreallocator, which appears in Derby's public API. The patch removes references to identity columns so that the javadoc now only talks about sequences. Committed at subversion revision 1311310.
Touches the following file:
M java/engine/org/apache/derby/catalog/SequencePreallocator.java
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5687) Back out the concurrency improvements
for identity columns introduced by derby-4437
Posted by "Rick Hillegas (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5687:
---------------------------------
Attachment: derby-5687-01-aa-backOutImprovement.diff
Attaching derby-5687-01-aa-backOutImprovement.diff. This patch backs out concurrency improvements introduced by DERBY-4437. Regression tests passed cleanly for me. Committed at subversion 1311285.
More specifically, this patch backs out the following patches:
derby-4437-01-aj-allTestsPass.diff
The main patch which ported the work on sequences to identity columns.
derby-4437-02-ac-alterTable-bulkImport-deferredInsert.diff
Test cases to verify that the port did not break various features.
derby-4437-03-aa-upgradeTest.diff
Upgrade/downgrade tests for the port.
Touches the following files:
M java/storeless/org/apache/derby/impl/storeless/EmptyDictionary.java
M java/engine/org/apache/derby/impl/sql/compile/CreateSequenceNode.java
M java/engine/org/apache/derby/impl/sql/compile/NextSequenceNode.java
M java/engine/org/apache/derby/impl/sql/execute/InsertResultSet.java
M java/engine/org/apache/derby/impl/sql/execute/BaseActivation.java
M java/engine/org/apache/derby/impl/sql/execute/InsertConstantAction.java
M java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java
M java/engine/org/apache/derby/impl/sql/catalog/SequenceUpdater.java
M java/engine/org/apache/derby/iapi/sql/dictionary/DataDictionary.java
M java/engine/org/apache/derby/iapi/sql/dictionary/SequenceDescriptor.java
M java/engine/org/apache/derby/iapi/reference/Property.java
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/AlterTableTest.java
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/AutoIncrementTest.java
D java/testing/org/apache/derbyTesting/functionTests/tests/lang/t_4437_2.dat
M java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/Changes10_9.java
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5687) Back out the concurrency improvements
for identity columns introduced by derby-4437
Posted by "Rick Hillegas (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5687:
---------------------------------
Attachment: derby-5687-03-aa-adjustUserDocs.diff
Attaching derby-5687-03-aa-adjustUserDocs.diff. This patch adjusts the reference guide so that it no longer mentions identity columns when discussing sequence pre-allocators. Committed at subversion revision 1311312.
Touches the following files:
M src/ref/rrefsqlj37836.dita
M src/ref/rrefsqljcreatesequence.dita
M src/ref/rrefproperpreallocator.dita
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5687) Back out the concurrency
improvements for identity columns introduced by derby-4437
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251158#comment-13251158 ]
Myrna van Lunteren commented on DERBY-5687:
-------------------------------------------
For what it's worth, with sane jars built sync-ed up to revision 1311499 I ran the 'Embedded small' nstest 10 times on a windows machine where before I would see at least 3 to 5 of the runs have SYSCOLUMNS deadlocks, and/or Asserts complaining about either transaction not pristine, or transaction changed on live cacheable...And this time there were none of these problems.
I'll start closing the various bugs that represent these issues.
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DERBY-5687) Back out the concurrency
improvements for identity columns introduced by derby-4437
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas resolved DERBY-5687.
----------------------------------
Resolution: Fixed
Resolving this issue. The change was backed out. DERBY-4437 remains open but the other related bugs have been closed.
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5687) Back out the concurrency improvements
for identity columns introduced by derby-4437
Posted by "Rick Hillegas (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-5687:
---------------------------------
Attachment: derby-5687-03-aa-adjustUserDocs.diff
Re-attaching the user docs changes in order to grant the license to ASF.
> Back out the concurrency improvements for identity columns introduced by derby-4437
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5687
> URL: https://issues.apache.org/jira/browse/DERBY-5687
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5687-01-aa-backOutImprovement.diff, derby-5687-02-aa-publicAPI.diff, derby-5687-03-aa-adjustUserDocs.diff, derby-5687-03-aa-adjustUserDocs.diff
>
>
> DERBY-4437 attempted to improve the concurrency of identity columns by using SYSSEQUENCE-style sequence generators. These improvements caused NsTest to behave differently than it used to and they disclosed a problem in clearing the identity cache. The community lost confidence in this solution and it was backed out of the 10.8 branch under issue DERBY-5448. This new issue is filed to back the improvements out of the 10.9 trunk. Further useful discussion about how to improve the concurrency and correctness of identity columns has been taking place on DERBY-5443 and DERBY-5493.
> For the 10.9 release, identity columns will return to their old behavior of being ill-suited for high concurrency applications. Applications which need higher concurrency should be re-coded to use sequences rather than identity columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira