You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (Created JIRA)" <ji...@apache.org> on 2012/02/20 15:59:34 UTC
[jira] [Created] (SOLR-3146) Create migration guide from 3.x to 4.0
Create migration guide from 3.x to 4.0
--------------------------------------
Key: SOLR-3146
URL: https://issues.apache.org/jira/browse/SOLR-3146
Project: Solr
Issue Type: Task
Components: documentation
Reporter: Jan Høydahl
Fix For: 4.0
Spinoff from SOLR-3141:
{quote}
Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!
{quote}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3146) Create migration guide from 3.x to
4.0
Posted by "Jan Høydahl (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211900#comment-13211900 ]
Jan Høydahl commented on SOLR-3146:
-----------------------------------
Perhaps a page on the WIKI, and when mature, move to CMS?
> Create migration guide from 3.x to 4.0
> --------------------------------------
>
> Key: SOLR-3146
> URL: https://issues.apache.org/jira/browse/SOLR-3146
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jan Høydahl
> Fix For: 4.0
>
>
> Spinoff from SOLR-3141:
> {quote}
> Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!
> {quote}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3146) Create migration guide from 3.x to
4.0
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501206#comment-13501206 ]
Otis Gospodnetic commented on SOLR-3146:
----------------------------------------
Is this still needed, considering Solr 4.0 has been out for a over a month now and we haven't seen a ton of issues...?
> Create migration guide from 3.x to 4.0
> --------------------------------------
>
> Key: SOLR-3146
> URL: https://issues.apache.org/jira/browse/SOLR-3146
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jan Høydahl
> Fix For: 4.1
>
>
> Spinoff from SOLR-3141:
> {quote}
> Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3146) Create migration guide from 3.x to
4.0
Posted by "Yonik Seeley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211918#comment-13211918 ]
Yonik Seeley commented on SOLR-3146:
------------------------------------
So I've thought about changing to soft commits by default too. Here's the issue:
People use commit to make their recent updates visible (and a NRT softCommit would now be most appropriate).
But commit also flushes all segments to disk and syncs them, and in a master-slave scenario causes index changes to be replicable.
One possibility is to add a softCommit default of true to the normal update handlers.
People migrating an existing solrconfig wouldn't get that default, but new users (or users starting from scratch with the new solrconfig would).
I don't know if it's worth it or not though. Thoughts?
> Create migration guide from 3.x to 4.0
> --------------------------------------
>
> Key: SOLR-3146
> URL: https://issues.apache.org/jira/browse/SOLR-3146
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jan Høydahl
> Fix For: 4.0
>
>
> Spinoff from SOLR-3141:
> {quote}
> Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!
> {quote}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3146) Create migration guide from 3.x to
4.0
Posted by "Torin Danil (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212469#comment-13212469 ]
Torin Danil commented on SOLR-3146:
-----------------------------------
I think there are a lot of features in upcoming lucene4: starting with NRTManager, and ending with automata support (with whole shebang of regexp queries, fast fuzzy and spellcheck)
All of these need to have hooks in SOLR (I might be mistaken, but from what I've seen in trunk, those are completely missing)
So I think it's acceptable that old solr users won't get new features, just some sane defaults, but to experience the full power of new release will be required to migrate.
> Create migration guide from 3.x to 4.0
> --------------------------------------
>
> Key: SOLR-3146
> URL: https://issues.apache.org/jira/browse/SOLR-3146
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jan Høydahl
> Fix For: 4.0
>
>
> Spinoff from SOLR-3141:
> {quote}
> Perhaps an official migration guide on the CMS would be helpful too when 4.0 hits the road. Such a guide would be more in-depth than the upgrading notes in CHANGES. We could have a paragraph about optimize/forceMerge, and another paragraph about softCommit/commitWithin as preferred to explicit commit, which is also a huge mistake many people do, they do over-committing!
> {quote}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org