►
From YouTube: 2020 07 14 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
B
A
C
A
B
Me
neither
I
was
just
looking
through
a
couple
of
issues
and
I
think
what
we
sometimes
have.
It's
basically
pushing
and
pushing
issues
into
the
next
milestone,
even
though
we
might
not,
you
know,
fully,
understand
them,
or
maybe
they're
not
well-defined
or
enough,
and
we
might
need
to
discuss
those
more
before
they
are
even
actionable.
So
I
was
looking
for
a
way
to
sort
of
call
it
out
on
the
issue
and
I
found
that
label
not
totally
sure.
B
A
B
A
Josh
is
not
here
so
on
the
CI
retention
strategy,
so
I,
don't
think,
there's
anything
specific
for
us
to
do.
I
think
we
just
need
to
continue
to
monitor,
see
our
attention
can
be
turned
on
that
only
marks
issues
for
archival
and
hard
delete
is
being
considered
for
13/4
by
the
continuous
integration
group
and
I
just
wanted
Josh
to
confirm.
But
that
makes
sense
that's
what
we
should
be
doing,
but
he's
not
here
so
I
can
follow
up
with
him
a
synchronously.
B
Yester,
but
it's
it's
sort
of
debatable
if
we
wanted
to
use
that
we
did
have
a
retention
strategy
for
events
that
was
set
to
one
year,
because
it
mostly
feeds
the
activity
calendar
thing.
You
know
your
profile
right
and
that
was
sort
of
extended,
because
we
wanted
to
keep
that
data
for
longer
I'm,
not
totally
sure
where
we
use
that
there.
But
the
notion
is
rather
the
other
direction
where
we
intend
to
use
that
data.
We
keep
that
data
forever,
I'm,
not
totally
sure
why
that
is
or
what
we're
doing.
With
that
data.
I.
A
A
I
think
this,
the
ux/ui
strand
yeah,
so
I've
been
pinging.
The
team
on
this
one
I
haven't
caught
up
on
my
email.
Today
they
were
considering
a
13-3
I'm,
not
sure
if
they're
actually
gonna
get
it
done
for
thirteen
three
or
not,
but
they're.
Certainly
talking
about
it
and
I
will
continue
to
watch
that
issue
and
make
sure.
A
As
far
as
there
was
a
conversation
in
there
as
well
about
the
UX
work
that
needs
to
be
done,
API
work
that
needs
to
be
done
and
unless
we're
not
logging.
The
events
it
doesn't
look
like
this
API
is
used
very
much.
I
got
this
query
help
from
Stan
in
over
the
last
seven
days.
It
just
doesn't
seem
to
be
a
lot
of
activity
on
on
to
the
vents
API.
A
It
don't
think
that'll
be
problematic.
The
API
work
shouldn't
block
the
UX
work
and
that's
something
I
know:
I've
talked
to
you
at
least
Yonex
about
so
I
think
we
can
proceed
with
the
UX
work
without
really
having
any
ill
effects
on
the
overall
API
use
did
so
he
grew
in
a
good
spot
and
we
can
put
API
on
the
backlog
for
later
on
and
forcing
those
date
ranges
and
in
the
API
calls
I,
don't
think
will
break
too
many
customers.
If
we
do
that,
but
not
a
current
problem.
A
B
C
D
D
Just
timing,
inserts
and
updates,
and
mainly
inserts
with
and
without
the
trigger,
so
we
have
run
a
benchmark,
a
test
with
10
million
inserts
and
then
followed
by
10
million
updates
in
10
minutes,
but
that
was
a
test
to
make
sure
that
the
trigger
and
the
partition
table
the
partition
of
the
same
comes
as
a
city
table,
and
that
was
the
the
important
we
want
to
make
sure
that
everything
works,
but
we
also
want
to
run
one
last
benchmark
to
count
the
time.
What's
the
effect
of
having
the
videos
are
okay,.
C
We
should
be
able
to
run
that
even
once
the
once
the
first
one
gets
merged,
which
fixes
the
class
named
issue,
then
we
would
be
able
to
run
it
the
other
one
we
wouldn't
need
to
have
merged,
because
that's
more
of
a
cleanup
so
I
think
the
only
really
issue
there
is
the
this
issue.
With
the
background
jobs
that
we
haven't
really
quite
been
able
to
figure
out.
C
When
you
run
everything
from
the
console,
at
least
it
looks
like
everything
runs
fine,
but
when
you
try
to
run
the
background
job,
so
we
still
have
not
really
been
figure
out.
Why
and
they're
not
getting
picked
up.
I
haven't
been
able
to
figure
out.
Luckily
they're,
looking
in
and
what's
happening,
I
see
things
happening,
but
nothing
actually
seems
to
execute.
B
C
B
C
D
C
D
C
I
ran
it
locally.
I
ran
it
locally
three
times
by
just
doing
the
steal
and
the
two
times
it
picked
up
all
the
batches
and
did
everything,
but
one
time
it
did
skip,
but
one
time
I
had
the
background
jobs
also
running
and
it
did
skip
the
person
as
well.
So
there
like
that
issue,
I
feel
like
is
in
conflict
with
something
in
this
happening
in
the
background
jobs.
At
the
same
time,
that's
yeah.
It's
I
really
like
to
figure
out
what's
happening.
Yeah.
D
B
C
D
B
C
B
B
There
is
a
couple
of
safety
nets
that
we
have
as
well
like.
We
were
going
to
see
that
in
staging
first
of
all,
so
we
should
be
able
to
check
very
quickly
if
the
first
job
was
was
executed
or
not,
and
then,
if
we
end
up
not
having
one
of
those
jobs
execute
in
production
and
we
still
have
the
tracking
of
the
jobs
Patrick
implemented.
So
once
we
run
the
steal
migration,
they
should
should
be
able
to
clean
up
after
them
right.
B
C
D
A
C
A
B
C
C
Yeah
I,
just
really
haven't,
had
a
chance
to
follow
up
with
the
change
that
I
made
it
like
I'm,
it's
it's
working.
What
I
haven't
had
it
go
back
to
Meir
and
he'll
go
through
it
and
kind
of
look
at
it
and
she'll
have
to
read
schedule
and
everything
on
her.
One
is
good
for
the
release
managers
so
I'm,
just
not
sure
what
the
timing
is,
but
since
it's
Tuesday
I,
don't
know
don't
happen
this
week.
A
C
A
Yeah
there's
nothing
specifically
actionable
about
this
I,
don't
know
if
you
all
saw
the
engineering
retro
there's
a
lot
of
issues
that
we're
doing,
especially
with
like
the
documentation
that
Yanis
is
working
on
right
now
to
improve
documentation
and
communication
around
the
review
process.
I,
don't
know
that
there's
any
immediate
action
needs
to
be
taken
here.
A
One
of
the
concerns
was
that
if
we
change
requirements
on
database,
reviews
would
find
a
way
to
propagate
that
better
engineers
felt
like
they
were
surprised
that
some
of
the
review
changes
there's
no
specific
examples
in
there.
So
I,
don't
think.
There's
anything
immediately
actionable
that
we
need
to
do
that.
Then
just
be
aware
that
the
concern
is
out
there.
I
will
update
this
one
and
move
it
over
to
thirteen
three.
A
Gonna
make
sure
that
what
we
talked
about
in
the
engineering
Retro
was
enough
and
that
we
have
laid
any
concerns
that,
if
something
changes,
we
are
aware
that
we
need
to
make
sure
we
cover
all
that
multimodal
communication,
so
I
just
want
to
make
sure
that
I
understand
all
the
concerns
are
in
that
issue
and
that
we
address
them
either
through
the
retro
or
just
by
communicating
that
yes,
anytime,
there's
a
change.
We
won't
follow
these
communication
channels
and
make
sure
we
have
adequate
coverage
there.
So.
B
That
make
sense,
by
the
way
that
that
also
got
attention
from
couple
database
minded
folks
and
they
were
asking
well
what
what
is
what
our
specific
concern
is
like
looking
at
the
issue
or
what
is
specific
actions
that
we're
going
to
take,
so
people
are
noticing
that
it
was
just
that
they
she
didn't
say
about
the
specifics
or
what
is
kind
of
expected
or
suggested
to
change
yeah.
That's
what
I
was
asking
the.
A
Valid
question
and
basically
I'll
just
copy
what
I
wrote
down
in
the
retro
and
ask
like
does
this
this
cover
your
printer
and
is
there
anything
else
we
need
to
do
here
and
then
hopefully
we
can
just
close
it
out,
because
I
think
maybe
they
just
didn't
know
where
to
look
and
a
lot
of
be
honest
as
recent
changes
to
documentation,
they
think
will
cover
those
concerns.
Oh
junket.
Are
you
planning
on
going
clean
the
issue
out
there
be
honest,
we
talked
about
this
one.
A
A
B
A
B
B
There
is
also
something
another
dependency
that
we
have
for.
The
migration
is
the
coordination
with
the
refactorings
that
they
compliance
group
is
doing
so
they're,
basically
working
on
adding
columns
to
the
table,
also
removing
one
and
sort
of
extracting
information
from
that
details,
hash
into
into
columns
and
as
soon
as
we
push
out
the
migration
on
those
respect
rings
are
still
possible,
but
they
need
a
bit
more
coordination
because
you
know
we
have
to
change
the
trigger
definition
and
also
the
partition
table,
and
that
sense
I
think
it's
nothing
that
should
block
us.
B
B
It's
the
former,
so
we
will
run
it
in
parallel
for
one
one:
stone
will
one
release.
We
use
that
to
copy
data
over,
so
we
do
double,
writes
those
tables
in
sync,
and
then
we
have
one
more
change
to
flip
it
over
and
use
it,
and
the
benefit
from
that
is
we
can
as
soon
as
that
is
synchronized.
We
can
already
try
and
see
what
the
without
changing.
A
D
C
B
A
A
B
Seeing
though
the
Kisa
pagination,
there
was
a
request
for
adding
that
to
another
endpoint
for
the
users,
endpoint
I
think
it
makes
sense.
I
thought
that
might
be
an
example
where
that
work
can
be
sort
of
scheduled
with
the
second
group
owning
the
API,
because
effectively
not
different
than
I'm
doing
for
the
projects.
Api
yeah.