: I'm wondering then if the Sorting infrastructure could be refactored
: to allow with some sort of policy/strategy where one can choose a
: point where one is not willing to use memory for sorting, but willing
...
: To accomplish this would require a substantial change to the
:
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488039
]
Mark Miller commented on LUCENE-794:
I use that to make the Range Query test pass. The old style Range Query
is
Initial thoughts and then more inline below, and keep in mind I long
ago drank the Maven kool-aid and am a big fan. :-)
I know it is a pain to a few, but realistically speaking there has
not been all that much noise about Maven artifacts not being
available. We use Maven for everything
Grant Ingersoll wrote:
Initial thoughts and then more inline below, and keep in mind I long ago
drank the Maven kool-aid and am a big fan. :-)
I know it is a pain to a few, but realistically speaking there has not
been all that much noise about Maven artifacts not being available. We
use
On Apr 11, 2007, at 11:02 AM, Sami Siren wrote:
We wouldn't touch the existing single maven artifact in the
repository,
just would deploy the new artifacts under different gId, nothing
existing is broken on the way. We could of cource continue publishing
under gId 'org.apache.lucene' if so
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488125
]
Hoss Man commented on LUCENE-855:
-
Another thing that occurred to me this morning is that the comparison test
Chris Hostetter wrote:
: Couldn't we just add various ANT targets that package the jars per
: the Maven way, and even copy them to the appropriate places? I
: wonder how hard it would be
: to have ANT output the POM and create Maven Jars. I know it is
This is what i would view as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Grant.
Initial thoughts and then more inline below, and keep in mind I long ago
drank the Maven kool-aid and am a big fan. :-)
I know it is a pain to a few, but realistically speaking there has not
been all that much noise about Maven
[
https://issues.apache.org/jira/browse/LUCENE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488213
]
Karl Wettin commented on LUCENE-625:
(from a mail i just posted to java-user)
There is a memoryleak in the trie
: Where and how would you store for example the dependency information
: that you would be using to generate the poms? For lucene java it is easy
: for most modules as there is only dependency to lucene-core but for
: example in solr, nutch and hadoop it starts to go beyond trivial.
Whatever
I agree. this falls into the area where technical limit is reached. Time to
modify the spec.
I thought about this issue over this couple of days, there is really NO
silver bullet. If the field is multi-value field and the distinct field
values are not too many, you might reduce memory usage by
Robert Engels wrote:
I think this is great, and it gave me an idea. What if another thread could
call a stop optimize which would stop the optimize after it came to a
consistent state (not in the middle of a segment merge).
We schedule our optimizes for the lull time period, but with 24/7
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Liu updated LUCENE-855:
Attachment: contrib-filters.tar.gz
I made a few changes to MemoryCachedRangeFilter:
- SortedFieldCache's
13 matches
Mail list logo
