Re: Error about Unsupported major.minor version 52.0

Solr 6.x requires Java 8 - you're using Java 7 (aka JDK 1.7). https://cwiki.apache.org/confluence/display/solr/Installing+Solr Cheers, -Brendan On 10 September 2016 at 19:21, Jiangenbo wrote: > Hello Everyone, > Sorry for disturbing you all > I am facing at a problem when I deploy SOLR 6.

Re: Script to upgrade a Solr index from 4.x to 6.x

Hi Jan, Thanks for the script! I for one will definitely try it out. Can you comment on how battle-tested it is? Are there any limitations or drawbacks? Cheers, -Brendan On Wednesday, 1 June 2016, Jan Høydahl wrote: > Hi > > Need to upgrade from Solr 4.x directly to the new 6.0? > Here is a

Re: Conditional Add/Overwrite a document

Hi Gili, It sounds like Solr's DocBasedVersionConstraintsProcessor is what you are looking for: https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents#UpdatingPartsofDocuments-DocumentCentricVersioningConstraints Cheers, -Brendan On 29 October 2015 at 06:33, Gili Nachum w

Re: Solr Spellalike Feature

Solr's SpellCheck component does what you are looking for. https://cwiki.apache.org/confluence/display/solr/Spell+Checking http://lucidworks.com/blog/getting-started-spell-checking-with-apache-lucene-and-solr/ HTH -Brendan On 27 June 2015 at 14:08, octopus wrote: > Hi, I am new to Solr and w

Re: Solr: Elevate with complex query specifying field names

Hi Thomas, The query elevation component matches queries exactly with entries in elevate.xml. You can nominate a query field type that is used to process the query before matching, but that won't help you when your queries have explicit boosts. Are you using the eDismax query parser? If so, you c

Re: Deep paging in solr using cursorMark

Apologies in advance for hijacking the thread, but somewhat related, does anyone have experience with using cursorMark and elevations at the same time? When I tried this, either passing elevatedIds via solrJ or specifying them in elevate.xml, I got an AIOOBE if a cursorMark was also specified. When

Re: no replication using commitWithin via curl?

I've raised https://issues.apache.org/jira/browse/SOLR-6903 for this, as I consider it a bug. Attached to the JIRA is a modified test demonstrating the failure. The test fails on 5.x and 4.x. Cheers, -Brendan On 30 December 2014 at 13:53, Brendan Humphreys wrote: > Thanks for the rep

Re: no replication using commitWithin via curl?

n. Cheers, -Brendan On 30 December 2014 at 12:57, Shawn Heisey wrote: > On 12/29/2014 4:11 PM, Brendan Humphreys wrote: > > We've noticed that when we send deletes to our SolrCloud cluster via curl > > with the param commitWithin=1 specified, the deletes are applied and

Re: no replication using commitWithin via curl?

On 30 December 2014 at 10:11, Brendan Humphreys wrote: > Hi, > > We've noticed that when we send deletes to our SolrCloud cluster via curl > with the param commitWithin=1 specified, the deletes are applied and > are visible to the leader node, but aren't replicated to ot

no replication using commitWithin via curl?

Hi, We've noticed that when we send deletes to our SolrCloud cluster via curl with the param commitWithin=1 specified, the deletes are applied and are visible to the leader node, but aren't replicated to other nodes. The problem can be worked around by issuing an explicit (hard) "commit". Is

Re: TrieLongField not store large longs correctly

I'd wager this is a loss of precision caused by Javascript rounding in the admin client. More details here: http://stackoverflow.com/questions/1379934/large-numbers-erroneously-rounded-in-javascript Cheers, -Brendan On 27 November 2014 at 11:45, Erick Erickson wrote: > Yep, see my second e-m

ClassCastException using elevations with cursorMark.

Hi Folks, I'd like to switch to using cursorMark for pagination, but I can't get it to work with elevations (Solr 4.10.2 / jdk7 / osx). I try a query like: q=foo&sort=score+desc,id+asc&elevateIds=1234567&cursorMark=* and get an exception: java.lang.ClassCastException: java.lang.Float cannot be