similar to: QueryParser : some remarks

*Hi all,* * * *The following is my general idea for the project. For a complete query parser I still need to consider more details. Please give me feedback because the description of this project is lack of detailed information, and I can submit my proposal without giant deviation.* * * design principle of query parsing: 1) better understanding user input. All search engine do is understanding

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'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. There are several problems I couldn't find a solution. 1. QueryParser does not perform stemming I am working with PHP5 and use the xapian wrapper written by Daniel M?nard I build a query using parseQuery. Output of the parsed query shows that terms are not stemmed, although a stemmer is set ( see code snippet) # create a XapianDatabase object to search in $db = new

Hi Guys, Here's a simple test case that causes a segfault with the perl bindings patched to enable spelling correction: use strict; use warnings; use Search::Xapian; my $db = Search::Xapian::WritableDatabase->new("test.db", Search::Xapian::DB_CREATE_OR_OPEN); if (!defined($db)) { die("Failed to open xapian_database: $!"); } my $indexer =

Hi All, I'm using the TermGenerator::index_text() on version 1.0.4 with the FLAG_SPELLING turned on, because the new spelling suggestion stuff seems awesome, but I'm getting a segv. (gdb) bt #0 0xb7ae153c in Xapian::WritableDatabase::add_spelling (this=0xa553988, word=@0xbff97724, freqinc=1) at ./include/xapian/ base.h:154 #1 0xb7becf47 in

Hi, Is it necessary to set the down below flag to the TermGenerator, if I want the "Did you mean ..." spelling corrections? Xapian::TermGenerator::flags::FLAG_SPELLING Thank you very much Markus

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

Greets, I'm giving a stab at patching the CPAN module to add the missing WritableDatabase::add_spelling and remove_spelling, but need a bit of guidance since I'm coming in cold, and pressed for time (aren't we all). I've modified XS/WritableDatabase.xs and added the two necessary functions, and also added the two basic tests in t/index.t. Compilation completes cleanly, but

Respected sir/ma'am, I, Saurabh Kumar, am a second year UG student in ?Department of Comp. Science at IIT Delhi, India and want to apply for GSOC. I am interested and would love to work on the following projects: ?-? QueryParser Reimplementation ?- ?Improve Spelling Correction I have worked on many programming projects and it makes me an eligible candidate for SOC. I have a experience of

Respected sir/ma'am, I, Saurabh Kumar, am a second year UG student in ?Department of Comp. Science at IIT Delhi, India and want to apply for GSOC. I am interested and would love to work on the following projects: ?-? QueryParser Reimplementation ?- ?Improve Spelling Correction I have worked on many programming projects and it makes me an eligible candidate for SOC. I have a experience of

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

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

Hello, guys! How's it going? I would like to offer you myself again to implement one of the ideas during the GSoC 2012. I want to take care of the "Learning To Rank" project, but I would also be glad to pick the "QueryParser reimplementation", "Dynamic Snippets", "Gmane Search improvements" or even "Replace socket code with ZeroMQ" project (I

Hey guys I noticed xapian using a lot of memory while indexing [1] so I decided to look at the bottle necks and where this can be improved. Here are some large spots that I noticed (Chert) - 1. Every document has map<string, OmDocumentTerm> and OmDocumentTerm contains the same string again. This results in every term being stored in memory twice. Additionally multiple documents may

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

Hello, First I wanted to say thanks for a great piece of software, thanks Olly and others who've contributed! I know that Xapian supports right-truncating, if that's the proper name for wildcard support, as in a search for "xapia*". I don't believe Xapian supports wildcards on both sides of a term, correct? Is this something that is technically unfeasable, unpalatable

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

Hello, I am Sehaj Singh Kalra, an Indian student. I am an undergraduation student in Indian Institute of Technology-Delhi (IIT-Delhi) pursuing Computer Science and Engineering. I want to work on the idea "QueryParser Reimplementation ". With the background I have in this field, I am fully comfortable with this project. I have went through the specification and through Query Parser

Hello, I'm wondering about how the QueryParser parses a query containing an "alias" when the default operator is OP_AND (by "alias", I mean a search field mapped to multiple term prefixes). With the following php code : <?php $parser=new XapianQueryParser(); $parser->set_default_op(XapianQuery::OP_AND); $parser->add_prefix('alias', 'AUT1:');