This one:
lucene/core/src/test/org/apache/lucene/search/TestSort.java
Yeah, I figured by comparing the size of these three... So, to make it
short -- every thread should get its own Random instance from a call
to LuceneTestCase's
public static Random random() {
return
Hi folks,
about the randomness: I think this should not be the case. if
different threads try to share the same random, actually there should
be an exception from the test framework saying that each thread should
get its own random (eg. initialized by a long value). So lucene-java
tests
So, if each thread gets the same seed, then they should also get the same
random values, right ?
They would start from the same seed so if they're calling that Random
in the same pattern then yes -- they'd get the same values. Any real
randomness will be non-reproducible. If this is needed for
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578212#comment-13578212
]
Dawid Weiss commented on LUCENE-4779:
-
There are three TestSort.java files (two in
[
https://issues.apache.org/jira/browse/SOLR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-4452:
--
Attachment: SOLR-4452.patch
New patch with testcase
Hunspell stemmer should not merge
[
https://issues.apache.org/jira/browse/SOLR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578228#comment-13578228
]
Jan Høydahl commented on SOLR-4452:
---
Think this is ready. Will commit in a day or two
[
https://issues.apache.org/jira/browse/SOLR-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-2043.
-
Resolution: Won't Fix
The dataimport.jsp is RIP
dataimport.jsp debug submission uses
[
https://issues.apache.org/jira/browse/SOLR-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578233#comment-13578233
]
Jan Høydahl commented on SOLR-2086:
---
Is this relevant for the new Admin GUI too? Else I'd
[
https://issues.apache.org/jira/browse/SOLR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-2314.
-
Resolution: Won't Fix
Closing old issue as the JSP's are now gone from Solr. Please re-open if still
a
[
https://issues.apache.org/jira/browse/SOLR-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-2696.
-
Resolution: Won't Fix
Closing old issue related to JSP which is now gone from Solr.
Please re-open if
[
https://issues.apache.org/jira/browse/SOLR-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-1573.
-
Resolution: Won't Fix
Closing old issue related to now non-existing JSP
Replication
[
https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578240#comment-13578240
]
Jan Høydahl commented on SOLR-1837:
---
[~solrtrey], is this something you still want to
Jan Høydahl created SOLR-4456:
-
Summary: Admin UI: Displays dashboard even if Solr is down
Key: SOLR-4456
URL: https://issues.apache.org/jira/browse/SOLR-4456
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578250#comment-13578250
]
Jan Høydahl commented on SOLR-4455:
---
+1
Stored value of NOW differs
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/179/
3 tests failed.
REGRESSION:
org.apache.lucene.index.TestIndexWriterOnDiskFull.testAddIndexOnDiskFull
Error Message:
Stack Trace:
java.lang.AssertionError
at
[
https://issues.apache.org/jira/browse/LUCENE-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578264#comment-13578264
]
Vojtěch Toman commented on LUCENE-4713:
---
We hit the same issue when using Lucene
Hi,
JIRA currently has 739 Open, Unresolved issues, with no activity for 1year,
which makes it difficult to get an overview over REAL issues.
The oldest of these, SOLR-36, have not been touched since July 2006 and is
probably not valid anymore.
Jan Høydahl created SOLR-4457:
-
Summary: Queries ending in question mark interpreted as wildcard
Key: SOLR-4457
URL: https://issues.apache.org/jira/browse/SOLR-4457
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-4453.
--
Resolution: Invalid
I suspect you have some kind of jar issue, because
1 it works fine for me
2
+1. We might be able to cut down on the spam a bit if people spent some
time triaging them first. I can do a little of that this weekend. 'course
just closing them will spam the list too, but in a good way G.
On Thu, Feb 14, 2013 at 6:13 AM, Jan Høydahl jan@cominvent.com wrote:
Hi,
I think this guy cannot assert this in close(), because upon exception
we will try to close file handles no matter what state we are in (even
if its the middle of a document)
On Thu, Feb 14, 2013 at 4:25 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build:
I also think these are redundant with checks in finish(). and finish()
could assert that numDocs is equal to the number of times
startDocument() was called.
On Thu, Feb 14, 2013 at 7:28 AM, Robert Muir rcm...@gmail.com wrote:
I think this guy cannot assert this in close(), because upon exception
Maybe a good idea would be to add asserting message too?
Shai
On Thu, Feb 14, 2013 at 2:32 PM, Robert Muir rcm...@gmail.com wrote:
I also think these are redundant with checks in finish(). and finish()
could assert that numDocs is equal to the number of times
startDocument() was called.
I never do this until I'm actually going to debug it.
On Thu, Feb 14, 2013 at 7:35 AM, Shai Erera ser...@gmail.com wrote:
Maybe a good idea would be to add asserting message too?
Shai
On Thu, Feb 14, 2013 at 2:32 PM, Robert Muir rcm...@gmail.com wrote:
I also think these are redundant
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578331#comment-13578331
]
Renaud Delbru commented on LUCENE-4642:
---
Hi, would this patch be considered for
You know, the more I think about it, the more I'm of the opinion that we
should just go ahead and close them aggressively. By that I mean take a
_very_ quick look and decide whether it's interesting. If we close it and
anyone's watching, they can feel free to re-open. If nobody's looking, the
[
https://issues.apache.org/jira/browse/SOLR-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jelsma updated SOLR-4280:
Attachment: SOLR-4280-trunk-1.patch
Patch for trunk introducing a
I did a scan like that, followed by close a long time ago, but then I did
it for 2 years old JIRAs. Perhaps you can bulk close all issues that were
not updated for more than 2 years?
That will generate much less spam (although I think that you can tick
somewhere to not send messages for bulk
Sorry for the spam, but one final thought: Let's tag them now so we can
find them again. That'll make closing them easier. Anyone who knows the
tagging mechanism better than me want to volunteer? I'll hold off on
closing any of them for a couple of days so others can chime in... And no,
I'm not
Hi,
yes you can click on „do not send emails“ for bulk operations. But there is a
big backside: The orginal reporter and watchers do not get the mail, too. And
this is not good.
In my opinion, we should simply do this as a one-time bulk action and we all
simply delete the mail. Another
Why should an issue be closed just because it's been open for N years?
It can easily be a real issue, just low priority. Eg likely many GSoC
tagged issues fall into this category.
I don't think we should do any bulk actions here: I think people who
care about the number of open issues should
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578377#comment-13578377
]
Robert Muir commented on LUCENE-4779:
-
this test tries to be way too clever (tracers
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578422#comment-13578422
]
Commit Tag Bot commented on LUCENE-4779:
[trunk commit] Robert Muir
On Feb 14, 2013, at 0:30, Dawid Weiss dawid.we...@gmail.com wrote:
This one:
lucene/core/src/test/org/apache/lucene/search/TestSort.java
Yeah, I figured by comparing the size of these three... So, to make it
short -- every thread should get its own Random instance from a call
to
On Wed, Feb 13, 2013 at 4:18 PM, Shawn Heisey s...@elyograg.org wrote:
On 2/13/2013 2:42 AM, Adrien Grand wrote:
Doc values are like FieldCache except that you don't need to uninvert
values from the inverted index whenever you open a new Reader. I think
there are two reasons why you would like
On Feb 14, 2013, at 9:00 AM, Michael McCandless luc...@mikemccandless.com
wrote:
I think people who
care about the number of open issues should actually look, issue by
issue, and make a call.
+1
- Mark
-
To unsubscribe,
[
https://issues.apache.org/jira/browse/SOLR-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578447#comment-13578447
]
James Dyer commented on SOLR-4280:
--
Markus,
On SOLR-4278, you said,
{quote}
It would be
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578457#comment-13578457
]
Commit Tag Bot commented on LUCENE-4779:
[trunk commit] Robert Muir
[
https://issues.apache.org/jira/browse/SOLR-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578460#comment-13578460
]
Markus Jelsma commented on SOLR-4280:
-
Hi James,
I'm not sure that i follow. This
[
https://issues.apache.org/jira/browse/SOLR-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578461#comment-13578461
]
Mark Beeby commented on SOLR-3819:
--
This is an issue we've encountered in our latest
[
https://issues.apache.org/jira/browse/SOLR-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578466#comment-13578466
]
James Dyer commented on SOLR-4280:
--
I'm thing I misunderstood initially. Thanks for the
[
https://issues.apache.org/jira/browse/SOLR-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated SOLR-3855:
---
Attachment: SOLR-3855.patch
Some progress: I removed support for DocValuesType.BINARY and modified
: Why should an issue be closed just because it's been open for N years?
...
: Why do we care about the number of open issues? Who is using this metric?
+1
Using a filter of has not been modified in X days to help find issues
that are *likeley* no longer relevant seems fine, and then
Hoss Man created SOLR-4458:
--
Summary: accespt uppercase ASC and DESC as sort orders
Key: SOLR-4458
URL: https://issues.apache.org/jira/browse/SOLR-4458
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-4458:
---
Attachment: SOLR-4458.patch
Patch is against 4.x but applies cleanly to trunk as well.
If you use a
: Not sure if there are any requirements to be a moderator,
Not really ... although I would probably raise some questions if a person
who had never participated in the list before tried to volunteer (but I've
never seen that happen)
Thanks to all 3 of our new volunteers, i've filed a Jira
[
https://issues.apache.org/jira/browse/SOLR-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578633#comment-13578633
]
David Smiley commented on SOLR-3973:
Zheng, could you comment on how this is different
[
https://issues.apache.org/jira/browse/SOLR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-4455:
--
Assignee: Hoss Man
Stored value of NOW differs between replicas
[
https://issues.apache.org/jira/browse/SOLR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4455:
---
Attachment: SOLR-4455.patch
Attaching a patch that adds the logic i was thinking of to
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/226/
Java: 64bit/jdk1.7.0 -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 8769 lines...]
[junit4:junit4] ERROR: JVM J0 ended with an exception, command line:
[
https://issues.apache.org/jira/browse/SOLR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4455:
---
Description:
I have a field in {{schema.xml}} defined like this:
{code:xml}
field name=timestamp type=date
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/246/
No tests ran.
Build Log:
[...truncated 11021 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
[
https://issues.apache.org/jira/browse/SOLR-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-1763:
--
Labels: extracting_request_handler solr_cell tika update_request_handler
(was: tag_test)
but arbitrarily deciding an issue should be closed just becuase it's old
doesn't really make sense to me to me.
That was never the suggestion either. More to get rid of all the noise which is
no longer relevant, neither to the issue creator or anyone else, then it's
easier to browse through
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578900#comment-13578900
]
Commit Tag Bot commented on LUCENE-4779:
[trunk commit] Robert Muir
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578903#comment-13578903
]
Commit Tag Bot commented on LUCENE-4779:
[trunk commit] Robert Muir
[
https://issues.apache.org/jira/browse/LUCENE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578929#comment-13578929
]
Commit Tag Bot commented on LUCENE-4779:
[trunk commit] Robert Muir
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/770/
No tests ran.
Build Log:
[...truncated 11059 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Mark Miller created SOLR-4459:
-
Summary: The Replication 'index move' optimization doesn't kick in
when using NRTCachingDirectory or the rate limiting option.
Key: SOLR-4459
URL:
Mark Miller created SOLR-4460:
-
Summary: When you have multiple collections, the cloud radial
graph view seems to place them right on top of each other.
Key: SOLR-4460
URL:
[
https://issues.apache.org/jira/browse/SOLR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4460:
--
Attachment: cloud.jpg
When you have multiple collections, the cloud radial graph view seems to
[
https://issues.apache.org/jira/browse/SOLR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-4460:
---
Attachment: cloud-radial-onecollection.png
Even with one collection, the radial graph is nearly
[
https://issues.apache.org/jira/browse/SOLR-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578971#comment-13578971
]
Mark Miller commented on SOLR-4316:
---
bq. If SolrCloud is enabled and you have a
[
https://issues.apache.org/jira/browse/LUCENE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578979#comment-13578979
]
Commit Tag Bot commented on LUCENE-4770:
[trunk commit] David Wayne Smiley
[
https://issues.apache.org/jira/browse/LUCENE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-4770.
--
Resolution: Fixed
Committed to 4.2 5.0 with this CHANGES.txt entry in the bugs area
[
https://issues.apache.org/jira/browse/LUCENE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578985#comment-13578985
]
Commit Tag Bot commented on LUCENE-4770:
[branch_4x commit] David Wayne Smiley
66 matches
Mail list logo
