Consider tag changes as fmd changes for indexing#6096
Conversation
|
Thanks @qqmyers, we'll review this. |
|
This change is straightforward enough. At some point it would make sense to look at the in the context of the version differences code and see if we can find a way to unify. (i.e. if the version differences for a file would show that something changed, then indexing should happen; if tomorrow we added something new* we shouldn't have to add the conditional for it twice. (*) for example file path. I'm actually not sure if changing the file path is shown in differences, but it is here. |
|
+1 - If indexing were fully difference-based, I think one could avoid deleting the docs for all files and then reindexing the ones that don't change along with the (probably few) that have. That could be a good speed boost. |
|
Can one of the admins verify this patch? |
mheppler
left a comment
There was a problem hiding this comment.
"This change is straightforward enough." -- @scolapasta
|
Added #6099 to refactor the code. |
|
@qqmyers This isn't your issue. It somehow made its way into develop, even though I tested all formats recently. @qqmyers OAI-ORE export is not working and seeing this in server log when publishing a new version of dataset: [2019-08-16T14:55:57.019-0400] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=54 _ThreadName=Thread-9] [timeMillis: 1565981757019] [levelValue: 1000] [[ [2019-08-16T14:55:57.019-0400] [glassfish 4.1] [SEVERE] [] [] [tid: _ThreadID=54 _ThreadName=Thread-9] [timeMillis: 1565981757019] [levelValue: 1000] [[ |
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Thanks!
Related Issues
Pull Request Checklist