You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2012/10/26 16:17:12 UTC
[jira] [Created] (STANBOL-790) Upgrade to Solr 3.6.1
Rupert Westenthaler created STANBOL-790:
-------------------------------------------
Summary: Upgrade to Solr 3.6.1
Key: STANBOL-790
URL: https://issues.apache.org/jira/browse/STANBOL-790
Project: Stanbol
Issue Type: Bug
Components: Commons
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
The intension is to upgrade to the latest Solr Version before the Solr/Lucene 4.0 release.
Stanbol is currently still using a rather old 3.2 release and before updating to the new major version we should use upgrade to the latest 3.+ release.
--
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
[jira] [Commented] (STANBOL-790) Upgrade to Solr 3.6.1
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485380#comment-13485380 ]
Rupert Westenthaler commented on STANBOL-790:
---------------------------------------------
As part of this upgrade the following changes will be made:
* Removal of the Solr specific xml-api, xerces and xalan: As 3.6.1 no longer provides its own xerces those dependencies can be loaded via the SystemBundle
* Removal of the embedded ICU4J: As of JDK 1.6 this is anyway available and therefore not needed to be embedded
* Replacement of a lot of embedded dependencies with bundles provided by the http://servicemix.apache.org project. Users with custom build launchers that do NOT use the stanbolcommons BundleList will need to adapt their Launcher configurations accordingly.
* servlet-api and portlet-api with score provided: As Stanbol anyway is expected to have a servlet container available.
Schema.xml changes
* This solr versions required omitNorm="false" on all fields if index time document boosts are used. As the Stanbol Entityhub does use this feature the default schema of the Entityhub was was changed accordingly. Note that the default schema for the Entityhub (entityhub.solrindex.zip) was NOT changed as the index time boosts are only used for ReferencedSite's.
The size of the org.apache.stanbol.commons.solr bundle is now ~6MByte (down form 24.3MByte in the last release)
> Upgrade to Solr 3.6.1
> ---------------------
>
> Key: STANBOL-790
> URL: https://issues.apache.org/jira/browse/STANBOL-790
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The intension is to upgrade to the latest Solr Version before the Solr/Lucene 4.0 release.
> Stanbol is currently still using a rather old 3.2 release and before updating to the new major version we should use upgrade to the latest 3.+ release.
--
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
[jira] [Resolved] (STANBOL-790) Upgrade to Solr 3.6.1
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-790.
-----------------------------------------
Resolution: Fixed
implemented with http://svn.apache.org/viewvc?rev=1402773&view=rev
> Upgrade to Solr 3.6.1
> ---------------------
>
> Key: STANBOL-790
> URL: https://issues.apache.org/jira/browse/STANBOL-790
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> The intension is to upgrade to the latest Solr Version before the Solr/Lucene 4.0 release.
> Stanbol is currently still using a rather old 3.2 release and before updating to the new major version we should use upgrade to the latest 3.+ release.
--
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