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

ASF GitHub Bot commented on TAJO-1176:
--------------------------------------

Github user hyunsik commented on the pull request:

    https://github.com/apache/tajo/pull/273#issuecomment-65762633
  
    It's really great job. I briefly investigated it in order to give good 
reviews. I'm still reviewing it. I'll give more comments soon.
    
    Now, I have one suggestion or discussion agenda related to this issue. It 
would be nice if ultimately we have a direction like **INFORMATION SCHEMA** 
(http://en.wikipedia.org/wiki/Information_schema). You may already know this 
concept more than me. It is required for Tajo to follow ANSI SQL standard. 
    
    BTW, I don't think that we have to do it in this issue. We can commit your 
current work now, and mark it as an experimental and evolving feature, Then, we 
change it later if other committers agree with my suggestion. I'd also like to 
help this work.
    
    The following is my suggestion for the future. There may be two approaches 
to achieve ```INFORMATION SCHEMA```.
    
    One is that we change current schemas to follow ```INFORMATION SCHEMA```. 
But, this approach requires lots of burden. Also, it may be hard to optimize 
table schemas for our system characteristics.
    
    Another approach is to provide virtual tables for ```INFORMATION SCHEMA```. 
Actually, we don't need to have catalog schemas which are physically equivalent 
to ```INFORMATION SCHEMA```. For example, Postgresql uses different schemas to 
maintain its catalog, but it provides a virtual table to show information 
schema. I think that we can do like them.
    
    * information schema of pgsql - 
http://www.postgresql.org/docs/current/interactive/information-schema.html
    * internal catalog schema of pgsql - 
http://www.postgresql.org/docs/current/interactive/catalogs.html
    
    How do you think about my future direction?


> Implements queryable virtual tables for catalog information
> -----------------------------------------------------------
>
>                 Key: TAJO-1176
>                 URL: https://issues.apache.org/jira/browse/TAJO-1176
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Jihun Kang
>            Assignee: Jihun Kang
>            Priority: Trivial
>             Fix For: 0.9.1
>
>
> I would like to propose queryable interfaces for catalog information. And 
> these information may contain tables, columns, any other information on tajo 
> catalog.
> Currently, TajoCli offers some meta commands for retrieving table list, 
> however queryable virtual tables can provide a handy way to tajo users.



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

Reply via email to