Re: Query Keyword Storage

Hi Erik, Thank you for the solution. I'll surely give it a try. But I was trying to collect the logs directly from Solr source base (maybe by extending the edismax query parser) because that way I don't have to write query keywords into log files. After that I want to feed that data into Banana

Grouping facets: Possible to get facet results for each Group?

Hello Solr Forum, Been trying to coerce Group faceting to give some faceting back for each group, but maybe this use case isn't catered for in Grouping? : So the Use Case is this: Let's say I do a grouped search that returns say, 9 distinct groups, and in these groups are various numbers of

Re: Solr cross core join special condition

On 10/11/2015 8:01 AM, Ali Nazemian wrote: > I did check the jira issue that you mentioned but it seems its target is > Solr 6! Am I correct? The patch failed for Solr 5.3 due to class not found. > For Solr 5.x should I try to implement something similar myself? Virtually all changes that are

Re: How to show some (paid) documents ahead of others (non-paid) - fantasy scenario

Hi, What if we write all paid results in a new, dedicated, core... let's call it: "PaidResultsCore" and lets call the non-paid results core: "NonPaidResultsCore" When a user asks for "red pepper" we first perform the query upon "PaidResultsCore" and get the first ranking 3 results and then we

Re: Solr cross core join special condition

Dear Susheel, Hi, I did check the jira issue that you mentioned but it seems its target is Solr 6! Am I correct? The patch failed for Solr 5.3 due to class not found. For Solr 5.x should I try to implement something similar myself? Sincerely yours. On Wed, Oct 7, 2015 at 7:15 PM, Susheel Kumar

Re: How to show some (paid) documents ahead of others (non-paid) - fantasy scenario

I think Walter suggested the simplest: make two requests. When you've got both results back, you can stick them together to make results. At present, there is no method to do multiple actions within a single request. Upayavira On Sun, Oct 11, 2015, at 01:38 PM, liviuchrist...@yahoo.com.INVALID

Re: How to show some (paid) documents ahead of others (non-paid) - fantasy scenario

On Sun, Oct 11, 2015 at 3:38 PM, wrote: > Hi, > What if we write all paid results in a new, dedicated, core... let's call > it: "PaidResultsCore" and lets call the non-paid results core: > "NonPaidResultsCore" > When a user asks for "red pepper" we first perform

Re: How to show some (paid) documents ahead of others (non-paid) - fantasy scenario

What about Streaming Expressions? Could they be used here? Disclaimer: I have not used them myself yet. https://cwiki.apache.org/confluence/display/solr/Streaming+Expressions Regards, Alex. Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On

Re: admin-extra

admin-extra allows one to include additional links and/or information in the Solr admin main page: https://cwiki.apache.org/confluence/display/solr/Core-Specific+Tools Bill On Wed, Oct 7, 2015 at 5:40 PM, Upayavira wrote: > Do you use admin-extra within the admin UI? > > If

Re: Solr cross core join special condition

Yes, Ali. These are targeted for Solr 6 but you have the option download source from trunk, build it and try out these features if that helps in the meantime. Thanks Susheel On Sun, Oct 11, 2015 at 10:01 AM, Ali Nazemian wrote: > Dear Susheel, > Hi, > > I did check the

Re: Unexpected delayed document deletion with atomic updates

Hi Allessandro, In the example I set the value to 1, but it's actually incremented in the code, so with time it should go up. You're right though, I could use an inc update instead. John On 08/10/15 16:45, Alessandro Benedetti wrote: > Not related to the deletion problem, only as a curiosity

Indexing logs when using post,jar

Hi, I am using Solr 5.3.0, and I would like to find out, is the logs for the indexing using post.jar stored anywhere in Solr? I would need to know which files has been successfully indexed and which has not, so that I can re-run the indexing for those files which has not been indexed