I thought about using ulimit, but it does not scale. In the scenario that the
app has to support, client applications could create hundreds of thousands of
unique properties, which would result in this many indexable fields.
Based on previous answers, the way out of this problem while still bein
Thanks for you reply.
We are still using Lucene v1.4.3 and I'm not sure if upgrading is an option. Is
there another way of disabling length normalization/document boosts to get rid
of those files?
Thanks,
Rico
: >From what I read in the Lucene docs, these .f files store the
: normalization fac
Hello,
What would be the best strategy to support an index with thousands or even
hundreds of thousands of individual field names?
I have client applications that create a lot of key/value type data. I use the
key as document field name so I end up with _a lot_ of .f files and
eventually the my
