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 (JIRA)" <ji...@apache.org> on 2017/11/10 18:07:00 UTC
[jira] [Commented] (DERBY-6977) Autogenerated index name
occasionally generates a name which already exists
[ https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247866#comment-16247866 ]
Rick Hillegas commented on DERBY-6977:
--------------------------------------
The value is being generated by some convoluted, bogus-looking code in DataDictionaryImpl.getSystemSQLName(). I don't know why the DataDictionary doesn't use a UUID generator. I will try replacing this code with something UUID-based and see if that breaks anything. Thanks for bringing this weird code to my attention.
> Autogenerated index name occasionally generates a name which already exists
> ---------------------------------------------------------------------------
>
> Key: DERBY-6977
> URL: https://issues.apache.org/jira/browse/DERBY-6977
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.13.1.1
> Reporter: Trejkaz
>
> This has been happening for as long as I can remember, but v10.13.1.1 is the version we're currently at and I still see builds fail at random due to this.
> In a migration, we execute this statement:
> {noformat}
> CREATE TABLE GuidMappingCache (
> guidhigh BIGINT NOT NULL,
> guidlow BIGINT NOT NULL,
> luceneid INTEGER NOT NULL,
> PRIMARY KEY (guidhigh, guidlow)
> )
> {noformat}
> This randomly fails with the following sort of error:
> {noformat}
> Caused by: java.sql.SQLException: Index 'SQL171110050418720' already exists in Schema 'APP'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at OurCode.execute(...)
> Caused by: ERROR X0Y32: Index 'SQL171110050418720' already exists in Schema 'APP'.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(Unknown Source)
> at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CreateIndexConstantAction.executeConstantAction(Unknown Source)
> at org.apache.derby.impl.sql.execute.CreateConstraintConstantAction.executeConstantAction(Unknown Source)
> at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(Unknown Source)
> at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> ... 37 more
> {noformat}
> The last time someone was looking into this, it was somehow very reproducible for them but not for anyone else. I'm now seeing it occasionally on tests on our build farm. As usual, no matter how many times I run the test here, I can't get the same failure to occur.
> How is this value being generated?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)