You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/28 23:15:12 UTC
[jira] [Commented] (TRAFODION-1948) Scan returns duplicate rows
after drop schema cascade
[ https://issues.apache.org/jira/browse/TRAFODION-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263014#comment-15263014 ]
ASF GitHub Bot commented on TRAFODION-1948:
-------------------------------------------
GitHub user prashanth-vasudev opened a pull request:
https://github.com/apache/incubator-trafodion/pull/456
Fix for TRAFODION-1948
Drop schema cascade internally selects against objects table.
The fix is to use a distinct clause in the internal select query.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prashanth-vasudev/incubator-trafodion trafodion-1948
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/456.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #456
----
commit 6e674c65c2a9ebd05c53f8a88b4464601a24808f
Author: Prashant Vasudev <pr...@esgyn.com>
Date: 2016-04-28T21:12:17Z
Fix for TRAFODION-1948
Drop schema cascade internally selects against objects table.
The fix is to use a distinct clause in the internal select query.
----
> Scan returns duplicate rows after drop schema cascade
> -----------------------------------------------------
>
> Key: TRAFODION-1948
> URL: https://issues.apache.org/jira/browse/TRAFODION-1948
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Prashanth Vasudev
>
> After a series of statements followed by drop schema cascade, scan of objects table returns duplicate rows.
> >>drop schema "t4sch" cascade;
>
> *** ERROR[1069] Schema TRAFODION.t4sch could not be dropped. Reason: schema t4sch is not empty.
> ObjectsInSchema: SB_HISTOGRAMS SB_HISTOGRAMS
>
> *** ERROR[1073] Schema TRAFODION.t4sch was partially dropped, call CLEANUP SCHEMA to remove remaining entries.
>
> --- SQL operation failed with errors.
> >>
>
> >>drop implicit volatile schema cleanup cascade;
>
> *** ERROR[1069] Schema TRAFODION.VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 could not be dropped. Reason: schema VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 is not empty.
> ObjectsInSchema: T4TAB2 T4TAB2
>
> *** ERROR[1073] Schema TRAFODION.VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 was partially dropped, call CLEANUP SCHEMA to remove remaining entries.
>
> --- SQL operation failed with errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)