[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12424412 ]
Mamta A. Satoor commented on DERBY-1543:
----------------------------------------
Satheesh, I ran the upgrade test (upgradeTests/Upgrade_10_1_10_2.java) on a
clean client and the test failed. It has following stack trace
SQLSTATE(XSAI2):ERROR XSAI2: The conglomerate (-1) requested does not exist.
at
org.apache.derby.iapi.error.StandardException.newException(StandardException.java:304)
at
org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(RAMTransaction.java:394)
at
org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(RAMTransaction.java:1315)
at
org.apache.derby.impl.sql.catalog.TabInfoImpl.getRow(TabInfoImpl.java:794)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.dropTablePermDescriptor(DataDictionaryImpl.java:2509)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.dropAllTableAndColPermDescriptors(DataDictionaryImpl.java:2416)
at
org.apache.derby.impl.sql.execute.DropTableConstantAction.executeConstantAction(DropTableConstantAction.java:219)
at
org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:56)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:357)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1181)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:584)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:516)
at
org.apache.derbyTesting.functionTests.tests.jdbcapi.metadata_test.runTest(metadata_test.java:1192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runMetadataTest(UpgradeTester.java:900)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runPhase(UpgradeTester.java:367)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runUpgradeTests(UpgradeTester.java:314)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.Upgrade_10_1_10_2.main(Upgrade_10_1_10_2.java:43)
Could this be related to your recent changes for dropping the permission
descriptors associated with a table? If not, may be I should open a new jira
for upgrade test failure.
ps I have been out of the loop for last couple days because my laptop died on
Thursday. So I hope this is not a known issue and there is already somebody
working on it.
> Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning
> when sqlAuthorization is on with authentication off 2) Drop permission
> descriptors when objects they cover are dropped.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1543
> URL: http://issues.apache.org/jira/browse/DERBY-1543
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.2.0.0
> Reporter: Satheesh Bandaram
> Assigned To: Satheesh Bandaram
> Fix For: 10.2.0.0
>
> Attachments: DERBY-1543.out, Derby1543.diff
>
>
> Address two remaining sub-tasks:
> Add warning when sqlAuthorization is on with authentication off: This is a
> precautionary warning, since sqlAuthorization doesn't mean much without
> authentication being ON.
> Drop permission descriptors when objects they cover are dropped: This applies
> to tables, routines. When these objects are dropped, automatically drop their
> permisson descriptors.
--
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
