-
Notifications
You must be signed in to change notification settings - Fork 23
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
elasticSearch.date.formats
is seemingly ignored
#79
Comments
To clarify: I'm using version |
The issue that I am dealing with is an exception when unmarshalling:
Notice that my input value does not contain milliseconds - thus the failure with the pattern on line 253 of |
I've got a fix for that in my fork. If interested, I could create a Pull Request... |
Let's see what @puneetbehl thinks. I think he is offline for a few days. |
As a workaround, I'm able to create a converter class:
And use that:
|
Right, it should first check the config value instead of hardcoded. Please feel free to send PR |
If I specify a value for
elasticSearch.date.formats
, I do not believe that this value is honored when unmarshalling.See: https://github.com/puneetbehl/elasticsearch-grails-plugin/blob/03931f05aa1d337603f5929b3f78924c8680af76/src/main/groovy/grails/plugins/elasticsearch/conversion/unmarshall/DomainClassUnmarshaller.groovy#L253
I would imagine that this line should first check the config for a value before defaulting to this hardcoded format.
The text was updated successfully, but these errors were encountered: