►
From YouTube: Magento Bulk API Community Meeting, 20 Jun 2018
Description
Walk through open pull requests by @nuzil:
- backport of Bulk and Async APIs to Magento 2.2. Having that Mganeto 2.2 has queues support in EE only, it will be released as an EE extension
- New feature: new API to search for bulk requests history by status and timestamp
- New feature: support of overriding on the bulk API endpoints
- bugfix: support of the topic schema declaration as a method signature
A
B
A
B
A
B
Generally,
we
have
rejoin
expect
to
have
synchronous
operations
and
bulk
of
API
in
2.2
version,
so
we
had
to
pull
request.
One
is:
was
the
basic
implementation
not
related
through
to
a
sink
or
bulk?
It
was
only
changing
the
Web
API
extension
to
have
inject
pelagic,
so
we
can
use
the
configuration
file
for
that
to
define
new
processors
and
that
will
journalists
I
understand
correctly.
C
A
B
B
A
Interface,
yep,
and
here
is
the
reason
why
this
political
to
pull
requests
because
the
into
the
twist
to
have
message,
queue
and
asynchronous
operations
modules
in
Enterprise
Edition.
So
that's
why
you
can
mean
in
to
the
to
a
single
I
synchronous,
a
title
there
will
be
just
in
Enterprise
Edition
in
the
correct
output
to.
B
B
B
A
Is
a
bog
of
previous
implementation
we're
in
magenta?
It
is
a
way
to
define
the
schema
based
on
the
method,
signature,
but
way
there
are
two
ways
to
define
the
interface
or
topic
based
on
the
data,
object
and
second
ways
to
define
based
on
the
message
signature.
So
my
support
definition
of
the
schema
as
data
object
was
supported.
So
our
definition
is
method.
Signature
was
not
supported,
just
two
different
passes
how
to
serialize
objects
and
yeah.
This
request
fixes
this
year
couple
common
soldiers
and.
B
A
B
A
Yes,
as
far
as
the
remembers,
the
main
problem
was
if
we
use
a
back
end
user.
So
there
are
different
types
of
users,
admin,
user,
integration,
user
and
front
right,
and
we
want
to
do
any
math
operation
bulk
operation
in
context
of
certain
user.
But
right
now
there
was
a
foreign
key
and
one
specific
table
and
had
been
user.
So
it
was
just
admin
who
was
able
to
execute
operation.
Otherwise
the
user
will
not
be
located.
So
we
removed
that
foreign
key.
But
now
there
is
discussion.
B
B
B
And
the
last
one
I
guess
no
way
it
was
smells
by
a
custom
road
for
Barca
periods.
We
can
define
that
from
bulk
API
when
we
replaces
those
URLs
for
food
requests
with
where
we
get
the
parameters.
We
have
not
two
dots
here
by
and
then
a
variable
name
and
for
future
that
we
created
an
implementation
that
we
can
define
custom
roles
for
the
all
those
URLs
or
if
you
make
an
escape
limitation,
you
can
also
have
some
more
nice
URLs.
Your
requests
about
implementation
and
yeah
just
go
through
it's
like
you.
A
Yeah
we
had
good
discussion
so
before
pile
created
in
the
file
which
allowed
to
define
your
outs,
but
then
we
agreed
that
probably
it
will
be
better
to
reuse
existing
asynchronous
web,
it
guy
it
smell.
It
already
have
a
definition
of
the
API
switch.
You
don't
want
to
make
a
synchronous,
as
it
was
implemented
last
spring.
A
cost
milestone
in
this
milestone.
We
extended
file,
as
this
customer
owes
definition
of
about
it,
guys
so
I
think
it
works
better
together,
yep,
alright.