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
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
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
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 octroll...@gmail.com wrote:
Hi, I
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
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.
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 bren...@canva.com wrote:
Thanks
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
December 2014 at 10:11, Brendan Humphreys bren...@canva.com 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 other nodes
,
-Brendan
On 30 December 2014 at 12:57, Shawn Heisey apa...@elyograg.org 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
are visible
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 erickerick...@gmail.com
wrote:
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=foosort=score+desc,id+ascelevateIds=1234567cursorMark=*
and get an exception:
java.lang.ClassCastException: java.lang.Float cannot be
12 matches
Mail list logo