[
https://issues.apache.org/jira/browse/PHOENIX-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930704#comment-15930704
]
Julian Hyde commented on PHOENIX-3732:
--------------------------------------
Yes, as long as there's a conformance setting to disallow it. We'd probably
have to allow {{INSERT INTO t (c1, c2 int) VALUES (1, 2)}} (note the {{int}})
in the parser, but the validator would give an error if it was not phoenix
conformance (or, strictly, a new conformance method,
{{SqlConformance#allowExtend()}}).
> Support for dynamic columns in UPSERT in Phoenix-Calcite
> --------------------------------------------------------
>
> Key: PHOENIX-3732
> URL: https://issues.apache.org/jira/browse/PHOENIX-3732
> Project: Phoenix
> Issue Type: Bug
> Reporter: Kevin Liew
> Labels: calcite
>
> https://phoenix.apache.org/dynamic_columns.html
> {quote}
> To upsert a row with dynamic columns:
> UPSERT INTO EventLog (eventId, eventTime, eventType, lastGCTime TIME,
> usedMemory BIGINT, maxMemory BIGINT) VALUES(1, CURRENT_TIME(), ‘abc’,
> CURRENT_TIME(), 512, 1024);
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
