Hi Mark,
I agree. :-) We already have a product released with Spark 1.4.1 with some
custom extensions and now we are doing a patch release. We will update
Spark to the latest 2.x version in the next release.
Best
On Thu, Jul 7, 2016 at 1:12 PM, Mark Hamstra
wrote:
> You've got to satisfy my cu
You've got to satisfy my curiosity, though. Why would you want to run such
a badly out-of-date version in production? I mean, 2.0.0 is just about
ready for release, and lagging three full releases behind, with one of them
being a major version release, is a long way from where Spark is now.
On W
Thanks Reynold
On Thu, Jul 7, 2016 at 11:40 AM, Reynold Xin wrote:
> Yes definitely.
>
>
> On Wed, Jul 6, 2016 at 11:08 PM, Niranda Perera
> wrote:
>
>> Thanks Reynold for the prompt response. Do you think we could use a
>> 1.4-branch latest build in a production environment?
>>
>>
>>
>> On Thu
Yes definitely.
On Wed, Jul 6, 2016 at 11:08 PM, Niranda Perera
wrote:
> Thanks Reynold for the prompt response. Do you think we could use a
> 1.4-branch latest build in a production environment?
>
>
>
> On Thu, Jul 7, 2016 at 11:33 AM, Reynold Xin wrote:
>
>> I think last time I tried I had s
Thanks Reynold for the prompt response. Do you think we could use a
1.4-branch latest build in a production environment?
On Thu, Jul 7, 2016 at 11:33 AM, Reynold Xin wrote:
> I think last time I tried I had some trouble releasing it because the
> release scripts no longer work with branch-1.4.
I think last time I tried I had some trouble releasing it because the
release scripts no longer work with branch-1.4. You can build from the
branch yourself, but it might be better to upgrade to the later versions.
On Wed, Jul 6, 2016 at 11:02 PM, Niranda Perera
wrote:
> Hi guys,
>
> May I know
