|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Since
HSEARCH-1096is now fixed for 4.2, I think it would be a potential performance nightmare not to fix HSEARCH-1093 for the same release. I imagine that @Transient @Fields are very common, they are with me. Most commonly to combine certain text fields (e.g. title and description) into one @Field. Superfluously reindexing these I guess would not represent a huge issue but if there are Lazy connections hidden underneath, it might. I imagine upgrading to 4.2 and suddenly all my objects are always considered dirty by Hibernate Search leading to a flurry of unnecessary queries. This is just the kind of situation (with classbridges) I managed to get away from with includePaths. I think I would prefer to not have HSEARCH-3910 fixed if HSEARCH-1093 wasn't also. I can always do periodic reindexes to compensate for that.