[
https://issues.apache.org/jira/browse/SOLR-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971125#action_12971125
]
Hoss Man commented on SOLR-2229:
--------------------------------
Marcin: using the example-DIH setup on the Solr 3x branch, i can not reproduce
the behavior you describe.
Steps i used:
1) in the examples directory run: "java -Dsolr.solr.home=example-DIH/solr -jar
start.jar"
2) load the URL "http://localhost:8983/solr/rss/dataimport?command=full-import";
to trigger full import in the rss core
3) verify documents were indexed using
"http://localhost:8983/solr/rss/select/?q=*%3A*";
4) load the URL "http://localhost:8983/solr/db/dataimport?command=full-import";
to trigger full import in the db core
5) verify documents were indexed using
"http://localhost:8983/solr/db/select/?q=*%3A*";
6) verify documents are still in the rss core by force reloading the URL from
#3.
nothing i did using DIH in one core affected the index in the other core.
w/o more info baout your configs, my best guess is that when you say "second
index" what you really mean is is that you have multiple DIH configs (or
entities) in a single SolrCore (ie: index) and you are running multiple
full-import commands.
DIH has a "clean" param which is documented to default to "true" on full-import
-- it deletes all docs from the index (of your current SolrCore) .. i think
that's may be what's confusing you.
please post a followup with more details to the solr-user mailing list if you
are still confused and having problems -- no need to worry about filing a Jira
until people on the user list have been able to help you verify it's a
reproducabile bug and not a missunderstanding in your configs
> DIH run on one index cause all others index's data to be deleted
> ----------------------------------------------------------------
>
> Key: SOLR-2229
> URL: https://issues.apache.org/jira/browse/SOLR-2229
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
> Affects Versions: 3.1, 4.0
> Environment: centos 5.4, tomcat 7.0.2, jdbc mysql connector
> Reporter: Marcin Rosinski
> Priority: Blocker
> Fix For: 3.1, 4.0
>
>
> Hi guys,
> sorry for posting this 3rd time, but I have realized what is causing this bug
> and how to repeat it.
> Tried on 3.1 and 4.0, exactly same issue on both.
> OK, once you run DIH on your forst index all is fine, but if you have second
> index then run DIH on second index cause first index's data to be completely
> deleted.
> Have been running DIH simultaneously before that;s why thought its unrelated
> but it was the last committed DIH which caused all other indexes data to be
> deleted.
> cheers,
> /Marcin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
