If you are using master/slave (non-cloud), here is an approach.
1. Build a new master with the new schema.
2. Index all content there.
3. Send all updates to both the old master and new master.
4. One by one, take a slave down, delete all the documents, configure with the
new schema and new maste
On 3/13/2017 3:07 AM, danny teichthal wrote:
> I have a limitation that our Solr cluster is "live" during full
> indexing. We have many updates and the index is incrementally updated.
> There's no way to index everything on a side index and replace. So,
> I'm trying to find a solution where users c
Thanks Shawn,
I understand that changing id to to string is not an option.
I have a limitation that our Solr cluster is "live" during full indexing.
We have many updates and the index is incrementally updated.
There's no way to index everything on a side index and replace.
So, I'm trying to find
On 3/9/2017 4:20 AM, danny teichthal wrote:
> I have an "id" field that is defined on schema.xml with type long.
> For some use cases the id that is indexed exceeds Max long limitation.
> I thought about solving it by changing the id to type string.
>
> For my surprise, by only changing the definit
Hi,
I have an "id" field that is defined on schema.xml with type long.
For some use cases the id that is indexed exceeds Max long limitation.
I thought about solving it by changing the id to type string.
For my surprise, by only changing the definition on schema.xml and
restarting Solr, I was able
