alamb commented on a change in pull request #840:
URL: https://github.com/apache/arrow-datafusion/pull/840#discussion_r685093844
##########
File path: ballista/rust/core/proto/ballista.proto
##########
@@ -144,18 +144,19 @@ enum ScalarFunction {
TOTIMESTAMP = 24;
ARRAY = 25;
NULLIF = 26;
- DATETRUNC = 27;
- MD5 = 28;
- SHA224 = 29;
- SHA256 = 30;
- SHA384 = 31;
- SHA512 = 32;
- LN = 33;
+ DATEPART = 27;
Review comment:
I think until we know someone is using the ballista codebase in a way
that such a change will affect them, we should not spend extra time striving
for backwards compatibility (aka in my opinion this change is fine).
Ballista also looks to me like more of an overall system (aka something
people could use directly rather than as a library) which is different than
DataFusion. I wonder if internal changes such as these enum values changes are
less of an issue with such a system.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
