First of all thank you for the repsonses/ideas.
The plain idea is to boost products that are sold more for a specific
customer.
I'll discuss this with my customer to see if we can start with limited
functionality as suggested by Walter.
Cheers,
Jan.
On 5 February 2016 at 17:33, Walter Und
Shawn - this worked great!
I reloaded the collection, the nodes recovered and it seems to work great
now.
Thank you,
Aki
On Thu, Feb 4, 2016 at 7:10 PM, Shawn Heisey wrote:
> On 2/4/2016 2:12 PM, Aki Balogh wrote:
> > I found the state.json file and it indeed shows that the range for shard1
>
It looked like there was another issue with my query. I had too many
boolean operators (I believe maxBooleanClause property in SolrConfig.xml).
I just looped in batch of 1000 to get all the docs. Not sure if there is a
better way of handling this.
Regards,
Salman
On Wed, Feb 3, 2016 at 12:29 AM,
And you're sure that you can't use the terms query parser, which was
explicitly designed for handling a very long list of terms to be implicitly
ORed?
-- Jack Krupansky
On Sat, Feb 6, 2016 at 2:26 PM, Salman Ansari
wrote:
> It looked like there was another issue with my query. I had too many
>
GET request length is limited by URL length. RFCs defining HTTP recommend
you keep it under 8KB but put no hard limit in place.
Because of no hard limit it boils down to the implementation - both on the
server side and client side:
- On client side Internet Explorer is limited to about 2KB for exam
On 2/6/2016 2:47 PM, Maciej Lisiewski wrote:
> GET request length is limited by URL length. RFCs defining HTTP recommend
> you keep it under 8KB but put no hard limit in place.
> Because of no hard limit it boils down to the implementation - both on the
> server side and client side:
> - On client
