search for: queryparsing

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

I have encountered the following build errors after 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

I've got a small test database setup with one record. $ delve -r 1 -V /tmp/1/ Values for record #1: 0:DD4F2162FFFF0E43741A4A1C2B8EC0E7 1:./Text_page_scan_2.jpg 2:jpg 3:.jpg Term List for record #1: E:.jpg P:./Text_page_scan_2.jpg Q:DD4F2162FFFF0E43741A4A1C2B8EC0E7 T:jpg The terms were added with lines like this: doc.add_term(string("P:") + path); Problem is, I can't seem to

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

I just started using Ferret and I successfully indexed some documents. I can search this 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

Probably an uncaught malformed query - the following form of search queries causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled): x-y NEAR test NEAR test The first term can be anything with a hyphen in it but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a

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

Hello list, * apache-solr-3.6.2 * dovecot-2.1.7 I configured fts_solr for dovecot, but I have two issues When doing a search request within telnet 127.0.0.1 143 it connects to solr. Jul 21, 2013 4:38:15 PM org.apache.solr.core.SolrCore execute INFO: [] webapp=/solr path=/select params={rows=1&q=box:10361d30f8c4ea51ad7c00002ecaff3b+user:" tom at

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",

Hello, My dovecot constantly runs into this error. I want to fix this one last time, I am tired of troubleshooting so please someone give me a lasting and proper solution for this error. I think its a problem with the dovecot-solr module. Please tell me how do I find the root of this problem with Dovecot. There is a problem with the body search text field. It always fails(with no result), other

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

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

Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a

Hi, Under gcc 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

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

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

This is another error different from the previous posting. I want to compile xapian-core-0.9.4_svn6707 with UTF-8 patch. But I failed to compile it due to the following errors. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- 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

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 ''a'' Cheers, Andy

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