eejbyfeldt commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3357771632
This config should probably also be used in aggregates like sum that can
also overflow.
--
This is an automated message from the Apache Git Service.
To respond to the mess
EeshanBembi commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3288845861
take
--
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.
T
findepi commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3288709369
awesome write up @EeshanBembi , thank you!
I don't think anyone is working on this yet, so you can go ahead
--
This is an automated message from the Apache Git Service.
To r
EeshanBembi commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3288688422
I did some digging into how other databases handle this and wanted
to share what I found.
Other databases consistently treat overflow as an error:
- MySQL (
findepi commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3288636673
I can see how it may be desirable for some use cases to keep numeric
overflow behavior. Having a flag for transition period sounds useful, but may
also complicate implementation
Omega359 commented on issue #17539:
URL: https://github.com/apache/datafusion/issues/17539#issuecomment-3286910949
This is not entirely true for some systems including Spark before ANSI mode
was enabled by default. I've been meaning to submit a PR to add an 'ANSI' flag
to the config that wh
findepi opened a new issue, #17539:
URL: https://github.com/apache/datafusion/issues/17539
### Describe the bug
In programming languages it's rather typical that numeric overflows are not
a runtime error.
In SQL, it's rather typical that numeric overflows are identified during