[
https://issues.apache.org/jira/browse/PHOENIX-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259231#comment-14259231
]
James Taylor commented on PHOENIX-1516:
---------------------------------------
Thanks, [~lhofhansl]. So that the Phoenix reset method is called at the same
time for both client and server, how about this logic?
- In evaluate, if this.random is not null, use that value, else generate and
assign it.
- In RandomFunction.reset(), set this.random to null
- Don't set this.random at construction/init() time
- Create the new ResetRowProjectionIterator that calls RowProjector.reset()
after the call to next() if not null.
That way, the calling sequence matches for both client and server.
We haven't done 4.3 yet - waiting on one more JIRA, so you have a bit more time
if you think you might be able to get it finished. Things are understandably a
little slowed down during the holidays, which is fine. We can't introduce new
built-ins at point releases, though, b/c it would cause issues if the
client-side is deployed first (and the new function is called).
> Add RANDOM built-in function
> ----------------------------
>
> Key: PHOENIX-1516
> URL: https://issues.apache.org/jira/browse/PHOENIX-1516
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: 1516-v2.txt, 1516-v3.txt, 1516.txt
>
>
> I often find it useful to generate some rows with random data.
> Here's a simple RANDOM() function that we could use for that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
