Hi,
I'm using in JoinBlock query - {!parent which="is_parent:true"}
I need to return the most relevant child for each parent.
I saw in Google there two options for this:
1. Expand
2. ChildDocTransformerFactory
what the difference between them? which one I need to use?
Thanks a lot,
Michael
As Shawn correctly stated, I see nothing strange in the input the More Like
This. I could not think a better input to be honest for this functionality.
You can potentially attach the MLT Component to your search request
handler, to run the MLT on each search result, but I discourage you to do
that,
Hi,
I'm new to Solr so maybe I don't understand Solr cluster right. I would
like to create a two-node cluster and the system should work if one of the
nodes is down.
I created a collection in a node and set the other as replication. Now when
I open Cloud Graph I can see that one of the nodes is L
[child] doesn't allow to score children. You may try SOLR-8208.
On Thu, Apr 7, 2016 at 10:30 AM, michael solomon
wrote:
> Hi,
> I'm using in JoinBlock query - {!parent which="is_parent:true"}
> I need to return the most relevant child for each parent.
> I saw in Google there two options for this
Maybe I should ask a question instead how to set up a two-node solr cluster
where both nodes contains the same data (collections are replicated to the
other) and if I shut down one of the nodes the other node will work and i
can send updates and queries to it. Is it possible?
On Thu, Apr 7, 2016 a
Afaik the quorum has to be in majority for cluster to be active. With 2
servers, a new leader cannot be selected by minority of less than 50% servers.
Since you have just 2, so quorum is not reached for leader selection. That's
why it is adviced to run odd number of nodes and minimum is 3. Hope
Thanks, as soon as I set up a third ZK server, it works like a charm.
On Thu, Apr 7, 2016 at 1:02 PM, prabhat singh wrote:
> Afaik the quorum has to be in majority for cluster to be active. With 2
> servers, a new leader cannot be selected by minority of less than 50%
> servers. Since you have j
Any comments regarding the issue I mentioned above "the proper procedure of
bringing old collections up after a restart of zookeeper ensemble and Solr
instances"?
Your feedback is appreciated.
Regards,
Salman
On Tue, Mar 29, 2016 at 12:04 PM, Salman Ansari
wrote:
> Moreover, I have created tho
On 4/7/2016 5:04 AM, Tamás Barta wrote:
> Thanks, as soon as I set up a third ZK server, it works like a charm.
The advice to run three servers minimum really only applies to
zookeeper. You can run two Solr servers in your cloud and have no
problems with redundancy, although if you do not have cl
On 4/7/2016 5:40 AM, Salman Ansari wrote:
> Any comments regarding the issue I mentioned above "the proper procedure of
> bringing old collections up after a restart of zookeeper ensemble and Solr
> instances"?
What precisely do you mean by "old collections"? The simplest
interpretation of that i
Thanks Alexandre
I didn't knew theese projects, and they could be a solution to my problem.
Thanks again.
El 02/04/2016 a las 1:10, Alexandre Rafalovitch escribió:
You may be interested in checking out:
http://luxdb.org/ - seems to be still on Solr 4.x though
http://siren.solutions/siren/overv
Hi all,
I'm trying to set the maxBooleanClauses parameter in solrconfig.xml to 1024
but I still have "Too many boolean clauses" error even with 513 terms (with
512 terms it works).
I've read in the documentation (
https://cwiki.apache.org/confluence/display/solr/Query+Settings+in+SolrConfig)
the wa
On 4/7/2016 8:05 AM, Zaccheo Bagnati wrote:
> I'm trying to set the maxBooleanClauses parameter in solrconfig.xml to 1024
> but I still have "Too many boolean clauses" error even with 513 terms (with
> 512 terms it works).
> I've read in the documentation (
> https://cwiki.apache.org/confluence/dis
Edismax phrase-boost terms?
-- Jack Krupansky
On Thu, Apr 7, 2016 at 10:28 AM, Shawn Heisey wrote:
> On 4/7/2016 8:05 AM, Zaccheo Bagnati wrote:
> > I'm trying to set the maxBooleanClauses parameter in solrconfig.xml to
> 1024
> > but I still have "Too many boolean clauses" error even with 513
No SolrCloud. however I've found the problem (though the reason it is not
completely clear to me).
I was passing terms as
field:("term1" "term2",,,)
I simply changed it as
field:(term1 term2 ...) and it worked as expected
I'm not so expert in reading debugQuery output but parsed_filter_queries
val
My gut instinct is that it's a hard path you're considering. There is the
logistics of sharding by document similarity on both the indexing side and
query side. Even if you pull that off, it would be extremely difficult to
know if you're getting good results and really hard to fix if you're not
get
I am working with new solr feature: facet heatmaps. It works great, i
create clusters on my map with counts. When user click on cluster i zoom in
that area and i might show him more clusters or documents (based on current
zoom level).
But all my cluster icons (i use round one, see screenshot below
What does your configuration file look like for the replication
handler? Does this happen whenever you restart a slave even if
_nothing_ has changed on the master?
And this will certainly happen if you're optimizing the master before
you restart, although that doesn't sound likely.
Best,
Erick
O
Hmmm, perhaps your running embedded Zookeeper? You should _not_ have
to run a third Zookeeper, but if you're only running two Zookeepers
_both_ must be up for SolrCloud to function. I often run with exactly
one _external_ zookeeper when developing locally.
So what it sounds like is that you're run
Hi there,
My team has been using Solr 4 on a large distributed system and we are
interested in upgrading to Solr 6 when the new version is released to
leverage some of the new features, such as graph queries. Is anyone able
to provide any insight as to the release schedule for this new version?
The release vote just passed, 6.0 should be released in a very few days.
Best,
Erick
On Thu, Apr 7, 2016 at 8:48 AM, Ben Earley wrote:
> Hi there,
>
> My team has been using Solr 4 on a large distributed system and we are
> interested in upgrading to Solr 6 when the new version is released to
>
Hi Ben,
The vote for 6.0 just passed about an hour ago and it should just a matter
of at the most 3-4 days depending on the availability of the release
manager before the artifacts are published to all mirrors and the official
note is sent out.
On Thu, Apr 7, 2016 at 8:48 AM, Ben Earley wrote:
Do you need to preserve your index data or are you able to fully re-index
all data from scratch? If the former, you will need to upgrade from 4 to 5
first, then force a full optimize to fully upgrade all index segments to 5
format, and then upgrade from 5 to 6. In fact, if you had originally
upgrad
No, I have two (now three) external zookeeper.
We have two Solr nodes and two JBoss nodes, each of them in different
machines. How many Zookeeper server should I start and on which machines
for better performance and for better HA?
2016. ápr. 7. du. 6:00 ezt írta ("Erick Erickson" ):
> Hmmm, perh
Congratulations.
Does this release mandate minimum JDK 1.8?
Thanks
Bosco
On 4/7/16, 9:11 AM, "Anshum Gupta" wrote:
>Hi Ben,
>
>The vote for 6.0 just passed about an hour ago and it should just a matter
>of at the most 3-4 days depending on the availability of the release
>manager before
On 4/7/2016 11:17 AM, Don Bosco Durai wrote:
> Does this release mandate minimum JDK 1.8?
JRE 1.8. The JDK is not required unless you want to build Solr from source.
Thanks,
Shawn
gotcha, thanks for the response. will check {!boost} out for now and start
working on moving our current query builders to a dismax/edismax
configuration.
best,
--
*John Blythe*
Product Manager & Lead Developer
251.605.3071 | j...@curvolabs.com
www.curvolabs.com
58 Adams Ave
Evansville, IN 477
Thanks Shawn and Alessandro. I get the part why id is needed. I was trying to
compare with the "mlt" request handler which doesn't enforce such
constraint. My previous example of title/keyword is not the right one, but I
do have fields which are unique to each document and can be used as a key to
e
Thanks for the reply.
I easily re produced it in my "sandbox" env. Steps to re produce
1. Setup a master
2. Setup a slave in a different server
3. The slave replicated the master index
4. From now on not even a single document is added. No optimization or what
so ever is done on the master or sla
Hi folks,
New Solr user here, attempting to apply the following Solr update command via
curl
curl 'my-solr-server:8983/solr/my-core/update?commit=true' \
-H 'Content-type:application/json' -d \
'[{"my_id_field":"some-id-value","my_other_field":{"set":"new-field-value"}}]'
I'm getting an err
hat's a strainge error to get.
I can't explain why LinuxFileSystem can't load LinuxNativeDispatcher, but
you can probably bypass hte entire situation by explicitly configuring
ConcurrentMergeScheduler with defaults so that it doesn't try determine
wether you are using an SSD or "spinning" disk
Hmm, I wonder whether I *am* using an SSD or spinning disk, in Apache. :) I
guess I can try to find out.
I forgot to mention, this is with Solr 5.2.1 — is that likely to make much
difference?
--
David Moles
UC Curation Center
California Digital Library
On 4/7/16, 4:19 PM, "Chris Host
Hi All ,
we are moving from master slave architecture to solr cloud architecture .
so i would like to know following
- what kind of challenges we can face on production .
- Is there any drawback of solrcloud
- How solr cloud distributes requests between nodes and how node will
behave on hea
33 matches
Mail list logo
