Re: Dynamic collections in SolrCloud for log indexing

I believe it is a misunderstandig to use custom routing (or sharding as Erick calls it) for this kind of stuff. Custom routing is nice if you want to control which slice/shard under a collection a specific document goes to - mainly to be able to control that two (or more) documents are indexed

Re: How to add the extra analyzer jar?

What about the jar file that containsorg.wltea.analyzer. solr.IKTokenizerFactory? You can change solrconfig.xml to include a new directive to path to new jars. You might start with absolute paths to get it working at all then move to relative paths when you're sure it works and it's just a matter

Re: Solr Cloud 4.0 Production Ready?

You also have the option of using a recent nightly build, just pick one and work with that. That'll be much closer to 4.1 than the official 4.0 release. You can get them from here: http://wiki.apache.org/solr/NightlyBuilds Best Erick On Fri, Dec 21, 2012 at 6:22 AM, Per Steffensen wrote: > I w

Re: SloppyPhraseScorer behavior change

Could you post the full query URL, so we can see exactly what your query was? Or, post the output of &debug=query, which will show us what Lucene query was generated. -- Jack Krupansky -Original Message- From: varun srivastava Sent: Monday, December 24, 2012 1:53 PM To: solr-user@luc

Re: SloppyPhraseScorer behavior change

Hi Jack, My query was simple /solr/select?query=ipad apple apple0ipad and doc contained "apple ipad" . If you see the patch attached with the bug 3215 , you will find following comment. I want to confirm whether the behaviour I am observing is in sync with what the patch developer intended or its

Re: SloppyPhraseScorer behavior change

Thanks. Sloppy phrase requires that the query terms be in a phrase, but you don't have any quotes in your query. Depending on your schema field type you may be running into a change in how auto-generated phrase queries are handled. It used to be that apple0ipad would always be treated as the q

solr java API for fuzzy query

Is there any java API available in Solr for fuzzy query, similar to the Lucene org.apache.lucene.search.FuzzyQuery class? More general, : is there any general way to define query with Lucene java API and invoke it thru Solr (kind of Lucene-Solr bridge)? Thanks Alexey _

How to modify Solr StatsComponent to support stats.range

Hi, I am trying to modify solr's code to support stats.range, just as Solr facet component. For example: q=*:*&stats=true&stats.field=fileSize&f.fileSize.stats.query=accesstime:[NOW-1MONTH TO NOW-7days]&f.fileSize.stats.query=accesstime:[NOW-1YEAR TO NOW-1MONTH]&f.fileSize.stats.query=fileSize:[*

Re: solr java API for fuzzy query

Hi Alexey, You can use the Lucene query syntax with Solr, does that help? Try Keyword~5 for example. Otis -- SOLR Performance Monitoring - http://sematext.com/spm/index.html Search Analytics - http://sematext.com/search-analytics/index.html On Tue, Dec 25, 2012 at 12:19 AM, Yakubovich Alexey

Re: Dynamic collections in SolrCloud for log indexing

Hi, Right, this is not really about routing in ElasticSearch-sense. What's handy for indexing logs are index aliases which I thought I had added to JIRA a while back, but it looks like I have not. Index aliases would let you keep a "last 7 days" alias fixed while underneath you push and pop an

Re: Dynamic collections in SolrCloud for log indexing

This is precisely it. It is a 'collections alias', allowing you to group collections together into 'super-collections'. You add a new collection (made up of a core on n hosts) every day/week/month/whatever. When you do so, you add this collection to your super-collection. Many you do a quick audit