You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alexandra Rodoni (Jira)" <ji...@apache.org> on 2019/12/14 02:26:00 UTC

[jira] [Comment Edited] (IMPALA-8405) Document UDA state machine

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

Alexandra Rodoni edited comment on IMPALA-8405 at 12/14/19 2:25 AM:
--------------------------------------------------------------------

Courtesy of Peter Ebert @ Cloudera.
 !screenshot-1.png! 


was (Author: arodoni_cloudera):
 !screenshot-1.png! 

> Document UDA state machine
> --------------------------
>
>                 Key: IMPALA-8405
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8405
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Docs
>            Reporter: Tim Armstrong
>            Assignee: Alexandra Rodoni
>            Priority: Major
>         Attachments: screenshot-1.png
>
>
> The documentation in "The Underlying Functions for a UDA" doesn't do a good job of explaining the state transitions that a UDA can go through. E.g. when is Serialize() called. It's complicated because data needs to be serialized to go over the network, but *sometimes* is serialized to spill to disk, which changes the sequence of function calls.
> See https://community.cloudera.com/t5/Interactive-Short-cycle-SQL/Function-execution-flow-in-UDAs-and-memory-implications-for/m-p/88892#M5532?eid=1&aid=1 for a user who is trying to understand this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org