dataparksearch - Project Hosting on Google Code

Today 5 hours ago r267 (Fix for mysql syntax ) committed by dp.maxime - Fix for mysql syntax Fix for mysql syntax Last 7 days Nov 18, 2009 r266 (A fix for loosing last line of text before storing into stor...) committed by dp.maxime - A fix for loosing last line of text before storing into storedoc database. A fix for loosing last line of text before storing into storedoc database. Nov 18, 2009 r265 (Add Uzbek language maps for latin and cyrillic based alphabe...) committed by dp.maxime - Add Uzbek language maps for latin and cyrillic based alphabets. Add Uzbek language maps for latin and cyrillic based alphabets. Last 30 days Nov 11, 2009 r264 (A fix for possible memory corruption. ) committed by dp.maxime - A fix for possible memory corruption. A fix for possible memory corruption. Nov 10, 2009 r263 (Add support for chuncked Transfer Encoding. ) committed by dp.maxime - Add support for chuncked Transfer Encoding. Add support for chuncked Transfer Encoding. Nov 09, 2009 issue 22 (Regex expressions in stopword file) changed by dp.maxime - It's a good idea. I'll implement the StopMatch command in next snapshot (within few days). Thanks for suggestion. Status: Started Labels: Type-Enhancement −Type-Defect It's a good idea. I'll implement the StopMatch command in next snapshot (within few days). Thanks for suggestion. Status: Started Labels: Type-Enhancement −Type-Defect Nov 09, 2009 russian.tgz (Russian ispell files are used at 43n39e.ru) file uploaded by dp.maxime - Labels: Type-Archive OpSys-All Labels: Type-Archive OpSys-All Nov 08, 2009 r262 (Ask for non chunked content. ) committed by dp.maxime - Ask for non chunked content. Ask for non chunked content. Nov 06, 2009 issue 22 (Regex expressions in stopword file) reported by Imlbrown - This is more a question or feature request. We have many words in our database (non-cached mode) that are irrelevant to the search engine and we would like an easy mechanism to exclude them from the index. For example, dict16 and dict32 have thousand of words, with multiple occurrences, that begin with "$##" and then a string of numbers. For us, words of this pattern are irrelevant and we would like to not index them. Is there a way to use regular expressions in the stopwords file? Any other way to achieve the same result without brute forcing the stopwords file with every combination we find? Thanks! This is more a question or feature request. We have many words in our database (non-cached mode) that are irrelevant to the search engine and we would like an easy mechanism to exclude them from the index. For example, dict16 and dict32 have thousand of words, with multiple occurrences, that begin with "$##" and then a string of numbers. For us, words of this pattern are irrelevant and we would like to not index them. Is there a way to use regular expressions in the stopwords file? Any other way to achieve the same result without brute forcing the stopwords file with every combination we find? Thanks! Nov 03, 2009 dpsearch-4.53-04112009.tar.bz2 (Latest snapshot as of November 04) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Nov 03, 2009 r261 (Improved support for Iternationalized Domain Names. Update t...) committed by dp.maxime - Improved support for Iternationalized Domain Names. Update to the latest snapshot released. Improved support for Iternationalized Domain Names. Update to the latest snapshot released. Oct 31, 2009 r260 (Change for libidn detection in Linux. ) committed by dp.maxime - Change for libidn detection in Linux. Change for libidn detection in Linux. Oct 30, 2009 r259 (Fix for libidn library dependence on Linux ) committed by dp.maxime - Fix for libidn library dependence on Linux Fix for libidn library dependence on Linux Oct 28, 2009 issue 21 (SearchD gives internal server error) Status changed by dp.maxime - Thank you for reporting. Status: Done Thank you for reporting. Status: Done Oct 28, 2009 issue 20 (free() pointer error in 4.53 12092009) Status changed by dp.maxime - Thank you for reporting. Status: Done Thank you for reporting. Status: Done Oct 28, 2009 issue 21 (SearchD gives internal server error) commented on by Imlbrown - Maxime, Upgrading from MySQL 5.0 to 5.3 solved this issue for us. Thanks for your help. Maxime, Upgrading from MySQL 5.0 to 5.3 solved this issue for us. Thanks for your help. Oct 28, 2009 issue 20 (free() pointer error in 4.53 12092009) commented on by Imlbrown - Maxime, this issue was due to an old version of the mysql_devel package on our system. Thanks for your help. Maxime, this issue was due to an old version of the mysql_devel package on our system. Thanks for your help. Oct 27, 2009 r258 ($(grand_total) template meta-variable has been added. ) committed by dp.maxime - $(grand_total) template meta-variable has been added. $(grand_total) template meta-variable has been added. Oct 26, 2009 r257 (-Esitemap command has been added ) committed by dp.maxime - -Esitemap command has been added -Esitemap command has been added Earlier this year Oct 23, 2009 r256 (Add Unicode normalization options ) committed by dp.maxime - Add Unicode normalization options Add Unicode normalization options Oct 23, 2009 r255 (Mixed waiting strategy for CAS locking. ) committed by dp.maxime - Mixed waiting strategy for CAS locking. Mixed waiting strategy for CAS locking. Oct 15, 2009 r254 (Force reindexing for lost documents after -TZZZ and -Edocinf...) committed by dp.maxime - Force reindexing for lost documents after -TZZZ and -Edocinfo Force reindexing for lost documents after -TZZZ and -Edocinfo Oct 14, 2009 dpsearch-4.53-15102009.tar.bz2 (Latest snapshot as of October 15) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Oct 14, 2009 r253 (Remove redundant logging. Revert back sleeping instead of sc...) committed by dp.maxime - Remove redundant logging. Revert back sleeping instead of sched_yield() calling. Remove redundant logging. Revert back sleeping instead of sched_yield() calling. Oct 14, 2009 r252 (Fix for Limit by tag construction. ) committed by dp.maxime - Fix for Limit by tag construction. Fix for Limit by tag construction. Oct 14, 2009 r251 (Fix for possible zero alloc. ) committed by dp.maxime - Fix for possible zero alloc. Fix for possible zero alloc. Oct 14, 2009 r250 (Check if SO_RCVLOWAT and SO_SNDLOWAT are writtable on Linux ) committed by dp.maxime - Check if SO_RCVLOWAT and SO_SNDLOWAT are writtable on Linux Check if SO_RCVLOWAT and SO_SNDLOWAT are writtable on Linux Oct 13, 2009 r249 (Don't store urls with status=0 in limits. ) committed by dp.maxime - Don't store urls with status=0 in limits. Don't store urls with status=0 in limits. Oct 12, 2009 dpsearch-4.53-13102009.tar.bz2 (Latest snapshot as of October 13) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Oct 12, 2009 r248 (Combine data from urlinfo and server table for tag limit ) committed by dp.maxime - Combine data from urlinfo and server table for tag limit Combine data from urlinfo and server table for tag limit Oct 11, 2009 r247 (Don't fetch urls with status < 200 for url data writing ) committed by dp.maxime - Don't fetch urls with status < 200 for url data writing Don't fetch urls with status < 200 for url data writing Oct 11, 2009 r246 (A fix for correct dbnum in -Edocinfo ) committed by dp.maxime - A fix for correct dbnum in -Edocinfo A fix for correct dbnum in -Edocinfo Oct 10, 2009 r245 (Fix for -Edocinfo on empty base. Fix for Pop_Rank value inje...) committed by dp.maxime - Fix for -Edocinfo on empty base. Fix for Pop_Rank value injected via htdb:/ scheme. Fix for -Edocinfo on empty base. Fix for Pop_Rank value injected via htdb:/ scheme. Oct 09, 2009 r244 (Don't check records with status 0 (not indexed) in stored da...) committed by dp.maxime - Don't check records with status 0 (not indexed) in stored database. Don't check records with status 0 (not indexed) in stored database. Oct 09, 2009 r243 (Don't update "server" sql-table if -q switch is specified. ) committed by dp.maxime - Don't update "server" sql-table if -q switch is specified. Don't update "server" sql-table if -q switch is specified. Oct 09, 2009 r242 (update to the latest snapshot released. fix for slow finish ...) committed by dp.maxime - update to the latest snapshot released. fix for slow finish with -U switch. update to the latest snapshot released. fix for slow finish with -U switch. Oct 09, 2009 dpsearch-4.53-09102009.tar.bz2 (Latest snapshot as of October 9) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Oct 06, 2009 dpsearch-4.53-07102009.tar.bz2 (Latest snapshot as of October 7) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Oct 06, 2009 r241 (A fix for parsing value of sections with zero number but non...) committed by dp.maxime - A fix for parsing value of sections with zero number but non-zero maximum length. A fix for parsing value of sections with zero number but non-zero maximum length. Oct 06, 2009 r240 (add locking if needed for ExecActions and SQL-based sections...) committed by dp.maxime - add locking if needed for ExecActions and SQL-based sections. add locking if needed for ExecActions and SQL-based sections. Oct 06, 2009 r239 (Fix for rare case when Neo PopRank havn't calculated. Make l...) committed by dp.maxime - Fix for rare case when Neo PopRank havn't calculated. Make link weights to be positive for Neo PopRank. Fix for rare case when Neo PopRank havn't calculated. Make link weights to be positive for Neo PopRank. Oct 04, 2009 r238 (set SNDLOWAT and RCVLOWAT options for sockets CAS based sync...) committed by dp.maxime - set SNDLOWAT and RCVLOWAT options for sockets CAS based synchronization for ia64 and amd64 set SNDLOWAT and RCVLOWAT options for sockets CAS based synchronization for ia64 and amd64 Oct 01, 2009 issue 21 (SearchD gives internal server error) commented on by Imlbrown - Thanks for the suggestion, I will try it and post the results. I submitted issue 20 for version 4.53. I don't fully recall why 4.52 didn't work, but I vaguely remember that with a clean db 4.52 would not index any files, then we would replace the w/4.51 and everything worked, no config changes just executables. Thanks for the suggestion, I will try it and post the results. I submitted issue 20 for version 4.53. I don't fully recall why 4.52 didn't work, but I vaguely remember that with a clean db 4.52 would not index any files, then we would replace the w/4.51 and everything worked, no config changes just executables. Oct 01, 2009 issue 9 (query with allinxx: behaves odd) Status changed by dp.maxime - Status: Fixed Status: Fixed Oct 01, 2009 issue 21 (SearchD gives internal server error) commented on by dp.maxime - try to reconfigure with --enable-multidbaddr option to configure and rebuild dataparksearch. Why you can't run 4.52 and 4.53 ? Do you encounter any error with these versions ? try to reconfigure with --enable-multidbaddr option to configure and rebuild dataparksearch. Why you can't run 4.52 and 4.53 ? Do you encounter any error with these versions ? Oct 01, 2009 issue 21 (SearchD gives internal server error) commented on by Imlbrown - Also, searchd.conf has the following line DBAddr mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock?dbmode=multi&stored=localhost Also, searchd.conf has the following line DBAddr mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock?dbmode=multi&stored=localhost Oct 01, 2009 issue 21 (SearchD gives internal server error) reported by Imlbrown - Trying to get searchd to run we have performed the following. 1. searchd.conf is configured with defaults from dist file 2. In search.htm we have the following two dbaddr lines. a. DBaddr mysql://user:pass@localhost/dpesarch/?socket=/var/lib/mysql/mysql.sock&dbmode=multi&trackquery&stored=localhost b. DBaddr searchd://localhost/ All processes, including searchd, are running on the same machine. When we navigate to to the search homepage it is displayed, but when a search is performed we receive an Internal Server Error (500). We are using v4.51 (can't successfully run .52 or 53) Any ideas or additional configuration necessary? Trying to get searchd to run we have performed the following. 1. searchd.conf is configured with defaults from dist file 2. In search.htm we have the following two dbaddr lines. a. DBaddr mysql://user:pass@localhost/dpesarch/?socket=/var/lib/mysql/mysql.sock&dbmode=multi&trackquery&stored=localhost b. DBaddr searchd://localhost/ All processes, including searchd, are running on the same machine. When we navigate to to the search homepage it is displayed, but when a search is performed we receive an Internal Server Error (500). We are using v4.51 (can't successfully run .52 or 53) Any ideas or additional configuration necessary? Sep 28, 2009 dpsearch-4.53-28092009.tar.bz2 (Latest snapshot as of September 28) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source Sep 28, 2009 r237 (A fix for boolean queries like xxx AND NOT (allinsec: xxx) A...) committed by dp.maxime - A fix for boolean queries like xxx AND NOT (allinsec: xxx) A fix for possible memory leak A fix for boolean queries like xxx AND NOT (allinsec: xxx) A fix for possible memory leak Sep 27, 2009 dpsearch-4.53-27092009.tar.bz2 (Latest snpashot as of September 27) file uploaded by dp.maxime - Labels: Featured Type-Source Labels: Featured Type-Source

issue 21 (SearchD gives internal server error) reported by Imlbrown - Trying to get searchd to run we have performed the following. 1. searchd.conf is configured with defaults from dist file 2. In search.htm we have the following two dbaddr lines. a. DBaddr mysql://user:pass@localhost/dpesarch/?socket=/var/lib/mysql/mysql.sock&dbmode=multi&trackquery&stored=localhost b. DBaddr searchd://localhost/ All processes, including searchd, are running on the same machine. When we navigate to to the search homepage it is displayed, but when a search is performed we receive an Internal Server Error (500). We are using v4.51 (can't successfully run .52 or 53) Any ideas or additional configuration necessary?

Trying to get searchd to run we have performed the following. 1. searchd.conf is configured with defaults from dist file 2. In search.htm we have the following two dbaddr lines. a. DBaddr mysql://user:pass@localhost/dpesarch/?socket=/var/lib/mysql/mysql.sock&dbmode=multi&trackquery&stored=localhost b. DBaddr searchd://localhost/ All processes, including searchd, are running on the same machine. When we navigate to to the search homepage it is displayed, but when a search is performed we receive an Internal Server Error (500). We are using v4.51 (can't successfully run .52 or 53) Any ideas or additional configuration necessary?

Today

Last 7 days

Last 30 days

Earlier this year