Non-local variables from let clauses are missing in subsequent for clauses about rumble HOT 3 CLOSED

I investigated. This query is known not to work but the error message deserved a better version.

RumbleDB now detects more proactively when a nested job attempts a parallel execution.

#1170

from rumble.

@ghislainfourny Thanks for the comments. Indeed technically this is a "job in a job" query, so it does make sense to directly throw an error. Although I just think that some expressions like count in the query I mentioned above will help avoid the nested job, because they can just return a long variable instead of a gigantic rdd/df variable.

from rumble.

@ghislainfourny Actually you are right, since the query can be rewritten to a working one:

let $i :=  count(parallelize((
     { "commits" : [ { "author" : "Einstein" } ], "repo":"r2"},
     { "commits" : [ { "author" : "Goedel" }, { "author" : "Ramanujan" } ], "repo": "r1"})).repo) 
for $j in parallelize(({"id": 1}, {"id": 2})) 
where $j.id < $i
return $j

So indeed a clearer error message in your fix is enough I think. I will close the issue. :)

from rumble.