►
From YouTube: Magento MSI Open Demo. March 1, 2019
Description
Today's agenda:
- Two big updates before Magento 2.3.1 by @iminiailo and @Stepan Furman
- Demonstration of Performance improvement for Product Save @TheRick
- The announcement of a new project (Sales Channel) which sync up Magento with (Amazon / Google Shopping ) by @Priya Bhat
- QA and Regression update by @Tom Erskine
A
So
looks
like,
like
I,
mean
I
managed
to
switch
on
the
recording.
It
was
not
so
easy,
so
I
had
I
had
to
use
three
attempts
to.
Did
it
hello,
everybody
we
are
on
a
new
place,
but
we
will
have
the
same
idea
that
same
intention
to
share
with
you
all
the
updates
we
have
regarding
the
MSI
and
there's
some
supplementary
projects,
because
I
really
hope
that
Priya
will
join
us.
A
A
So
I
wouldn't
say
that
that
is
directly
dependent
on
MSI,
but
taking
into
account
that
we
spent
quite
a
lot
of
time
during
this
week
on
this
pull
request,
and
actually
we
are
still
working
on
it.
I
believe
that
it
definitely
makes
sense
to
spend
a
few
and
a
few
time
and
talk
a
little
bit
in
highlight
the
work
being
done
in
the
scope
of
this
pull
request
remain,
unfortunately,
can't
attend.
A
So
it's
literally
in
ten
days
and
we
had
a
risk
to
release
magenta
to
Lucy
that
one
without
any
maintained
version
of
elasticsearch,
so
that
remain
from
smile
created
the
school
address
where
he
introduced
a
module.
Her
hinge
rededicated
module
where
we
support
the
elastic
36
version,
which
is
pretty
my
pretty
cool,
and
also
you
can
see
that
our
main
committed
that
he
will.
A
Wouldn't
use
still
remain
stroll
so
that
we
will
spend
some
time
here
in
your
next
presentation
in
a
week
where
a
man
will
demonstrate
how
the
elastic
search
six
supported
and
how
it
works
in
magenta,
maybe
he'll,
to
make
some
even
comparison
with
the
elastic
search,
five
or
like
previous
version,
we
still
supported.
But
this
is
really
great
because
guys
from
community
you
even
having
some
gaps
from
from
magenta
side,
yes
from
community,
don't
let
us
make
this
gap
see
in
relief,
oceans
and
another
another
community.
Here.
A
One
so
I
would
not
also
tell
too
much
because
Stepan
currently
is
on
the
call,
and
he
will
give
ok,
he
can
describe
all
the
background
of
the
pull
request
and
the
work
you've
done
by
himself,
so
sleep
and
feel
free
to
share
your
screen.
I
am
stopping
sharing
mine
yep
and
you
can
you
can
tell
more
about
what
you
did.
B
Yep,
ok,
ok!
So
the
problem
was
that
an
msi
with
until
we've
implemented
support
of
products.
We
use
my
SQL
view
for
providing
available
quantity
and
our
rollback
system
back
up
and
rollback
system
didn't
support
that
because
magenta
didn't
differentiate
the
table
and
you
and
if
we
had
some
created
products
assigned
to
default
stock,
so
we
had
a
magenta
tried
to
create
that
database
them
and
yeah
and
magenta
walks
foreign
keys
for
this
purpose.
The
second
member
yeah
I,
can
start
to
show
so
for
showing
this
server
I
decided
to
use
them
aside.
B
B
B
Yeah
so,
as
you
can
see
in
a
in
a
database
backup,
we
have
this.
The
table
drop
table
three
table
and
it
tries
to
log
table
and
outdoor
table
disabling
keys
to
and
try
to
insert
something
here,
but
we
can't
insert
something
to
review.
So
that's
why
this
is
the
main
error.
So,
okay
I'll,
try
to
restore
and
show
you
that
it
doesn't
work.
B
B
B
B
Deleted
whose
file
so
as
you
can
see
that
a
very
strong
bed
was
completed
successfully
and
I
will
pick
up
one
more
time,
just
to
show
you
what
the
Declaration
of
the
wheels
was
created
there
so
and
meanwhile,
maybe
I
can
show
you
in
the
court
what
was
created
so
instead
of
instead
of
using
old,
get
all
tables
method
I
injected
the
new
service
that
returns
list
of
tables
instead
of
show
tables,
I
used.
These
show
full
tables
where
table
type
is
very
stable
and
yeah.
B
So,
and
this
way
we
just
get
here
on
the
tables
without
any
views
and
after
breaking
up
tables
I
injected
here
the
I
get
views
backup
service
that
provides
backup
for
views
yeah,
and
here
we
also,
you
also
get
the
we
have
the
same.
The
same
query:
the
difference
is
only
the
table,
type
is
view
instead
of
face
table
and
we
also
create
the
show
great
view,
drop,
use,
exists
and
yeah
yeah
and
so
some
basic
structure
for
this.
B
A
Yeah
cool
sink
his
chopper,
so
like
Japan
introduced
if
the
ability
on
the
level
of
the
whole
framework
to
differentiate
regular
tables
out
of
my
sickle
views,
and
now
we
preserve
this
functionality
at
the
time
of
the
backing
up
and
the
restoration
and
currently
like
take,
especially
taking
into
account
that
MSI
now
is
a
part
of
the
part
of
standard
magenta
delivery
in
standard
magenta
deployment.
So
actually
all
that
all
the
merchants
were
affected
because
at
least
for
the
single
stock,
at
least
for
default
stock,
to
support
bundle
product
as
a
stopper
correctly
mention.
A
We
still
use
the
Mexico
view
and
to
support
the
functionality
of
the
tech
up
and
in
the
restoration
we
have
to
implement
it
fix.
But
I
want.
Is
that
all
the
other
extension
developers
who
use
views
in
their
functionality
also
will
benefit
from
this
cool
request,
and
also
we
have
preached
interesting
conversation
because
in
a
DMS
a
sectional,
because
yesterday
they
were
out
the
pills
like,
let's
get
bundled
product
great
again.
So
we
would
definitely
for
it.
A
We
and
we
definitely
support
the
bundled
product
transition
to
support
the
msi
and
as
soon
as
we
will
get
some
volunteers
who
would
like
to
support
the
bundled
product
will
definitely
introduce
this
support
because
currently
introduced
introduced
in
support
for
bundle
product
wouldn't
be
also
just
a
bundle
product
support.
But
we
can.
We
can
like
get
rid
of
this
view.
We
can
the
default
index,
we
can.
A
We
can
switch
the
default
index
to
the
real
index,
told
to
the
materialized
table,
but
not
to
the
view,
and
that
will
introduce
that
actually
pretty
big
the
performance
boost
for
the
inventory
mechanism.
So
it's
currently
stopper
made
the
big
step
to
work
towards
the
bright
future
of
magenta,
with
the
new
inventory
and
with
the
supportin
of
the
of
the
expert
in
important
data.
So
this
definitely
matters
so
now.
Let's
switch
to
other
presenter
and
the
other
presidents
are
going
to
be.
A
Not
anybody,
not
anyone
else,
but
recorder,
and
the
recorder
will
make
the
presentation
of
the
performance
improvement
and
the
performance
improvement,
as
we
already
mentioned,
especially
crucial,
because
currently
we
see
that
more
and
more
merchants
are
migrating
to
magenta.
To
the
three
that
oh
and
the
two,
the
three
that
one
when
it's
going
to
be
released
so
that
that
performance
fixes
for
us
from
the
top
priority
right
now.
So
I'm
stopped
talking
and
recorded
for
your
screen
and
make
a
demonstration.
C
Cool
so
well
I'm,
just
playing
with
the
performance,
so
I'm
I
started
solving
this
problem
and
I
started
from
one
one
point:
one
entry
point
that
you
go
suggested
me
so
basically
you
know
that
a
messiah
is
one
module
on
the
top
of
the
standard
merchant
implementation,
and
thus
we
have
to
keep
the
backward
compatibility
with
the
auditory
system.
So
every
time
you,
for
example,
save
something
in
the
default
source.
C
You
have
to
align
all
the
old
inventory
stacks
or
the
so-called
legacy
cattle
inventory,
and
this
is
done
not
the
database
level,
but
at
application
level
with
a
plug-in
and
plugins
in
years.
When
you
you
can
see
in
my
screen,
so
basically
it
happens.
Every
time
you
save
a
new
source.
Basically,
if
this
source
belongs
to
the
default
source,
we
are
going
to
update
even
the
legacy
cattle
inventory.
So
I
tried
to
make
something
following
the
egor
directives
and
it
was
to
synchronize
this
process.
C
So
basically
we
just
say
the
source
item,
and
then
we
have
an
emitter
consistency
using
on
a
synchronous
queue.
So
this
is
just
a
test
at
it.
So
I
change
the
default
implementation
that
was
made
by
set
data
to
legacy
catalog
inventory
to
a
new
class
I
created.
This
is
just
test
is
not
the
final
implementation,
that
is
a
synchronous
set
data
to
legacy
cut
rockumentary.
That,
basically,
is
skewing
this
alignment
process
using
rabbitmq,
and
this
is
what
happens
actually
so
here
we
have
product
with
quantities.
70,
let's
say
we
change.
This
is
too
much.
C
Let's
say
we
are
50,
oh
yeah,
but
we
start
the
queue
of
course,
and
if
I
click
Save,
basically
it
saved
the
source
item,
but
the
operation
of
alignment
of
the
legacy
battery
is
made
as
synchronously
and
if
it
works
that
I
did
not
break
anything.
Actually,
we
should
see
something
in
rabbitmq.
So,
okay,
you
can
see
what
message
is
incoming
and
then
this
message
should
be
handled
by
on
a
synchronous,
consumer
and
again,
if
I
didn't
broke
anything
since
the
last
implementation,
we
should
have
the
data
aligned
in
our
legacy
documentary.
C
So
basically,
this
should
actually
improve
performance,
because
we
we
don't.
We
don't
have
to
keep
this
if
this
information
online-
that's
application
level,
because
this
is
good
when
you
have
just
one
product,
but
you
can
figure
what
what
may
happen.
If
you
have
the
update,
let's
say
1000
products
or
10,000
products
or
more
so
basically,
it's
consuming
a
lot
of
time,
and
if
you
can
run
this,
a
synchronously
from
my
perspective
is
a
very
good
performance
improvement,
and
this
is
what
I
did
till
now.
C
A
Generally
speaking,
we
have
the
rabbit
in
Cuba
which
send
messages
and
when
they
handler
handles
it
message
at
the
event
like
worker
and
the
the
message
back
to
message:
queue
that
I
accepted
the
message
and
that
was
handled.
But
potentially
it
could
happen.
The
situation
when
the
broker
sent
the
message
to
handler
and
the
handler
will
handle
that
message
process
and,
for
example,
update
data
and
the.
But
the
problem
will
happen
at
the
time
when.
A
D
A
C
D
C
A
I
believe
you
could
be
good
choice
for
us
if
you
would
have
just
an
operation
like
that
data,
because
like
where
we
trying
to
apply
the
separation
for
the
for
the
product
say
where
we
have
to
synchronize
the
inventory
update
to
all
them
to
all
the
storages,
like
catalog
inventory
stock
item,
so
that
if
we
have
just
set
operation
so
the
set
operation,
is
it
important?
So
we
can
apply
it
several
time
to
know
and
the
result
would
be
the
same.
But
we
have
to.
D
A
C
A
Yeah,
so
just
want
to
say
thank
you
to
you,
because
this
this
performance
improvement
is
really
crucial
and
we
already
had
several
merchants
who
complain
on
performance
on
a
product
save
operation
because
they
have
mass
product
synchronization
with
external
system,
and
they
have
quite
a
lot
of
product
save
operation
and
that's
why
the
the
performance
degradation
on
this
operation
actually
was
pretty
irritating
for
them.
That's
why
such
performance
improvement,
where
we
can
make
the
some
part
of
the
operation
I
think
Romeo's
will
be
definitely
will
be.
Definitely
crucial.
A
Parts
for
this
merchants,
and
just
one
more
thing
to
say
that,
like
as
this
performance
improvement,
the
same
as
a
presentation
by
Stephan
is
all
the
root
causes
that
we
currently
have
to
support
the
bed.
We
have
to
come
be
backward
compatible
with
the
previous
system.
So
if
we
were
allowed
to
just
drop
support
of
the
Cadillac
inventory,
more
you'll
wish
you
had
before
we
did
not
have
any
of
the
synchronization.
A
So
just
this
is
actually
the
cost
to
be
backward
compatible
and
we
probably
eventually
will
drop
the
support
for
the
catalog
inventory
module
since
magenta
2.4
and
along
with
that,
we
will
get
gain
4
for
the
performance,
because
we
no
need
to
keep
the
same
data
in
two
different,
two
different
storages.
We
no
need
to
make
all
the
synchronization.
So
that's.
Why,
like
this
is
the
cost
of
the
backward
compatibility.
So
it's
pretty
pretty
important
to
understand.
A
E
D
A
D
Can
you
hear
me
yep
so
I'm
working
on
a
new
extension?
That's
an
Amazon
channels,
integration.
What
our
extension
will
do
is
it
will
allow
merchants
to
publish
their
Magento
catalog
products
into
Amazon
and
also
pull
their
Amazon
listings
into
Magento,
and
they
can
use
Magento
as
a
single
platform
for
all
their
product
administration.
D
Import
orders
fulfill
orders,
so
it
has
a
lot
of
features
and
along
with
Amazon,
we
are
also
for
now
it's
it's.
It's
a
Google
Ads
channel
integration,
which
allows
merchants
to
publish
ads
on
Google
in
future,
we'll
have
more
integration
like
Walmart,
eBay
and
Google
shopping
actions,
Facebook
ads.
So
for
that
we
would
like
msi
to
have
export
feature
like
in
within
the
Amazon
integration.
D
What
we
have
is
a
rule
that
says
if
the
customer
has,
if
the
merchants
have
of
wants
to
manage
their
own
stock,
then
because
within
Amazon
for
listing
to
become
active,
they
need
a
quantity
on
product.
So
what
they
can
do
is
set
a
default
quantity
on
when
they
integrate
to
Amazon,
so
that
will
be
the
quantity
that
will
be
used
for
all
the
products
which
says
I
want
to
manage.
D
My
own
stock
for
this,
for
that,
if,
within
an
aside,
we
had
an
export
or
to
an
index
table
where
I
can
say,
this
is
my
stock
ID,
and
this
is
the
default
quantity
that
I'd
like
to
use
on
all
the
products
which
is
set
to
manage
stock
on
their
own.
Please
use
this
quantity.
It
will
be
a
great
feature.
D
E
A
Actually
like
because
we
never,
we
now
consider
it
before
MSI
or
magenta,
plus
MSI
as
kind
of
Europe
East
system,
because,
for
example,
we
have
the
enterprise
solution
provided
by
Magento
order
management,
but
magenta
order
management
makes
that
spoke,
aggregation
and
provide
this
aggregated
data
into
into
magenta,
so
that
magenta
still
behaves
as
a
single
stop
system.
But
now
we
like,
with
this
kind
of
integration
which
Priya
just
just
mentioned
like
if
you
want
to
make
an
integration,
it's
Amazon,
eBay,
Google,
Shopping
or
whatever.
So
we
will
magenta
will
behave
exactly
like
an
European.
A
A
We
need
to
introduce
additional
service
I
believe
that
this
server
is
going
to
delegate
it
in
all
module
like
inventories,
stock,
export
module
or
inventory
expert
stock
module,
and
probably
it's
going
to
be
two
modules,
because
we
will
have
the
API
module
and
we
would
have
the
implementation
module
and
in
the
API
module
would
have
probably
the
only
service
and
this
service
gonna
be
called
like
expert
stock
data.
Something
like
that
and
probably
it's
supposed
to
be.
Capitalized
I
just
made
a
typo
and
the
the
main
idea
we
want
to
preserve.
Here.
A
We
want
to
accept
that
search
criteria.
This
is
pretty
typical,
because
I
expect
that
we
will
have
currently
like
with
the
initial
step
that
we
will
send
the
full
stock
to
the
external,
my
marketplace,
but
probably
our
desire
both
desirable
states
that
after
some
time
we
would
be,
we
would
be
updating
external
market
place
with
just
delta
of
updated
data,
so
no
need
to
send
the
who
talked
at
the
every
synchronization
and
also
as
pre
mentioned.
A
We
want
like,
because
some
of
the
marketplaces
don't
support
the
manage
stock
0
product
which
we
have
magenta,
so
that
the
quantity
supposed
to
be
provided
for
all
products
so
now,
for
example,
to
work
in
to
work
with
Amazon.
We
want
to
specify
like
predefined
quantity,
let's
say
100
for
all
the
product
where
his
manage
stock
zero
is
specified.
So
may
I
just
put
this
graph
of
the
service
here.
A
Maybe
it
would
be
slightly
slightly
changed
because
I
still
don't
know
whether
it
makes
sense
to
return
the
result
interface,
because
potentially
this
service
would
be
used
by
big
merchants
who
have
like
maybe
100,000,
maybe
millions
SQ
in
their
their
catalog,
so
that
if
we
will
return
the
1
million
1
million
object
of
the
result
interface,
it
could
be
little
bit
harmful
for
our
memory
terms.
That
may
be
in
maybe
just
a
plain
error
could
be
used
here.
A
A
E
E
What
we're
at
right
now.
So
this
is
ongoing.
These
are
figures
from
yesterday,
so
you
can
see.
We've
run
through
as
a
yesterday
275
as
of
this
morning,
a
little
over
300,
so
those
are
progressing
somewhere
between
25
and
40
a
day,
and
we
expect
to
be
we're
about
halfway
through
the
602
test
cases
and
we
expect
to
be
finished
up,
probably
at
this
pace
within
about
a
week
week
and
a
half
and
then
we'll
have
a
full
regression
for
one
one
Oh
covered.
There
have
been
a
few
failures,
which
is
great.
E
We
can
save
a
total
of
seven
failures,
all
within
catalog,
currently
of
a
couple
of
blocks
and
a
couple
of
skip,
so
those
of
you
resolved
before
we
finish
up.
So
this
is
how
we're
proceeding
through
this
and
any
bugs
that
were
fine.
Have
been
logged,
but
all
together
and
pretty
positive
results
on
this,
with
a
good
confidence
in
one
one
out
moving
on
from
that
automated
testing.
Currently,
our
coverage
sits
primarily
in
our
s.
Zeros
we've
been
working,
a
little
on
getting
coverage
of
SEO
is
complete
and
moving
into
ass
once
moving
on
components.
E
This
is
essentially
quite
a
lot
of
the
catalog
and
we're
trying
to
catch
the
seals
numbers
up
to
match
the
one
one
o
scope,
that's
based
on
our
zeros,
that's
142
total.
What
we're
currently
running
in
these
seas
that
date
hasn't
updated,
that
is,
from
yesterday
we're
131,
past
and
12
skip,
and
we
have
some
pending
PRS
to
unskipable
I
on
some
of
the
core
functionality
and
that
DB
backup
actually
affects
the
way
MSI
automated
test
run
as
well.
E
E
We
do
have
a
focus
on
MSI
for
that,
in
terms
of
automation
and
as
a
basis
of
sort
of
looking
at
how
to
run
an
extension
and
test
them
so
we're
hoping
to
get
some
better
numbers
out
of
that
get
some
more
contributors
and
then
the
next
two
weeks
bring
up
that
automation
number.
So
it's
in
a
much
better
place
for
next
msi
release,
but
currently
the
tests
are
running
there,
passings
or
happy
with
that,
and
our
manual
regression
is
going
well
as
well.
So
any
questions.
Otherwise,
that's
quality.
Fluid.