"pass wt=json and/or indent=off to use the previous unindented XML format" : Should it be pass wt=xml or am I misunderstanding this statement ?
Additionally should we add a bullet regarding point fields ? * Numeric and date data use point field types by default. All trie fields types have been deprecated On Wed, Sep 20, 2017 at 7:21 AM, Christine Poerschke (BLOOMBERG/ LONDON) < cpoersc...@bloomberg.net> wrote: > Totally agree with choosing _7_ highlights for the Solr _7_ release! > > Below is the revised draft I came up with: > > (Notice that v2 is the 2nd bullet, though I think it yet needs to mention > one or _two_ benefits of using the new API especially since we mention that > /solr/ continues to work.) > > (Also notice some re-ordering of the bullets starting with the > used-by-many JSON first, then v2 API second, then third collection creation > which mentions faceting and so leads over to the fourth bullet re: facet > refinement. Fifth is the new replica types (that bullet being slightly > longer than the others to explain what the types are about). Sixth is > auto-scaling which mentions future releases (would folks use new replica > types first before moving on to auto-scaling?). Seventh and last then is > Solr _7_ mention with Java _9_ i.e. the just-arrived future again there.) > > Solr 7.0 Release Highlights: > > * Indented JSON is now the default response format for all APIs, > pass wt=json and/or indent=off to use the previous unindented XML format. > > * The new v2 API, exposed at /api/ and also supported via SolrJ, is now the > preferred API, but /solr/ continues to work. > > * A new `_default` configset is used if no config is specified at > collection > creation. The data-driven functionality of this configset indexes strings > as > analyzed text while at the same time copying to a `*_str` field suitable > for > faceting. > > * The JSON Facet API now supports two-phase facet refinement to ensure > accurate > counts and statistics for facet buckets returned in distributed mode. > > * Replica Types - Solr 7 supports different replica types, which handle > updates > differently. In addition to pure NRT operation where all replicas build an > index and keep a replication log, you can now also add so called PULL > replicas, achieving the read-speed optimized benefits of a master/slave > setup while at the same time keeping index redundancy. > > * Auto-scaling. Solr can now allocate new replicas to nodes using a new > auto > scaling policy framework. This framework will in future releases enable > Solr > to move shards around based on load, disk etc. > > * Solr 7 is tested with and verified to support Java 9. > > From: dev@lucene.apache.org At: 09/20/17 15:02:38 > To: dev@lucene.apache.org > Subject: Re: Release 7.0 process starts > > > > On Wed, Sep 20, 2017 at 9:16 AM Jan Høydahl <jan....@cominvent.com> wrote: > >> And please, I was serious about choosing 7 major features and not adding >> random single improvements. The list has already creeped from 7 to 9 >> bullets. If you want to add something, then ask youself which of the other >> bullets that are less important to MOST USERS and then replace that bullet >> instead of adding more. Agree? >> > > I agree with that very much! *Each bullet added de-values the list as a > whole. *IMO the Java 9 bullet can be removed (too few are even using it > yet) and we get to 8 bullets; and those 8 are pretty good. > -- > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www. > solrenterprisesearchserver.com > >
