►
Description
Our prolific contributor Alexander Lyzun is presenting his brainchild - the Async Import Service project. Check it out to learn how to get involved and contribute.
https://github.com/magento/async-import
A
A
No,
it's
official,
oh
no.
Everybody
will
see
that
okay,
so
welcome
everybody.
Basically,
that's
a
guest
elekid,
it's
not
the
biggest
meeting
weekly
we
had
for
the
this
project,
but
it's
because
for
this
year
oh
I
see
at
least
nine
eight.
Eight
people
here
welcome
everybody
who
is
also
a
new.
So
idea
was
today
that
different
guys
asked
me
about
the
project
itself.
What's
new
is
coming
and
what
is
our
plan
and
what
is
a
project
about?
A
So
basically,
what
I
wanted
to
do
today
is
to
present
the
project
one
more
time,
just
to
give
some
overview
about
what
we
are
doing,
what
we
are
planning
to
do,
what
is
the
progress
and
how
you
can
join
us
and
we
have
one
more
people.
This
coming
person
is
coming
yep,
so
yeah
I'll
start
basically
I'll
share.
My
screen
I'll
give
you.
A
A
We
have
two
phases
of
the
project:
one
is
the
bulk
API
improvements,
the
project
that
was
done
last
year,
which
has
multiple
tasks
for
for
improving
the
I
think
in
bulk
appear
in
general.
Some
of
them
are
also
required
or
like
nice,
to
have
MSI
project
related,
for
example,
to
switch
the
default
execution
to
database
that
you
don't
need
a
queuing
system,
that's
basically
the
biggest
one.
A
So
we
here
here
in
architectural
repository,
we
have
the
document
the
design
document
for
this
project.
So
what
is
the
general
idea?
The
general
idea
that
we
have-
or
we
plan
to
have
the
independent
service
like
module
of
horizontal,
that
can
be
installed
separately
from
magenta
monoliths
or
from
the
main
system,
and
it
will
communicate
with
Magento's
through
API,
and
it
will
provide
the
functionality
that
in
future
will
replace
the
default
magenta
import.
So
in
a
version
number
one,
we
are
planning
basically
to
have
the
best
functionality
of
magenta
import.
A
B
A
B
A
Good
so
yeah,
so
the
workflow
will
be
follow
so
the
first
customer
or
not
customer
customer
admin,
no
matter
will
upload
the
source
file.
He
will
do
it
also
with
API.
So
on
a
face
number
one
which
is
described
which
is
described
here.
He
will
send
the
post
request
with
his
data
to
the
source,
upload
endpoint
and
we
have
three
times
three
types
of
uploaded
source
currently
planned.
Is
that
you
use
in
the
local
paths
for
your
file.
A
I
know
it's
visible,
make
it
a
bit
bigger,
then
you
can
use
the
remote
URL
or
you
can
do
it
in
base64,
which
is
quite
popular
now
way,
magenta
to
upload
data.
Also,
there
is
a
way.
So
there
is
a
special
case,
because
the
input
data
can
be
quite
big
and
we
megabytes
hundreds
of
megabytes
and
one
base64
may
be
which
to
be
so.
They
will
be
presented.
A
So
in
this
way
that's
kind
of
similar
to
Magento
standard
import.
When
you
first
upload
the
file,
you
click
the
validate
button.
It's
uploading
the
file
on
a
Magento
folder
on
Magento,
installation,
folder,
I.
Guess
it's
a
new
bar
import
and
then
validate
it
and
deliver
you
an
errors.
If
they
existed
and
then
you
can
start
an
import.
So
this
start
an
import
is
step
number
two,
that's!
Basically,
when
you
start
import
by
by
your
source,
ID
or
UID,
and
with
the
start
import.
A
Also,
the
bit
bigger
you
have
here
the
data
which
can
be
transferred
so
kind
of
you
configure
in
an
import.
It's
currently
replicating.
They
also
default
emergent
import
functionality
with
one
more
modification
which
is:
let's
go
down,
so
you
hear
history,
we
have
a
start
import.
We
have
here
the
profiles,
so
we
will
provide
insight
functionality
like
a
profile.
A
So
first
idea
of
the
of
this
extension
when
we
will
finish
the
development
like
on
a
face
number
one
that
we
always
can
accept
the
file.
That
is,
we
file
in
a
format
that
Magento
accepts
currently
so
the
standard
Magento
import
file,
but
in
our
own
experience
and
experience
of
other
developers,
I
can
tell
that
the
files
are
always
different
and
you
always
have
to
do
this
work
with
transferring
your
own
formats
to
the
format
of
Magento
import.
A
So
what
you
provided
you
provide
in
the
profile
when
you
can,
where
you
can
configure
in
the
mapping
between
your
file
and
Magento
system,
so
you
can
basically,
then
ruies
reusing
this
profile
or
import
your
file
again
and
again,
with
your
own
format.
Ya
know.
So
if
you
can
see
here
before,
we
have
currently
here
the
SV
source
type
supported,
but
it's
in
the
future
can
be
basically
any
format
which
contains
the
data
inside
also,
by
the
way,
those
import
processors.
A
We
already
made
a
base
implementation,
so
any
new
one
can
be
added
by
developers
if
they
want
to
just
with
xml
configuration
and
then
they
will
process
the
file
itself.
So
yeah
with
the
same
point,
we
start
in
our
import,
which
is
basically
then
parse
your
file
and
we'll
send
the
objects
to
Magento
by
using
a
sync
bulk
API.
We
didn't
came
to
this
implementation.
Yet
so
I
guess
bark
is
more
useful
here
and
these
points
and
then
basically
we
planted
those
operation
will
be
a
synchronous.
A
So
we
don't
need
to
wait
a
while
it
will
process
your
ten
thousands
of
lines
in
your
file.
So
basically
you
then
can
request
the
status
of
this
file
import,
and
you
will
see
the
information
about
this
file.
Then
you
will
see
the
items
list
in
this
items.
Loop,
that's
your
kind
of
line
and
you
will
have
the
day
which
is
coming
in
coming
out.
So
the
outputs
of
Magento
what
was
sent
to
Monsanto
you
can
also
do
by
it.
That's
phase
number
one
of
the
project
in
a
phase
number
two.
A
It's
basically
can
be
done
almost
separately,
because
it's
only
providing
the
UI
quite
shot,
which
you
didn't
discuss
it
it
to
tell
so
basically
just
a
UI
for
Magento,
so
kind
of
separate
model
where
you
can
start
the
import
without
API,
no
knowledge.
So
if
you
are
end
user,
basically
we
can
just
start
an
import
yeah
from
UI,
and
then
we
have
phase
number
three,
which
is
basically
describing
and
implementing
this
profile
pictures.
A
So
here
we
have
a
profile,
so
we
can
basically
have
an
end
points
for
creating
new
profile
for
edit
and
delete
the
profiles.
And
here
you
can
define
the
mapping
for
fields.
Let's
say
between
your
file
and
Magento.
You
can
define
some
custom
processing
rules,
even
though,
basically
quite
flexible.
This
part
is
only
like
a
prototype
because
we
didn't
come
to
this
implementation.
Yet
because
it's
kind
of
yeah
number,
three
and
one
more
feature
is
repeatable.
Repeatable
calls.
A
So,
basically,
when
you
start
an
import
you,
then
you
request
the
status
of
you
import
and
then
you
see,
let's
say
you
had
100
items
and
you
have
that's
almost
servicing
is
fine,
but
item
number
10,
20
25
has
failed
by
some
reason.
I
know,
image
is
missing.
Some
attributes
some
required
attribute
is
missing.
So
what
you
want
to
do
with
it?
You
basically
just
can
restart
this
transaction
and
you
can
restart
it
by
you,
knowing
the
operation
ID
and
your
priority,
which
move
here
base
number
one
where
we
have
those
statuses.
A
Basically,
we
have
here
operation
AG,
which
is
basically
you
are
UID.
Okay,
sorry
for
that.
We
deliver
this
changes
only
like
beginning
this
here
a
couple
of
weeks
ago
when
we
decided
to
use
UID
everywhere
and
the
gas
phase
number
three
is
to
using
the
old
names,
but
basically
yeah,
that's
our
source
ID
and
that's
our
operation,
which
is
item
and
then
idea
of
this
item.
And
then
you
just
transfer
your
serialize
data,
which
you
basically
have
also
here.
A
That's
the
data
that
module
created
like
a
body
for
the
endpoint
to
the
sender,
to
magenta,
and
you
can
basically
change
it
and
repeat
this
call.
If
you
want
in
this
way,
yeah
you
don't
need
to
restart
the
whole
input.
You
can
just
point,
Li
repeat
the
calls
which
we
have
failed
yep.
That's
currently
about
idea.
A
A
A
So
for
the
guys
who
want
to
contribute
and
start
to
do
something
just
to
make
it
easier,
we
import.
So
we
have
this
module
here,
sprite,
you
want
an
import
service
and
it
basically
have
only
the
the
interfaces,
some
responses
models,
yeah.
So
quite
quite
simple:
nothing
currently
there
special
and
on
top
of
it
we
have
the
well.
We
have
to
pull
request.
A
One
is
remote
file,
upload
processor,
which
is
basically
in
radio
which
was
delivered
by
guy
named
mariana
like
week
ago,
and
we
now
in
some
review,
face
about
the
architecture
and
the
code
review,
and
we
have
one
more
full
request,
which
was
delivered
not
much
central
repository.
It
was
done
in
our
fork,
which
was
from
DEP
informant,
which
its
implementation
of
local
Pascal
processor.
So
when
you
can
upload
the
file
located
on
your
local
file
system,
so
basically
Stefan
promised
to
convert
it
to
the
Magento
repository
cuz.
A
He
developed
it
before
we
deliver
it
the
base
extension,
so
the
interface
is
very
changed,
but
it's
not
not
so
bad
I
hope
to
it
next
days
yeah.
So
our
status
basically
is
quite.
We
are
on
a
start.
I
would
stay.
We
have
here
an
ecologist
Alex
Vasily,
who
is
working
currently
on
on
basically
than
import,
so
the
functionality
that
will
yep
yeah
correct
the
functionality
that
will
parse
the
file
and
will
send
it
to
much
enter
via
the
API.
A
This
task
also
kind
of
in
progress
yeah,
and
we
have
quite
rich
backlog
here,
which
covered
the
phase
number
one,
also
not
fully
so.
In
any
case,
we
are
open
for
new
people
if
you're
interested
to
start
with
something
it
should
not
be
the
source
upload.
If
you
want
to
start
with
profile
or
with
you,
do
I
join
our
meetings.
Yeah
then
shortly
about
the
project,
because
that
was
all
from
my
side.
Any
questions.
C
D
C
A
Good
then,
no
other
questions
on
now
good.
Then
we
have
yeah.
Then
we
will
proceed
with
our
weakest
link.
I'll
be
having
a
call
today,
Patrick,
who
basically
delivered
the
poor
request
that
allows
the
lead
operation
from
synchronous,
about
API
particular
welcome
to
present
your
poor
request
and
how
it
works.
C
B
Yeah,
so
what
happens
when
you
send
a
delete
request
to
the
asynchronous
API
it
gets
processed
by
the
by
a
consumer
when
the
consumer
runs
it
defaults
to
the
global
area,
so
there's
a
remove
action
validator.
Basically,
that
determines
whether
or
not
that
is
the
removal
or
the
deletion
will
be
allowed
and
in
the
global
area.
It's
not
so
I
would
create
a
failure
where
anytime,
you
were
trying
to
send
the
delete
operation
to
the
asynchronous
API
for
things
like
products,
for
example,
those
requests
would
fail
and
they
would
do
so
relatively
silently.
B
B
B
Haven't
done
so
I'd
really
like
to
submit
a
proposal
in
the
architecture
repo
to
potentially
either
change
the
area
code
that
the
consumers
are
ran
in
by
default
or
create
a
separate
area
for
the
consumers
to
be
able
to
set
the
remove
action.
The
right
way
there
in
a
similar
fashion
to
what's
done
in
the
rest.
Api
is
and
had
been
HTML,
but
to
keep
backwards,
compatibility
and
2.3.
A
Anybody
yep,
in
any
case,
if
you
have
a
proposal,
you
can
post
it
that
quite
interesting
topic
towards.
Basically
the
the
registers
was
deprecated
in
2.3
and
we
have
still
I
guess
a
lot
of
places
in
a
core
that
have
to
be
replaced.
It
cosmic
history
registry
is
still
using
there
yeah,
but
in
any
case
we
have
a
proposal
related
to
the
consumer
wards
and
so
on.
Just
feel
free,
yeah,
that's
I!