| Following a conversation on HipChat:
[5:12 PM] Guillaume Smet: I wonder if we should prevent people from doing advanced things with the id field
[5:13 PM] Yoann Rodière: Yeah, it may be something to discuss for 6.0. Since we don't allow everything (sorts in particular), we may as well not allow anything, and force users to add their own fields
[5:14 PM] Yoann Rodière: Personally I would even remove the "name" attribute of the @DocumentId annotation, and always use some kind of internal name ("__Hsearch_id" or something)
[5:15 PM] Yoann Rodière: @Guillaume
[5:16 PM] Yoann Rodière: Customizing the ID property may make sense for Elasticsearch, but only if we decide to support the use of Hibernate Search on pre-existing schemas. And that would require lots of work
[5:19 PM] Guillaume Smet: yeah, I'm against supporting it
[5:19 PM] Guillaume Smet: it's a bad idea
[5:19 PM] Guillaume Smet: and +1 on everything you wrote
|
