►
From YouTube: GitLab 13.3 Kickoff- Enablement:Global Search
A
Hi
I'm
John
Blair
I,
am
the
product
manager
for
global
search
I'm,
going
to
take
you
through
some
of
the
changes
that
we
are
getting
ready
for,
13
3,
so
the
first
one.
Now
that
we've
actually
gotten
gitlab
calmed
rolled
out
to
all
of
our
bronze
and
above
subscribers
we
are
going
to
focus
on
addressing
some
operation
maturity
areas,
and
this
has
a
lot
to
do
with
some
of
the
reporting.
A
Sometimes,
when
we
see
larger
groups,
we
actually
see
a
pretty
large
increase
in
query
response
time
as
much
as
five
seconds.
We
think
that
this
is
probably
due
to
kind
of
what
Wayne's
elasticsearch
works,
where,
as
you
actually
have
all
these
different
projects
that
are
in
a
larger
group,
it's
going
to
search
across
each
one
of
these
project,
IDs
and
essentially
after
so
many
times
it
just
takes
a
much
longer
time.
Very
so
we're
gonna
find
and
test
a
couple
different
ways
to
address
this.
A
We
do
have
some
IDs
on
and
what
will
actually
make
it
go
faster
and
if
it
doesn't
really
resolve
the
root
cause
of
this
problem,
it
should
still
make
search
faster
anyway,
all
right.
The
next
one
is
also
targeting
performance,
sometimes
on
the
advanced
search
result.
Page
specifically,
when
you're
doing
a
code
search,
you
will
find
that
it
can
take
up
to
a
minute
to
completely
load
the
page.
A
The
page
actually
starts
to
paint
pretty
quickly
like
within
a
few
seconds,
but
then
it
just
hangs
for
a
long
period
of
time,
while
it's
loading,
other
elements
and
they're
still
actually
a
search
request
going
on,
and
then
it
will
finally
finish
loading,
including
adding
a
few
more
results
and
overall
it
can
take
more
than
a
minute
for
that
page
load.
So
we're
going
to
this
may
be
related
to
the
previous
issue.
May
not
we're
going
to
take
a
look
at
it
and
see
if
we
can
figure
out
how
to
make
this
work
better.
A
All
right,
so
that's
what
we
actually
want
to
automate
the
deletion
of
our
old
indexes
after
a
reindex
is
completed.
So
this
would,
you
know,
primarily
be
a
health
self
manage
users
and
right
now,
we've
done
a
lot
of
the
previous
releases.
Where
we've
added
a
button
to
allow
you
to
do
re-indexing
well
today,
you
would
still
need
to
go
in
and
run
a
write
command
to
delete
that
old
index
or
it's
just
gonna
sit
around
taking
up
extra
space.
A
A
A
The
problem
that
we
kind
of
ran
across
was
that
in
when
you
actually
do
an
issue
search
or
an
EMR
search,
there's
a
little
piece
in
the
query
that
actually
makes
it
do
a
sort
by
updated
at
in
descending
order,
and
that
means
that
it's
not
really
taking
into
account
any
of
the
elasticsearch
scoring
that's
happening
so
you're,
not
necessarily
really
seeing
a
rank
or
relevant
results
based
on
what
you
search.
What
you're,
seeing
anything
that
could
have
been
returned
and
then
sorted
by
updated
act
in
descending
order.
A
So
that's
way
too
high
to
a
freshest
level,
and
it
can
make
several
cases
where
people
where
you're
trying
to
search
for
something
very
specific,
very
hard
to
find
it
can
bury
it,
especially
if
it's
it
gets
old
at
all
or
if
there's
a
lot
of
results.
That
frequently
happen
with
the
type
of
search
that
you're
conducting.
A
So
this
is
fortunately
if
this
is
actually
a
very
quick
fix.
We
there's
even
a
chance
we'll
be
able
to
get
it
into
32.
At
this
point,
it
is
not
in
32,
but
it
might
go
into
13
and,
if
not,
we'll,
certainly
get
it
in
for
13
3,
and
this
will
you'll
see
the
immediate
improvement
to
issue
relevancy
as
well
as
in
our
search
relevancy.
A
All
right,
the
next
one,
so
I
kind
of
noticed
that
when
you're
in
slack
and
you
paste
a
search
URL
in
slack,
you
get
back
information.
It's
not
necessarily
that
helpful,
and
you
know
this
is
because
we
don't
have
some
of
the
metadata
in
place
that
allows
for
Open
Graph
to
really
unfurl
your
the
information
for
URL
correctly,
and
we
can't
improve
that.
So
we
are
going
to
take
a
look
at
just
adding
some
extra
metadata
to
that.
That
should
be
a
relatively
easy
and
quick
fix
for
us
to
have
something.
A
All
right
and
the
last
one
I
wanted
to
just
remind
you
that
we
do
love
to
have
our
users
and
customers
give
us
or
feedback.
You
can
track
the
status
as
they're
actually
going
through
13-3
by
visiting
our
milestone
board
or
by
going
to
our
roadmap
and
link
into
any
of
the
the
epics
that
we
have
and
leave
us
comments.
Leave
us
uploads
downloads,
whatever
you
want
to
give
us
his
feedback.
All
of
it
is
extremely
helpful
and
definitely
helps
us
in
making
us
and
what's
going
to
create
the
best
value
for
our
customers.