data-config.xml: delta-import unclear behaviour pre/postDeleteImportQuery with clean
I have some unclear behaviour with using clean and pre/postImportDeleteQuery for delta-imports. The docs under http://wiki.apache.org/solr/DataImportHandler#Configuration_in_data-config.xml are not clear enough. My observation is: - preImportDeleteQuery is only executed if clean=true is set - postImportDeleteQuery is only executed if clean=true is set - if preImportDeleteQuery is ommitted and clean=true then the whole index is cleaned => config with postImportDeleteQuery itself won't work Is above correct? I don't need preImportDeleteQuery only post is necessary. But to make post work I am doubling the post to pre so clean=true doesn't delete whole index. This looks a bit like a workaround as wanted behaviour. solr version is 1.4.1 thanks. -- manuel aldana mail: ald...@gmx.de | man...@aldana-online.de blog: www.aldana-online.de
restart server necessary when changing schema+config?
it is not explicitly mentioned in solr documentation but I guess when changing stuff inside conf/ folder a restart of webserver is necessary? Or is there a reload URL call available? -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
problems with + operator (seem to be treated as normal char and not as operator)
hi, I am having queries: +a b a b I always wondered why the + operator did not work. Looking at the http://localhost:8983/solr/admin/analysis.jsp analysis trace the query analzyer indeed is removing the + through the WordDelemiterFilterFactory. So I removed this filter (btw: why is this the default setting, which I think is a bit dangerous because the special + - operators are thus removed). Still '+a b' matches documents which have no 'a' inside the field. Now I guess solr is handling the '+' as a normal match character and not as an lucene (required) operator at all? Is this correct. If so, why is this lucene operator overridden? Maybe I need to escape the + for solr, so it treats it as an operator? thanks. -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
Re: problems with + operator (seem to be treated as normal char and not as operator)
Koji Sekiguchi wrote: To debug quert parser, use FULL INTERFACE admin form (http://localhost:8983/solr/admin/form.jsp) and check Debug: enable and see debug info. You cannot use analysis.jsp for this purpose because it doesn't use query parser. I see, good to know... I was already very confused and debugged my head off :) Solr should use lucene query parser as long as you never explicitly use query parser other than lucene through defType, localParams, etc... I'm just guessing 'a' was filtered out by StopFilter? you were right, the default lucene query parser was overridden. thanks. -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
Re: search suggest
also watch out that you have a good stopwords list otherwise the suggestions won't be helpful for the user. Jack Bates wrote: how can i use solr to make search suggestions? i'm thinking google-style suggestions, which suggests more refined queries - vs. freebase-style suggestions, which suggests top hits. i've been looking at the query params, http://wiki.apache.org/solr/StandardRequestHandler - and searching for "solr suggest" - but haven't figured out how to get search suggestions from solr -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
Re: plans for switching to maven2 (after 1.4 release)?
I know migrating to maven2 has its pain points but in my view is worth it if one sees it as a long run investment. It follows standards/conventions and importing projects to IDEs like eclipse or IntelliJ is much more straightforward. When using maven getting used to a new project using it is also much quicker as grasping propriertary builds reinventing the wheel. After having used maven2 for three years now I really couldn't live with it (though in the beginning when migrating builds I was swearing at its evil details). Support (documentation + mailing-list) has also greatly improved since then. Because smooth migration is not that easy, one should maybe take the cut after release 1.4 or 1.5? Though I am not so much into codebase history would like to help out. Grant Ingersoll schrieb: I'm not particularly opposed to it, but I'm not exactly for it either. I very much have a love hate relationship with Maven. The simple things work fine w/ Maven and the power of pointing Eclipse or IntelliJ at a POM file and having the whole project imported and ready to work on w/o one iota of setup is something that the proponents of Ant just don't get, especially when it comes to multiple module builds like Solr and Lucene have.That being said, there are a lot of headaches with Maven, number one being releases, number two being anything custom and number three being the constant instability of the magic happening behind the scenes with it upgrading dependencies, etc. automatically. Finally, I've always had a hard time getting help in Maven land. It always seemed to me the number of incoming questions outweighed the number of answers about 10 to 1. I converted Mahout to Maven and it was a pain. I also use Maven for personal development as well. It is much easier to start fresh on Maven than it is to add it in later. And, there is something to be said for the Maven Ant plugin, but even that is clunky. In the end, I think I'd be +0 on it. It's also come up in the past on the lists and there never is a clear consensus. -Grant On Jun 28, 2009, at 12:33 PM, aldana wrote: hi, are there plans to migrate from ant to maven2? maybe not for the current trunk (mainline for 1.4), but maybe for the trunk after releasing solr 1.4. it makes the build more standard and easier to import to IDEs. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/plans-for-switching-to-maven2-%28after-1.4-release%29--tp24243036p24243036.html Sent from the Solr - User mailing list archive at Nabble.com. -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
dropping index at startup
is it possible to clean up solr index by passing a start param? currently I am deleting the data/ folder to achieve this, which feels a bit unnatural. It would be cool to have something like -Dsolr.drop.index as parameter. btw, how does solr generally handle documents in index which aren't matching the schema.xml (e.g. after a change done to schema.xml)? Is it discarding them, the server itself starts up OK (doesn't give an error, that inconsistent documents exist). -- manuel aldana ald...@gmx.de software-engineering blog: http://www.aldana-online.de
