Hello! You don't need the <fields> and <types> section anymore, you can just include type or field definition anywhere in the schema.xml section. You can find more in https://issues.apache.org/jira/browse/SOLR-5228
-- Regards, Rafał Kuć Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ > In which sense fields and types are now deprecated in schema.xml? Where can > I found any pointer about this? > On Mon, Apr 28, 2014 at 6:54 PM, Uwe Schindler <uschind...@apache.org>wrote: >> 28 April 2014, Apache Solr™ 4.8.0 available >> >> The Lucene PMC is pleased to announce the release of Apache Solr 4.8.0 >> >> Solr is the popular, blazing fast, open source NoSQL search platform >> from the Apache Lucene project. Its major features include powerful >> full-text search, hit highlighting, faceted search, dynamic >> clustering, database integration, rich document (e.g., Word, PDF) >> handling, and geospatial search. Solr is highly scalable, providing >> fault tolerant distributed search and indexing, and powers the search >> and navigation features of many of the world's largest internet sites. >> >> Solr 4.8.0 is available for immediate download at: >> http://lucene.apache.org/solr/mirrors-solr-latest-redir.html >> >> See the CHANGES.txt file included with the release for a full list of >> details. >> >> Solr 4.8.0 Release Highlights: >> >> * Apache Solr now requires Java 7 or greater (recommended is >> Oracle Java 7 or OpenJDK 7, minimum update 55; earlier versions >> have known JVM bugs affecting Solr). >> >> * Apache Solr is fully compatible with Java 8. >> >> * <fields> and <types> tags have been deprecated from schema.xml. >> There is no longer any reason to keep them in the schema file, >> they may be safely removed. This allows intermixing of <fieldType>, >> <field> and <copyField> definitions if desired. >> >> * The new {!complexphrase} query parser supports wildcards, ORs etc. >> inside Phrase Queries. >> >> * New Collections API CLUSTERSTATUS action reports the status of >> collections, shards, and replicas, and also lists collection >> aliases and cluster properties. >> >> * Added managed synonym and stopword filter factories, which enable >> synonym and stopword lists to be dynamically managed via REST API. >> >> * JSON updates now support nested child documents, enabling {!child} >> and {!parent} block join queries. >> >> * Added ExpandComponent to expand results collapsed by the >> CollapsingQParserPlugin, as well as the parent/child relationship >> of nested child documents. >> >> * Long-running Collections API tasks can now be executed >> asynchronously; the new REQUESTSTATUS action provides status. >> >> * Added a hl.qparser parameter to allow you to define a query parser >> for hl.q highlight queries. >> >> * In Solr single-node mode, cores can now be created using named >> configsets. >> >> * New DocExpirationUpdateProcessorFactory supports computing an >> expiration date for documents from the "TTL" expression, as well as >> automatically deleting expired documents on a periodic basis. >> >> Solr 4.8.0 also includes many other new features as well as numerous >> optimizations and bugfixes of the corresponding Apache Lucene release. >> >> Please report any feedback to the mailing lists >> (http://lucene.apache.org/solr/discussion.html) >> >> Note: The Apache Software Foundation uses an extensive mirroring network >> for distributing releases. It is possible that the mirror you are using >> may not have replicated the release yet. If that is the case, please >> try another mirror. This also goes for Maven access. >> >> ----- >> Uwe Schindler >> uschind...@apache.org >> Apache Lucene PMC Chair / Committer >> Bremen, Germany >> http://lucene.apache.org/ >> >> >>
