►
From YouTube: 2021 07 14 EMEA Sharding Group Sync
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
B
So
I
wanted
to
share
that
here,
because
that
was,
I
think,
is
slash,
was
quite
relevant
for
for
this
effort.
A
All
right
were
you
in
the
apac
meeting
fabian.
A
I
want,
oh,
that's,
I'm
sorry
you're
still
that's
right,
you're
in
the
us
right
now,
so
I
was
there
quick.
Why
do
you
need
to
know
something?
No,
no.
I
was
reading
through
the
agenda
and
I
was
about
10
minutes
into
the
video
this
morning.
I
think
they
only
got
2.3.
A
C
A
A
C
One
of
the
interesting
is
like
that
there
are
probably
gonna
look
at
the
security
set
of
the
features,
because
this
is
probably
like
one
of
the
bigger
risks
with
the
the
composition
that
we
need
to
probably
engage
security
team
earlier,
so
the
iran
will
be
looking
at
that
I,
with
tongue,
will
be
working
on
the
poc
with
the
intent
that
we
kind
of
see
how
far
we
got
and
out
of
this
plc.
C
B
A
D
Yeah
I'm
trying
to
compile
a
you
know
interim
report,
just
monitoring
the
progress
every
day
of
discovered
items.
Maybe
I
will
move
this
table
to
the
top
until
we
we
conclude
this
effort,
and
already
there
is
one
item
identified
that
as
a
blocker,
which
is
this
one
and
I
think
craig
already
worked
with
jake
the
en
of
that
product
management
team
to
schedule
it
for
40.2
and
other
things.
I
think
I
called
out
the
links
here.
If
someone
is
available.
Please
look
at
those
questions
or
scenes
to
see.
D
If
there
is
you
know,
items
to
work
on
if
there
are
please
also
identify
if
they're,
blockers
or
they're
nice
to
have
blogger
means
the
blocker
for
the
first
iteration.
So
we
only
want
to
work
on
the
critical
issues
for
the
first
iteration
then
highlight
those
to
either
me
or
craig.
D
And
the
the
distribution
team
already
started
already
scheduled
the
omnibus
and
cng
for
14.2
that
that's
updated
yesterday,
so
they
will
work
on
those
two
issues
in
parallel
described
here
yeah.
That's
my
update.
D
Oh
camille
added
a
new
comment,
so
this
one
tongs
that
is
blocking
our
moving
moving.
The
text
table.
C
I
don't
think
so
like
I
think
we
can
still
move
it
and
it's
gonna
have
like
minimal
impact
on
the
projects.
It's
like
in
some
cases,
probably
will
just
be
from
another
database,
so
this
can
be
like
acceptable
technical
depth,
but
I
I
don't
think
that
it's
going
to
be
critical.
It's
only
going
to
be
like
medium
thing
to
solve
over
time.
C
D
Okay,
craig,
maybe
we
can
talk
offline,
what
we
want
to
do
with
six
team
or
maybe.
A
D
Cool
and
also
along
the
same
line,
I
just
pinged
todd
the
security
development
direct
director
of
the
notes
below
here
in
the
meeting
earlier
so
camille.
You
mentioned
that
dylan
and
tom
will
work
with
a
secure
team
to
identify
the
broken
features.
So
I
pinned
the
thought
on
that
in
in
our
working
group,
slack
channel.
D
Yeah
so
basically
we
got
todd
notified,
so
hopefully
he
will
activate
his
teams
sooner.
I
don't
know
maybe
already
activated,
but
just
no
issues
under
that.
I
pick
from
the
secure
team
so
just
want
to
make
sure
they
are
working
on
that.
Yes,.
C
The
tricky
part
is
still
like
pretty
early
like
to
to
like
to
engage
them,
because
I
think
we
needed
that
one
to
like
take
a
look
at
the
poc
and
like
what
was
changed
and
kind
of
like
create
an
issue
and
kind
of
summary
of
the.
In
that
changes
was
like
on
like
from
from
like
from
one
of
the
like
set
of
the
high
level
aspects.
So,
let's
see
how
it
goes,
but
at
least
in
my
head.
D
B
A
D
D
E
No,
I'm
just
writing
a
reply
on
the
schema
proposal
from
camille,
I'm
just
going
to
summarize
it
and
there's
no
real
point
in
here.
I
think
discussing
it
short
story.
Is
I
I
don't
see
the
point.
E
That's
that's
me,
being
very
frank,
I
read
it.
I
read
it
back
and
forth
unless
I
misunderstand
something:
it
strikes
me
as
wasted
effort,
basically,
but
I'll
put
that
in
issue
comments
and
we
can
discuss
it
there.
I
suppose
yes.
C
I
I
think,
like
eric,
I'm
kind
of
looking
like
for,
like
the
proposal,
how
we
can
approach
that,
because,
like
it's
kind
of
like
interconnected
organisms,
that
we
are
doing
that
for
more
reasons
in
the
future,
so
if
you
have
some
proposal
on
how
to
approach
it
differently,
if
you
could
like
document
that
it
would
be
very
like
useful
like
to
discuss
that
and
how
how
it
plays
like
with
our
plans
for
the
migration
and
like
managing
structures,
keeping
coherency
and
all
of
that
stuff.
C
It's
like
yes,
like
schema,
is
like
one
of
the
ways
to
do
it.
It's
not
the
only
ways
it
just
makes
some
things
easier,
something's
harder.
But
if
you
have
like
something
better,
I
I'm
up
for
it.
So.
E
So
my
the
summary
of
what
I'm
writing
and
it's
it's
a
little
difficult
to
write
because
there's
a
whole
bunch
of
different
things
being
discussed.
Actually
this
the
sort
of
isolated
step
of
now
we're
actually
discussing
it,
does
the
isolated
step
of
how
are
we
going
to
move
tables?
Are
we
going
to
move
them
to
a
database
first
or
a
separate
schema
on
the
same
database
and
then
a
separate
database
and
fyi?
E
E
So
you
can
tell
hey
this
connection:
dump
structure.sql
in
this
directory,
but
for
the
other
one
dump
it
over
there,
whereas
if
we
use
different
postgresql
schemas,
I
don't
think
it
supports
that.
I
think
at
that
point
we
would
have
to
write
custom
code
where
we
say,
oh
for
tables
in
the
ci
schema.
Put
them
in
this
file
for
tables
in
a
public
schema,
put
them
in
that
file
or
just
put
them
on
the
same
one.
C
It's
actually
like
more
like
very
like
money
size
to
that,
like
you
can
configure
that
anyway,
how
you
create
structures,
but
this
is
also
like
related
with
how
we
gonna
migrate
data
and
like
how
we're
gonna
migration,
the
data
look
on
the
production
but
like.
If
we
talk
about
the
schema,
you
can
configure
that
pg
down
when
executed,
you're
gonna
follow
schema
search
marks.
If
this.
C
E
Let's
listen
to
that.
That's
I
see
like
sure,
because
I
don't
want
to
keep
everybody
here,
but
that
is
true,
like
you
can
do
all
that,
but
it
sounds
a
bit
harsh,
but
you
can
also
make
it
pick
pretty
by
putting
lipstick
on
it.
It
doesn't
necessarily
mean
it's.
You
know
beneficial
in
this
case
from
what
I
understand
if
we
focus
exclusively
on
moving
a
certain
set
of
tables
to
a
different
database
and
just
keep
it
in
a
public
schema.
E
The
work
we
need
to
do
on
the
application
is
the
same
and,
more
importantly,
there's
no
like
reals
has
support
for
multiple
databases.
It's
support
for
multiple
schema
search
paths.
I
I'm
a
little
skeptical.
Maybe
it
works,
but
that's
part
of
the
problem.
We
don't
know
we
do
know
it
supports
different
connections.
E
We
also
don't
really
know
how
the
database
load
balancer
will
play
with
this.
We
know
pg
bouncer
has
support
for
us,
but
we've
never
tried
it
before
so
there's
a
lot
of
unknowns,
but
the
benefits
they
they're
the
same
as
moving
to
a
different
database,
because
the
work,
the
things
we
discover
they
are
all
the
same.
E
E
Now
we
can
decide
not
to
do
that.
Just
move
it
to
both
a
different
database
and
schema
at
the
same
time,
but
then
it
rises
brings
the
question.
Why
did
we
bother
with
different
schemas
in
the
first
place
because
it
ends
up
in
a
different
database
anyway,
but
I'll
try
to
capture
that
in
the
the
comments.
E
E
I
added
it
to
the
agenda.
I'm
still
writing
the
comment.
What
I'll
probably
do
is
write
it
yeah
I'll,
try
to
keep
it
in
one
comment:
instead
of
a
stream
of
thoughts,
basically,.