Skip to content

Empty objects are not stored #471

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

Closed
0x64746b opened this issue Oct 10, 2016 · 2 comments
Closed

Empty objects are not stored #471

0x64746b opened this issue Oct 10, 2016 · 2 comments

Comments

@0x64746b
Copy link

While it's possible to store empty objects through the API (cf elastic/elasticsearch#4047) and the low level client, it's not possible through the DocType wrapper.

In addition, empty objects (e.g. stored through the low level client) are removed when updating the doc through its DSL wrapper.

If it's not possible to initialize objects, scripts have to check for the existence of such an object before each access, since it might be still null.

@honzakral
Copy link
Contributor

This is a duplicate of #460, let us discuss all the issues around not storing empty fields there. Thank you!

@0x64746b
Copy link
Author

Sure, just didn't wanna hijack that issue, since it's related to retrieval/serialization, not storing.

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

No branches or pull requests

2 participants