<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to override previous schema configuration in Elastic Search in Nuxeo in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316726#M3727</link>
    <description>&lt;P&gt;This will not directly answer your question, but I would never recommend to change the type of an atrribute. You can be sure of side effects you won't predict - there are some already.&lt;/P&gt;
&lt;P&gt;I would add a new field, migrate values and remove the old one. Guaranteed it will save a lot of time - but again, thats my approach.&lt;/P&gt;
&lt;P&gt;Sent from my Android phone using TouchDown (www.symantec.com)&lt;/P&gt;</description>
    <pubDate>Mon, 20 Apr 2020 19:54:44 GMT</pubDate>
    <dc:creator>michal_m</dc:creator>
    <dc:date>2020-04-20T19:54:44Z</dc:date>
    <item>
      <title>How to override previous schema configuration in Elastic Search in Nuxeo</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316725#M3726</link>
      <description>&lt;P&gt;I had one of my field 'published_date' as 'timestamp' datatype.But eventually I had to make it as 'string' . I corrected in my schema file. But both db and elastic search suggested that it must be timestamp while adding new record.&lt;/P&gt;
&lt;P&gt;I solved in db by deleting previous table from db......and new table was created by server with corrected schema.&lt;/P&gt;
&lt;P&gt;But I dont know how to solve in elasticSearch.It still says that 'published_date' must be 'timestamp' datatype.(I know its data is stored in data folder inside nxsever, but i dont know how to delete its previous schema)&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2020 13:55:50 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316725#M3726</guid>
      <dc:creator>dipesh_kc</dc:creator>
      <dc:date>2020-04-20T13:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to override previous schema configuration in Elastic Search in Nuxeo</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316726#M3727</link>
      <description>&lt;P&gt;This will not directly answer your question, but I would never recommend to change the type of an atrribute. You can be sure of side effects you won't predict - there are some already.&lt;/P&gt;
&lt;P&gt;I would add a new field, migrate values and remove the old one. Guaranteed it will save a lot of time - but again, thats my approach.&lt;/P&gt;
&lt;P&gt;Sent from my Android phone using TouchDown (www.symantec.com)&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2020 19:54:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316726#M3727</guid>
      <dc:creator>michal_m</dc:creator>
      <dc:date>2020-04-20T19:54:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to override previous schema configuration in Elastic Search in Nuxeo</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316727#M3728</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You'd better create another property and not edit an existing property type: this is always risky.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2020 19:59:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/how-to-override-previous-schema-configuration-in-elastic-search/m-p/316727#M3728</guid>
      <dc:creator>Gregory_Carlin</dc:creator>
      <dc:date>2020-04-20T19:59:05Z</dc:date>
    </item>
  </channel>
</rss>

