Hi, team.
I want to make the same test on ARM like existing CI does(x86). As building
and testing the whole spark projects will cost too long time, so I plan to
split them to multiple jobs to run for lower time cost. But I cannot see
what the existing CI[1] have done(so many private scripts
On Fri, Jun 14, 2019 at 9:13 AM shane knapp wrote:
> the campus colo will be performing some electrical maintenance, which
> means that they'll be powering off the entire building.
>
> since the jenkins cluster is located in that colo, we are most definitely
> affected. :)
>
> i'll be out of
unsubscribe
On Mon, Jul 29, 2019 at 2:46 PM Sean Owen wrote:
> TL;DR is: take the below as feedback to consider, and proceed as you
> see fit. Nobody's suggesting you can't do this.
>
> On Mon, Jul 29, 2019 at 2:58 AM Lars Francke
> wrote:
> > The way I read your point is that anyone can publish material
>From my look, +1 on the proposal, considering ASCI and other DBMSes in
general.
2019년 7월 30일 (화) 오후 3:21, Wenchen Fan 님이 작성:
> We can add a config for a certain behavior if it makes sense, but the most
> important thing we want to reach an agreement here is: what should be the
> default
We can add a config for a certain behavior if it makes sense, but the most
important thing we want to reach an agreement here is: what should be the
default behavior?
Let's explore the solution space of table insertion behavior first:
At compile time,
1. always add cast
2. add cast following the
