Skip to content
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

_kuzzle_info.updatedAt and .updater are still null after a mUpdate() operation #2532

Open
psam44 opened this issue May 21, 2024 · 1 comment
Labels

Comments

@psam44
Copy link

psam44 commented May 21, 2024

The single update() operation is not affected because its code is different.

The bug is at /lib/service/storage/elasticsearch.ts#L3120, _processExtract():

    _source: Object.assign({}, metadata, document.body),

The metadata content is correct, but assign() states that "Later sources' properties overwrite earlier ones.",
and document.body has already these properties, with null values.
I got the expected behaviour with this hack in the distributed js:

            _source: Object.assign({}, document.body, metadata),

I didn't investigate on the two other assign() usages in this file, but they probably have a similar defect.

Context (Environment)

Kuzzle version: master
Node.js version:
SDK version:

@psam44 psam44 added the bug label May 21, 2024
@rolljee
Copy link
Contributor

rolljee commented May 21, 2024

Thank you for reporting this issue, we will have a look into into it.

If you have the time to do it PRs are welcomed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants