Hi,
I'm evaluating the impact of reordering a partition before indexing it. A file sharing violation occurs on Windows in the call to ibis::part::reorder(). The file sharing violation occurs because the data file has been opened as a memory mapped file with read-only sharing access in the call to ibis::column:actualMinMax and the method ibis::part::reorderValues attempts to open that same file with write access using a call to UnixOpen() It looks like adding a call to ibis::fileManager::instance().flushFile(...) before returning from ibis::column::actualMinMax fixes the issue, but I'm not sure that it does not impact performance in order code path. Thanks, -Joel
_______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
