You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have described the situation in which the bug arose, including what code was executed, information about my environment, and any applicable data others will need to reproduce the problem.
I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a description of what I expected instead.
If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.
Processing queries across base and nested columns is not possible in NestedFrame.query today, so expressions of this kind are detected and prohibited. However, it does not presently prohibit queries that go across two different nests:
nf.query("n1.c < 0.5 and n2.d > 1e-7")
The above will "work", but only selects the nested rows in n1, simply because n1 is earlier in the string.
The solution is to treat such cross-nest queries exactly the same as queries that cross base and nested columns: error out today, and as split queries, in the future.
The text was updated successfully, but these errors were encountered:
Bug report
Before submitting
Please check the following:
Processing queries across base and nested columns is not possible in
NestedFrame.query
today, so expressions of this kind are detected and prohibited. However, it does not presently prohibit queries that go across two different nests:The above will "work", but only selects the nested rows in
n1
, simply becausen1
is earlier in the string.The solution is to treat such cross-nest queries exactly the same as queries that cross base and nested columns: error out today, and as split queries, in the future.
The text was updated successfully, but these errors were encountered: