RE: Overseer queues confused me
can someone answer my question? Thanks in advance Best Regards, Illu Ying -Original Message- From: Illu.Y.Ying (mis.sh04.Newegg) 41417 [mailto:illu.y.y...@newegg.com] Sent: Wednesday, July 10, 2013 10:44 AM To: solr-user@lucene.apache.org Subject: Overseer queues confused me Hi there： In solr4.3 source code , I found overseer use 3 queues to handle all solrcloud management request: 1: /overseer/queue 2: /overseer/queue-work 3: /overseer/collection-queue-work ClusterStateUpdater use 1st 2nd queue to handle solrcloud shard or state request. When peek request from 1st queue, then offer it to 2nd queue and handle it. OverseerCollectionProcessor use 3rd queue to handle collection related request. My question is why ClusterStateUpdater use 2 queues but OverseerCollectionProcessor use 1 also can handle request correctly? Is there any additional design for ClusterStateUpdater? Thanks in advance:) Best Regards, Illu Ying
Overseer queues confused me
Hi there： In solr4.3 source code , I found overseer use 3 queues to handle all solrcloud management request: 1: /overseer/queue 2: /overseer/queue-work 3: /overseer/collection-queue-work ClusterStateUpdater use 1st 2nd queue to handle solrcloud shard or state request. When peek request from 1st queue, then offer it to 2nd queue and handle it. OverseerCollectionProcessor use 3rd queue to handle collection related request. My question is why ClusterStateUpdater use 2 queues but OverseerCollectionProcessor use 1 also can handle request correctly? Is there any additional design for ClusterStateUpdater? Thanks in advance:) Best Regards, Illu Ying Assistant Supervisor, NESC-SH.MIS +86-021-51530666*41417 Floor 19, KaiKai Plaza, 888, Wanhangdu Rd, Shanghai (200042) ONCE YOU KNOW, YOU NEWEGG. CONFIDENTIALITY NOTICE: This email and any files transmitted with it may contain privileged or otherwise confidential information. It is intended only for the person or persons to whom it is addressed. If you received this message in error, you are not authorized to read, print, retain, copy, disclose, disseminate, distribute, or use this message any part thereof or any information contained therein. Please notify the sender immediately and delete all copies of this message. Thank you in advance for your cooperation. 保密注意：此邮件及其附随文件可能包含了保密信息。该邮件的目的是发送给指定收件人。如果您非指定收件人而错误地收到了本邮件，您将无权阅读、打印、保存、复制、泄露、传播、分发或使用此邮件全部或部分内容或者邮件中包含的任何信息。请立即通知发件人，并删除该邮件。感谢您的配合！
Re: Delete documents in SOLR 1.4.1
I tried your second case with SOLR3.5, It runs fine and the record could be
deleted when you only configure deletedPkQuery.
Could you consider upgrading your SOLR to version 3.5?
Best Regards,
Illu Ying
-邮件原件-
发件人: RPSolrUser [mailto:roopa.parek...@gmail.com]
发送时间: 2012年11月27日 23:49
收件人: solr-user@lucene.apache.org
主题: Delete documents in SOLR 1.4.1
Question: We have Solr 1.4.1 in Production currently. We need to delete
documents identified by ids on daily basis from solr.
--Following deletes by keys and delta data load works--
-- snippet of db-data-config.xml
dataConfig
dataSource name=goodtest driver=oracle.jdbc.OracleDriver
url=jdbc:oracle:thin:@server:port:servicename
user=userid
password=password batchSize =5000/
document
entity name=agreement_master pk=AGREEMENT_KEY dataSource=goodtest
transformer=RegexTransformer,TemplateTransformer,DateFormatTransformer,ClobTransformer,
OracleTimestampTransformer
deletedPkQuery=select AGREEMENT_KEY from solr_part_supplier_agreement_del
query= select AGREEMENT_KEY, bunch of other fieldsFROM
SOLR_part_supplier_agreement
deltaQuery=select AGREEMENT_KEY, bunch of other fields FROM
SOLR_part_supplier_agree_delta
deltaImportQuery=select AGREEMENT_KEY, bunch of other fields FROM
SOLR_part_supplier_agree_delta where AGREEMENT_KEY =
'${dataimporter.delta.AGREEMENT_KEY}'
/entity
/document
/dataConfig
-- snippet of solrconfig.xml
/requestHandler
requestHandler name=/dataimport
class=org.apache.solr.handler.dataimport.DataImportHandler
lst name=defaults
str name=configdb-data-config.xml/str
/lst
/requestHandler
I am invoking Delta-Import using dataimport.jsp. Everything works good.
Delta data (indentifed by SOLR_PART_SUPPLIER_AGREE_DELTA) get indexed and bunch
of documents identified by solr_part_supplier_agreement_del get deleted.
However, I have a need to just delete the documents from another solr core
without loading delta data. How can I achieve that?
-- This does not work. Does not delete any docs as deletedPkQuery is supposed
only work with delta loads -- dataConfig dataSource name=test
driver=oracle.jdbc.OracleDriver
url=jdbc:oracle:thin:@server:port:servicename
user=userid
password=password
/
document
entity name=part_master_del pk=UNIQUE_ID dataSource=test
deletedPkQuery=select part_master_key as UNIQUE_ID
from PART_MASTER_DEL
/entity
/document
/dataConfig
Question: How can I just delete the documents by id? Is deleteDocById the
answer? How can I use it? I tried but the DIH does not show any updates. Can we
use any other approach?
Do I need to patch SOLR 1.4.1 with any bug fix?
Example of deleteDocById is appreciated.
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Delete-documents-in-SOLR-1-4-1-tp4022660.html
Sent from the Solr - User mailing list archive at Nabble.com.
