Are you referring to SPARK-6330?

If you are able to build Spark from source yourself, I believe you should just need to cherry-pick the following commits in order to backport the fix:

67fa6d1f830dee37244b5a30684d797093c7c134 [SPARK-6330] Fix filesystem bug in newParquet relation
9d88f0cbdb3e994c3ab62eb7534b0b5308cc5265 [SPARK-6330] [SQL] Add a test case for SPARK-6330

(And if it's a different bug you're talking about, you could probably find the commit(s) that fix that bug and backport them instead.)


Jonathan Kelly

Elastic MapReduce - SDE

Port 99 (SEA35) 08.220.C2


From: Shuai Zheng <szheng.code@gmail.com>
Date: Monday, March 30, 2015 at 12:34 PM
To: "user@spark.apache.org" <user@spark.apache.org>
Subject: When will 1.3.1 release?

Hi All,

 

I am waiting the spark 1.3.1 to fix the bug to work with S3 file system.

 

Anyone knows the release date for 1.3.1? I can’t downgrade to 1.2.1 because there is jar compatible issue to work with AWS SDK.

 

Regards,

 

Shuai