[
https://issues.apache.org/jira/browse/TAJO-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237347#comment-14237347
]
ASF GitHub Bot commented on TAJO-1176:
--------------------------------------
Github user ykrips commented on the pull request:
https://github.com/apache/tajo/pull/273#issuecomment-65966012
Hello @hyunsik,
Yes, information schema is definitely ansi standard, and it would be better
if we follow this standard. I agree with your opinion that implementing
information schema is needed to split into multiple tasks, and catalog store
and any other components needs to change to handle more information. It
requires more time, and adopting a new feature could need lots of efforts on it.
And let's talk about the strategy on information schema implementation. I
would like to vote the second approach. I think that the first one would limit
the capability of Tajo. When Tajo supports the view on it, we can define the
information schema with this view feature.
> 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)
