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
HSEARCH-1268 Make it possible to plug in a custom MassIndexer implementation #380
Conversation
I don't think I can leave on inline comment on this one because it's about file I didn't change, anyway: ClassLoaderHelper#classForName is using the contextClassloader before using the one passed as a parameter. Shouldn't be the opposite? |
Order is not important, it only has a performance impact as it might try the correct one first, avoiding one reource access. |
} | ||
|
||
private MassIndexerFactory createFactory(String factoryClassName) { | ||
return ClassLoaderHelper.instanceFromName( MassIndexerFactory.class, factoryClassName, getClass() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you check if ORM isn't providing you the classloader as a Service?
getClass().getClassLoader()
If we still use this code, then the fix in the previous commit isn't as useful as I thought it would be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't check.
I will take a look at it
I'm asking because It's seems a bit awkward that I pass the classloader that I want to use and then another one is used. By the way, I've noticed this writing some unit tests. |
Added some documentation and javadoc |
Rebased. All the changes should be applied now. |
Changed a comment |
merged! |
https://hibernate.onjira.com/browse/HSEARCH-1268
I have a couple of question. I will ask as inline comments