search for: queryparser

--- 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/query...

...fter applying xapian-qp-utf8-0.9.2.patch. There is no build error before the patch. - CentOS 4.2 64 bit version (RHEL 4.0.2 compatible) - AMD Opteron dual processor Can anybody tell me what I am missing? Thanks! Sungsoo Kim -------------------------------------------------- [root at saturn queryparser]# make make all-am make[1]: Entering directory `/usr/src/redhat/BUILD/xapian-core-0.9.4/queryparser' if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../common -I../api -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -W -Wr...

...jpg The terms were added with lines like this: doc.add_term(string("P:") + path); Problem is, I can't seem to run a query that returns the document using any of the terms. Here is the outline of the code that runs the queries I'm trying to run: Database db(db_path.string()); QueryParser queryparser; Stem stemmer("english"); //queryparser.set_stemmer(stemmer); queryparser.set_database(db); queryparser.add_prefix("type", "T"); queryparser.add_prefix("md5sum", "Q"); queryparser.add_prefix("path", "P"); query...

I don't know whether this is a BUG or for special purpose... According to the definition of "xapian/queryparser.h", FLAG_AUTO_MULTIWORD_SYNONYMS contains bit of FLAG_AUTO_SYNONYMS . Therefore, long as I set the parse flag with FLAG_AUTO_SYNONYMS, the query parser will automatically activate the function of FLAG_AUTO_MULTIWORD_SYNONYMS. See the below source code part from "queryparser.lemon"...

...index using the following code: index = Index::Index.new(:path => path) index.search_each("something") do |doc, score| print "##{doc} #{index[doc][''url'']} - #{score}" print "\n" end However, when I try to use Search::Searcher and QueryParser I don''t get any results. I tried the following code: queryparser = QueryParser.new() searcher = Searcher.new(path) queryparser.fields = searcher.reader.fields searcher.search(queryparser.parse("something")) I index all my documents as follows: index = Index::Index.new(:path =&...

...er 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a crash, but "test NEAR test NEAR x-y" will. Stemming language was "english", strategy STEM_SOME. Default op was OP_AND_MAYBE. This is the offending Perl code: [...] my $qp = Search::Xapian::QueryParser->new(); my $stemmer = Search::Xapian::Stem->new("english"); $qp->set_stemmer($stemmer); $qp->set_database($database); $qp->set_stemming_strategy(STEM_SOME); $qp->set_default_op(OP_AND_MAYBE); $query_string = " x-y NEAR test NEAR test &...

...roach, but since it adds a new, publically visible, operator to Xapian::Query, I thought I'd better put the patch up for review on the mailing list rather than commit it directly. It's attached to this email, so, comments welcome! -- Richard -------------- next part -------------- Index: queryparser/queryparser.lemony =================================================================== --- queryparser/queryparser.lemony (revision 7552) +++ queryparser/queryparser.lemony (working copy) @@ -148,6 +148,9 @@ add_to_query(q, Query::OP_OR, Query(*t, 1, pos)); ++t; } + if (q.empty()) { +...

...solr.schema.IndexSchema.getDynamicFieldType(IndexSchema.java:1330) at org.apache.solr.schema.IndexSchema$SolrQueryAnalyzer.getAnalyzer(IndexSchema.java:408) at org.apache.solr.schema.IndexSchema$SolrIndexAnalyzer.reusableTokenStream(IndexSchema.java:383) at org.apache.lucene.queryParser.QueryParser.getFieldQuery(QueryParser.java:574) at org.apache.solr.search.SolrQueryParser.getFieldQuery(SolrQueryParser.java:206) at org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1436) at org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:131...

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", Xapian::QueryParser::FLAG_PARTIAL|Xapian::QueryParser::FLAG_AUTO_MULTIWORD_SYNONYMS |Xapian::QueryParser::FLAG_PHRASE ); cout << "Performing query `" << query.g...

...cene.analysis.DelegatingAnalyzerWrapper$DelegatingReuseStrategy.getReusableComponents(DelegatingAnalyzerWrapper.java:74) at org.apache.lucene.analysis.Analyzer.tokenStream(Analyzer.java:175) at org.apache.lucene.util.QueryBuilder.createFieldQuery(QueryBuilder.java:207) at org.apache.solr.parser.SolrQueryParserBase.newFieldQuery(SolrQueryParserBase.java:374) at org.apache.solr.parser.SolrQueryParserBase.getFieldQuery(SolrQueryParserBase.java:742) at org.apache.solr.parser.SolrQueryParserBase.handleBareTokenQuery(SolrQueryParserBase.java:541) at org.apache.solr.parser.QueryParser.Term(QueryParser.java:299)...

I cooked up a little script to show what I mean. This doesn''t look right to me, but maybe I just completely misunderstand QueryParser. Same output on mswin32, unix, ferret 0.9 and 0.10 Cheers, Sam require ''rubygems'' require ''ferret'' p Ferret::VERSION # 0.10.6 index = Ferret::Index::Index.new() index << {:title => "Programming Ruby", :content => "yada yada yada&quot...

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 can''t find the corresponding method i...

...e term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a document with "XLABEL:xapian". Running 'delve' on the index afterwards confirms the term is there. Now, if I pass "label:xapian" to the QueryParser, no results are returned. It turns out that the Query object built by QueryParser has the term "XLABELxapian" instead of "XLABEL:xapian". On the other hand, if the label starts with an upper-case, ie "Xapian", the Query will contain the term "XLABEL:Xapian" a...

...2.95 Xapian fails to build like so: g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I/home/dsainty/not-backed-up/pkgsrc/textproc/xapian/work/.buildlink/include -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c queryparser/queryparser_internal.cc -Wp,-MD,queryparser/.deps/queryparser_internal.TPlo -fPIC -DPIC -o queryparser/.libs/queryparser_internal.o /data/home/olly/tmp/xapian-svn-snapshot/tags/1.0.10/xapian/xapian-core/queryparser/queryparser.lemony:25: queryparser_internal.h: No such file or directory /data/h...

hey. I'm using the Search::Xapian interface version 0.9.2 (and xapian-core 0.9.2), and feeding the queryparser such things as "one AND NOT two" or "test NOT NOT really" makes it go "Aborted"... I've tried adding the exception handling from the other stubs to QueryParser.xs as well, but I still can't catch this error from perl. Does this mean it's not an exc...

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 m...

...------------------------ g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../common -I../api -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -W -Wredundant-decls -Wundef -Wpointer-arith -Wcast-qual -Wcast-align -Wno-multichar -Wno-long-long -fno-gnu-keywords -g -O2 -MT queryparser_internal.lo -MD -MP -MF .deps/queryparser_internal.Tpo -c queryparser_internal.cc -fPIC -DPIC -o .libs/queryparser_internal.o In file included from /usr/include/glib-2.0/glib/gquark.h:30, from /usr/include/glib-2.0/glib/gerror.h:24, from /usr/include/glib-2.0/gl...

Hi there, I am stomped as to why QueryParser''s parse method behaves differently between query ''a'' and ''b''. See http://pastie.caboo.se/private/4rlwrecyyow3yl6qtf4tq Could someone please help me understand why that is the case. p.s. I also found ''i'' produce the same behavour as ...

According to the following link: http://ferret.davebalmain.com/api/classes/Ferret/QueryParser.html :handle_parser_errors => true is enabled by default and seems to be in acts_as_ferret in class_methods.rb of the plugin. However, when I pass a special character as a query (e.g., !, -, <, >, etc) it throws an error and pukes. -- snip -- Error occured in src/q_parser.y:279 - yyerror...

Hello, My name is Sean Mikalson. I am a second year Software Engineering student with a combined degree in Philosophy. I am interested in participating with Xapian in GSOC this year and a couple of projects have initially caught my eye: - Dynamic Snippets - QueryParser Reimplementation I have good working knowledge in C/C++, Java and SQL (specifically Transact-SQL). In order to determine where my skills and interests are best suited, as well as to provide the best proposal possible for my application, I would like to get better acquainted with the Xapian code ba...