If the bitset is something you control you can use the binary
field type, although it's not a horribly efficient way to store binary
data.
If the bitset is bounded, you could do something with indexing
N long values that will contain the set and write a custom
similarity class to work with it.
Be
Oh fine. Caution point was useful for me.
Yes I wanted to do something similar to filer queries. It is not XY
problem. I am simply trying to implement something as described below.
I have a [non-clinical] group sets in system and I want to build bitset
based on the documents belonging to that gro
Why are you saving this? Because if the bitset you're saving
has anything to do with, say, filter queries, it's probably useless.
The internal bitsets are often based on the internal Lucene doc ID,
which will change when segment merges happen, thus the caution.
Otherwise, theres the binary type y
