►
From YouTube: 2020 03 31 Database Team Weekly
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
a
couple
things
so
actually
the
first
item
won't
affect
Pat
I'm,
not
sure
how
we're
gonna
handle
it
with
you
Yanis,
but
the
360
feedbacks
been
pushed
back
to
at
least
the
end
of
April
due
to
the
Cova
virus
issues
going
on
so
there's
a
link
to
more
details
there
12:9
retrospective
is
I,
think
it's
next
Tuesday
at
about
this
time.
So
if
you
have
anything,
you
want
to
add,
please
add
comments
in
there
before
the
end
of
this
week,
so
that
I
can
summarize
and
add
it
to
the
engineering
wide
retrospective.
A
Any
questions
on
either
of
those
cool,
so
feedback
I've
gotten
from
the
working
group.
The
charting
working
group
is
a
little
more
detail
on
what
we're
doing
with
siteís,
specifically
they're
looking
for
timeline
like
when
do
we
and
the
exploration?
When
do
we
determine
whether
moving
forward
on
actually
using
situs
as
our
charting
solution?
A
A
I
have
requested
a
time
to
set
up
a
call
with
them,
and
anybody
on
this
call
is
welcome
to
join
that
conversation.
Whenever
I
get
set
up,
I'm
still
waiting
your
feedback
from
that,
but
it's
way
too
expensive
and
doesn't
meet
like
a
return
on
investment.
Then
it
might
be
a
non-starter
there
too.
So
we'll
have
to
start
looking
into
alternatives
once
we're
done
with
this
exploration,
so
that
you're
probably
the
most
involved
on
this.
How
much
time?
Probably
you
are
the
most
involved
on
this
right
now?
B
Well,
the
cluster
is
set
up,
but
I
think
we
have
still
an
issue
with
not
really
having
an
updated,
attested
it's
early,
so
one
of
the
things
I
was
thinking.
Probably
we
need
to
do
is
maybe
have
some
kind
of
like
production
like
cleaning
script
or
something
cleaner
script
that
we
can
kind
of
anonymizes
data
so
that
we
can
use
it
because
I
just
don't
think
that
we
have
the
data
stuff
set
large
enough
really
to
do
proper
testing
otherwise,
but
I
think
also
some
of
that
I.
Don't
have
the
access
to
do
that.
B
B
A
A
A
A
B
Yeah
I
mean
I,
know,
there's,
there's
gonna
be
a
significant
amount
of
change
that
needs
to
be
done
to
support
it.
I
don't
think
it's
gonna
be
hopefully
as
easily
able
to
be
dropped
and
as
what
we
may
be,
but
I
think
the
biggest
concern
right
now
is
I.
Guess
the
the
licensing
that
you
talked
about.
If,
if
were
saying
that
we're
not
gonna
pursue
an
enterprise
or
it's
not
worth
the
cost
and
I
think
at
that
point,
it's
probably
not
worth
investigating
further,
because
some
of
the
features
that
we
want
our
enterprise
anomaly
right.
A
So
my
understanding
of
situs
is
it
greatly
simplifies
a
lot
of
things
that
we
could
do
otherwise
on
our
own,
with
Postgres
sequel,
sharding
right,
it's
not
like
it's
yeah,
I,
don't
know
any
other
way
to
play.
Just
simplifies
the
work
that
we
would
otherwise
have
to
build
on
our
own
correct,
right,
yeah,
okay,
so
if
siteís
becomes
a
non-starter
for
us,
then
it
would
just
probably
mean
a
longer
development
timeline
for
us
to
develop
those
features
on
our
own.
A
If
we
have
no
other
extensions
or
other
options
that
we
can
look
into
correct,
right,
yeah,
okay
and
we
haven't
even
I-
don't
recall
any
other
technology
that
we
were
considering
looking
into.
There
was
really
nothing
else
that
would
help
accelerate
our
development.
Like
situs,
like
we
originally
thought,
situs
would
right,
there's
no
other
extension
or
drop
in
that
we
could
use
yeah.
A
A
So
we'll
revisit
this
on
well,
we'll
talk
some
more
about
it
tomorrow.
Maybe
Alvaro
can
give
us
some
more
feedback
on
whether
or
not
he
thinks
situs
can
meet
our
use
case.
I
haven't
heard
any
concern
for
them
other
than
asking
implementation
details.
He
hasn't
said
it's
a
non-starter
yet.
We
can
certainly
restate
that
question
tomorrow.
During
the
sink
and
for
now
we
should
probably
consider
we're
in
the
middle
of
12:10
right
now.
A
We
should
do
a
gut
check
by
the
end
of
12:10
to
see
if,
if
we
need
to
continue
that
exploration
or
if
we
need
to
abandon
and
start
over
with
our
own
implementation
of
sharding
and
hopefully
I'll
get
feedback
from
Microsoft
I'll
start
I
will
continue
to
badger
them
over
the
next
couple
days
they
are
Microsoft
is
still
in
the
process
of
even
incorporating
cite
us
into
their
offering.
So
it's
not
part
of
their
enterprise
offering
yet
they
said
they
were.
A
A
B
So
I
think
that
I
think
that
the
issue
here
like
we,
this
you
know
we
can
use
triggers
that
works
I,
think
there
was
sort
of
we
wanted
to
talk
about
me
me
a
longer
term
solution
to
of
maybe
we
don't
want
to
roll
on
cascading
deletes
as
much
going
forward
because
it's
going
to
become
an
issue,
but
that's
sort
of
a
bigger
conversation.
B
Yeah
that
one
was
merged
and
just
waiting
for
it
to
be
released.
Okay,
the
status
cluster
is
running.
It's
just
a
matter
of
you
know
needing
to
load
some
more
data
there
I
like
the
issue
or
the
label
that
one,
but
then
this
one
I
just
kind
of
started
looking
at
yesterday
to
how
I
would
implement
that
I'm-
probably
gonna
work
on
that
one.
Today,
okay
and
then
the
last
one
was
an
issue
that
was
raised
yesterday.
A
A
C
C
A
A
A
And
then,
at
one
point
in
time
we
talked
about
building
out
the
retention
SLI
pad
I
know
you
brought
this
up
and
I
don't
know
since
then,
if
we
built
an
issue
for
it,
but
I
just
made
a
note
of
it,
because
a
couple
folks
brought
it
up
in
the
last
week
so
something
we
should
track
for
the
future
and
I'll
follow
up
with
Josh
to
make
sure
he
gets
prioritized
and
that
if
we
don't
have
an
issue
for
this,
then
one
will
get
built.
So
this.
B
One
I
know
andreas:
he
had
created
an
issue
about
trying
to
restrict
the
size
of
the
database
growth
and
in
there
I'll
see
if
I
can
find
it,
but
in
there
there
was
linked
to
another
issue
about
something
when
CI
builds
about.
There
is
a
work
in
progress
or
an
issue
out
there
to
trim
that
table
down,
so
I
think
that
maybe
work
is
underway
at
least
for
that
table.
So
you
find
the
issues.
Okay,.