title: Which changes in Solr schema and/or in mapped class are breaking?
body: <p>We are using Solr by SolrNet package with default attributes-based mapping.</p>
  
  <pre><code>public class MyType
  {
      [SolrUniqueKey("id")]
      public int Id { get; set; }
  
      [SolrField("name")]
      public string Name { get; set; }
  
      //[SolrField("new_field")]
      //public string NewField { get; set; }
  }
  </code></pre>
  
  <p>Which of those changes will be breaking for the application that use it? </p>
  
  <ol>
  <li>Adding new field to the existing core schema without reindexing with code left intact.</li>
  <li>... the same as above... with reindexing that populate new fields.</li>
  <li>Adding new property to mapped class keeping Solr schema intact.</li>
  </ol>