Re: How to implement Autosuggestion

Hi Chandan, I will answer as my previous answer to a similar topic that got lost : "First of all, simple string autosuggestion or document autosuggestion ? ( with more additional field to show then the label) Are you interested in the analysis for the text to suggest ? Fuzzy suggestions ? exact "be

Tutorial example loading of exampledocs for *.xml fails due to bad request

I am following the tutorial documentation at http://lucene.apache.org/solr/quickstart.html . I successfully indexed the "docs" folder using the SimplePostTool (Windows, using the Java method). When I attempt the second example, of loading the *.xm

Re: Tutorial example loading of exampledocs for *.xml fails due to bad request

The stack trace says that it is a number format exception, which means that some field which is expecting a numeric value is receiving a non-numeric value. You should check you schema for all the fields pertaining to these docs which are numeric and check those against the docs themselves to ensur

Re: Tutorial example loading of exampledocs for *.xml fails due to bad request

OK, but this content was provided by the people who created the tutorial. Perhaps there is a change in the recent release as the data files need to be modified to work? The tutorial says it is for Solr 5.3 and I am using 5.5. The XML files all seem very simple. Example: SP2514N Samsung

Re: Tutorial example loading of exampledocs for *.xml fails due to bad request

You should check the logs. They'll tell you the exact fields that pose a problem in this case. On Mon, 4 Apr 2016, 19:22 onixterry, wrote: > OK, but this content was provided by the people who created the tutorial. > Perhaps there is a change in the recent release as the data files need to > be

Re: Sorting question

Hi, FYI: the final solution I found is that I created a custom "listpos(fieldName, listId)" function and now I can display a sorted list via: fq=listid_s:378 sort=listpos(listpos_s,378) asc Regards, Tamas On Fri, Apr 1, 2016 at 8:55 PM, John Bickerstaff wrote: > Tamas, > > This feels a bit li

Porting LTR plugin for Solr-5.5.0

I need to use the LTR plugin which compiles for Solr-6.0.0 [here](https://github.com/bloomberg/lucene-solr/tree/master-ltr-plugin-rfc-cpoerschke-comments) I have attempted to port the plugin for Solr-5.5.0 [here](https://github.com/aanilpala/lucene-solr/commit/94ad14c4b9eae2c899e3941967f59b9fc20

Re: Sorting question

Thanks for sharing the solution Tamas -- I was hoping you'd let us know... On Mon, Apr 4, 2016 at 8:05 AM, Tamás Barta wrote: > Hi, > > FYI: the final solution I found is that I created a custom > "listpos(fieldName, listId)" function and now I can display a sorted list > via: > > fq=listid_s:37

Re: Same origin policy for Apache Solr 5.5

Why would you want to do this? On Sun, 3 Apr 2016, at 04:15 AM, Aditya Desai wrote: > Hello SOLR Experts > > I am interested to know if SOLR 5.5 supports Same Origin Policy. I am > trying to read the data from http://localhost:8984/Solr_1/my/directory1 > and > display it on UI on http://localhost

Re: Same origin policy for Apache Solr 5.5

Hello Upayavira I am trying to build an application to get the data from independent stand alone SOLR4.10 and then parse that data on global map. So effectively there are two SOLRs, one is independent(4.10) and the other one is having Map APIs(SOLR 5.10 here). I want to give customers the my entir

SolrCloud backup/restore

I've tested backup/restore successfully in a SolrCloud installation with a single node (no replicas). This has been achieved in https://issues.apache.org/jira/browse/SOLR-6637 Can you do something similar when more replicas are involved? What I'm looking for is a restore command that will restore

Sort order for *:* query

Hi everyone, When I send Solr the query *:* the result I get back is sorted based on Lucene's internal DocID which is oldest to most recent (can someone correct me if I get this wrong?) Given this, the most recently added / updated document is at the bottom of the list. Is there a way to reverse

Re: Sort order for *:* query

1) The hard coded implicit default sort order is "score desc" 2) Whenever a sort results in ties, the final ordering of tied documents is non-deterministic 3) currently the behavior is that tied documents are returned in "index order" but that can change as segments are merged 4) if you wish

Re: Sort order for *:* query

You can sort like this (I believe that _version_ is the internal id/index number for the document, but you might want to verify) In the Admin UI, enter the following in the sort field: _version_ asc You could also put an entry in the default searchHandler in solrconfig.xml to do this to every in

Re: Tutorial example loading of exampledocs for *.xml fails due to bad request

: When I attempt the second example, of loading the *.xml files, I receive an : error back. I tried just one of the XMLs and receive the same error. Yeah ... there's a poor assumption here in the tutorial. note in particular this paragraph... --SNIP-- Solr's install includes a handful of So

Solr 4 replication

Hi all, Is solr 4 replication push or pull? Best Regards, Abhishek

Re: Tutorial example loading of exampledocs for *.xml fails due to bad request

Ah, ok. I was just figuring that out when I stripped everything down to two fields and it was still failing until I put a numeric value in a field called "name". Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Tutorial-example-loading-of-exampledocs-for-xml-fails-du

Re: Sort order for *:* query

: You can sort like this (I believe that _version_ is the internal id/index : number for the document, but you might want to verify) that is not true, and i strongly advise you not to try to sort on the _version_ field ... for some queries/testing it may deceptively *look* like it's sorting by

Re: Sort order for *:* query

On Mon, Apr 4, 2016 at 2:24 PM, Chris Hostetter wrote: > > : You can sort like this (I believe that _version_ is the internal id/index > : number for the document, but you might want to verify) > > that is not true, and i strongly advise you not to try to sort on the > _version_ field ... for some

Re: Solr 4 replication

It's pull, but you can trigger pulling. On Mon, Apr 4, 2016 at 9:19 PM, abhi Abhishek wrote: > Hi all, > Is solr 4 replication push or pull? > > Best Regards, > Abhishek > -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics

RE: using custom analyzer on SolrCloud

Thanks that simplifies things! Creating a lib folder under solr home and placing the customanalyzer.jar there works for me :) I also had to change how I start solr and create the collection, here are the steps I followed after copying 'basic_configs' to 'tdt_configs' in the solr/configsets fo

Parallel Updates

Hi, Does Solr have any sort of limit when attempting multiple updates, from separate clients? Are there any safe thresholds one should try to stay within? I have an index of around 60m documents that gets updated at key points during the day from ~200 downloaded files - I'd like to fork off

Re: Parallel Updates

Will the processes be Solr processes? Or do you mean multiple threads hitting the same Solr server(s)? There will be a natural bottleneck at one Solr server if you are hitting it with a lot of threads - since that one server will have to do all the indexing. I don't know if this idea is helpful,

Re: Parallel Updates

Thanks John, I have 2 shards, 1 replica in each. The issue is the external processing job(s) I have to convert external data into JSON, and then upload it via cURL. Will one Solr server only accept one update at a time and have any others queued? (And possibly timeout). I like the idea of

Re: Parallel Updates

The short answer is - There's no real limit on Solr in terms of concurrency. Here are a few things that would impact your numbers though: * What version of Solr are you using and how ? i.e. SolrCloud, standalone, traditional replication ? * Do you use atomic updates? * How do you index ? Assuming

Re: Sort order for *:* query

: : Not sure I understand... _version_ is time based and hence will give : roughly the same accuracy as something like : TimestampUpdateProcessorFactory that you recommend below. Both Hmmm... last time i looked, i thought _version_ numbers were allocated & incremented on a per-shard basis and "

Re: Sort order for *:* query

On Mon, Apr 4, 2016 at 6:06 PM, Chris Hostetter wrote: > : > : Not sure I understand... _version_ is time based and hence will give > : roughly the same accuracy as something like > : TimestampUpdateProcessorFactory that you recommend below. Both > > Hmmm... last time i looked, i thought _version

Re: Parallel Updates

Does SOLR cloud push indexing across all nodes? I've been planning 4 SOLR boxes with only 3 exposed via the load balancer, leaving the 4th available internally for my microservices to hit with indexing work. I was assuming that if I hit my "solr4" IP address, only "solr4" will do the indexing...

Re: Parallel Updates

Solr would push all updates to all shards that are supposed to host the data. The documents are initially forwarded to the leader of the shard, which can dynamically change and the leader is responsible for versioning and ensuring replication across the followers but other than that, all nodes woul

Re: Parallel Updates

On 4/4/2016 3:46 PM, Robert Brown wrote: > I have 2 shards, 1 replica in each. > > The issue is the external processing job(s) I have to convert external > data into JSON, and then upload it via cURL. > > Will one Solr server only accept one update at a time and have any > others queued? (And poss

Re: Complex Sort

: I am not sure how to use "Sort By Function" for Case. : : |10#40|14#19|33#17|27#6|15#6|19#5|7#2|6#1|29#1|5#1|30#1|28#1|12#0|20#0| : : Can you tell how to fetch 40 when input is 10. Something like... if(termfreq(f,10),40,if(termfreq(f,14),19,if(termfreq(f,33),17,))) But i suspect

solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

hi there, i have an solr 5.2.1, when i do data import, after the job is done, it's shown 165,191 rows processed successfully. but when i query with *:*, the "numFound" shown only 163,349 docs in index. when i tred to do it again, , it's shown 165,191 rows processed successfully. but the *:

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

1) Are you sure you don't have duplicates? 2) All of your records might have been indexed but a new searcher may not have opened on the updated index yet. Try issuing a commit and see if that works. On Tue, 5 Apr 2016, 08:56 cqlangyi, wrote: > hi there, > > > i have an solr 5.2.1, when i do dat

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

The first question is whether you have duplicate ID's in your data set. I had the same kind of thing a few months back, freaked out, and spent a few hours trying to figure it out by coding extra logging etc... to keep track of every single count at every stage of the process.. All the numbers mat

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

Sweet - that's a good point - I ran into that too - I had not run the commit for the last "batch" (I was using SolrJ) and so numbers didn't match until I did. On Mon, Apr 4, 2016 at 9:50 PM, Binoy Dalal wrote: > 1) Are you sure you don't have duplicates? > 2) All of your records might have been

Re: solr 5.2.1, data import issue, shown processed rows doesn't match acturally indexed doc quantity.

Both of us implied it, but to be completely clear - if you have a duplicate ID in your data set, SOLR will throw away previous documents with that ID and index the new one. That's fine if your duplicates really are duplicates - it's not OK if there's a problem in the data set and the duplicates ID

How to Get info about clusterstate in solr 5.2.1 just like ping request handler with distrib=true

Hi, I am using solr 5.2.1 . We need to configure F5 load balancer with zookeepers. For that we need to know whether our cluster as a whole is eligible to serve queries or not. We can get cluster state using ping request handler but in solr 5.2.1 with distrib=true it gives exception(known bug in so