Thanks for fixing that. I typed it on my phone, looks like autocorrect bit
me!
> try this http://dhruvbird.com/lfu.pdf
>
> On Fri, Apr 20, 2012 at 12:06 PM, Uwe Schindler wrote:
>> 404 Not Found for me.
-
To unsubscribe, e-ma
try this http://dhruvbird.com/lfu.pdf
On Fri, Apr 20, 2012 at 12:06 PM, Uwe Schindler wrote:
> 404 Not Found for me.
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
>> -Original Message-
>> From: Shawn Heisey [mailto:
404 Not Found for me.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Shawn Heisey [mailto:s...@elyograg.org]
> Sent: Friday, April 20, 2012 8:32 AM
> To: dev@lucene.apache.org
> Subject: LFU cache - SOL
The LFU cache implementation I wrote for SOLR-2906 is O(log n), which is
pretty inefficient. Today I came across an implementation that claims to
be O(1). Specifically, it is found in an open source project called
hawtdb. They reference a paper at the following URL (pdf warning):
http://dhruvbir
Just wanted to confirm my above suspicion about the code cache --
those long build times are fully repeatable on my machine (including
the time when code cache explodes). Timing from my machine for that
long test (when run in complete mode):
Suite: org.apache.lucene.search.TestNumericRangeQuery64
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257984#comment-13257984
]
Mark Miller commented on SOLR-3178:
---
Per Steffensen, can you attach whatever you have, ev
[
https://issues.apache.org/jira/browse/LUCENE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257948#comment-13257948
]
Chris Male commented on LUCENE-3997:
{quote}
Of course, another option is to combine
[
https://issues.apache.org/jira/browse/LUCENE-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257945#comment-13257945
]
Chris Male commented on LUCENE-4001:
I have real reservations about doing this. In L
[
https://issues.apache.org/jira/browse/LUCENE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257942#comment-13257942
]
Chris Male commented on LUCENE-3997:
I do echo Yonik's concern here, I don't think we
Oh, I just digested a spoonful of hotspot source code. It seems there
is a magic option to attempt to clean the code cache before shutting
down the compiler...
product(bool, UseCodeCacheFlushing, false,\
"Attempt to clean the code cache before shutting o
[
https://issues.apache.org/jira/browse/LUCENE-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257884#comment-13257884
]
Dawid Weiss commented on LUCENE-4000:
-
Not so harmless after all. Code cache exhausti
On 4/19/2012 2:12 PM, Shawn Heisey wrote:
I notice that SOLR-2724 and SOLR-3161 are in the CHANGES.txt for
3.6.0, but that they both got reverted on trunk. Are there plans to
put them back in trunk in a possibly altered form? I like the general
direction that David Smiley is going, as long as
I notice that SOLR-2724 and SOLR-3161 are in the CHANGES.txt for 3.6.0,
but that they both got reverted on trunk. Are there plans to put them
back in trunk in a possibly altered form? I like the general direction
that David Smiley is going, as long as the client API keeps up.
If I follow all
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257703#comment-13257703
]
Yonik Seeley commented on SOLR-3178:
Are there any technical objections to this patch?
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257682#comment-13257682
]
Yonik Seeley edited comment on SOLR-3178 at 4/19/12 7:14 PM:
-
b
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257682#comment-13257682
]
Yonik Seeley commented on SOLR-3178:
bq. it is hard to push too many small partly-done
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257664#comment-13257664
]
Per Steffensen edited comment on SOLR-3178 at 4/19/12 6:42 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257664#comment-13257664
]
Per Steffensen commented on SOLR-3178:
--
I dont care about credit :-)
It is just that
[
https://issues.apache.org/jira/browse/SOLR-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257644#comment-13257644
]
Robert Muir commented on SOLR-2928:
---
I tried to enable this again (by disabling this test
Ah, yes, building it first would help, wouldn't it? :-/
Thanks Sami and Ryan. The new UI looks very nice, too!
On 19 Apr 2012, at 17:44, Sami Siren wrote:
> On Thu, Apr 19, 2012 at 7:13 PM, Alan Woodward
> wrote:
>> Hi all,
>>
>> I'm trying to get the Solr example running in a checkout of tr
[
https://issues.apache.org/jira/browse/SOLR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257637#comment-13257637
]
Robert Muir commented on SOLR-2020:
---
FYI: 3.6 branch is already setup for 3.6.1 backports
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257630#comment-13257630
]
Yonik Seeley commented on SOLR-3178:
I think the best way to do this is really incremen
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257625#comment-13257625
]
Per Steffensen commented on SOLR-3178:
--
I really hope you will give us a chance to con
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257620#comment-13257620
]
Per Steffensen commented on SOLR-3178:
--
I will have a look at the patch provided by yo
[
https://issues.apache.org/jira/browse/SOLR-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257600#comment-13257600
]
Patrick Sauts commented on SOLR-2755:
-
Excellent news, thank you.
Another thing was al
On Thu, Apr 19, 2012 at 7:13 PM, Alan Woodward
wrote:
> Hi all,
>
> I'm trying to get the Solr example running in a checkout of trunk (r1327775),
> but it seems to be broken - jetty starts up, but doesn't load the Solr webapp.
>
> solr/example$ ant resolve
> solr/example$ java -jar start.jar &
d
try:
http://localhost:8983/solr/
without the /admin path
In /trunk since SOLR-3337, /solr/admin should redirect to the new UI
$ curl -v http://localhost:8983/solr/admin
* About to connect() to localhost port 8983 (#0)
* Trying ::1...
* connected
* Connected to localhost (::1) port 8983 (#0)
>
[
https://issues.apache.org/jira/browse/SOLR-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257571#comment-13257571
]
Ryan McKinley commented on SOLR-3371:
-
got it. +1 when you are ready
I'm also +1 to co
Hi all,
I'm trying to get the Solr example running in a checkout of trunk (r1327775),
but it seems to be broken - jetty starts up, but doesn't load the Solr webapp.
solr/example$ ant resolve
solr/example$ java -jar start.jar &
2012-04-19 17:01:00.028:INFO:oejs.Server:jetty-8.1.2.v20120308
2012-0
[
https://issues.apache.org/jira/browse/LUCENE-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257547#comment-13257547
]
Martijn van Groningen commented on LUCENE-4001:
---
It turns out that three fi
Grouping module shouldn't depend on queries module
--
Key: LUCENE-4001
URL: https://issues.apache.org/jira/browse/LUCENE-4001
Project: Lucene - Java
Issue Type: Task
Reporter: Marti
[
https://issues.apache.org/jira/browse/SOLR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki resolved SOLR-1535.
-
Resolution: Fixed
Committed with minor tweaks in rev. 1327982.
> Pre-anal
[
https://issues.apache.org/jira/browse/SOLR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257535#comment-13257535
]
Shawn Heisey commented on SOLR-2020:
If this is a problem for 3.6 as well can you commi
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-3178:
---
Attachment: SOLR-3178.patch
Here's a patch that seems to work fine.
There's really no extra input-API
[
https://issues.apache.org/jira/browse/SOLR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257520#comment-13257520
]
Mark Miller commented on SOLR-1535:
---
+1 - I have not fully reviewed the patch, but did a
[
https://issues.apache.org/jira/browse/SOLR-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki resolved SOLR-3322.
-
Resolution: Fixed
Committed in rev. 1311812.
> Add more context to IndexR
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257439#comment-13257439
]
Per Steffensen commented on SOLR-3178:
--
Changed the response codes to not always be 40
[
https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257431#comment-13257431
]
Per Steffensen commented on SOLR-3178:
--
We have been working on it ourselves (SOLR-317
[
https://issues.apache.org/jira/browse/LUCENENET-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257395#comment-13257395
]
Björn edited comment on LUCENENET-486 at 4/19/12 10:57 AM:
---
M
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/13277/
No tests ran.
Build Log (for compile errors):
[...truncated 7147 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional com
[
https://issues.apache.org/jira/browse/SOLR-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257400#comment-13257400
]
Roger Håkansson commented on SOLR-3375:
---
I've downloaded HttpSolrServer.java from tru
Hello,
of course this is a problem. But the current solution doesn't find words
that are in the lucene indexe. Here are some samples:
https://issues.apache.org/jira/browse/LUCENENET-486 And this is a real
problem with a 'default' lucene analyzer. Not with a hypothetical ;)
Thank you
Björn
A
Hello,
I have added the issue:
https://issues.apache.org/jira/browse/LUCENENET-486 A testproject is
attached.
Björn
Am 17.04.2012 20:40, schrieb Christopher Currens:
I should also add, that directly reading the token stream, will produce
"bjor" (no wildcard) from "björ*".
Björn,
It would
[
https://issues.apache.org/jira/browse/SOLR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki reassigned SOLR-1535:
---
Assignee: Andrzej Bialecki
> Pre-analyzed field type
> ---
>
[
https://issues.apache.org/jira/browse/SOLR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257392#comment-13257392
]
Jan Høydahl commented on SOLR-1535:
---
+1 (not tested but positve to splitting up the eleph
[
https://issues.apache.org/jira/browse/SOLR-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257372#comment-13257372
]
Stefan Matheis (steffkes) commented on SOLR-3371:
-
Will see that we get SOL
This is probably a better idea as it allows fine-grained control (i.e.
excluding just tight loops)?
Dawid
On Thu, Apr 19, 2012 at 10:15 AM, Uwe Schindler wrote:
> To disable clover for heavy tests, we can use (its just a code comment to be
> included, that tells the instrumenter to disable cove
To disable clover for heavy tests, we can use (its just a code comment to be
included, that tells the instrumenter to disable coverage for this code part
between the comments):
http://goo.gl/ZohAv
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@t
[
https://issues.apache.org/jira/browse/SOLR-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257348#comment-13257348
]
Stefan Matheis (steffkes) commented on SOLR-3330:
-
Style-Changes committed
Hi,
Maybe TestNRQ does not like SimpleText (it seeks heavily), so maybe thats the
reason (we should check that with the seed) and add assume. Do other MTQ tests
allow SimpleText (like Fuzzy, which is also heavy)? With Clover the NRQ tests
then gets *very* slow. Compare with TestNRQ32, which suc
[
https://issues.apache.org/jira/browse/SOLR-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-3174:
Attachment: SOLR-3174-rgraph.png
SOLR-3174-graph.png
Updated
[
https://issues.apache.org/jira/browse/SOLR-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-3174:
Attachment: SOLR-3174.patch
So, there we go, updated patch with the logic, p
I'll try to inspect later today why these are so slow in that run:
[junit4] says g'day! Master seed: C26BAC36B9BF265D
[junit4] Suite: org.apache.lucene.index.TestByteSlices
[junit4] Completed in 1852.84s, 1 test
[junit4] Suite: org.apache.lucene.search.TestNumericRangeQuery64
[ju
[
https://issues.apache.org/jira/browse/SOLR-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Watermeyer updated SOLR-3381:
-
Attachment: FieldStreamDataSource.java
> FieldStreamDataSource should support CLOBs
>
[
https://issues.apache.org/jira/browse/SOLR-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Watermeyer updated SOLR-3381:
-
Attachment: (was: FieldStreamDataSource.java)
> FieldStreamDataSource should suppo
Non-redirected JVM output causes build errors
-
Key: LUCENE-4000
URL: https://issues.apache.org/jira/browse/LUCENE-4000
Project: Lucene - Java
Issue Type: Sub-task
Components: general/tes
[
https://issues.apache.org/jira/browse/SOLR-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Watermeyer updated SOLR-3381:
-
Attachment: FieldStreamDataSource.java
I have attached a subclass of FieldStreamDataSource
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-3377:
--
Fix Version/s: 3.6.1
> eDismax: A fielded query wrapped by parens is not recognized
> --
> I have seen this on jenkins several times (especially with Clover
> instrumentation). In this case instrumentation was running.
Clover is a hog, we've experienced that too.
> I think its caused by too many instrumentation (per statement) in heavy tests
> like TestNRQ or similar. Unfortunately
FieldStreamDataSource should support CLOBs
--
Key: SOLR-3381
URL: https://issues.apache.org/jira/browse/SOLR-3381
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler
[
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257334#comment-13257334
]
Bernd Fehling commented on SOLR-3377:
-
A suggestion, how would it be to do a simple "cl
Improve java client(s) test coverage
Key: SOLR-3380
URL: https://issues.apache.org/jira/browse/SOLR-3380
Project: Solr
Issue Type: Bug
Components: clients - java
Reporter: Sami Siren
I have seen this on jenkins several times (especially with Clover
instrumentation). In this case instrumentation was running.
I think its caused by too many instrumentation (per statement) in heavy tests
like TestNRQ or similar. Unfortunately we don’t see here, which test exactly
was leading to
[
https://issues.apache.org/jira/browse/SOLR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-2020.
--
Resolution: Fixed
> HttpComponentsSolrServer
>
>
> Key: SOL
[
https://issues.apache.org/jira/browse/SOLR-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257325#comment-13257325
]
Sami Siren commented on SOLR-2020:
--
bq. I also just added a simple test to TestDistributed
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257323#comment-13257323
]
uygar bayar commented on SOLR-2242:
---
hi
I tried it 3.6.0 with SOLR-2242-3x_5_tests.patc
[
https://issues.apache.org/jira/browse/SOLR-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren updated SOLR-3374:
-
Fix Version/s: 3.6.1
Assignee: Sami Siren
HttpSolrServer in 3.6.0 is buggy (SOLR-3375) so even if
[
https://issues.apache.org/jira/browse/SOLR-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren reassigned SOLR-3375:
Assignee: Sami Siren
> Charset problem using HttpSolrServer instead of CommonsHttpSolrServer
> -
[
https://issues.apache.org/jira/browse/SOLR-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257311#comment-13257311
]
Andrzej Bialecki commented on SOLR-1535:
-
The latest patch implements requested im
Whoa... never seen this one before --
[junit4] >>> error stream from forked JVM (verbatim)
[junit4] OpenJDK 64-Bit Server VM warning: CodeCache is full.
Compiler has been disabled.
[junit4] OpenJDK 64-Bit Server VM warning: Try increasing the code
cache size using -XX:ReservedCodeCac
70 matches
Mail list logo
