[DuraSpace JIRA] (DS-3658) Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration

12 views
Skip to first unread message

Tim Donohue (DuraSpace JIRA)

unread,
Jul 31, 2017, 4:27:01 PM7/31/17
to dspace-...@googlegroups.com
Tim Donohue updated an issue
 
DSpace / Improvement DS-3658
Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration
Change By: Tim Donohue
Summary: discovery- Full reindex ( index runs anytime -discovery) is triggered whenever Flyway finds a new DB migration , make this process more intelligent
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.3#73014-sha1:d5be8da)
Atlassian logo

Tim Donohue (DuraSpace JIRA)

unread,
Jul 31, 2017, 4:35:00 PM7/31/17
to dspace-...@googlegroups.com
Tim Donohue commented on Improvement DS-3658
 
Re: Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration

How this occurs is as follows:

Sven Soliman (DuraSpace JIRA)

unread,
Aug 1, 2017, 5:03:00 AM8/1/17
to dspace-...@googlegroups.com
Sven Soliman commented on Improvement DS-3658

I needed to Full-Index as well when upgrading from 6.0 to 6.1 and it took 5 hours ..

Tim Donohue (DuraSpace JIRA)

unread,
Sep 7, 2017, 3:11:00 PM9/7/17
to dspace-...@googlegroups.com

Mark Diggory (DuraSpace JIRA)

unread,
Aug 24, 2018, 3:01:02 PM8/24/18
to dspace-...@googlegroups.com
Mark Diggory commented on Improvement DS-3658
 
Re: Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration

I feel very strongly that this code should be removed (or made an option that is disabled by DEFAULT). It should be left up to the individual installing the update of the repository to decide if further steps that will be taken. Large production Solr search indexes take a long time (entire days) to reconstruct on many of our repositories, they should not be completely destroyed and rebuilt from scratch without human input.

This message was sent by Atlassian JIRA (v7.10.0#710001-sha1:0399717)

Mark Diggory (DuraSpace JIRA)

unread,
Aug 24, 2018, 3:05:01 PM8/24/18
to dspace-...@googlegroups.com
Mark Diggory edited a comment on Improvement DS-3658
I feel very strongly that [this code|https://github.com/DSpace/DSpace/blame/master/dspace-api/src/main/java/org/dspace/storage/rdbms/DatabaseUtils.java#L1216-L1256] should be removed (or made an option that is disabled by DEFAULT). It should be left up to the individual installing the update of the repository to decide if further steps that will be taken. Large production Solr search indexes take a long time (entire days) to reconstruct on many of our repositories, they should not be completely destroyed and rebuilt from scratch without human input.


I would raise the priority of this and identify it as an important issue that should be corrected.

Andrew Wood Atmire (DuraSpace JIRA)

unread,
Aug 28, 2018, 1:46:01 PM8/28/18
to dspace-...@googlegroups.com

I've created a PR that wraps the automatic invocation of the ReindexerThread with a configurable property. Effectively allowing the user to configure the automatic triggering of the ReindexerThread

 

https://github.com/DSpace/DSpace/pull/2184

Anonymous (DuraSpace JIRA)

unread,
Aug 28, 2018, 2:23:02 PM8/28/18
to dspace-...@googlegroups.com
Issue was automatically transitioned when Andrew Wood created pull request #2184 in GitHub
 
Change By: Andrew Wood
Status: Volunteer Code Review Needed

Mark H. Wood (DuraSpace JIRA)

unread,
Mar 28, 2019, 2:08:01 PM3/28/19
to dspace-...@googlegroups.com

Mark H. Wood (DuraSpace JIRA)

unread,
May 15, 2019, 1:29:03 PM5/15/19
to dspace-...@googlegroups.com
Mark H. Wood commented on Improvement DS-3658
 
Re: Full reindex (index-discovery) is triggered whenever Flyway finds a new DB migration

Draft 7.0 documentation updated.  6_x documentation should not be updated until 6.4 is released, and should note that this feature did not exist before that release.

Tim Donohue (DuraSpace JIRA)

unread,
May 20, 2019, 10:54:01 AM5/20/19
to dspace-...@googlegroups.com
Tim Donohue updated an issue
 
Change By: Tim Donohue
Status: Code Review Needed Awaiting Documentation

Anonymous (DuraSpace JIRA)

unread,
May 20, 2019, 12:25:03 PM5/20/19
to dspace-...@googlegroups.com
Issue was automatically transitioned when pull request #2433 was created in GitHub
Change By: Automated Transition
Status: Awaiting Documentation Code Review Needed

Tim Donohue (DuraSpace JIRA)

unread,
May 20, 2019, 12:50:03 PM5/20/19
to dspace-...@googlegroups.com
Tim Donohue updated an issue
Change By: Tim Donohue
Status: Code Review Needed Awaiting Documentation

Anonymous (DuraSpace JIRA)

unread,
May 31, 2019, 7:25:01 AM5/31/19
to dspace-...@googlegroups.com
Issue was automatically transitioned when pull request #2441 was created in GitHub
Change By: Automated Transition
Status: Awaiting Documentation Code Review Needed

Kim Shepherd (DuraSpace JIRA)

unread,
Mar 28, 2020, 7:08:02 PM3/28/20
to dspace-...@googlegroups.com
Kim Shepherd updated an issue

switching status to remind us about the need for 6.x doc before 6.4 is released

Change By: Kim Shepherd
Status: Code Review Needed Awaiting Documentation
This message was sent by Atlassian Jira (v8.4.1#804002-sha1:94e96d6)
Atlassian logo

Tim Donohue (LYRASIS JIRA)

unread,
Aug 3, 2021, 4:40:01 PM8/3/21
to dspace-...@googlegroups.com
Tim Donohue closed an issue as Fixed
 

In order to close out the "7.0" Version in Jira (so that nothing new can be added to it), I need to close this ticket as fixed in 7.0.

I realize it's (possibly) still being documented in 6.4, but that will need to occur in a separate Jira ticket as needed.  Sorry about that.

Change By: Tim Donohue
Resolution: Fixed
Status: Awaiting Documentation Closed
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages