You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Markus Jelsma (JIRA)" <ji...@apache.org> on 2011/06/30 18:17:28 UTC
[jira] [Created] (NUTCH-1025) Add option not to commit to Solr
Add option not to commit to Solr
--------------------------------
Key: NUTCH-1025
URL: https://issues.apache.org/jira/browse/NUTCH-1025
Project: Nutch
Issue Type: Improvement
Components: indexer
Affects Versions: 2.0
Reporter: Markus Jelsma
Assignee: Markus Jelsma
Priority: Minor
Fix For: 2.0
We need an option to prevent a job from sending a commit to Solr. A commit can take a lot of resources (cache warming) and it's not always necessary to commit after index, dedup or clean, especially if they are run immediately after the other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NUTCH-1025) Add option not to commit to Solr
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma reassigned NUTCH-1025:
------------------------------------
Assignee: (was: Markus Jelsma)
> Add option not to commit to Solr
> --------------------------------
>
> Key: NUTCH-1025
> URL: https://issues.apache.org/jira/browse/NUTCH-1025
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Affects Versions: 2.0
> Reporter: Markus Jelsma
> Priority: Minor
> Fix For: 2.0
>
>
> We need an option to prevent a job from sending a commit to Solr. A commit can take a lot of resources (cache warming) and it's not always necessary to commit after index, dedup or clean, especially if they are run immediately after the other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NUTCH-1025) Add option not to commit to Solr
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney updated NUTCH-1025:
----------------------------------------
Fix Version/s: (was: nutchgora)
2.1
Set and Classify
> Add option not to commit to Solr
> --------------------------------
>
> Key: NUTCH-1025
> URL: https://issues.apache.org/jira/browse/NUTCH-1025
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Affects Versions: nutchgora
> Reporter: Markus Jelsma
> Priority: Minor
> Fix For: 2.1
>
>
> We need an option to prevent a job from sending a commit to Solr. A commit can take a lot of resources (cache warming) and it's not always necessary to commit after index, dedup or clean, especially if they are run immediately after the other.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NUTCH-1025) Add option not to commit to Solr
Posted by "Ferdy Galema (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ferdy Galema resolved NUTCH-1025.
---------------------------------
Resolution: Fixed
Fixed per NUTCH-1306.
> Add option not to commit to Solr
> --------------------------------
>
> Key: NUTCH-1025
> URL: https://issues.apache.org/jira/browse/NUTCH-1025
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Affects Versions: nutchgora
> Reporter: Markus Jelsma
> Priority: Minor
> Fix For: 2.1
>
>
> We need an option to prevent a job from sending a commit to Solr. A commit can take a lot of resources (cache warming) and it's not always necessary to commit after index, dedup or clean, especially if they are run immediately after the other.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira