This seems to me to be A Bad Thing. Zero is different from not existing. And let's claim that I want to process a stream and, say, facet on in integer field over the result set. There's no way on the client side to distinguish between a document that has a zero in the field and one that didn't have the field in the first place so I'll over-count the zero bucket.
So before I raise a JIRA, my question is whether this is expected behavior or not? I've found a mechanism that _shouldn't_ be very expensive to omit the field if it doesn't exist in the returned tuples. Now, how badly this would break Streaming Expressions, ParallelSQL and the like I haven't looked into yet. So before I work up a trial patch am I going off in the weeds? Best, Erick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
