Thank you Walter Under Underwood for a complete honest review.
I will start simple by using the sample.
Regards,LavanyaOn Tuesday, 22 January 2019, 12:31:55 pm AEDT, Walter
Underwood wrote:
There are many, many problems with this analyzer chain definition.
This is a summary of the i
Do you mind if I ask why so many collections rather than a field in one
collection that you can apply a filter query to each customer to restrict the
result set, assuming you’re the one controlling the middle ware?
> On Jan 22, 2019, at 4:43 PM, Monica Skidmore
> wrote:
>
> We have been runni
On 1/22/2019 2:43 PM, Monica Skidmore wrote:
Is anyone successfully running Solr 7x in cloud mode with thousands or more of
collections? Are there some configurations we should be taking a closer look
at to make this feasible? Should we try a different replica type? (We do want
NRT-like que
We have been running Solr 5.4 in master-slave mode with ~4500 cores for a
couple of years very successfully. The cores represent individual customer
data, so they can vary greatly in size, and some of them have gotten too large
to be manageable.
We are trying to upgrade to Solr 7.3 in cloud mo
What do you mean schema.xml from managed-schema? schema.xml is old
non-managed approach. If you have both, schema.xml will be ignored.
I suspect you are not running with the schema you think you do. You can
check that with API or in Admin UI if you get that far.
Regards,
Alex
On Tue, Jan 22,
Hi,
I'm using solr 7.5, in my schema.xml I have this, which I took
from the
managed-schema:
stored="false" />
docValues="true" />
However, on startup, solr complains:
Caused by: org.apache.solr.common.SolrException: _version_ field
must exist in schema and be searchable (indexed or
Hi all,
I have a Solr index which has been evolving since Solr1.4 and now is in
SolrCloud6.6.
This cluster is composed of 4 servers, few collections and shards.
Since first time I deployed to production in 2009 I am using the same
approach to deploy. I think it's probably the time to review and
We're preparing to upgrade from Solr 6.4.2 to Solr 7.6.0, and found an
inconsistency in scoring. It appears that term boosts in the query are not
applied in Solr 7.
The query itself against both versions is identical (removed un-important
params):
("one"^1) OR ("two"^2) OR ("three"^3)
edismax
max
I will certainly try it out. Thanks!
On Mon, Jan 21, 2019 at 8:48 PM Joel Bernstein wrote:
> You find the significantTerms streaming expressions useful:
>
>
> https://lucene.apache.org/solr/guide/7_6/stream-source-reference.html#significantterms
>
>
> Joel Bernstein
> http://joelsolr.blogspot.c
Perhaps you're looking for the traversalFilter parameter of the graph query?
https://lucene.apache.org/solr/guide/7_6/other-parsers.html#graph-query-parser
Dan Meehl
Meehl Technology Solutions Inc
On Tue, Jan 22, 2019 at 7:13 AM Magnus Karlsson wrote:
> Hi,
>
>
> anyone using any of the funct
Hi,
You might want to check out the documentation, which goes over
split-shard in a bit more detail:
https://lucene.apache.org/solr/guide/7_6/collections-api.html#CollectionsAPI-splitshard
To answer your question directly though, no. Split-shard creates two
new subshards, but it doesn't do anyth
i use the following defintion :
< request handler name="my_export" class="solr.exportHandler"
useParams="_EXPORT">
json
false
{!xport}
myComponent
query
and recieve a nullPointerException when the im loading the core. the
exception is at
org.apache.solr.common.params.solrParams.toMultiM
Hi,
anyone using any of the functionality of graphs either in a single collection
(shortest path) or streaming expressions (nodes)?
Experiences?
/ Magnus
Från: Magnus Karlsson
Skickat: den 17 december 2018 14:51:17
Till: solr-user@lucene.apache.org
Ämne: It
Hi,
If I split shard1 to shard1_0,shard1_1, Is the parent shard1 will
never be clean up?
Best,
Tinswzy
Hello,
As described in https://issues.apache.org/jira/browse/SOLR-13126 multiplicative
boots (in certain conditions) seem to be broken since 7.3.
The error seems to be introduced in
https://issues.apache.org/jira/browse/LUCENE-8099. Reverting the SOLR parts to
the now deprecated BoostingQuery a
+1 for the most elegant solution so far :)
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 22. jan. 2019 kl. 03:15 skrev Joel Bernstein :
>
> Streaming Expressions can do this:
>
> plist(stats(collection1, q="*:*", count(*)),
>stats(collection2, q="*:*", cou
16 matches
Mail list logo