Steven Jacobs has posted comments on this change. Change subject: Enable job compilation for variables that will be created at runtime ......................................................................
Patch Set 3: Are they modifiable at runtime? When are they created/modified/deleted? These variables are specific to pre-distributed jobs (i.e. compile time and run time are vastly different). This means that the expressions for them are put in the plan when it is compiled and distributed. When the pre-distributed job is run, the value for these variables needs to be passed to the NCs, whose evaluators will use these values at runtime. The full list is overwritten each time the pre-distributed job is run. The list is part of the stored info for the job, so it will be deleted when the job is destroyed permanently. Why do we need a new expression type for them? Could the access be handled with regular variables or function calls? This was based off of my initial discussions with Yingyi. I'm curious for his thoughts on this change. I think potentially they could have been done with function calls, e.g. a new builtin function called getRuntimeContextVariable(String name). That's an interesting idea but vastly different from this implementation. If the consensus is that it should be done that way, I can redo the work. -- To view, visit https://asterix-gerrit.ics.uci.edu/1722 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ie66ed97d9c25cb64afc8ac38d6675211cf76d97b Gerrit-PatchSet: 3 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Steven Jacobs <[email protected]> Gerrit-Reviewer: Ildar Absalyamov <[email protected]> Gerrit-Reviewer: Jenkins <[email protected]> Gerrit-Reviewer: Steven Jacobs <[email protected]> Gerrit-Reviewer: Till Westmann <[email protected]> Gerrit-Reviewer: Yingyi Bu <[email protected]> Gerrit-HasComments: No
