-
Notifications
You must be signed in to change notification settings - Fork 185
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Context-free "filtered" keyword semantics (#1513)
Currently, both the Tile::filtered_ and the query context (e.g. in the read or write path) are required to determine if the Tile::buffer_ contains the on-disk format. For example: when 'filtered_' is true in the write path, 'buffer_' contains the on-disk format. When 'filtered_' is true in the read path, 'buffer_' does not contain the on-disk format. This patch changes the semantics of the "filtered" to mean "filtered, on-disk formatted" and "unfiltered" to mean "reverse-filtered, in-memory formatted". This may be a useful cleanup, but the motiviation for this patch is to prepare for the vectorized tile buffer patch: 'void* Tile::buffer_' will be removed in favor of 'ChunkedBuffer* Tile::chunked_buffer_' and 'void* Tile::filtered_buffer_'. The 'chunked_buffer_' contains the "reverse-filtered, in-memory formatted" data. The 'filtered_buffer_' contains the "filtered, on-disk formatted" data. With the new semantics of the "filtered" keyword, 'bool Tile::filtered_' becomes unneccessary because "bool Tile::filtered()" can be implemented by determing which of the two buffers ('chunked_buffer_' or 'filtered_buffer_') are non-empty. In other words: the state of Tile will become more complex to support two separate buffers. This patch is a pre-requisite to reducing some of that state by allowing us to eliminate "bool Tile::filtered_".
- Loading branch information
joe maley
authored
Feb 20, 2020
1 parent
6d6dce5
commit 8f09548
Showing
9 changed files
with
89 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.