►
From YouTube: GitLab 15.7 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
B
Thank
you
season,
hi,
I'm,
Maddie
and
I'll
be
talking
about
user
search.
We
are
basically
trying
to
leverage
elasticsearch
in
our
Tech
stack
to
improve
the
way
we
do
user
search,
because
currently
we
are
performing
database
queries
to
search
users.
So
we've
done
the
work
to
add
the
data
necessary
to
perform
searches
on
users
and
in
1507
we
will
be
writing
the
search
queries
in
elasticsearch
to
perform
those
queries
next
up
in
15
7
we'll
also
be
adding
Auto
completion
for
users
in
the
global
search
bar
similar
to
the
current
or
typical
competitions.
B
A
Thank
you
Maddie.
Next,
we
have
Thomas
who
will
be
talking
about
the
programming
language
filters
and
a
couple
of
other
front-end
improvements.
C
Hi
everyone,
so
in
last
Milestone
1506,
we
finished
adding
a
vertical
navigation
into
our
search
page
and
that
gave
us
a
nice
space
to
add
other
additional
filters.
So
in
this
Milestone
we
are
going
to
be
adding
a
language
filter
I'll,
just
underneath
the
the
search
Scopes,
and
there
is
a
lot
more
coming
in
next
milestones.
We
are
also
working
to
finish
some
minor
stuff.
C
That
is
adding
some
help
for
filtering
methods
for
the
search,
and
we
are
also
finishing
a
little
fix
for
the
header
search
that
will
allow
us
to
properly
to
work
with
it
with
a
table
later
so
on.
The
keyboard.
A
Thank
you
so
much.
We
have
a
couple
more
issues
that
are
terrible,
explain.
A
D
Thanks
Susie,
so
the
first
issue
is
going
to
be
a
change
that,
if
you're
searching
with
any
of
the
Syntax
for
code
search,
which
is
the
glob
extension
path
or
file
name
currently,
that
will
default
to
the
project
scope,
which
wouldn't
return
any
results
so
we'll
be
making
changes
so
that,
if
you
appear
to
be
searching
for
blobs,
will
automatically
switch
over
to
the
blob
scope
to
make
your
search
experience
a
little
bit
faster.
D
D
A
Thank
you
Terry
other
than
the
features
we
also
planned
performance
improvements
for
the
next
Milestone,
so
first
I'll
pass
to
Zhang.
Who
will
be
talking
about
the
work
that
we
are
going
to
do
to
improve
the
performance.
E
Thanks
Susie
yeah,
so
we're
very
passionate
on
search
team
about
performance,
and
we
want
to
make
sure
that
we
budget
time
for
every
Milestone
to
improve
performance
and
how
we're
tracking
performances
through
our
Global
search
error
budget.
And
this
is
where
we
set
the
standard
on
how
fast
we
want
things
to
be
so
we're
looking
forward
to
improving
user
search
performance
with
the
optimizations
that
we've
made
with
indexing
users
and
also
we're
looking
to
explore
ways.
We
can
improve
the
indexing
as
a
load
that
we've
made
for
ourselves.
A
Okay,
thank
your
job.
The
next
one
I
think
a
terrible
will
be
able
to
help
to
cover
I
think
that's
related
to
our
the
code
structure.
D
Right
so
we
are
starting
the
work
to
get
us
ready
for
some
refactoring
of
one
of
our
main
service
classes.
Currently,
the
search
controller
has
a
pretty
heavy
Reliance,
upon
instance,
variables
and
so
we'll
plan
to
replace
that
Reliance
with
a
presenter
which
is
one
of
the
best
practices
in
the
get
lab
development
guide
as
well.
I
think
they'll
still
start
us
on
the
journey
to
getting
that
search
service,
refactored,
okay,.
A
Thank
you,
Terry,
okay,
the
next
one
is
related
to
other
efforts
on
the
index.
Integrity
John.
Do
you
have
anything
to
say
about
this?
One.
E
Yes,
so
this
is
for
when
sometimes
the
elasticsearch
index
doesn't
match
up
exactly
to
the
database
and
with
large
systems
things
fail,
and
so
what
we
want
to
explore
is
a
way
to
make
sure
that
there
is
integrity
between
the
two
data.
If
a
failure
does
happen
when
we're
indexing,
something
into
elasticsearch
that
we
make
sure
that
we're
addressing
that
and
we
keep
the
the
parity
between
the
two.
A
Okay,
thank
you
Rochelle.
The
next
Improvement
is
about
the
group
level
code
search
from
our
data.
We
have
seen
the
slow
searches
from
the
code
search,
so
we
are
going
to
try
to
improve
it
on
the
good
level
code.
Search
John
may
have
more
information
for
this
one
as
well.
E
Yeah,
so
this
is
definitely
Performance
Based
at
gitlab.
When
we
do
a
search,
we
have
to
take
a
lot
of
things
under
consideration
when
it
comes
to
visibility
and
permissions,
and
if
a
member,
if
a
user
is
a
member
for
many
projects
and
namespaces,
it
can
become
an
expensive
operation,
and
so
what
this
is
is
optimization
to
speed
that
up.
I
won't
go
into
the
technical
details,
but
we're
excited
to
roll
this
out
because,
where
we
have
and
other
Scopes
roll,
this
out
has
made
a
big
performance.
Improvement.
Okay,.
A
Thank
you
John,
the
next
part.
Actually,
we
have
a
few
issues
that
will
be
originally
planned
for
15
6
that
we
have
to
move
over
to
15
7.,
the
first
one
sidas.
Would
you
mind
to
talk
about
the
first
line.
F
A
E
Sure
so,
with
index
lifecycle
management,
what
that
means
is
we're
creating
more
indices,
to
have
an
Optimum
amount
of
shards
and
Shard
sizes
with
their
elastic
search
indices
and
what
the
R
spec
trade
is.
Is
we
want
to
make
sure
that
all
of
our
existing
tests
interact
with
multiple
indices
at
a
time,
so
that
we
know
that
we
have
the
proper
test
coverage
and
that
the
behavior
is
still
working
as
expected?
E
E
A
Your
job,
the
next
two
issues
are
related
to
the
testing
for
framework
using
is
ready.
Sorry,
you
may
help
to
talk
more
about
this
tool.
D
That's
something
it's
easy,
so
these
two
items
were
rolled
over
from
15-6.
They
will
be
the
first
one
is
trying
to
determine
our
data
strategy
for
the
first
rally
tests
we're
going
to
conduct
where
it's
stored,
how
we're
going
to
gather
that
data
things
like
that.
The
next
one
is
again
just
more
data
Gathering
and
determining
what
workload
we'll
be
using
for
the
first
test
and
how
that
workload
will
be
gathered
from
Cabana
and
kind
of
how
we're
going
to
track
it
going
forward.
D
A
You
Terry
other
than
features
and
the
performance
improvements
will
also
continue
to
fix
the
high
priority
bucks
in
the
coming
milestones
and
for
the
ux
design
need.
Our
direct
designer
will
probably
spend
majority
of
his
time
on
the
navigation
group
in
the
next
Milestone,
so
we
don't
than
any
specific
award
for
the
ux
data
for
the
global
search,
but
Nick
will
help
us
to
address
any
concerns
from
the
ux
site
when
they
come.