►
From YouTube: GitLab 14.2 - Enablement:Global Search
Description
Code Search for Big Code
https://gitlab.com/groups/gitlab-org/-/epics/6220
A
Hi
I'm
john
mcguire.
I
am
the
search
product
manager
and
I'm
going
to
take
you
through
some
of
the
changes
that
we
have
coming
up
for
get
lab,
14
2..
So
the
first
item
that
we're
looking
at
is
the
ability
to
sort
issues
and
merge
requests
by
the
number
of
uploads
and
likes
pretty
simple.
We've
actually
seen
a
lot
of
success.
A
lot
of
usage
around
some
of
the
other
sort
options
that
we've
made
available
in
the
past.
A
You
can
see
that
we'll
also
be
adding
in
the
the
little
icon
with
the
thumbs
up
or
the
like
option
in
the
result
as
well,
so
that,
as
you
choose
that,
so
we're
going
to
be
able
to
see
that
you
did
actually
get
a
response
back,
that's
worth
these.
A
A
A
In
this
case,
we
have
some
options
that
allow
you
to
save
on
your
total
indexing
size,
so
you
can
set
a
max
size
limit
for
files
that
you
don't
want
to
index,
and
what
we
realize
is
that
we
don't
really
need
to
index
that
file.
A
A
If,
in
the
previous
releases,
we
had
updated
how
this
looks
in
view,
so
it
is
more
readable
and
so
really
interested
to
see.
If
this
is,
you
know
successful
and
to
hear
feedback
from
users
on
how
much
this
is
really
gonna,
you
know
help
them
just
kind
of
navigate
through
the
maybe
handful
of
groups
of
projects
that
they're
looking
through
we're,
always
focused
on
improving
performance
and
one
of
the
areas.
A
That's
come
up
in
the
last
couple
couple
months
that
we've
seen
we
have
an
opportunity
to
improve
performance
on
has
to
do
with
the
service,
for
the
search
controller
account.
So
in
the
example
of
search
controller
account
is
the
the
number
that
gets
populated
next
to
the
tab
in
the
global
search.
A
This
can
sometimes
be
in
in
a
large
amount
of
calls
that
can
be
six
or
seven
or
eight
different
calls
happening
at
the
same
time
it
we
think
we
have
found
a
way
to
improve
this
quite
a
bit
and
if
we
can
indeed
improve
the
speed
of
these,
these
count
calls
we'll
see
an
overall
shorter
amount
of
time
to
send
any
responses
back
through
the
elasticsearch
service
or
anything
that's
using
the
search
controller
service,
and
that
could
create
some
improvements
that
go
beyond
just
accounts
and
actually
improve.
A
Any
potential
bottlenecks
might
be
happening
to
anything
through
the
search
controller,
we're
always
happy
to
find
ways
to
improve
performance.
And
if
this
works,
as
we
were
expecting
it
actually
could
be
a
huge
improvement
for
us
and
improve
the
experience
for
users
that
are
using
advanced
search
as
well
as
using
basic
search.
A
We
are
doing
some
more
user
experience,
research
right
now
that
has
to
do
with
adding
labels
as
a
facet
into
advanced
search.
Now
I
am
incredibly
excited
as
a
product
manager
about
being
able
to
filter
search
results
by
how
something
is
labeled.
This
is
not
going
to
live
that.
Yet
this
is
about
trying
to
understand
what
we
want.
That
user
experience
to
look
like
and
operate
like,
so
that
we
can,
you
know,
make
it
easy
to
use.
A
There
are
a
lot
of
complexities
that
come
with
how
labels
can
be
set
up,
and
so
there
is
some
testing
you'll
need
to
do
with
these,
but
I
wanted
to
make
it
clear.
This
is
something
we're
excited
about
we're
working
on
we're
kind
of
in
that
ux
phase
right
now,
stratifying
like
what
that's
going
to
need
to
look
like,
and
it
will
be
coming
to
us
in
a
future
iteration
when
we
can,
particularly
so
we
can
actually
get
this
feature
live
and
out
there.
So
this
is
going
into
the
pipe.