Thanks Steve and Michael for your response.

Is there a tentative release date for Spark 1.5?

From: Michael Armbrust [mailto:[email protected]]
Sent: Tuesday, August 4, 2015 11:53 PM
To: Steve Loughran <[email protected]>
Cc: Ishwardeep Singh <[email protected]>; [email protected]
Subject: Re: Spark SQL support for Hive 0.14

I'll add that while Spark SQL 1.5 compiles against Hive 1.2.1, it has support 
for reading from metastores for Hive 0.12 - 1.2.1

On Tue, Aug 4, 2015 at 9:59 AM, Steve Loughran 
<[email protected]<mailto:[email protected]>> wrote:
Spark 1.3.1 & 1.4 only support Hive 0.13

Spark 1.5 is going to be released against Hive 1.2.1; it'll skip Hive .14 
support entirely and go straight to the currently supported Hive release.

See SPARK-8064 for the gory details

> On 3 Aug 2015, at 23:01, Ishwardeep Singh 
> <[email protected]<mailto:[email protected]>> wrote:
>
> Hi,
>
> Does spark SQL support Hive 0.14? The documentation refers to Hive 0.13. Is
> there a way to compile spark with Hive 0.14?
>
> Currently we are using Spark 1.3.1.
>
> Thanks
>
>
>
> --
> View this message in context: 
> http://apache-spark-user-list.1001560.n3.nabble.com/Spark-SQL-support-for-Hive-0-14-tp24122.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> [email protected]<mailto:[email protected]>
> For additional commands, e-mail: 
> [email protected]<mailto:[email protected]>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: 
[email protected]<mailto:[email protected]>
For additional commands, e-mail: 
[email protected]<mailto:[email protected]>


________________________________






NOTE: This message may contain information that is confidential, proprietary, 
privileged or otherwise protected by law. The message is intended solely for 
the named addressee. If received in error, please destroy and notify the 
sender. Any use of this email is prohibited when received in error. Impetus 
does not represent, warrant and/or guarantee, that the integrity of this 
communication has been maintained nor that the communication is free of errors, 
virus, interception or interference.

Reply via email to