[
https://issues.apache.org/jira/browse/PHOENIX-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-2874:
-----------------------------------
Attachment: PHOENIX-2874_v3.patch
bq. The DROP SCHEMA call should respect the QueryServices.DROP_METADATA_ATTRIB
parameter as well.
Yes, Thanks James for checking. Now in attached patch, DROP SCHEMA also respect
the mentioned config.
bq. Also, the CREATE SCHEMA call should only throw if the SYSTEM.CATALOG has
the schema already, but not if the namespace already exists. That'd be
consistent with how we handle tables.
Yes , CREATE SCHEMA throws when schema already exists and not if namespace
already exists.
> Delete schemas also during clean up after test
> -----------------------------------------------
>
> Key: PHOENIX-2874
> URL: https://issues.apache.org/jira/browse/PHOENIX-2874
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Attachments: PHOENIX-2874.patch, PHOENIX-2874_v1.patch,
> PHOENIX-2874_v2.patch, PHOENIX-2874_v3.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
