[ 
https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208121#comment-15208121
 ] 

ASF GitHub Bot commented on PHOENIX-1311:
-----------------------------------------

Github user ankitsinghal commented on the pull request:

    https://github.com/apache/phoenix/pull/153#issuecomment-200264320
  
    Currently ,VIEW can be created in different schema name than it's base 
table name. are you recommending to use same schema?
    
    I checked MySQL and postgres and they also allow creation of VIEW in 
different namespace/schema than its physical table. (may be it's because VIEW 
is logical and can be created on joined tables residing in different namespaces 
[though phoenix doesn't support join query in VIEW currently])
    
    http://dev.mysql.com/doc/refman/5.7/en/create-view.html
    http://www.postgresql.org/docs/9.2/static/sql-createview.html
    "If a schema name is given (for example, CREATE VIEW myschema.myview ...) 
then the view is created in the specified schema. Otherwise it is created in 
the current schema"
    
    What do you think about VIEW Indexes created with different schema as they 
all share a single physical table for storage and currently with above changes 
we are keeping a index table in same hbase namespace as of it's base/physical 
table.


> HBase namespaces surfaced in phoenix
> ------------------------------------
>
>                 Key: PHOENIX-1311
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1311
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: nicolas maillard
>            Assignee: Ankit Singhal
>            Priority: Minor
>             Fix For: 4.8.0
>
>         Attachments: PHOENIX-1311.docx, PHOENIX-1311_v1.patch, 
> PHOENIX-1311_v2.patch, PHOENIX-1311_wip.patch, PHOENIX-1311_wip_2.patch
>
>
> Hbase (HBASE-8015) has the concept of namespaces in the form of 
> myNamespace:MyTable it would be great if Phoenix leveraged this feature to 
> give a database like feature on top of the table.
> Maybe to stay close to Hbase it could also be a create DB:Table...
> or DB.Table which is a more standard annotation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to