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.

Sign up for GitHub

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

Jump to bottom

change back index entries to just contain list of keys #2

Closed
mschoch opened this issue Jul 7, 2014 · 2 comments
Closed

change back index entries to just contain list of keys #2

mschoch opened this issue Jul 7, 2014 · 2 comments
Labels
enhancement index

Comments

@mschoch
Copy link
Member

mschoch commented Jul 7, 2014

Currently the back index contains 2 separate lists of more strongly typed data. This should be changes to just a flat list of keys. This will make it easier to introduce new index row types in the future without having to keep updating the way the back index works.
@mschoch
Copy link
Member Author

mschoch commented Aug 3, 2014

the counter-argument to this is that information like docID occurs in many of the keys and this information would be repeated unnecessarily

still undecided for now

@mschoch
Copy link
Member Author

mschoch commented Aug 11, 2014

closing this for now, no immediate plans to add new row types, and the current encoding is more compact

@mschoch mschoch closed this as completed Aug 11, 2014
@DustinHigginbotham DustinHigginbotham mentioned this issue May 14, 2015
Closed
steveyen added a commit to steveyen/bleve that referenced this issue Mar 23, 2018
@steveyen
scorch zap replace locsBitmap w/ 1 bit from freq-norm varint encoding
7a19e6f 
This is attempt blevesearch#2 of the optimization that replaces the locsBitmap,
without any changes from the original commit attempt.  A commit that
follows this one contains the actual fix.

See also...
- commit 621b58d (the 1st attempt)
- commit 49a4ee6 (the revert)

-------------
The original commit message body from 621b58 was...

NOTE: this is a zap file format change.

The separate "postings locations" roaring Bitmap that encoded whether
a posting has locations info is now replaced by the least significant
bit in the freq varint encoded in the freq-norm chunkedIntCoder.

encode/decodeFreqHasLocs() are added as helper functions.
steveyen pushed a commit that referenced this issue Mar 26, 2018
Merge pull request #857 from steveyen/replace-locsBitmap-attempt2
33b1f06 
optimization to replace locations bitmap, attempt #2
misberner added a commit to misberner/bleve that referenced this issue Aug 30, 2019
@misberner
Start analysis workers lazily (blevesearch#2)
8762239
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement index
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mschoch