phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-2999) Upgrading Multi-tenant table to map with namespace using upgradeUtil
Date Thu, 23 Jun 2016 18:34:16 GMT


Ankit Singhal updated PHOENIX-2999:
    Attachment: PHOENIX-2999_v1.patch

bq.  is there a way we can check what namespaces are views and view indexes getting mapped
to? Can you add a test for the same?
Done in the latest patch.

bq. Or point me to test cases where you are checking that views with different schema names
are mapped to the same namespace as the data table.
- You mean view indexes right? Views with different schema names can exist without namespace
mapping. ViewIndexIT and ViewIT.testViewAndTableInDifferentSchemasWithNamespaceMappingEnabled
somewhat has test cases for the same.

bq. Similarly, tests to assert that view indexes on these views are all mapped to the same
name space as data table.Also, it would be better to have different view names and view indexes
for global and tenant specific connections.
Done in the latest patch

> Upgrading Multi-tenant table to map with namespace using upgradeUtil
> --------------------------------------------------------------------
>                 Key: PHOENIX-2999
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0
>            Reporter: Ankit Singhal
>            Assignee: Ankit Singhal
>             Fix For: 4.8.0
>         Attachments: PHOENIX-2999.patch, PHOENIX-2999_v1.patch
> currently upgradeUtil doesn't handle multi-tenant table with tenant views properly.

This message was sent by Atlassian JIRA

View raw message