Hi Yu,
I found it's because DateTimeUtils passed to StaticInvoke is not
serializable.
I think it's potential bug that StaticInvoke can receives
non-Serializable objects.
I opened a PR about this issue.
https://github.com/apache/spark/pull/10357
- Kousuke
On 2015/12/17 16:35, Yu Ishikawa
+1 (non-binding, of course)
1. Compiled OSX 10.10 (Yosemite) OK Total time: 29:32 min
mvn clean package -Pyarn -Phadoop-2.6 -DskipTests
2. Tested pyspark, mllib (iPython 4.0)
2.0 Spark version is 1.6.0
2.1. statistics (min,max,mean,Pearson,Spearman) OK
2.2. Linear/Ridge/Laso Regression OK
Okay thanks guys, that's two -1s and that's fair enough. I'll leave it at
that.
On Thu, Dec 17, 2015 at 1:39 AM, Josh Rosen
wrote:
> Personally, I'd rather avoid the risk of breaking things during the
> reimport. In my experience we've had a lot of unforeseen problems
Agree with Andrew, we shouldn't block the release for this.
This issue won't be there in Spark distribution from Hortonworks since we
set the HDP version.
If you want to use the Apache Spark with HDP you can modify mapred-site.xml
to replace the hdp.version property with the right value for