►
From YouTube: GitLab 13.11 Kickoff - Enablement:Global Search
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
A
Over
the
last
few
milestones,
we've
been
working
on
separating
out
the
index.
Instead
of
having
each
scope
in
one
large
index,
we've
been
breaking
out
each
scope
into
their
own
individual
index.
That's
going
to
give
us
a
lot
more
flexibility
for
how
we
can
finally
adjust
details
over
that
index,
as
well
as
make
some
performance
improvements
that
you
will
see
because
search
will
work
faster.
A
In
order
to
do
this,
we've
done
a
lot
of
things
to
make
sure
that
we're
not
adding
extra
complexity
to
administering
your
elasticsearch
component
for
advanced
search
and
we
have
broken
out
most
of
the
scopes.
The
next
one
that
we're
going
to
be
taking
on
is
merge,
requests,
so
merge
requests
are
going
to
be
broken
into
their
own
index.
A
A
A
So
we've
seen
some
great
improvement
to
the
latency
since
we've
been
making
these
changes.
This
is
this
originally
was
was
about
twice
the
latency
that
we
were
seeing,
and
this
has
gone
down
considerably
and
we
have
noticed
that
it's
starting
to
tail
up
a
little
bit
with
the
exception
of
a
couple
dips
down
here
now,
because
of
that
we're
going
to
continue
to
do
some
work
that
is
going
to
enhance
performance.
A
A
That
should
allow
for
these
groups
to
kind
of
quickly
go
in
impact
performance
and
get
back
to
normal
and
allow
for
a
higher
chance
of
just
long-term,
better
latency
results,
the
only
exception
being,
of
course,
when
it's
running
through
a
batch
of
elites,
but
even
batching.
Those
together
allows
them
to
run
faster.
A
As
we
start
looking
at
what
we've
kind
of
changed
and
applied
across
git
lab
and
global
search,
we've
focused
on
the
details
of
these
scopes
and
one
of
the
things
that
we've
seen
in
feedback
and
it's
you
know
we
thought
we
could
make
it
better.
Is
that
the
tab
order,
the
scope,
order
that
comes
back
when
you
do
a
search
has
not
been
consistent.
It
will
change
depending
on
where
you're
coming
from
and
a
lot
of
variables.
A
Those
variables
don't
necessarily
help
if
they're
changing
the
order.
Maybe
it
helps
for
what
default
scope
you're
in,
but
we
didn't
see
that
changing
the
order
is
actually
beneficial,
and
so
we
intend
to
fix
the
order
so
that
it's
the
same
each
time,
and
this
means
that
every
time
you'll
you'll
be
able
to
reference
and
learn
the
same
order
of
of
these
scopes
without
having
to
worry
about
them.
A
So,
finally,
we've
gotten
some
feedback
from
some
of
our
customers
that
we
could
have
some
better
documentation.
Now,
we've
made
some
good
documentation,
changes
that
were
part
of
1310
and
have
reorganized
the
information
as
part
of
our
get
lab
docs
we.
The
next
piece
I
want
to
try
to
handle,
is
the
details
on
how
you
set
up
advanced
search,
integration
with
elastic
and
the
general
setup
documentation
for
advanced
search,
and
so
this
is
the
the
goal
is
to
actually
have
this
kind
of
revised.
A
I've
also
added
the
ideas
of
having
some
walk-through
videos,
which
is
something
that
we
we
haven't,
really
done
a
lot
of
in
the
documentation,
but
I
think
it
actually
could
be
helpful
to
see
at
least
a
walk-through
of
some
of
the
general
configurations
in
a
video
so
that
it's
just
easier
for
anybody
that
might
get
stuck
trying
to
figure
out
what
they
need
to
do.
If
they're
trying
to
set
up
advanced,
search
or
install
advanced
search
with
elastic-
and
that's
it
that's
what
we're
looking
at
doing
for.