-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting item processor property with lambda error #3749
Labels
Milestone
Comments
riane5
added
status: waiting-for-triage
Issues that we did not analyse yet
type: bug
labels
Jul 21, 2020
fmbenhassine
added
in: core
and removed
status: waiting-for-triage
Issues that we did not analyse yet
labels
Apr 14, 2021
fmbenhassine
added
the
for: backport-to-4.2.x
Issues that will be back-ported to the 4.2.x line
label
Apr 14, 2021
Thank you for opening this issue. This is indeed a bug in The change you are suggesting fixes the issue, so you are welcome to submit a PR if you want. |
fmbenhassine
pushed a commit
that referenced
this issue
May 11, 2021
Resolved with #3897 . |
fmbenhassine
pushed a commit
that referenced
this issue
May 11, 2021
fmbenhassine
pushed a commit
that referenced
this issue
May 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Please do a quick search on Github issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
Bug description
Setting processor property with lambda error
My code is as follows
So I found that the item processor did not work,because the
itemprocessorfunction
property ofFaulttolerantstepbuilder
isnull
,its itemProcessor property isnull
。Why is the
itemprocessorfunction
attribute not synchronized in the constructor ??????Should I add the following code to the constructor ??
this.itemprocessorfunction =parent.itemprocessorfunction
Thank you
The text was updated successfully, but these errors were encountered: