►
From YouTube: Enablement:Global Search - GitLab 14.7 Kickoff
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
We
have
been
working
on
refreshing
and
building
out
a
lot
of
different
features
in
the
header
where
you
have
the
search
bar
as
well
as
some
drop
downs
when
you
actually
get
to
the
search
result
page
and
it's
really
kind
of
a
great
milestone
for
us,
we're
completing
our
efforts
and
revving
that
up
and
improving
it
with
this
last
final
header
change,
feature
flag,
that's
being
enabled
so
with
this
we'll
have
all
of
the
new
features
that
we've
been
planning
available
and
turned
on
in
14.7,
it's
faster.
A
It
gives
more
accurate
autocomplete
results,
it
has
better
descriptions
and
better
sizing.
There
are
a
lot
of
changes
that
really
are
completed
with
this
total
change,
so
definitely
interested
in
seeing
the
improvements
that
you've
had
with
using
the
the
gitlab
header
in
the
search
bar
and
the
features
that
are
connected
to
that.
This
has
been
a
several
month,
long,
iterative
process
that
we've
been
completing
and
working
through,
and
this
will
be
14.
A
7
really
does
tie
up
the
end
with
the
last
piece
of
it
with
this
feature
flag
going
out,
so
we're
really
excited
for
that
and
a
special
call
out
to
our
developer
zach,
who
had
worked
in
in
most
cases
very
much
single-handedly
on
this
he's
done
a
great
job.
Getting
us
through
a
lot
of
the
organizations
been
needed
for
this.
So
I
really
am
appreciative
of
the
work
that
he's
done
with
us
to
get
the
new
header
completed
for
search.
A
A
We
have
commits
so
we've
been
moving
a
lot
of
the
different
scopes
into
their
own
indexes
and
we've
seen
great
performance
improvements
with
that.
Generally,
when
we
do
this,
we
see
important
performance
improvements
in
the
scope
that
we've
moved
out.
They
usually
greatly
improve,
and
then
we
see
a
little
bit
or
sometimes
even
more
performance
improvements
that
happen
on
doing
blob,
searches
or
code
searches,
because
that
is
the
index
that
remains
is
primarily
going
to
be
the
code,
the
code
that
we're
searching
so
moving
commits
out.
A
We
expect
to
see
the
same
type
of
performance
improvements
and,
if
you
haven't
been
using
gitlab.com
gitlab.com,
we've
seen
like
4x,
maybe
even
5x
improvement
and
the
speed
of
search
results
coming
back
within
the
last
12
months
from
this,
and
some
of
the
other
changes
that
we
had
been
mating
been
making,
including
one
of
the
bigger
changes
that
we'd
recommend
is,
is
the
upgrading
to
the
more
recent
versions
of
elasticsearch.
A
We
saw
a
great
improvement
with
that.
Speaking
of
elasticsearch,
we
are
bimodally
compatible.
At
this
point,
we've
had
some
customers
that
have
reached
out
to
us
and
told
us
that
they're
using
open
search
or
they
plan
to
use
open
search
and
our
intent
is
not
to
in
any
way
limit
customers
to
only
use
elasticsearch
there.
The
there's
a
brief
history
on
that
is
that
elasticsearch
was
forked
in
version.
A
710
aws
created
their
own
version,
and
that
is
now
called
open
search
and
we
have
customers
that
are
successfully
using
open
search
to
catch
up
with
that.
A
We
are
wanting
to
really
ensure
and
test
to
see
as
we're
going
through
our
iterations
and
changes
that
we
can
detect
any
type
of
open
search
issues
that
may
occur
so
we're
now
putting
in
place
our
open
search
testing
framework
so
that
we
can
start
to
see
any
details
that
might
change
and
detect
any
problems
and
correct
them
and
at
least
have
a
better
insight
into
what
happens
there.
As
this
version
evolves
separately
from
elasticsearch
and
cz's.
Gonna
explain
a
little
bit
of
details
on
the
next
change
that
we
have
coming.
B
Thank
you,
so
another
effort
that
we
are
going
to
do
on
the
testing
front
is
to
improve
the
efficiency
of
how
we
use
elasticsearch
in
our
pipelines.
B
Right
now,
in
our
testing
pipeline,
we
have,
we
have
to
start
turn
it
on
and
off
a
few
times
each
time
when
we
turn
this
on,
then
we
have
to
make
wait
until
the
elasticsearch
instance
to
be
ready.
So
we
hope
to
reduce
the
time
that
we
have
to
turn
it
off
and
on
back
on
again,
and
so
in
order
to
do
that,
we
hope
it
can
improve
the
experience
of
other
development
and
testing
for
our
engineers.
A
A
That's
you
know
in
a
60
second
time
frame
or
less
is,
is
tremendous
and
and
being
able
to
add
performance
back
to
the
pipelines,
and
so
this
is
a
great
overall
improvement,
not
just
for
the
elastic
search
piece,
but
also
for
you
know,
kind
of
creating
efficiencies
across
the
use
of
the
pipeline,
really
great
okay
and
that's
what
we're
planning
for
14-7.
So
thank
you
and
I
hope
you
really
enjoy
the
new
changes
that
are
coming
out
with
the
header.
A
Definitely
I'm
always
open
to
getting
your
feedback
on
that
and
understanding
what
you
think
we
should
be
doing
next
to
make
additional
improvements
there.
Thank
you.
Thank
you.