You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/12/04 00:53:13 UTC
[jira] [Commented] (CALCITE-496) Allow key/value properties to be
passed through DDL statements
[ https://issues.apache.org/jira/browse/CALCITE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233686#comment-14233686 ]
Julian Hyde commented on CALCITE-496:
-------------------------------------
Calcite doesn't have support for DDL right now (except in the dusty archives of the original code base) and DDL tends to be very product-specific. I think we would take the same approach as Drill and let Phoenix "sub-class" the parser, using freemarker templates to add product-specific pieces, and CREATE TABLE can be one of these.
> Allow key/value properties to be passed through DDL statements
> --------------------------------------------------------------
>
> Key: CALCITE-496
> URL: https://issues.apache.org/jira/browse/CALCITE-496
> Project: Calcite
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: Julian Hyde
> Labels: phoenix
>
> Most database systems provide a means of passing through properties to define system-specific behavior. For example, the default block encoding for a table may need to be overridden. This can be done by allowing KEY=VALUE properties to be tacked onto the end of DDL statements. For examples, see http://phoenix.apache.org/language/index.html#create_table
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)