You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Alexandre Rafalovitch (Jira)" <ji...@apache.org> on 2019/10/07 01:07:00 UTC
[jira] [Resolved] (SOLR-1828) DIH Handler separate connection for
delta and full index
[ https://issues.apache.org/jira/browse/SOLR-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch resolved SOLR-1828.
-----------------------------------------
Resolution: Abandoned
This ancient issue does not seem to be relevant to either the current clustering approach, or current methods of injesting data (DIH is not recommended anymore). And it is definitely not "major" at this point.
Marking it as resolved.
> DIH Handler separate connection for delta and full index
> --------------------------------------------------------
>
> Key: SOLR-1828
> URL: https://issues.apache.org/jira/browse/SOLR-1828
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
> Affects Versions: 1.4
> Environment: Linux
> Reporter: Bill Bell
> Priority: Major
>
> We would like to configure the DIH handler for a SLAVE connection for FULL imports, and a MASTER connection for DELTA.
> Use case:
> 1. The DIH full index slams the database pretty hard, and we would like those to run one a day on the SLAVE MYSQL connection.
> 2. The DIH delta index does not hit the database very hard, and we would like that to run off the MASTER MYSQL connection.
> Currently the DIH handler does not allow a name="db-1" on the deltaQuery="", it is only at the entity level. Please add it to each delta, full, etc as an option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org