[jira] [Updated] (LUCENE-3093) Build failed in the flexscoring branch because of Javadoc warnings

[ https://issues.apache.org/jira/browse/LUCENE-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Mark Nemeskey updated LUCENE-3093: Affects Version/s: flexscoring branch Thanks Robert! I have added the flexscoring

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 8078 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/8078/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 8080 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/8080/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional c

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 8077 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/8077/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 8079 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/8079/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional c

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 8076 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/8076/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[jira] [Commented] (LUCENE-3096) MultiSearcher does not work correctly with Not on NumericRange

[ https://issues.apache.org/jira/browse/LUCENE-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033878#comment-13033878 ] Xiaoyang Gu commented on LUCENE-3096: - Thank you very much! Xiaoyang > MultiSearche

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 8078 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/8078/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional c

[JENKINS] Solr-3.x - Build # 356 - Failure

Build: https://builds.apache.org/hudson/job/Solr-3.x/356/ No tests ran. Build Log (for compile errors): [...truncated 94 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: de

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 8075 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/8075/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 8077 - Still Failing

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/8077/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional c

[JENKINS] Lucene-Solr-tests-only-docvalues-branch - Build # 1124 - Failure

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-docvalues-branch/1124/ No tests ran. Build Log (for compile errors): [...truncated 47 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org Fo

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 8074 - Failure

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/8074/ No tests ran. Build Log (for compile errors): [...truncated 51 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[JENKINS] Lucene-Solr-tests-only-3.x - Build # 8076 - Failure

Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/8076/ No tests ran. Build Log (for compile errors): [...truncated 51 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional c

[JENKINS] Lucene-trunk - Build # 1563 - Failure

Build: https://builds.apache.org/hudson/job/Lucene-trunk/1563/ All tests passed Build Log (for compile errors): [...truncated 19381 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

[jira] [Commented] (LUCENE-3097) Post grouping faceting

[ https://issues.apache.org/jira/browse/LUCENE-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033865#comment-13033865 ] Bill Bell commented on LUCENE-3097: --- Here is another example... Doctors have multiple

Re: Reorganizing JIRA components

On May 15, 2011, at 10:42 PM, Shai Erera wrote: > I was aiming at avoiding that scenario. I think every issue should be > assigned to a specific component, and if there isn't one available, we should > create it. Based on history and how these things normally go, unless you are planning on

Re: Reorganizing JIRA components

Thanks Mark. Is it technically ok to rename existing components? Will the JIRA issues assigned to that component "survive" the rename? Sure - other will likely be not picking a component - common enough. > I was aiming at avoiding that scenario. I think every issue should be assigned to a specif

[jira] [Commented] (LUCENE-1149) add XA transaction support

[ https://issues.apache.org/jira/browse/LUCENE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033860#comment-13033860 ] Trejkaz commented on LUCENE-1149: - Is there an issue which this one is a true "duplicate"

[jira] [Created] (SOLR-2520) Solr creates invalid jsonp strings

Solr creates invalid jsonp strings -- Key: SOLR-2520 URL: https://issues.apache.org/jira/browse/SOLR-2520 Project: Solr Issue Type: Bug Affects Versions: 4.0 Reporter: Benson Margulies Please

[jira] [Commented] (SOLR-2399) Solr Admin Interface, reworked

[ https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033839#comment-13033839 ] Mark Miller commented on SOLR-2399: --- bq Used this rainy Saturday to complete the Replicat

Re: Reorganizing JIRA components

On May 15, 2011, at 2:20 PM, Shai Erera wrote: > Hi > > I noticed that we don't have a component for every contrib/module today, as > well as some components are misplaced, due to recent changes (e.g., analysis > should be IMO under modules/analysis). > > I would like to propose the following

[jira] [Updated] (SOLR-2458) post.jar fails on non-XML updateHandlers

[ https://issues.apache.org/jira/browse/SOLR-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2458: -- Fix Version/s: 3.2 Marking fo 3.2 since patch is ready > post.jar fails on non-XML updateHandlers > ---

[jira] [Updated] (SOLR-2489) Remove old lucene.apache.org/solr/who page

[ https://issues.apache.org/jira/browse/SOLR-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-2489: -- Fix Version/s: 3.2 > Remove old lucene.apache.org/solr/who page > --

[jira] [Updated] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated LUCENE-3098: -- Attachment: (was: LUCENE-3098.patch) > Grouped total count > -

[jira] [Updated] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated LUCENE-3098: -- Attachment: LUCENE-3098-3x.patch Last but not least: the 3x branch backport.

[jira] [Issue Comment Edited] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033801#comment-13033801 ] Martijn van Groningen edited comment on LUCENE-3098 at 5/15/11 7:58 PM: ---

[jira] [Updated] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated LUCENE-3098: -- Attachment: LUCENE-3098.patch LUCENE-3098.patch {quote} * May

Reorganizing JIRA components

Hi I noticed that we don't have a component for every contrib/module today, as well as some components are misplaced, due to recent changes (e.g., analysis should be IMO under modules/analysis). I would like to propose the following reorganization to JIRA components: * core/index, core/search etc

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033796#comment-13033796 ] Michael McCandless commented on LUCENE-3098: bq. The random tests are really

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033795#comment-13033795 ] Michael McCandless commented on LUCENE-3098: {quote} bq. I'm nervous that you

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033794#comment-13033794 ] Michael McCandless commented on LUCENE-3098: Patch looks great! And the chan

[jira] [Updated] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated LUCENE-3098: -- Attachment: LUCENE-3098.patch Attached new patch. * Added total count collecto

[jira] [Commented] (LUCENE-3102) Few issues with CachingCollector

[ https://issues.apache.org/jira/browse/LUCENE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033788#comment-13033788 ] Shai Erera commented on LUCENE-3102: bq. I will start w/ "svn mv" this to core Or, w

[jira] [Commented] (LUCENE-3102) Few issues with CachingCollector

[ https://issues.apache.org/jira/browse/LUCENE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033787#comment-13033787 ] Shai Erera commented on LUCENE-3102: bq. Hmm, I think it does clear cachedScores? (Bu

RE: Field should accept BytesRef?

Hi, I think Jason meant the field value, not the field name. Field names should stay Strings, as they are only "identifiers" making them BytesRefs is not really useful. But when you create an untokenized field (or even a binary field, which is stored-only at the moment), you could theoretical

[jira] [Commented] (LUCENE-3102) Few issues with CachingCollector

[ https://issues.apache.org/jira/browse/LUCENE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033784#comment-13033784 ] Michael McCandless commented on LUCENE-3102: Great catches Shai -- thanks for

Re: Field should accept BytesRef?

On Sun, May 15, 2011 at 12:05 PM, Jason Rutherglen wrote: > In the Field object a text value must be of type string, however I > think we can allow a BytesRef to be passed in? > it would be nice if we sorted them in byte order too? I think right now fields are sorted in utf-16 order, but terms ar

Field should accept BytesRef?

In the Field object a text value must be of type string, however I think we can allow a BytesRef to be passed in? - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.

[jira] [Updated] (SOLR-2519) Improve the defaults for the "text" field type in default schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated SOLR-2519: - Fix Version/s: 4.0 3.2 > Improve the defaults for the "text" field type

[jira] [Updated] (SOLR-2519) Improve the defaults for the "text" field type in default schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated SOLR-2519: - Attachment: SOLR-2519.patch Patch. I created a simple Chinese test, which fails w/ the de

[jira] [Assigned] (SOLR-2519) Improve the defaults for the "text" field type in default schema.xml

[ https://issues.apache.org/jira/browse/SOLR-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned SOLR-2519: Assignee: Michael McCandless > Improve the defaults for the "text" field type in def

[jira] [Created] (SOLR-2519) Improve the defaults for the "text" field type in default schema.xml

Improve the defaults for the "text" field type in default schema.xml Key: SOLR-2519 URL: https://issues.apache.org/jira/browse/SOLR-2519 Project: Solr Issue Type: Bug

[jira] [Created] (LUCENE-3102) Few issues with CachingCollector

Few issues with CachingCollector Key: LUCENE-3102 URL: https://issues.apache.org/jira/browse/LUCENE-3102 Project: Lucene - Java Issue Type: Bug Components: contrib/* Reporter: Shai Erera

Re: Apache Jenkins emails

Well, Gmail ignores (for grouping) everything that in between brackets []. That's how we made all issue emails appear under the same thread, the status (Commented, Created, Resolved etc.) now appears in brackets. So, I think that if we put the build # in brackets, the rest of the message is the sa

RE: Apache Jenkins emails

It's possible to change the header, as the mails are already customized. How should it look like (I don't use f*g Gmail) - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From: Shai Erera [mailto:ser...@gma

Apache Jenkins emails

Hi Is it possible to change the subject format of the emails Jenkins server sends? I was thinking, if we put the build # in [], all failures will be grouped under one thread (in Gmail). Since we have so many of them, it will at least collapse all of them into a single thread. We can still tell the

[jira] [Resolved] (SOLR-2518) Empty of so that it resolves the parent pom from the repositories

[ https://issues.apache.org/jira/browse/SOLR-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe resolved SOLR-2518. --- Resolution: Fixed Fix Version/s: 4.0 3.2 Assignee: Steven Rowe Than

[jira] [Commented] (LUCENE-3099) Grouping module should allow subclasses to set the group key per document

[ https://issues.apache.org/jira/browse/LUCENE-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033692#comment-13033692 ] Michael McCandless commented on LUCENE-3099: I was thinking we could paramete

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033691#comment-13033691 ] Michael McCandless commented on LUCENE-3098: OK thanks Martijn! The new coll

[jira] [Commented] (LUCENE-3099) Grouping module should allow subclasses to set the group key per document

[ https://issues.apache.org/jira/browse/LUCENE-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033688#comment-13033688 ] Martijn van Groningen commented on LUCENE-3099: --- All the current group coll

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033687#comment-13033687 ] Martijn van Groningen commented on LUCENE-3098: --- bq. SentinelIntSet rehashe

[jira] [Commented] (LUCENE-3101) TestMinimize.testAgainstBrzozowski reproducible seed OOM

[ https://issues.apache.org/jira/browse/LUCENE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033680#comment-13033680 ] Uwe Schindler commented on LUCENE-3101: --- {quote} [14:08] s1monw: that automaton has

[jira] [Commented] (LUCENE-3101) TestMinimize.testAgainstBrzozowski reproducible seed OOM

[ https://issues.apache.org/jira/browse/LUCENE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033679#comment-13033679 ] Uwe Schindler commented on LUCENE-3101: --- Thanks! What to do? > TestMinimize.testAg

[jira] [Assigned] (LUCENE-3101) TestMinimize.testAgainstBrzozowski reproducible seed OOM

[ https://issues.apache.org/jira/browse/LUCENE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir reassigned LUCENE-3101: --- Assignee: Uwe Schindler > TestMinimize.testAgainstBrzozowski reproducible seed OOM > ---

[jira] [Created] (LUCENE-3101) TestMinimize.testAgainstBrzozowski reproducible seed OOM

TestMinimize.testAgainstBrzozowski reproducible seed OOM Key: LUCENE-3101 URL: https://issues.apache.org/jira/browse/LUCENE-3101 Project: Lucene - Java Issue Type: Bug Repo

[jira] [Commented] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033668#comment-13033668 ] Michael McCandless commented on LUCENE-3098: Thanks for the quick pach Martij

[jira] [Issue Comment Edited] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033660#comment-13033660 ] Martijn van Groningen edited comment on LUCENE-3098 at 5/15/11 11:00 AM: --

[jira] [Updated] (LUCENE-3098) Grouped total count

[ https://issues.apache.org/jira/browse/LUCENE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated LUCENE-3098: -- Attachment: LUCENE-3098.patch Attached an initial patch for computing the tota