This repository has been archived by the owner on Jul 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 20
[JIT] map function with tuple input #353
Comments
In fact, I realize that "map" is not really "Map", so the problem is probably elsewhere. Probably the error comes from the serde. |
What does the json look like |
|
Having a fix to #349 would allow me to debug this myself |
Yah I'm looking into that, it's something funky to do with serde |
Found the issue, "306" : {
"Map" : {
"input" : 293,
"map_fn" : {
"args" : [ {
"id" : 1,
"layout" : 7,
"flags" : "input"
}, {
"id" : 2,
"layout" : 7,
"flags" : "output"
} ],
"ret" : "Unit",
"entry_block" : 1,
"blocks" : {
"1" : {
"id" : 1,
"body" : [ [ 3, { } ], [ 4, {
"Constant" : {
"is_null" : true
}
} ], [ 5, { additionally |
I will add some validation for this case myself. I think empty objects never make sense for you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The JIT validator does not like the implementation of this Rust function:
The code I generate for the JIT has a map function with 2 inputs, one for () and one for the Tuple1, but the JIT code validator reports:
invalid value: map, expected map with a single key at line 536 column 1
This function shows up as part of the aggregate implementations. In general GROUP-BY+AGGREGATE will have a non-empty tuple for the first component of the map function.
The text was updated successfully, but these errors were encountered: