similar to: [issue] The difference between QueryParser::FLAG_AUTO_SYNONYMS and QueryParser::FLAG_AUTO_MULTIWORD_SYNONYMS

Very few people seem to be using synonym in Xapian, I recently found some problems in the use of synonyms. Normally, I think we should not contain any prefix info in synonym table except that 'Z'. For example, I have the following synonyms and prefix info: db.add_synonym("search", "find"); db.add_synonym("Zsearch", "Zfind");

Hello, As I know, get_matches_estimated() return an estimate for the number of documents with matches the query. But now, I found it get a disparity between the return value and real mathced number. For an example: the real matched number is 58, but the return value is 458; so when the users click the hinder page, get a blank page ... so they often complain to me. I found that the main reason is

Hi, I'm using xapian to build my search engine, but met with a problem. The code snippet is like: ----------------------Code begin------------------------------------------------------------- Xapian::QueryParser qp; qp.add_prefix("Singer", "S"); Xapian::Query query = qp.parse_query("Singer:s.h.e",

I am working with version 1.2.7 and want to use stemming and synonyms. I use the perl-bindings and get some problems. First of all: the perl-bindings dont allow the QueryParser a third argument when calling parse_query! So i cannot set a default prefix (which perhaps is the solution to my problem, but later more) i have a simple testcase: 3 documents, every document only has one word:

Hi guys I've just had a thought about something we do with our search on ReportBuyer.com: we cater for both American and British English in our searches and we have had plans for a while now to implement something that allows users to find 'colour' and 'color', 'tap' and 'faucet' by doing some clever programming. Looking at the Xapian docs, though, it appears

Hello, I am looking for a documentation or an example to use the synonym function. I tried this db.add_synonym("omega","xapain"); and this works by adding the flag FLAG_AUTO_SYNONYMS. If i try to use the db.add_synonym("omega","xapain is search engine "); it fails why? Can xapian use synonym for Abbreviations like MBA => Master of business

Hi, I have already re-make the patch file, based on the trunk codes in SVN respo. But I can not build the xapian, because there are many errors when building 'languages/' for stemmer. Therefore, I could not test the new patching code. Patching code can be accessed from: http://www.xunsearch.com/download/xapian-scws-1.3.x-trunk.patch Need to install SCWS first as below steps: 1.

--- search-xapian/XS/QueryParser.xs | 6 ++++++ search-xapian/Xapian/QueryParser.pm | 7 +++++++ xapian-core/include/xapian/queryparser.h | 3 +++ xapian-core/queryparser/queryparser.cc | 6 ++++++ xapian-core/queryparser/queryparser.lemony | 9 +++++++++ xapian-core/queryparser/queryparser_internal.h | 4 +++- 6 files changed, 34

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the

Xapian is a very excellent open source search engine library, but there is no native support for Chinese word segmentation in queryparser and termgenerator. Therefore, I modified small amount of source codes, integrated into the SCWS tokenizer, that is the same open-source and developped by myself. Anyone can obtain the patch from below URL. After patching, Xapian::QueryParser::parse_query and

I attempted to use the sortable_serialize function from perl, however doesn't seem to exist. The only occurrence of the string "sortable" in the /usr/local/perl/5.10.1/Search/ tree is in the pod in Xapian.pm. What am I doing wrong? use Search::Xapian; ... $doc->add_value(4,sortable_serialize($recdate)); Undefined subroutine &main::sortable_serialize called

Hello, Thanks James for the reply. That cleared a few things out. Apologies for replying late because of exams going on. I was going through the previous clustering API to understand how it worked and it seems like the the approach for construction of the termlists which are used for distance metrics use TF-IDF weighting with cosine similarity, which is very similar to the approach I would need

I have an application for synonyms for tags in in notmuch, which means synonym expansion for a particular boolean prefix. I have a vague memory of Olly telling me this doesn't work, but I'm not sure about the details. My higher level goal is to support a kind of indirection with tags, where query tag:foo can really generate tag:bar or tag:fub, depending on some kind of configuration.

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe

QueryParser fails badly allocating enormous amount of memory when processing query strings with special/accented characters. See: irb(main):002:0> require ''rubygems'' irb(main):003:0> require ''ferret'' irb(main):004:0> include Ferret irb(main):005:0> index = Index::Index.new irb(main):008:0> index << "something" # Now the error

Hi all, Thanks to the authors for the amazing work on Ferret! I have a question about setting up the standard operators on a QueryParser. I would like my parser to default to AND queries rather than the default OR. In Java I would simply do: QueryParser parser = new QueryParser("contents", new StandardAnalyzer()); parser.setDefaultOperator(QueryParser.Operator.AND); But I

Hello, What happened to "clean_string" in QueryParser? Benjamin

I use the QueryParser::parse_query() method but I see it uses "OR" by default between words? Is there a way to make it use "AND" instead? I see there are flags I can pass to the parse_query() method but none seems to allow a switch from OR to AND. I would like to do that without having to write my own query parser. Everything else is fine with the QueryParser parsing, for

Hi, I would like to "pull apart" a search string to populate distinct search fields in a UI; something like how Google toggles between simple and advanced search modes. I realise going from simple to advanced may well be lossy but that's fine for my purposes. I thought the obvious place to start was xapian's QueryParser. Unfortunately, Query instances appear to be a little

Hi Olly, valgrind showed me what seems to be a memory leak: QueryParser owns the Stopper and Stem instances it points to (since it deletes them e.g. in set_stemming_options), but it does not delete them at destruction. (Btw., I don't test before deleting, but maybe "delete 0;" does not work on all platforms?) -- Robert Pollak GPG Key ID: 748646AD -------------- next part