Re: URI is too long

On 1/31/2016 7:20 AM, Salman Ansari wrote: > I am building a long query containing multiple ORs between query terms. I > started to receive the following exception: > > The remote server returned an error: (414) Request-URI Too Long. Any idea > what is the limit of the URL in Solr? Moreover, as a

Re: MLT Component only returns ID and score

Thanks for the info, does this replace the mlt component? ie, can I remove that component from being loaded/used? These are my parameters, the results look okay, just want to ensure I'm using it right... fq => [ 'market:uk' ], q =>

Re: Determine if Merge is triggered in SOLR

Hi All, any suggestions/ ideas? Thanks, Abhishek On Tue, Jan 26, 2016 at 9:16 PM, abhi Abhishek wrote: > Hi All, > is there a way in SOLR to determine if a merge has been triggered in > SOLR? is there a API exposed to query this? > > if its not available is there a

Re: Determine if Merge is triggered in SOLR

You would have to implement your own MergeScheduler that wrapped an existing merge scheduler and then save the merge info and then write a custom request handler to retrieve that saved info. See: https://lucene.apache.org/core/5_4_1/core/org/apache/lucene/index/MergeScheduler.html

Re: Executing Collector's Collect method on more than one thread

Before thinking at all about threads you might try to speeding things up with your implementation. In particular your call to the top level docValues is going to be very slow. The way to speed this up is to switch to the segment level doc value at each segment switch. That way you avoid the rather

Re: Full Indexing is geeting failed with hybris application

Manoj - the log attachments don’t come through on the listserv. Did you upgrade all nodes in your system? What version of Solr is running? — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com > On Jan 31, 2016, at 1:12 PM, Manoj Agrawal

RE: Which version of java is preferrable to install on a Red Hat Enterprise Linux 7?

Thanks a lot, Oracle Java 8 and is the version that I usually use, and I install a standard JRE. Thanks again. -- Gian Maria Ricci Cell: +39 320 0136949 -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: mercoledì 27 gennaio 2016 16:07 To:

Re: URI is too long

Or try the terms query parser that lets you eliminate all the OR operators: https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-TermsQueryParser -- Jack Krupansky On Sun, Jan 31, 2016 at 9:23 AM, Paul Libbrecht wrote: > How about using POST? > > paul

MLT Component only returns ID and score

Hi, I've had to switch to using the MLT component, rather than the handler, since I'm running on Solrcloud (5.4) and if I hit a node without the starting document, I get nothing back. When I perform a MLT query, I only get back the ID and score for the similar documents, yet my fl=*,score.

Re: Memory leak defect or misssuse of SolrJ API?

I already answered this. Move the creation of the HttpSolrClient outside the loop. Your code will run much fast, because it will be able to reuse the connections. Put another way, your program should have exactly as many HttpSolrClient objects as there are servers it talks to. If there is one

RE: Monitor backup progress when location parameter is used.

Thanks for the link, I'll have a look as soon as possible. -- Gian Maria Ricci Cell: +39 320 0136949 -Original Message- From: KNitin [mailto:nitin.t...@gmail.com] Sent: domenica 31 gennaio 2016 19:35 To: solr-user@lucene.apache.org Subject: Re: Monitor backup progress when

Re: Full Indexing is geeting failed with hybris application

Hi, One more thing i observed that i have multiple cores and after running the indexing for a particualr core but all the core are indexednign as per log. -Manoj On Sun, Jan 31, 2016 at 10:32 AM, Manoj Agrawal wrote: > Hi Erik, > > Thanks for helping on this! i

Re: Memory leak defect or misssuse of SolrJ API?

Thanks Walter. Yes, I saw your answer and fixed the issue per your suggestion. The JavaDoc need to make this clear. The fact there is a close() on this class and the JavaDoc does not say "your program should have exactly as many HttpSolrClient objects as there are servers it talks to" is a

Re: Increasing maxMergedSegmentMB value

Make sure you fully digest Mike McCandless' blog post on segment merge before trying to outguess his code: http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html Generally, I don't think you would want to merge just two segments. Generally, you should do a bunch at a time,

Re: User-defined properties and configsets

Ah,OK. There's no mechanism that I know of for that. I'd guess system properties wouldn't even work as two cores in the same JVM would potentially want different values for the same embedded system variable if they used different configsets. So I think you're stuck at present with specifying the

Re: Memory leak defect or misssuse of SolrJ API?

The JavaDoc needs a lot more information. As I remember it, SolrJ started as a thin layer over Apache HttpClient, so the authors may have assumed that programmers were familiar with that library. HttpClient makes a shared object that manages a pool of connections to the target server.

Re: Monitor backup progress when location parameter is used.

You can also checkout : https://github.com/bloomreach/solrcloud-haft for doing backup and restore of your solrcloud collections. On Fri, Jan 15, 2016 at 12:23 AM, Gian Maria Ricci - aka Alkampfer < alkamp...@nablasoft.com> wrote: > Ok thanks, I also think that it's worth a jira, because for

Re: MLT Component only returns ID and score

Try the MLT query parser, which is a much newer way of doing this. Perhaps it will work better for you. Upayavira On Sun, Jan 31, 2016, at 06:31 PM, Robert Brown wrote: > Hi, > > I've had to switch to using the MLT component, rather than the handler, > since I'm running on Solrcloud (5.4) and

Re: Memory leak defect or misssuse of SolrJ API?

Thank you all for your feedback. This is code that I inherited and the example i gave is intended to demonstrate the memory leak which based on YourKit is on java/util/LinkedHashMap$Entry. In short, I'm getting core dumps with "Detail "java/lang/OutOfMemoryError" "Java heap space" received "

Re: URI is too long

Cool. I would give POST a try. Any samples of using Post while passing the query string values (such as ORing between Solr field values) using Solr.NET? Regards, Salman On Sun, Jan 31, 2016 at 10:21 PM, Shawn Heisey wrote: > On 1/31/2016 7:20 AM, Salman Ansari wrote: > > I

Re: implement exact match for one of the search fields only?

> In our case we want to boost exact search ( not phrase search). > Simply adding the copy field not tokenised with the related boost to the > qf list should be fine. > Am I missing something ? Please try it out and report back. You’ll find that the “qf” param will only ever produce matches for

Re: Nested documents and many-many relation

Thanks, query time joins are not an option for me, because of the size of the index and hence the join performance, I will look at Siren. On 29/01/16, 10:16 PM, "Alessandro Benedetti" wrote: >Probably if you are interested in a many-to-many relation, you could be

CorruptIndexException during optimize.

Hi, Got following error during optimize of index on 2 nodes of 12 node cluster. Please let me know if the index can be recovered and how and what could be the reason? Total number of nodes: 12 No replica. Solr version - 5.4.0 Java version - 1.7.0_91 (Open JDK 64 bit) Ubuntu version : Ubuntu

Re: Full Indexing is geeting failed with hybris application

one more issue i am getting in solr is as below. how can i fix that issue. INFO | jvm 1| main| 2016/01/31 22:04:33.471 | ERROR [solr indexer thread] [10.240.2.252] (Hagemeyerce) (3N68) [RexelSolrDocumentFactory] Cannot resolve values for item with PK: 8814537801729 by

Re: Full Indexing is geeting failed with hybris application

yes, we updated all the nodes. we are using solr 4.6 as part of upgrade , we have cloned the solr server of and their configuration. On Sun, Jan 31, 2016 at 3:21 PM, Erik Hatcher wrote: > Manoj - the log attachments don’t come through on the listserv. Did you > upgrade

Re: Increasing maxMergedSegmentMB value

Hi Jack, Yes, I plan to merge all the 10GB segments to 20GB, and not just two of the segments. Sorry for the confusion. I have recently increased the system memory from 64GB to 192GB, but as our index size grows (which means more segments are created), I found that the query speed actually slow

Re: Full Indexing is geeting failed with hybris application

thanks Erik! On Sun, Jan 31, 2016 at 7:12 PM, Erik Hatcher wrote: > This needs to be addressed by hybris support - it's in one of their custom > components. > > > On Jan 31, 2016, at 19:53, Manoj Agrawal > wrote: > > > > one more issue i am

Solr-8496

Hi I am just starting off on a project (using solr 5.4) which uses multi select faceting as one of the key features. Should I wait till solr 5.5 is released and resolves the issue outlined in solr-8496? Is there a recommended version I should be using? Is there an ETA on when will 5.5 be

Handling fields used for both display & index

Hi, I am trying to decide if I should use text_en or string as my field type. The fields have to be both indexed and stored for display. One solution is to duplicate fields, one for indexing other for display.One of the field happens to be a description field which I would like to avoid

Re: Handling fields used for both display & index

Hi Jay, You could use one field for both unless there is a specific requirement you are looking for that is not being met by that one field (e.g. faceting, etc). Typically, if you have a field that is marked as both "indexed" and "stored", the value that is passed while indexing to that field is

Re: Full Indexing is geeting failed with hybris application

This needs to be addressed by hybris support - it's in one of their custom components. > On Jan 31, 2016, at 19:53, Manoj Agrawal wrote: > > one more issue i am getting in solr is as below. how can i fix that issue. > > INFO | jvm 1| main| 2016/01/31

Re: Handling fields used for both display & index

Adding to sameer's answer, use string types when you want exact matches, both in terms of query and case. In case you want to perform additional operations on the input, like tokenization and applying filters, then you're better off with one of the other text types. You should take a look at the

Re: User-defined properties and configsets

Erick Erickson schrieb am Fr., 29. Jan. 2016 um 17:55 Uhr: > These are system properties, right? They go in the startup for all of > your Solr instances scattered about your cluster. > No, they will be used in the solrconfig.xml and schema.xml. I just mentioned the

Re: Full Indexing is geeting failed with hybris application

Manoj - looks like the master isn’t available? Did you start up all nodes? As a related aside - I/we/Lucidworks have done some hybris/Solr/Fusion work, so if you need any assistance let us know. — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com

Re: Full Indexing is geeting failed with hybris application

Hi Erik, Thanks for helping on this. But i cheked all the nodes are alreday started. but i am getting this error. Please see the error coming in the solr loggin. Master Solr- [image: Inline image 1] Slave Solr- [image: Inline image 2] On Sun, Jan 31, 2016 at 9:51 AM, Erik Hatcher

URI is too long

Hi, I am building a long query containing multiple ORs between query terms. I started to receive the following exception: The remote server returned an error: (414) Request-URI Too Long. Any idea what is the limit of the URL in Solr? Moreover, as a solution I was thinking of chunking the query

Executing Collector's Collect method on more than one thread

I am using RankQuery to implement my applicative scorer that returns a score based on the value of specific field (lets call it 'score_field') that is stored for every document. The RankQuery creates a collector, and for every collected docId I retrieve the value of score_field, calculate the

Re: URI is too long

How about using POST? paul > Salman Ansari > 31 January 2016 at 15:20 > Hi, > > I am building a long query containing multiple ORs between query terms. I > started to receive the following exception: > > The remote server returned an error: (414) Request-URI Too

Full Indexing is geeting failed with hybris application

Hi Team, We have migrated our application from hybris version 5.2 to version 5.5.1.4 and we are using solr version 4.6. After running the full indexing , below error is coming in the application log. Could anyone help me on this . I can give also give you more information on this as well.

Full Indexing is geeting failed with hybris application

Hi Team, We have migrated our application from hybris version 5.2 to version 5.5.1.4 and we are using solr version 4.6. After running the full indexing , below error is coming in the application log. Could anyone help me on this . I can give also give you more information on this as well.

Re: Increasing maxMergedSegmentMB value

Thanks for your reply Shawn and Jack. I wanted to increase the segment size to 15GB, so that there will be lesser segments to search for during the query, which should potentially improve the query speed. What if I set the segment size to 20GB? Will all the existing 10GB segments be merge to