Looks like we missed this one, feel free to submit a patch, thanks for your
finding!
On Fri, Jan 26, 2018 at 3:39 PM, Jacek Laskowski wrote:
> Hi,
>
> I've just noticed that every time Dataset.hint is used it triggers
> execution of logical commands, their unions and hint resolution (among
> oth
Thanks Wenchen --> https://github.com/apache/spark/pull/20405
I'd also like to write a new test where broadcast hint could be specified
with table identifiers + improve scaladoc for Dataset.hint to note that
hint does not have to be used with the Dataset but any Dataset (as long as
the table ident
I probably missed this, but what is the new "*** UNCHECKED ***" message in
the subject line of some JIRAs?
Examples?
On Fri, Jan 26, 2018 at 9:56 AM, Sean Owen wrote:
> I probably missed this, but what is the new "*** UNCHECKED ***" message in
> the subject line of some JIRAs?
>
This is an example of the "*** UNCHECKED ***" message I was talking about
-- it's part of the email subject rather than JIRA.
-- Forwarded message -
From: Xiao Li (JIRA)
Date: Fri, Jan 26, 2018 at 11:18 AM
Subject: ***UNCHECKED*** [jira] [Resolved] (SPARK-23218) simplify
ColumnVec
I have no idea. Some JIRA update? Might want to file an INFRA ticket.
On Fri, Jan 26, 2018 at 10:04 AM, Sean Owen wrote:
> This is an example of the "*** UNCHECKED ***" message I was talking about
> -- it's part of the email subject rather than JIRA.
>
> -- Forwarded message -
>
This vote has failed due to a number of aforementioned blockers. I'll
follow up with RC3 as soon as the 2 remaining (non-QA) blockers are
resolved: https://s.apache.org/oXKi
On 25 January 2018 at 12:59, Sameer Agarwal wrote:
>
> Most tests pass on RC2, except I'm still seeing the timeout caused
Yeah sounds like some JIRA 'feature' or issue. It's not any particular
bother. If it persists I'll ask INFRA, sure.
On Fri, Jan 26, 2018 at 12:00 PM Reynold Xin wrote:
> Examples?
>
>
> On Fri, Jan 26, 2018 at 9:56 AM, Sean Owen wrote:
>
>> I probably missed this, but what is the new "*** UNCHE
our firewall was running a bit... slowly... and needed a reboot. this
means access to jenkins will be gone for ~10 mins.
i'll send out an all-clear when we're back up and running.
and we're back!
On Fri, Jan 26, 2018 at 2:32 PM, shane knapp wrote:
> our firewall was running a bit... slowly... and needed a reboot. this
> means access to jenkins will be gone for ~10 mins.
>
> i'll send out an all-clear when we're back up and running.
>
10 matches
Mail list logo