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

IS_NULL should be allowed against nested message fields #136

Closed
MMcM opened this issue Nov 8, 2018 · 0 comments
Closed

IS_NULL should be allowed against nested message fields #136

MMcM opened this issue Nov 8, 2018 · 0 comments

Comments

@MMcM
Copy link
Contributor

MMcM commented Nov 8, 2018

Currently validation and evaluation fail, but this operation seems well-defined.

I do not believe that there is ever an index that can be used for this operation.

If the message has a repeated field, IS_NULL is still disallowed without fan-out, since that seems less well-defined. Also, as noted recently, an index on that repeated field would not put any entry into the index if the message were null or the repeated field were empty.

alecgrieser added a commit that referenced this issue Nov 8, 2018
Resolves #136: IS_NULL should be allowed against nested message fields
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

1 participant