<h3><u>#general</u></h3><br><strong>@mailtobuchi: </strong>Hey everyone, if I include some unknown (not existing in the table) columns in the selections or groupBy's of a Pinot query, what's the expected behavior? Should the query error out or silently give empty results?<br><strong>@steotia: </strong>It will fail on the server<br><strong>@steotia: </strong>or may be the DataSchemaSegmentPruner will prune all the segments and will return empty results<br><strong>@mailtobuchi: </strong>I was expecting the query to fail saying unknown or non-existing columns.<br><strong>@mayanks: </strong>Curious, why would you include non-existing columns in the query?<br><strong>@mayanks: </strong>Seems like we might be getting empty results<br><strong>@mailtobuchi: </strong>It wasn't intentional @mayanks There is a code bug, because of which some wrong selections were given in the query. Because Pinot wasn't erroring out, it was a bit difficult to understand what's going on so I asked.<br><strong>@diego.aguilar: </strong>@diego.aguilar has joined the channel<br><h3><u>#random</u></h3><br><strong>@diego.aguilar: </strong>@diego.aguilar has joined the channel<br>
