[
https://issues.apache.org/jira/browse/TAJO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jihoon Son resolved TAJO-573.
-----------------------------
Resolution: Won't Fix
I had a talk about this issue with Hyunsik in off-line. In the talk, we agreed
on that this issue doesn't need to be solved currently. When a real problem is
occured in later, we can reopen and solve this issue.
> Allow the same column in a schema
> ---------------------------------
>
> Key: TAJO-573
> URL: https://issues.apache.org/jira/browse/TAJO-573
> Project: Tajo
> Issue Type: Improvement
> Components: catalog
> Reporter: Jihoon Son
> Fix For: 0.8-incubating
>
>
> Recently, I have been working on TAJO-554, and I found that we should allow
> two or more same columns in a schema to handle the asterisk properly.
> My try in TAJO-554 is rewriting asterisks with their relations' schemas. So,
> the resulting schema can contain multiple same columns. Here is an example.
> {noformat}
> postgres=# select n_name, n_nationkey+10, *, n_regionkey from nation;
> n_name | ?column? | n_nationkey | n_name
> | n_regionkey |
> n_comment | n_regionkey
> ---------------------------+----------+-------------+---------------------------+-------------+--------------------------------------------------------------------------------------------------------------------+-------------
> ALGERIA | 10 | 0 | ALGERIA
> | 0 | haggle. carefully final deposits detect slyly agai
> | 0
> ARGENTINA | 11 | 1 | ARGENTINA
> | 1 | al foxes promise slyly according to the regular accounts.
> bold requests alon | 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
