Re: Timeline for Spark 2.3

+1 for cutting a branch earlier. In some Asian countries, 1st, 2nd, and 3rd January are off. https://www.timeanddate.com/holidays/ How about 4th or 5th? Regards, Kazuaki Ishizaki From: Felix Cheung To: Michael Armbrust , Holden Karau

R: Decimals

Thanks for your answer Xiao. The point is that behaving like this is against SQL standard and is different also from Hive's behavior. Then I would propose to add a configuration flag to switch between the two behaviors, either being SQL compliant and Hive compliant or behaving like now (as

FW: Anyone know how to bypass tools.jar problem in JDK9 when mvn clean install SPARK code

Hi Sean: Thanks for your reply, You mentioned that “You need to run ./dev/change-scala-version.sh 2.12 first” I have done that but still have this problem, currently the problem is about tools.jar does not exist in JDK9 but some dependencies on it when using “mvn clean install –DskipTests”.

Re: Anyone know how to bypass tools.jar problem in JDK9 when mvn clean install SPARK code

You need to run ./dev/change-scala-version.sh 2.12 first On Thu, Dec 21, 2017 at 4:38 PM Zhang, Liyun wrote: > Hi all: > > Now I am using JDK9 to compile Spark by (mvn clean install –DskipTests), > but exception was thrown > > > > [root@bdpe41 spark_source]# java

Anyone know how to bypass tools.jar problem in JDK9 when mvn clean install SPARK code

Hi all: Now I am using JDK9 to compile Spark by (mvn clean install -DskipTests), but exception was thrown [root@bdpe41 spark_source]# java -version java version "9.0.1" Java(TM) SE Runtime Environment (build 9.0.1+11) Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode) #mvn clean

Re: Decimals

Losing precision is not acceptable to financial customers. Thus, instead of returning NULL, I saw DB2 issues the following error message: SQL0802N Arithmetic overflow or other arithmetic exception occurred. SQLSTATE=22003 DB2 on z/OS is being used by most of biggest banks and financial

Any way for users to help "stuck" JIRAs with pull requests for Spark 2.3 / future releases?

Hi all, I was wondering with the approach of Spark 2.3 if there's any way us "regular" users can help advance any of JIRAs that could have made it into Spark 2.3 but are likely to miss now as the pull requests are awaiting detailed review. For example: