Julien Opoix
Julien Opoix
My results are very far from yours, I can't really explain that.
"b.settings.value is undefined" error happens when you apply the slider on something else than an input. Is it your issue ?
Hi, does it mean that the `command` arg will no longer be required for `emissary` executor in v3.4? If so, shouldn't the documentation be updated? https://github.com/argoproj/argo-workflows/blob/v3.4.0-rc4/docs/workflow-executors.md#:~:text=command%20must%20be%20specified%20for%20containers.
Hi, is there any update on this issue?
Throwing and catching exceptions hundreds of thousands of times has a performance cost that would be good to avoid, any progress on this issue?
Any updates on that issue?
I understand, thank you for the answer.
Due to #92 the generated schema for the Spark Row has all its fields nullable, which gives the following output schema: ```javascript { "type": "record", "name": "topLevelRecord", "fields": [{ "name":...
It is linked to the nullable issue (#92), the expected new input data for the generated schema is: ```javascript { "properties": { "map": { "object": { "array": [ {"properties": {"string":...
I found a workaround by using the schema to generate the right StructType with SchemaConverters and creating a new dataset with this StructType: ```java public static void main(String[] args) throws...