[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-67?page...
]
Hardy Ferentschik commented on HSEARCH-67:
------------------------------------------
No I mean that you can define those values per DirectoryProvider
hibernate.search.myindex1.max_merge_docs=100
hibernate.search.default.max_merge_docs=10
Of course. One per ´index´. Sorry for not understanding what you were talking about. Your
suggstions makes of course much more sense. I guess I got confused by the terminology. In
fact there are a few things which are now maybe a little ambiguous. For example we are
talking about batch indexing when talking about collecting index operation within a single
transaction. At the same time we call indexing via the FullTextSession ´batch indexing´.
Maybe we need a better terminology? But that´s another issue.
So the internal structure would probably be more like
searchFactoryImplementor.getIndexingParameters(
(directoryProvider).getMaxMergeDocs()
Sure. Makes sense from an API level. I guess
this type of configuration is consistent with other parameters, but I am not sure about th
possible use cases. It feels almost like overkill. On the other hand it´s just an option.
You can just stick with the defaults.
I can work on it if you're busy.
Sure. Go ahead. I wouldn´t
have time until I am back in Sweden next week.
Expose mergeFactor, maxMergeDocs and minMergeDocs
-------------------------------------------------
Key: HSEARCH-67
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-67
Project: Hibernate Search
Issue Type: New Feature
Components: directory provider
Reporter: Emmanuel Bernard
Assignee: Hardy Ferentschik
Fix For: 3.0.0.beta4
Attachments: HSEARCH-67-2.diff, HSEARCH-67-3.diff, HSEARCH-67.diff
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira