Ahmed Hussein
Ahmed Hussein
#6256 added support to the `OverflowInTableInsert` and the tests were modified to pass that check. This issue was opened to revisit the behavior including handling the exception and the error....
**EDIT**: Please aware of the followup change [[SPARK-40054](https://issues.apache.org/jira/browse/SPARK-40054)][SQL] Restore the error handling syntax of try_cast() https://github.com/apache/spark/commit/f8d51b9940
Spark-3.4 addressed this as bug - https://github.com/NVIDIA/spark-rapids/issues/6015 - https://github.com/apache/spark/commit/c621df269d - Followup: https://github.com/apache/spark/commit/5bd47640dc
Trying to build for DB 11.3 / Spark 3.3.0. Apparently the castBase was ported to 3.3 on databricks. ``` [INFO] Compiling 313 Scala sources and 59 Java sources to /home/ubuntu/spark-rapids/sql-plugin/target/spark330db/classes......
The discussion on PR #2878 and HDFS-15957 sounds to be around the same concept. By definition, if there is a "network issue", the NameNode in general because all RPCs will...
> @amahussein Thanks for your quick response. I think this is not the same concept/issue between [HDFS-15957](https://issues.apache.org/jira/browse/HDFS-15957) and [HDFS-15869](https://issues.apache.org/jira/browse/HDFS-15869). I have leave comment at [HDFS-15869](https://issues.apache.org/jira/browse/HDFS-15869) and suggest to change it...
Thanks @functioner The detailed discussions (except the lambda argument) should have been on the Jira. > IMO, this is a classic Producer-Consumer problem, and it is natural idea to improve...