phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Liew (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3732) Support for dynamic columns in UPSERT in Phoenix-Calcite
Date Tue, 14 Mar 2017 03:34:41 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923496#comment-15923496
] 

Kevin Liew commented on PHOENIX-3732:
-------------------------------------


To clarify, Phoenix supports the following syntax with dynamic columns specified separately
after the table
{code:sql}
SELECT eventTime, lastGCTime, usedMemory, maxMemory
FROM EventLog(lastGCTime TIME, usedMemory BIGINT, maxMemory BIGINT)
WHERE eventType = 'OOM' AND lastGCTime < eventTime - 1
{code}

but not embedding the dynamic column definitions with the {{SELECT}} columns (but it is supported
in the {{UPSERT}} case)
{code:sql}
SELECT eventTime, lastGCTime TIME, usedMemory BIGINT, maxMemory BIGINT
FROM EventLog
WHERE eventType = 'OOM' AND lastGCTime < eventTime - 1
{code}

Is this something we want to support in Calcite and/or Phoenix?

> 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)

Mime
View raw message