There is no empty text in the data. Indeed each text column is a fixed-size string.
Cheers, Bailu ________________________________ From: [email protected] [[email protected]] on behalf of Enns, Steven [[email protected]] Sent: Wednesday, May 29, 2013 1:59 PM To: FastBit Users Subject: Re: [FastBit-users] incorrect query results using JNI for text columns We may have seen something similar where rows with empty values for text columns were omitted. Did you try replacing any empty text values with 'NULL'? From: Bailu Ding <[email protected]<mailto:[email protected]>> Reply-To: FastBit Users <[email protected]<mailto:[email protected]>> Date: Wednesday, May 29, 2013 1:56 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [FastBit-users] incorrect query results using JNI for text columns Hi, After I load the data and issue queries to FastBit.build_query(), I often get a warning like the following: Warning -- text[test.col1]::stringSearchdata file "/path/to/file/folder/test/col1" contains 18721 strings, but expected 18722 When I load the data into FastBit with FastBitStringWriter.addText(), the number of columns is 18722. The metadata of the column in -part.txt also says 18722. I double-check the result from what is returned from MySQL, the result is incorrect when I have this kind of warnings. There is no index built on the text column, the query is equality, i.e. where col1 = some_text_string. Have anyone ever had this problem before? Cheers, Bailu
_______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
