[
https://issues.apache.org/jira/browse/TRAFODION-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370292#comment-16370292
]
ASF GitHub Bot commented on TRAFODION-2954:
-------------------------------------------
Github user zellerh commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1444#discussion_r169392533
--- Diff: core/sql/optimizer/GroupAttr.cpp ---
@@ -1793,6 +1793,8 @@ void
GroupAttributes::resolveCharacteristicInputs(const ValueIdSet& externalInpu
ItemExpr * vidExpr = vid.getItemExpr();
if ((vidExpr->getOperatorType() == ITM_CURRENT_USER) ||
(vidExpr->getOperatorType() == ITM_CURRENT_TIMESTAMP) ||
+ (vidExpr->getOperatorType() == ITM_UNIQUE_SHORT_ID) ||
+ (vidExpr->getOperatorType() == ITM_UNIQUE_ID) ||
--- End diff --
This comment applies to all the changes in this commit: Don't these code
changes do the opposite of what you want to achieve? Functions like
CURRENT_TIMESTAMP and CURRENT_USER are carefully designed such that we execute
them only once per query, in the master. You want to make sure your functions
are evaluated once per row. Did you find that these changes helped fix the
issues you were seeing?
> support sleep/unix_timestamp/uuid/uuid_short of MySQL
> -----------------------------------------------------
>
> Key: TRAFODION-2954
> URL: https://issues.apache.org/jira/browse/TRAFODION-2954
> Project: Apache Trafodion
> Issue Type: Sub-task
> Reporter: liu ming
> Assignee: liu ming
> Priority: Major
>
> support these MySQL functions:
> uuid
> uuid_short
> unix_timestamp
> sleep
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
