[
https://issues.apache.org/jira/browse/TAJO-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647554#comment-14647554
]
ASF GitHub Bot commented on TAJO-1723:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/668
TAJO-1723: INSERT INTO statement should allow nested fields as target
columns.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1723
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/668.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #668
----
commit 5faaeccdf3e1ccffa445107ac65ed6a0cef11f54
Author: Hyunsik Choi <[email protected]>
Date: 2015-07-30T11:00:12Z
initial work
* Improve SQL parser to recognize nested target fields in INSERT INTO
statement.
* Add workaround for hanging TaskContainer.
* Improve logical planner to recognize nested target fields in INSERT INTO
statement.
commit ef499b3dffa846d31462c5a4be9042d83eec9ed1
Author: Hyunsik Choi <[email protected]>
Date: 2015-07-30T12:21:33Z
TAJO-1723: INSERT INTO statement should allow nested fields as target
columns.
commit 334db6d0cf471fd1f00a41ee44133ac70d1153e6
Author: Hyunsik Choi <[email protected]>
Date: 2015-07-30T12:23:43Z
Refine changes.
commit e9acd683a1e075c20bc78ca26058a84b1305b078
Author: Hyunsik Choi <[email protected]>
Date: 2015-07-30T12:24:57Z
Moved some methods to SchemaUtil.
----
> INSERT INTO statement should allow nested fields as target columns
> ------------------------------------------------------------------
>
> Key: TAJO-1723
> URL: https://issues.apache.org/jira/browse/TAJO-1723
> Project: Tajo
> Issue Type: Sub-task
> Components: Planner/Optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.11.0
>
>
> INSERT INTO statement support target fields. For example, you can specify
> target column as follows:
> {code}
> INSERT INTO t1 (c1, c3) SELECT x, y FROM t2
> {code}
> But, the current INSERT INTO statement does not support nested fields as
> target columns. We should support it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
