-
Notifications
You must be signed in to change notification settings - Fork 80
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
Use chunks in DynamicWhereFilter, fix a chunk leak, and cleanup some code generally #4826
Conversation
engine/table/src/main/java/io/deephaven/engine/table/impl/select/DynamicWhereFilter.java
Show resolved
Hide resolved
engine/table/src/main/java/io/deephaven/engine/table/impl/select/DynamicWhereFilter.java
Outdated
Show resolved
Hide resolved
engine/table/src/main/java/io/deephaven/engine/table/impl/select/DynamicWhereFilter.java
Show resolved
Hide resolved
final Chunk<Values> keyChunk = Chunk.downcast(tupleSource.getChunk(keyGetContext, selectionChunk)); | ||
final int thisChunkSize = keyChunk.size(); | ||
setInclusionKernel.matchValues(keyChunk, matches); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There isn't anything "special" about SetInclusionKernel
; do we always know it will be an object chunk now?
There doesn't seem to be any value in copying into matches, to then just use it later as filter. I think we can simply check against liveValues
as we iterate and build index.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I combined the single column case and the tuple case, we do not know it will always be an object chunk. Set inclusion let's us do non-boxing inclusion tests. That is, it is special.
No description provided.