Re: Restrict/change "numFound" solr result

Can you explain a little bit more, what you are trying to do? I don't get, what you want to do. On 07/06/2013 08:39 AM, aniljayanti wrote: Hi, I am working on solr 3.3. i am getting total 120 records with below query, in response xml "numFound" is showing 540 records. http://localhost:8080/te

Re: TZ parameter

The TZ parameter only applies to "date math" rounding. You haven't used any date math. What are you actually trying to accomplish? Would [* TO NOW] cover your cases? Or [* TO NOW/DAY+1DAY]? -- Jack Krupansky -Original Message- From: Matt Mitchell Sent: Sunday, July 07, 2013 11:24 P

Re: Are the XML element names in schema.xml case sensitive?

Yes, the XML element names (tags) and attribute names are all case sensitive, but... Solr has a special hack for "fieldtype" as well as "fieldType". -- Jack Krupansky -Original Message- From: Alexandre Rafalovitch Sent: Sunday, July 07, 2013 11:25 PM To: solr-user@lucene.apache.org S

Are the XML element names in schema.xml case sensitive?

I am looking at example's schema.xml and suddenly realize that it seems to spell fieldtype definition as both fieldtype and fieldType. XML by definition is case sensitive. But is Solr? The Wiki seems to offer it both ways as well. I am curious about this for all the XML files: solr.xml, schema.xm

TZ parameter

Hi, I'm a little stumped on the TZ param for running a date range query. I've indexed a single doc with a dateTime field value as "2013-07-08T00:00:00Z". My query is basically this: ?q=date_dt:[* TO 2013-07-07T23:00:00Z]&TZ=America/New_York >From what I'm seeing here: http://wiki.apache.org/s

Custom Hashing

Hello , I use Solr Cloud 4.3.1. We use query join , so we need index some documents together . For this, I want chang hash function by my logic . by SOLR-2592, I can add to solrconfig. This doesn't working. I need change hash function. Does exist some solution for this? TNX -- View

Re: searching both english and japanese

Shalom, isn't the StandardAnalyzer supposed to take care of "forking" in case of ideograms? I.e. use a Japanese-friendly analyzer for japanese characters and an English-friendly analyzer otherwise. As Jack pointed out, edismax is nifty to expand a query on multiple fields. If you need to do mor

Re: searching both english and japanese

Shalom, isn't the StandardAnalyzer supposed to take care of "forking" in case of ideograms? I.e. use a Japanese-friendly analyzer for japanese characters and an English-friendly analyzer otherwise. As Jack pointed out, edismax is nifty to expand a query on multiple fields. If you need to do mor

Re: Why shouldn't lang-id component work at query-time?

Default Lucen/Solr searching doesn't support "qf" or a list of fields to search, so you can't use that technique there. -- Jack Krupansky -Original Message- From: adfel70 Sent: Sunday, July 07, 2013 1:54 PM To: solr-user@lucene.apache.org Subject: Re: Why shouldn't lang-id component w

Re: Why shouldn't lang-id component work at query-time?

Well, yes, the problem is indeed simple.. Regarding the approach you're offering - if I query on multiple fields, each field for another language, why should it matter if I use edismax searching or default lucene searching? Jack Krupansky-2 wrote > The problem at query time is simple: a typical

Re: Why shouldn't lang-id component work at query-time?

Proper nouns are the worst for language ID. What language is "Laserjet" or "Obama"? --wunder On Jul 7, 2013, at 10:47 AM, Jack Krupansky wrote: > The problem at query time is simple: a typical query has too few terms to > reliably identify the language using statistical techniques, especially

Re: Why shouldn't lang-id component work at query-time?

The problem at query time is simple: a typical query has too few terms to reliably identify the language using statistical techniques, especially for a language like English which is famous for "borrowing" words from other languages. I mean, is "raison d'être" REALLY French anymore? Or, are "so

Why shouldn't lang-id component work at query-time?

Hi, I'm trying to integrate solr's lang-id component in my solr environment. In my scenario, I have documents in many different languages. I want to index them in the same solr collection, to different fields and apply language-specific analyzers on each field by its language. So far lang-id compo

Re: searching both english and japanese

Just use the edismax query parser and set "qf" to all of the searchable first, in both languages. And then just use to copy from the main field(s) to the parallel, alternate language fields. -- Jack Krupansky -Original Message- From: Shalom Ben-Zvi Kazaz Sent: Sunday, July 07, 2013

searching both english and japanese

Hi, We have a customer that needs support for both english and japanese, a document can be any of the two and we have no indication about the language for a document. ,so I know I can construct a schema with both english and japanese fields and index them with copy field. I also know I can detect t

lang.fallback doesn't work when using lang.fallbackFields

Hi I'm trying to index a set of documents with solr's language detection component. I set user_lan en,it en In some documents user_lan has 'sk', solr falls-back to 'sk' ,which is not in the whitelist, and instead of falling back to 'en' as stated here

Re: Sorting

You're probably running into memory issues, perhaps swapping. Or you have commits (hard with openSearcher=true or soft) happening very frequently. Lucene's sort algorithm reads all the values into memory even for a single-field document result. So if this is getting reloaded for each search, that'

Re: Is it possible to find a leader from a list of cores in solr via java code

What Jack and Shalin said Jack's comments about leaders changing is absolutely correct, although practically they won't change all that often unless you're bouncing nodes all over the place. But as Shalin says, CloudSolrServer will already to this, at least as far as sending updates to a lead

Re: Sorting

Jack, Do you think DocValues with unique field make sense? From what I read, it will only double index size for that field. It will give just a different numbers of field. I have really big problem with sorting by unique field. Without sorting, event in 40-50 GB index, almost every query is quite