Thank you, Shane!
Xiao
On Tue, Dec 1, 2020 at 5:34 PM Dongjoon Hyun
wrote:
> Yay! Thanks!
>
> Bests,
> Dongjoon
>
> On Tue, Dec 1, 2020 at 5:31 PM Takeshi Yamamuro
> wrote:
>
>> Many thanks, guys!
>> I've checked I can re-trigger Jenkins tests.
>>
>> Bests,
>> Takeshi
>>
>> On Wed, Dec 2,
Yay! Thanks!
Bests,
Dongjoon
On Tue, Dec 1, 2020 at 5:31 PM Takeshi Yamamuro
wrote:
> Many thanks, guys!
> I've checked I can re-trigger Jenkins tests.
>
> Bests,
> Takeshi
>
> On Wed, Dec 2, 2020 at 9:55 AM shane knapp ☠ wrote:
>
>> https://amplab.cs.berkeley.edu/jenkins/
>>
>> i cleared the
Many thanks, guys!
I've checked I can re-trigger Jenkins tests.
Bests,
Takeshi
On Wed, Dec 2, 2020 at 9:55 AM shane knapp ☠ wrote:
> https://amplab.cs.berkeley.edu/jenkins/
>
> i cleared the build queue, so you'll need to retrigger your PRs. there
> will be occasional downtime over the next
Thank you, Shane.
On Wed, Dec 2, 2020 at 8:55 AM shane knapp ☠ wrote:
> https://amplab.cs.berkeley.edu/jenkins/
>
> i cleared the build queue, so you'll need to retrigger your PRs. there
> will be occasional downtime over the next few days and weeks as we uncover
> system-level errors and more
https://amplab.cs.berkeley.edu/jenkins/
i cleared the build queue, so you'll need to retrigger your PRs. there
will be occasional downtime over the next few days and weeks as we uncover
system-level errors and more reimaging happens... but for now, we're
building.
a big thanks goes out to jon
Wenchen, could you start a new thread? Many people have probably already
muted this one, and it isn't really on topic.
The question that needs to be discussed is whether this is a safe change
for the 3.1 release, and reusing an old thread is not a great way to get
people's attention about
quick update: the migration to the new primary node is complete and i can
bring up jenkins and it's queueing builds and looks good to go.
the final bits that need attention are SSL, apache2 and firewall configs,
and i'm hoping to get this sorted ASAP. once that's done, we'll start
building and
I'm reviving this thread because this feature was reverted before the 3.0
release, and now we are trying to add it back since the CREATE TABLE syntax
is unified.
The benefits are pretty clear: CREATE TABLE by default (without USING or
STORED AS) should create native tables that work best with
