[
https://issues.apache.org/jira/browse/TAJO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722106#comment-13722106
]
Jinho Kim edited comment on TAJO-87 at 7/29/13 2:32 AM:
--------------------------------------------------------
+1 Looks great.
Hyunsik,
The error handling code in the new parser is omitted. If you are ok, I'll move
the error handling code from the old parser to new parser.
was (Author: jhkim):
Hyunsik,
The error handling code in the new parser is omitted. If you are ok, I'll move
the error handling code from the old parser to new parser.
> Integration of tajo algebra module and SQL parser.
> --------------------------------------------------
>
> Key: TAJO-87
> URL: https://issues.apache.org/jira/browse/TAJO-87
> Project: Tajo
> Issue Type: Improvement
> Components: parser
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.2-incubating
>
> Attachments: TAJO-87.patch
>
>
> In the current implementation, QueryAnalyzer transforms a sql statement into
> a data structure that represents a parser tree and a query block. They has
> the following limitations:
> * They can't support multiple block queries including table and scalar
> subqueries.
> * They are tightly coupled to a certain grammar.
> Before ASF incubation, I have developed tajo-algebra and tajo-frontend-sql.
> Tajo-algebra is a kind of intermediate layer. It represents a just relational
> algebraic expression. With this, we can do more interesting things. For
> example, we can enable users to describe a logical plan for a certain query.
> It also very helpful to support an another DSL.
> For this work, tajo-algebra should be improved to support full
> specifications, and we should rewrite a SQL parser to use tajo-algebra.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
