|
What is your question? I am ready to finish this udf in udf-example reference In addition , for
|
Replies: 4 comments
|
|
Yes, these are the same types. libcudf does not have a map type, so it's implemented as a list of struct of key,value pairs. This shouldn't be a problem in practice for the UDF because Spark knows the expected type being returned from the UDF (this type is derived from the CPU implementation), and therefore the RAPIDS Accelerator knows the expected Spark result type as well. The plugin checks that the returned
I don't think this will work. If I understand the intent of the After constructing the |
Probably. Implementing |
|
Closing as answered. Please reopen if there are further questions on this. |
Yes, these are the same types. libcudf does not have a map type, so it's implemented as a list of struct of key,value pairs. This shouldn't be a problem in practice for the UDF because Spark knows the expected type being returned from the UDF (this type is derived from the CPU implementation), and therefore the RAPIDS Accelerator knows the expected Spark result type as well. The plugin checks that the returned
ColumnVectorcan be converted to the expected Spark type, and Spark'sMapTypeis implemented in libcudf as aLISTofSTRUCTof twoSTRING