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

fields cannot be reset/emptied in index #88

Closed
benwalch opened this issue Jul 3, 2024 · 1 comment
Closed

fields cannot be reset/emptied in index #88

benwalch opened this issue Jul 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@benwalch
Copy link
Member

benwalch commented Jul 3, 2024

Q A
Branch master, 2.x
Bug report? yes/no
Feature request? yes/no
BC Break report? yes/no
RFC? yes/no

This issue addresses exactly the same case like in #81, but for all types of optional data, where empty means null.
Pimcore returns null for non-required fields. The current implementation leads to data inconsistency between backend and index.

Scenario

Consider having indexed a pimcore data object, with an optional field which has a value.
Now in pimcore backend, the field is emptied / cleared.
With the current implementation, it is impossible that this change will be comitted to the index out of the box (Object getter extractor).
The data in the index won't clear, because of the above issue.

@solverat solverat added the enhancement New feature or request label Nov 14, 2024
@benwalch
Copy link
Member Author

benwalch commented Dec 9, 2024

closed with #95

@benwalch benwalch closed this as completed Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants