►
From YouTube: GitLab 13.9 Kickoff - Enablement:Global Search
Description
You can follow along with our planning issue.
https://gitlab.com/gitlab-org/search-team/team-tasks/-/issues/29
Elasticsearch Migrating Issues To Separate Index Technical Overview
https://www.youtube.com/watch?v=1znFvPH_wjU
A
B
Thank
you,
john.
So,
in
this
39
release
we
are
going
to
continue
our
efforts
on
improving
the
user
experience
with
the
advanced
search.
We
have
one
issue.
We
are
going
to
add
a
scope
in
a
top
level
search
bar
to
show
users
at
which
scope
the
search
will
happen.
So
here
is
a
screenshot.
That
is,
is
our
design.
B
A
Yeah,
so
I
particularly
like
this
change,
because
you
know
we're
not
really
changing
the
functionality
that
exists
today,
we're
just
making
it
more
apparent
to
the
users
who
you
know
in
our
current
experience.
It's
not
really
clear
that
when
you
do
the
search
in
the
search
box
that
you're
gonna
go
to
the
same
project
that
you're
already
in,
and
so
this
will
hopefully
make
it
clear
and
also
promote
users
to
maybe
change
that
project
if
they
don't
want
to
search
in
the
project.
B
B
B
The
purpose
of
this
change
is
to
give
user
more
information
about
the
search
result
before
they
can
apply
the
filters,
for
example,
if
in
this
page,
if
we
ended
up
with
a
search
results
there,
you
can
see
the
status
open,
merged
and
closed,
for
example,
if
nothing
gets
merged
will
show
that
the
counter
as
zero.
So
you
don't
have
to
apply
the
filter
because
they
know
there
are
no
such
such
results.
A
B
B
A
You
know
again
with
the
the
user
experience
piece
like
you
know.
This
is
a
another
way
to
kind
of
research,
the
the
understanding
of
how
users
and
what's
important
to
users.
So
this
is
an
example
where
we've
taken
data.
That
is
how
our
users,
in
our
sas
environment,
are
using
the
issue
board
for
search,
not
necessarily
search
but
we're
using
that
to
then
try
to
understand
what
would
be
the
next
sort
option
that
we
should
create.
A
That
will
be
the
most
useful,
and
so
that's
where
we
come
up
with
the
idea
of
the
of
adding
in
the
last
updated,
and
so
that's
that's
a
great
example,
multiple
ways
to
do
kind
of
user
experience.
I'm
sure
it's
going
to
use
a
lot.
I
use
the
new
sword
feature
every
day.
I
hope
everybody
else
is
enjoying
it.
B
A
So,
thank
you
and
you
know
going
into
the
next
thing.
We
have
been
noticing
that
there
has
really,
since,
like
the
november
time
frame,
maybe
even
into
the
end
of
october,
we've
noticed
that
latency
has
kind
of
slowly
been
increasing
for
elasticsearch
and
our
sas
experience,
and
this
may
be
something
that
is
also
occurring
in,
like
really
really
large
instances
for
our
self-managed
users.
A
We
haven't
heard
that
feedback
directly,
but
as
we
continue
to
grow
the
index
size
as
gitlab
continues
to
grow,
we
continually
will
bring
in
pieces
to
try
to
keep
a
focus
on
performance
and
improve
the
performance
of
elasticsearch
in
gitlab,
and
so
in
this
next
in
this
next
model.
In
this
next
release
in
139,
we're
actually
going
to
continue
some
work
that
we've
been
doing
to
improve
performance
around
splitting
out
the
search
index.
A
So
a
lot
of
what
happens
in
elasticsearch
as
there's
a
lot
of
performance,
it
gets
taken
up
by
how
it
actually
does
indexing
and
we
had
found
that
there
is
an
efficiency
when
we
start
to
separate
out
these
indices
by
each
of
the
search
scopes,
and
so
in
13
8.
We
have
just
finished
doing
this
with
issues
in
139.
We're
going
to
do
this
with
notes,
also
referred
to
as
comments
and
then
we'll
be
moving
on
through
the
rest
of
these
scopes
in
future
and
future
releases
as
well.
A
A
We
have
added
a
lot
of
migration
details
that
allow
for
these
type
of
changes
to
happen
in
a
hopefully
very
uneventful
way
for
you
and
all
you
really
need
to
do
is
just
do
your
update
and
as
it
as
it
does,
the
update
it
will
actually
start
pulling
in
the
index
for
the
new
version
and
then
removing
the
old
one
as
it
goes
it
does.
This
shard
by
shard
dylan
on
our
team,
has
created
a
great
video
that
gives
a
more
detailed
walkthrough
of
what
happens
in
that
migration.