similar to: QueryParser and utf-8 strings

Full_Name: Albrecht Gebhardt Version: 0.99.0 OS: alpha, osf4.0 Submission from: (NULL) (143.205.180.40) DEC cc doesn't like c++ style comments // like this one Please use standard cc comments or #if 0 ... #endif A quite large patch follows (I hope it will pass mailing with not too much wrapped lines): --- ./src/main/g_her_glyph.c.dec-cc.patch Mon Feb 7 14:48:10 2000 +++

Processing commands for control at bugs.debian.org: > # sorry for the noise > submitter 585188 ! Bug #585188 [convirt] convirt: Python string exceptions no more allowed in Python 2.6 Changed Bug submitter to 'Sandro Tosi <morph at debian.org>' from 'Sandro Tosi <morph at ravel.debian.org>' > submitter 585189 ! Bug #585189 {Done: Julien BLACHE <jblache at

Hi, We are using kernel 2.4.24, tcng version 10b. I''m trying to do some policing in the ingress queue of the internet device. Until now we had configured some filters dividing traffic into queues, and on these queues the Double Leaky bucket meter was applied. The idea is to have a minimum of bandwidth assigned per class (the cir values) and a maximum (pir values), just as with the

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

Hi, I wanted to configure the following : 1. VPN + some other special connections (TCP 82,8282,23,22 and ICMP) to have priority over the rest 2. special upstream for our updating system on port 4000 3. within the VPN tunnels citrix traffic ( TCP 1494, 2598) + icmp has priority I need this for both incoming and outgoing traffic as it is the bandwith managment config on a central system from

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

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

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8186 > Date: 2007-04-11 23:38:53 +0100 (Wed, 11 Apr 2007) > > Log message (7 lines): > queryparser/queryparser.lemony: Fix regression introduced by > Richard's change, and restructure to make the handling for each case > more obvious. Thanks for the catch: I

I'm wondering what the intended semantics for the contents of the list returned by QueryParser::stoplist_begin() is. Currently, if a query parser is created, and then used multiple times, the list returned by stoplist_begin() is the list of all terms that have been excluded from any query due to being considered a stoplist. I would have expected it to only return items from the previous

hello everyone, I am Maheshwar, a prefinal year Computer Science undergraduate student at BITS-Pilani, India. When i was going through the GSOC ideas , i felt interested in Quesry parser project. Till now i have implemented a couple of LL(1) parsers as a part of my assignment in Compiler construction course, so i would love to join and contribute to this project. So can any one tell me how to go

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

I'm new to Xapian and we just recently upgraded to version 1.0.0.0. However, something seems to have changed during the upgrade and I need help figuring out how my code should be written. In version 0.9.9.1 of Search::Xapian, the following code results in this output "Xapian::Query(pet:(pos=1))". my $qp = new Search::Xapian::QueryParser; $qp->set_stemmer(new

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

I am having a bit of a problem with my search queries being parsed correctly it seems, and I wonder if anyone else has experienced this. I have written an index using StandardAnalyzer for analysis. I want to search that index by passing my user query through a QueryParser instance which is also using a StandardAnalyzer. However the resultant query does not seem to be a valid term query and