You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ElasticSearchService has two ways of indexing an image, one is an individual record (ElasticSearchService.indexImage) and the second is a bulk index of all records in the database (ScheduleReindexAllImagesTask using ImageService.exportIndexToFile and ElasticSearchService.bulkIndexImageInES). The ES documents these produce are inconsistent in the fields they provide, the data types of some of those fields (ie bulkIndex all fields are strings, individual doc has ints for width, height, etc) and the name of some fields (contentmd5hash, contentsha1hash in bulk index vs contentMD5Hash, contentSHA1Hash in individual index).
I suggest updating the bulk index to match the individual index in fields, field names and data types.
The
ElasticSearchService
has two ways of indexing an image, one is an individual record (ElasticSearchService.indexImage
) and the second is a bulk index of all records in the database (ScheduleReindexAllImagesTask
usingImageService.exportIndexToFile
andElasticSearchService.bulkIndexImageInES
). The ES documents these produce are inconsistent in the fields they provide, the data types of some of those fields (ie bulkIndex all fields are strings, individual doc hasint
s for width, height, etc) and the name of some fields (contentmd5hash, contentsha1hash in bulk index vs contentMD5Hash, contentSHA1Hash in individual index).I suggest updating the bulk index to match the individual index in fields, field names and data types.
Something something well defined schemas.
Example
indexImage
document:Example
bulkIndexImageInES
document:The text was updated successfully, but these errors were encountered: