Hi,
I have a collection with 2 TLOG and 6 PULL replicas. When one of the pull
nodes dies and is replaced with a new instance. It is being replaced by an
NRT replica in the collection (the desired action is to be replaced by a
PULL replica).
collection is being created by
collections?action=CREA
Thank you for the reply. Sorry I did not include more information in the first
post.
So maybe there's some confusion here from my end. So both the target and source
clusters are running in cloud mode. So I think you're correct that it is a
different issue. So it looks like the source leader to
Thank you for the reply. Sorry I did not include more information in the
first post.
So maybe there's some confusion here from my end. So both the target and
source clusters are running in cloud mode. So I think you're correct that it
is a different issue. So it looks like the source leader to ta
If you absolutely want to use Kafka after trying other mechanisms, I would
suggest Kafka Connect. Jeremy Custenborder has a good Kafka connector as a
sink to SOLR. You can define your own avro schemas on the Kafka topic that
adhere to your SOLR schema to give you that degree of control.
We have us
Depending on how complicated you need this to be, you can just write
your own in SolrJ, see:
https://lucidworks.com/2012/02/14/indexing-with-solrj/
You haven't said a lot about the characteristics of your situation.
Are you talking 1B rows
from the DB? 1M? what is the pain point? Because until on
Clean your data. The whole point of that limitation is that it makes
no sense to try to index a 32K field for _searching_ anyway. By
"index" here, I mean have a _token_ in your index that you can search.
Storing it away with stored="true" field is another matter.
Best,
Erick
On Thu, Jan 31, 2019
I think you're making this much more difficult for yourself than necessary.
I'd _strongly_ recommend you abandon this approach and use the
collections AP. Perhaps you'd need to create some kind of script
that handles core creation and the like. If you know where the
core.properties file should be
CDCR does _not_ replicate to followers, it is a leader<->leader replication
of the raw document.
Once the document has been forwarded to the target's leader, then the
leader on the target system should forward it to followers on that
system just like any other update.
The Solr JIRA is unlikely th
1> please don't hijack threads, start a new topic
2> Please follow the instructions here:
http://lucene.apache.org/solr/community.html#mailing-lists-irc. You
must use the _exact_ same e-mail as you used to subscribe.
If the initial try doesn't work and following the suggestions at the
"problems"
