-
Notifications
You must be signed in to change notification settings - Fork 230
problems on import(roaring) #36
Comments
i'm wondering if the roaring implementation needs to replace the 16bit containers with 32 bit containers. The idea behind those containers is to have half the bits for low and half for high. So the container should be 32 bits instead of 64 bits. Thought? |
I pushed up a PR to actually return the error message: 🤦 Can you rerun the import and send the error?
i'm wondering if the roaring implementation needs to replace the 16bit containers with 32 bit containers. The idea behind those containers is to have half the bits for low and half for high. So the container should be 32 bits instead of 64 bits.Thought?— |
You right on the inefficiency. Looking at the roaring code it seems to chop up the 32 bit number into 16bit parts..a high and a low. Perhaps we split up into 4 16 bit chunks. HighHigh, HighLow, LowHigh, LowLow and do the search. Never needing the 64 bit ops..ie search64. And I would search in this order(for it would be just the same performance as roaring for values< 2^32 How does that grab you? Here is the error... The error is in importing the attached file above in slice 59, i'm trying to get it narrowed down better than that, but I haven't found the culprit. Below is the profile ids of the failed "import" |
It seems like it would add a lot of complexity by adding 4 levels instead of just 2. Unless we had a lot of containers it doesn't seem like it would help much. |
…keys Add column keys support to IncludeColumn
Something not right on the roaring bitmap. I've got it narrowed down to the WriteTo method of the array.
The error reported is
2016/01/08 10:09:30 import error: db=3, frame=b.n, slice=59, bits=5434
I'm thinking there might be an overflow somewhere, but i can't find it.
1237.txt
The text was updated successfully, but these errors were encountered: