We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug my dto object has a field with LocalDateTime type
@DateTimeFormat(pattern = "yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'") @JsonFormat(pattern = "yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'") private LocalDateTime createTime;
and i use RestHighLevelClient write to elasticsearch UpdateRequest request = new UpdateRequest(index, id); Gson gson = new GsonBuilder().registerTypeAdapter(LocalDateTime.class,new LocalDateTimeAdapter()).create(); request.doc(gson.toJson(t), XContentType.JSON) .docAsUpsert(true); request.scriptedUpsert(true); try { return client.restHighLevelClient.update(request, RequestOptions.DEFAULT); } catch (IOException e) { log.error(e.getMessage()); } return null;
UpdateRequest request = new UpdateRequest(index, id); Gson gson = new GsonBuilder().registerTypeAdapter(LocalDateTime.class,new LocalDateTimeAdapter()).create(); request.doc(gson.toJson(t), XContentType.JSON) .docAsUpsert(true); request.scriptedUpsert(true); try { return client.restHighLevelClient.update(request, RequestOptions.DEFAULT); } catch (IOException e) { log.error(e.getMessage()); } return null;
now ,this datetime format is corret in kibana, but is incorret in dejavu like 'yyyy-08-Sa 07:54:58.366' { "_index": "test_info", "_type": "_doc", "_id": "22321", "_version": 5, "_score": 1, "_source": { "orderNo": "22321", "terminalNo": "2323", "createTime": "2020-08-03 07:54:58.366" }, "fields": { "createTime": [ "2020-08-03T07:54:58.366Z" ] } }
{ "_index": "test_info", "_type": "_doc", "_id": "22321", "_version": 5, "_score": 1, "_source": { "orderNo": "22321", "terminalNo": "2323", "createTime": "2020-08-03 07:54:58.366" }, "fields": { "createTime": [ "2020-08-03T07:54:58.366Z" ] } }
Dejavu Version v3.4.5
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
@silvermoonhy thank you for reporting will look into this.
Sorry, something went wrong.
I can confirm I'm also seeing this issue, in Firefox with the version of dejavu I got from appbaseio/dejavu on Friday.
I ran the same issue too >_<
I ran the same issue too too >_< , with version 3.6.0
lakhansamani
No branches or pull requests
Describe the bug
my dto object has a field with LocalDateTime type
@DateTimeFormat(pattern = "yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'") @JsonFormat(pattern = "yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'") private LocalDateTime createTime;
and i use RestHighLevelClient write to elasticsearch
UpdateRequest request = new UpdateRequest(index, id); Gson gson = new GsonBuilder().registerTypeAdapter(LocalDateTime.class,new LocalDateTimeAdapter()).create(); request.doc(gson.toJson(t), XContentType.JSON) .docAsUpsert(true); request.scriptedUpsert(true); try { return client.restHighLevelClient.update(request, RequestOptions.DEFAULT); } catch (IOException e) { log.error(e.getMessage()); } return null;
now ,this datetime format is corret in kibana, but is incorret in dejavu like 'yyyy-08-Sa 07:54:58.366'
{ "_index": "test_info", "_type": "_doc", "_id": "22321", "_version": 5, "_score": 1, "_source": { "orderNo": "22321", "terminalNo": "2323", "createTime": "2020-08-03 07:54:58.366" }, "fields": { "createTime": [ "2020-08-03T07:54:58.366Z" ] } }
Dejavu Version
v3.4.5
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: