Oh I totally forgot about .indexwriter.
OK so here is how it will be
we keep hibernate.search.[indexname].indexwriter.transaction/batch for
most with batch inheriting tx
And we support
hibernate.search.[indexname].indexwriter.use_compound_file
hibernate.search.[indexname].indexwriter.max_fiel
2 answers inline:
2008/11/13 Emmanuel Bernard <[EMAIL PROTECTED]>:
> Plus it seems the default value is compound = true, just like in Lucene.
> This is not what we are saying in the doc.
> Am I completely off-base?
No, you are correct.
2008/11/12 Emmanuel Bernard <[EMAIL PROTECTED]>:
> So where
Plus it seems the default value is compound = true, just like in
Lucene. This is not what we are saying in the doc.
Am I completely off-base?
On Nov 12, 2008, at 17:59, Emmanuel Bernard wrote:
Actually I sat down and read more about compound file format.
Basically, instead of creating sever
Actually I sat down and read more about compound file format.
Basically, instead of creating several files representing a single
segment, the compound format creates a single file for the whole
segment.
And you can have a mix of compound and non compound segments for a
given index. So you ca
So where would we put these?
under hibernate.search.[index name]. straight?
eg
hibernate.search.[index name].use_compound_file
On Nov 11, 2008, at 11:17, Hardy Ferentschik wrote:
On Tue, 11 Nov 2008 16:07:06 +0100, Emmanuel Bernard <[EMAIL PROTECTED]
> wrote:
It seems that a few parameter
actually "term_index_interval" should have not harm if configured differently,
and can be useful to tune the batch indexing speed in a different way.
The other 2 should be invariant.
2008/11/12 Sanne Grinovero <[EMAIL PROTECTED]>:
> what to you mean by structural setting?
>
> I think we should al
what to you mean by structural setting?
I think we should always apply the same values for both transaction
and batch (shouldn't be possible to have them configured differently).
we had a chat about this, and as far as I remember the idea was to log
a warning for the moment.
If you explain me wh
On Tue, 11 Nov 2008 18:53:14 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
maybe structural setting?
+1 Sounds good to me.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
maybe structural setting?
On Nov 11, 2008, at 11:17, Hardy Ferentschik wrote:
On Tue, 11 Nov 2008 16:07:06 +0100, Emmanuel Bernard <[EMAIL PROTECTED]
> wrote:
It seems that a few parameters should not be configurable per
transaction|batch
- use_compound_file
- max_field_length? not sure
-
On Tue, 11 Nov 2008 16:07:06 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
It seems that a few parameters should not be configurable per
transaction|batch
- use_compound_file
- max_field_length? not sure
- term_index_interval (is that a config influencing IndexReader?)
What do you
It seems that a few parameters should not be configurable per
transaction|batch
- use_compound_file
- max_field_length? not sure
- term_index_interval (is that a config influencing IndexReader?)
What do you think?
I am a bit worried to stick them as is in the project / book as they
are rig
11 matches
Mail list logo
