►
From YouTube: GitLab 13.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
B
Sure
so
today
in
elasticsearch
we
store
all
of
our
data
in
a
single
index,
and
while
there
are
a
lot
of
problems
with
that,
I
think
the
biggest
reason
for
us
to
decide.
We
are
going
to
try
to
start
splitting
data
out
of
the
large
index
into
individual
indexes
is
due
to
performance,
so
we're
hoping
to
see
a
large
increase
in
performance
for
searching
issues
if
we
break
them
out
into
their
own
index.
B
That
is
really
exciting
and
it
is
quite
a
few
steps.
So
the
proposed
solution
has
about
eight
steps,
which
are
also
going
to
be
broken
down
into
smaller,
merge
requests
when
we
work
on
them,
but
ideally
we're
going
to
try
to
remove
all
of
the
joins
with
the
issue.
Queries.
Currently,
the
issue
queries
have
to
look
at
the
project
to
see
whether
they
can
be
queried
or
not
for
permissions.
B
B
Yes,
we're
really
excited
for
that
and
we're
also
beginning
to
introduce
migrations
for
elasticsearch
data.
That's
going
to
be
talked
a
little
bit
later
by
dimitri,
but
we
have
a
framework
to
do
migrations
to
set
up
the
new
index
for
issues
to
copy
the
issue,
data
into
it
and
then
to
clean
up
data
from
the
old
index.
B
A
Yeah
and
we'll
cover
that
in
just
one
second,
and
I
think
one
of
the
key
things
here
that
users
should
expect
you
know
this
is
quite
a
bit
of
work
to
start
breaking
out
these
indexes
and
if
you
can
imagine
for
the
get
lab
as
the
sas
solution,
this
is
quite
a
large
index
as
well.
I
know
a
lot
of
our
customers
are
also
operating
pretty
large,
repos
and
they're
for
pretty
large
indexes,
but
the
advantage
advantages
that
I
everybody
should
get
from
this
is
improved
performance.
A
It
will
allow
us
to
expand
on
the
content
that
we
are
aggregating
and
indexing,
which
will
allow
us
to
continue
to
build
additional
features
out
and
we're
going
to
cover
some
of
the
examples
of
what
those
features
look
like
and
where
they're
going
to
go
in
the
new
experience
that
we're
working
on
and
a
little
bit
later.
A
But
ultimately
we
need
to
do
this
so
that
we
can
expand
that
out,
keep
performance
up
and
also
keep
scalability,
as
we
continue
to
grow
with
that
one
of
the
things
that
we've
had
a
concern
with
is
every
time
we
make
some
type
of
data
change.
You
have
to
put
that
data
change
into
the
index
and
when
that
happens,
in
order
to
take
advantage
of
it,
a
lot
of
our
self-managed
users
would
be
asked
to
do
a
full,
re-index
or
a
re-index,
so
they
could
actually
get
that
new
data
component.
A
So
dimitri
worked
on
something
that's
coming
in
13-7
and
it
is
available
now,
but
it's
not
going
to
be
used
yet
related
to
the
migrations
demetri.
You
want
to
tell
us
about
that.
A
The
next
thing
is
something
that
is
really
enabling
the
first
part
of
what
all
of
these
pieces
kind
of
come
together
to
allow
us
to
do
so.
We
are
updating
the
user
experience,
which
is
really
the
first
time
we've
made
this
change
a
major
change
to
our
global
search
experience
in
over
two
years
and
zach.
Could
you
give
us
a
walkthrough
of
what
you've
been
working
on
with
this
and
what
users
can
expect
with
this
new
ux.
D
Absolutely
so
I'm
zach,
I'm
the
front
engineer
on
the
global
search
team
and
sorry
about
that.
So,
as
you
have
probably
seen
on
the
issues
and
in
our
screen,
we've
really
been
trying
to
kind
of
clean
up
the
design
and
bring
it
more
aligned
with
gitlab
and,
along
with
that,
we're
adding
these
new
filters
to
the
left,
rail
and
with
them.
We
have
some
functionality.
Where
now
you
can
filter
down
your
search
more
than
just
the
keyword.
D
So
if
you
wanted
to
search
for
maybe
just
open
and
non-confidential
issues,
you
go
ahead
and
click
apply
and
you'll
see
that
now
your
results
all
match
just
that
query
as
well
as
if
it
doesn't
match
the
query.
You'll
see
that
your
address
that
you
couldn't
find
anything,
but
you
can
simply
reset
the
filters
so
right
now,
this
is
available
going
to
be
available
in
137
on
the
issues,
as
well
as
the
merge
request,
page
and
so
similar
to
issues
with
their
status.
You
can
also
search
based
on
the
status
of
the
mr.
D
A
Yeah,
that's
great
a
couple
things
that
users,
if
you
can
keep
sharing
there,
that
mutuals
might
also
notice,
is
that
we
had
recently
added
in
the
sort
functionality
that's
listed
on
the
right.
This
was
something
that
we
did
not
have
before.
It's
gotten
a
lot
of
use
since
we've
added
it
and
it's
definitely
a
good
reason.
If
you're
considering
upgrading
to
get
lab
six
or
seven,
this
is
a
good
reason
to
add
it
is
these
advanced
features
that
we're
adding
into
advanced,
search
and
basic
search
along
with
these
filters?
A
We
are,
you
know,
just
to
kind
of
talk
about
where
we
came
up
with
this
design.
This
may
seem
very
familiar
in
regards
to
having
options
to
facet
filter.
On
the
left
hand,
side.
This
is
used
in
about
90
of
more
complicated,
advanced
searches
across
the
entire
internet.
This
is
a
very
common
feature
to
kind
of
use
and
explore
content
and
try
to
find
it.
A
The
idea
of
having
this
in
a
left
rail
versus
drop
down
to
the
top,
which
is
what
they
were
when
we
first
launched
them,
is
that
a
user-
that's
not
as
familiar
with
get
lab.
Might
not
be
fully
aware
of
what
confidentiality
and
status
might
mean
so
displaying
what
options
are
underneath
that
for
them
to
select
help
define
the
meaning
for
what
that
status
is
now
that,
in
general,
isn't
going
to
be
a
big
problem
with
status
confidentiality.
A
But
this
is
also
the
area
where
we're
going
to
be
adding
additional
filters
in
the
future,
which
is
going
to
be
enabled
by
the
work
that
we
just
talked
about
from
the
migrations,
as
well
as
the
new
method
of
how
we're
going
to
break
out
our
indexes,
and
so
once
we
start
adding
this
good
content,
we'll
be
able
to
add
new
filtering
we're
going
to
make
a
more
rich
experience
for
everybody
to
be
able
to
use,
and
all
those
are,
are
the
path
of
what
we're
actually
starting
with
right
now.
A
A
You
know
your
your
state
as
well
as
we're
going
to
look
at
confidentiality
too
and
see
if
we
can
add
this
into
13
7..
Eventually,
we
want
to
be
able
to
build
out
that
similar
functionality
across
all
those
scopes
and
we
are
discussing
if
we
want
to
then
bring
those
scopes
into
one
result,
page
that
kind
of
combines
them
all
we're
kind
of
working
through
the
details
of
what's
going
to
work
best
for
users
with
that,
and
we
would
love
to
hear
your
feedback
if
you
have
time
to
interact
with
us.
A
So
that
is
the
overview
of
what
we
have
for
thirteen
seven.
I
wanted
to
thank
zach,
demetri
and
terry
for
joining
me,
and
I
hope
you
guys
have
a
great
kickoff.
You.