-
Notifications
You must be signed in to change notification settings - Fork 33
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
Initial Vortex Layouts #1805
Initial Vortex Layouts #1805
Conversation
#[derive(Debug, Clone, Copy, PartialEq, Eq, PartialOrd, Ord)] | ||
pub struct SegmentId(u32); | ||
|
||
impl From<u32> for SegmentId { |
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.
For the curiosity of someone unfamiliar with the Vortex code base...how is a Segment
defined? What is the relationship between a segment and a chunk?
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.
You can think of a segment as some abstract buffer of bytes that can be stored anywhere.
Where ArrayData holds buffers, LayoutData holds segment IDs which can later be resolved to segments.
Hmmm... maybe I should just stick with the name "buffer"
self.state = State::Reading(Reading { | ||
chunk_idx, | ||
chunk_layout, | ||
statistics: None, | ||
}); |
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.
I think you want to support out of order reads, if one chunk is very big but you know you have to read the next chunk you don't have to block reading chunk + 1 on previous chunk
Initial implementation of the new structure of vortex layouts per #1676
Up next:
Open Questions: