-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to convert (2017) into YYYY format and couldn't index it (dsDescriptionDate) #4558
Comments
The () are likely being added by the display formatting, but I would've though the indexing code would not be using that. Not sure if this is a new regression or not, but thanks for bringing to our attention. |
Over at http://irclog.iq.harvard.edu/dataverse/2018-03-29#i_65142 @andrewSC mentioned he's running 4.8.5 but I wanted to mention that I see this problem in the develop branch as well. The phoenix server is running 3845816 and this is what I see:
Here's where the exception is being caught: https://github.com/IQSS/dataverse/blob/v4.8.5/src/main/java/edu/harvard/iq/dataverse/search/IndexServiceBean.java#L730 |
Checked my notes; similar behavior seen for |
Right, I'd expect you'd see it with any date subfield of a compound field that has a display format. @pameyer at some point you had made a change to how these things were indexed, no? Could that have introduced this regression? (not trying to call you out, sorry) |
@scolapasta I did make some changes there; but I'm pretty sure I didn't add parenthesis anywhere. |
@pameyer not that you added the parenthesis, but that if you use the displayformat version of the field the parenthesis would be added due to being defined that way for display in the db. |
@scolapasta if I'm remembering correctly, the changes I made sent value instead of display value to solr. I'd expect that to mean that things that were sent to solr with parenthesis in displayvalue wouldn't have the parenthesis anymore - but that doesn't seem to be what's happening here. Not at all discounting the possibility that this was something that change broke without noticing (especially since that's happened previously)... |
I have tried upgrades from 4.7.1 -> 4.8 -> 4.8.1 -> 4.8.2 -> 4.8.3 -> 4.8.4 -> 4.8.5 in our test instance and I saw these indexing errors in each released build!
Does it mean we will have to fix dates in DB! |
@bikramj I don't think you need to worry about your dates in general but "(2015-02)" doesn't pass our validator. Check this out: We haven't investigated this issue yet. It's still in the "inbox" according to our kanban board: https://waffle.io/IQSS/dataverse If anyone wants to poke around and try figure out what's happening, please go ahead! |
Took a quick look since I'm investigating #4560 in the same general area. I'm pretty sure that the parenthesis are coming from |
Some possible clues into how this regression was introduced: #4906 (comment) |
The same fix was used for this issue and #4906. They should be reviewed together. |
After clearing the Solr index and kicking off a full-reindex I noticed multiple log messages similar to:
After running
asadmin set-log-levels edu.harvard.iq.dataverse.search.IndexServiceBean=FINE
I was able to capture some more descriptive output (of a different dataset failing) from the logging in IndexServiceBean.java#L713 which provided:Which seems to imply that the conversion is failing due to parenthesis existing around the date at the time of conversion. I did some quick spelunking and it doesn't seem immediately obvious what's adding them? Here's what I found in the codebase:
The text was updated successfully, but these errors were encountered: