You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We have run into a lot of issues with GpuAttributeReference It would be great if we could just replace it with AttributeReference. The reason we originally split the two was so that we could have type safety. A GpuExpressions has children that are all GpuExpressions too. But it has resulted in more problems then we hoped to prevent.
This is to discuss if we should remove them and then to do it if we decide it is the right course of action to take.
The text was updated successfully, but these errors were encountered:
This has certainly been one of the challenges during testing with AQE, where Spark code fails to bind references because it is looking for AttributeReference and does not recognize GpuAttributeReference.
Is your feature request related to a problem? Please describe.
We have run into a lot of issues with
GpuAttributeReference
It would be great if we could just replace it withAttributeReference
. The reason we originally split the two was so that we could have type safety. AGpuExpressions
has children that are allGpuExpressions
too. But it has resulted in more problems then we hoped to prevent.This is to discuss if we should remove them and then to do it if we decide it is the right course of action to take.
The text was updated successfully, but these errors were encountered: