Thanks, is it a problem if fastbit_build_index(indexLocation, cname, NULL) doesn't update -part.txt for min/max either ?
Thanks, -----Original Message----- From: K. John Wu [mailto:[email protected]] Sent: Tuesday, February 14, 2012 12:58 PM To: Dominique Prunier Cc: FastBit Users Subject: Re: [FastBit-users] Min/max in -part.txt Hi, Dominique, Thanks for the follow up. The function fastbit_built_index was not updating the metadata file -part.txt. Just changed the function update the file -part.txt if the incoming argument indexOptions is not an empty string or a nil pointer. Previously, only the function fastbit_build_indexes updates -part.txt. The new change makes the two function behave more consistently. This change is in the SVN revision 473. John On 2/13/12 1:29 PM, Dominique Prunier wrote: > Hey John, > > About the min/max, it seems that the metadata doesn't get rewritten > in r472 (and the description is not updated). I'm not sure it is a > real problem but just to let you know. I'm using the C API function > fastbit_build_index(indexLocation, cname, indexOptions). > > Thanks, > _______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
