Skip to content
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 dynamic fastfield codes for multivalues fixes #1093 #1097

Merged
merged 7 commits into from
Jun 30, 2021

Conversation

PSeitz
Copy link
Contributor

@PSeitz PSeitz commented Jun 23, 2021

Use dynamic fastfield codes for multivalues fixes (only sorting case covered)
Rename get to get_val due to conflict with Vec
use u64 precision instead of u32 for get_range, to allow use of existing fast field interface interface (actually not sure if it would be better have a different interface)

@PSeitz PSeitz requested a review from fulmicoton June 23, 2021 18:01
src/indexer/merger.rs Outdated Show resolved Hide resolved
Copy link
Collaborator

@fulmicoton fulmicoton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except one comment

fn get(&self, doc: u32) -> u64 {
self[doc as usize]
fn get_val(&self, position: u64) -> u64 {
self[position as usize]
}
}

impl<'a> FastFieldDataAccess for &'a Vec<u64> {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect this one is useless...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because &[u64] exists? type deduction doesn't work in some case properly

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's remove it...

src/indexer/merger.rs Outdated Show resolved Hide resolved
PSeitz added 5 commits June 30, 2021 08:57
Use dynamic fastfield codes for multivalues fixes (only sorting case covered)
Rename get to get_val due to conflict with Vec
use u64 precision instead of u32 for get_range, to allow use of existing fast field interface interface (actually not sure if it would be better have a different interface)
add dynamic fastfield for single fast field unsorted
fix scary documentation bug
add num_len instead of len
make docid mapping non optional
add trivial flag for docid mapping
add time measurements
@PSeitz PSeitz marked this pull request as ready for review June 30, 2021 07:16
Cargo.toml Outdated
@@ -53,6 +53,7 @@ rayon = "1.5"
lru = "0.6.5"
fastdivide = "0.3"
itertools = "0.10.0"
measure_time = "0.6.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is unused.

src/lib.rs Outdated Show resolved Hide resolved
@PSeitz PSeitz merged commit aea2e77 into quickwit-oss:main Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants