Open jayzhan211 opened 3 weeks ago
I am working on this :)
Well I am not anymore. We have a problem :D @jayzhan211 the problem is that if we modified the proto and remove min, we remove the 0 value, and this is not allowed in protobuf see https://protobuf.dev/programming-guides/proto3/#enum
Well I am not anymore. We have a problem :D @jayzhan211 the problem is that if we modified the proto and remove min, we remove the 0 value, and this is not allowed in protobuf see https://protobuf.dev/programming-guides/proto3/#enum
We can change it to 'unknown', as I know Datafusion does not ensure the backward compatibility for proto, so it is fine. We will even remove whole proto after converting all the functions to UDAF
@jayzhan211 https://github.com/apache/datafusion/pull/11013/files in this draft I started to face a challenge, many tests in expr depends on min/max, and I need to remove them to avoid a circular dependency. Shall we add them back as sql tests?
@jayzhan211 https://github.com/apache/datafusion/pull/11013/files in this draft I started to face a challenge, many tests in expr depends on min/max, and I need to remove them to avoid a circular dependency. Shall we add them back as sql tests?
For tests in datafusion_expr, you can use function_stub. See datafusion/expr/src/test/function_stub.rs
For tests in optimizer or others, you can import function in dev-dependencies or move them to slt.
Is your feature request related to a problem or challenge?
Similar to other issues in #8708
I think the change of this might be large, could split it in several PR.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response