Re: pom.xml.template schemaLocation

Thanks Steve! I've gone with the http:// which is what the maven.html is using. - Original Message - From: dev@lucene.apache.org To: Christine Poerschke (BLOOMBERG/ LONDON), dev@lucene.apache.org At: 10/16/17 16:18:35 I guess canonical is overstating it - here’s the one from both the POM

pom.xml.template schemaLocation

I noticed that we have xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; currently and that doesn't seem to exist at present. There's a https://maven.apache.org/xsd/maven-v3_0_0.xsd and a https://maven.apache.org/xsd/maven-4.0.0.xsd linked

Re: Welcome Hrishikesh Gadre as Lucene/Solr committer

Welcome Hrishikesh! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 10/03/17 09:37:51 Welcome Hrishikesh On Mon, Oct 2, 2017 at 9:32 PM, Adrien Grand wrote: > Welcome Hrishikesh! > > Le lun. 2 oct. 2017 à 02:34, Koji Sekiguchi

Re: Release 7.0 process starts

Sure. Joel, could you edit directly in the WIKI? (I'm about to go into a meeting.) Thanks! Christine From: dev@lucene.apache.org At: 09/20/17 16:07:11To: Christine Poerschke (BLOOMBERG/ LONDON ) , dev@lucene.apache.org Subject: Re: Release 7.0 process starts For streaming expressions let's

Re: Release 7.0 process starts

, a new statistical programming syntax for the statistical analysis of sql queries, random samples, time series and graph result sets. * Solr 7 is tested with and verified to support Java 9 From: dev@lucene.apache.org At: 09/20/17 15:54:54To: Christine Poerschke (BLOOMBERG/ LONDON ) , dev

Re: Release 7.0 process starts

Totally agree with choosing _7_ highlights for the Solr _7_ release! Below is the revised draft I came up with: (Notice that v2 is the 2nd bullet, though I think it yet needs to mention one or _two_ benefits of using the new API especially since we mention that /solr/ continues to work.)

Re: [VOTE] Release Apache Lucene/Solr 7.0.0 RC3

Thanks Jan for these observations! The Couldn't add files WARNing seems be pre-existing and I've created SOLR-11346 to explore if actually it should be an ERROR/exception. About the solr.LatLonType WARNing, does the DIH example actually use those field types? If not could they simply be

preferredLeader vs. preferredleader

Hi Everyone, As part of SOLR-11090 i noticed that in some places "preferredLeader" is used and in other places "preferredleader" is used i.e. upper vs. lower case L. From a quick-ish look around i couldn't quite tell if that's unintended or if there is a difference in usage and meaning

Re: 10 Resource Leak warnings dated to Q2 2017

but not all resource leaks. Implementation wise, how might one go about that? Redirecting precommit output and post-processing it should be do-able but seems hacky ... Christine - Original Message - From: dev@lucene.apache.org To: Christine Poerschke (BLOOMBERG/ LONDON), dev@lucene.apache.org

Re: Feature freeze @ 7.0 branch

I'd like to see https://issues.apache.org/jira/browse/SOLR-10985 included in 7.0 since it's a small low-risk change but it being in cache classes will benefit many users. Christine From: dev@lucene.apache.org At: 07/05/17 16:00:48 To: dev@lucene.apache.org Subject: Re: Feature freeze @ 7.0

10 Resource Leak warnings dated to Q2 2017

Hi Everyone, The following list is the latest Q2 2017 portion of the dated-warnings.log file I've attached to https://issues.apache.org/jira/browse/SOLR-10778 and it was generated by the also attached shell script that correlates warnings with git commit history. Any help to investigate and

Re: Release planning for 7.0

Hi Anshum, SOLR-10962 is turning out bigger (and better) than it seemed at first. So please don't delay any branch cutting etc. because of it. Thanks & Have a good weekend! Christine From: dev@lucene.apache.org At: 06/30/17 04:47:47 To: dev@lucene.apache.org Subject: Re: Release planning for

Re:[1/2] lucene-solr:master: SOLR-1095: Refactor code to standardize replica assignment

The addition of the new ReplicaPosition.java file here appears to have broken (the documentation-lint part of) precommit. [exec] missing description: org.apache.solr.common.cloud [exec] [exec] Missing javadocs were found! - Original Message - From: dev@lucene.apache.org

Re: Release planning for 7.0

I'd be interested in https://issues.apache.org/jira/browse/SOLR-10962 making it into 7.0 if there's time but wouldn't want to block progress. Christine From: dev@lucene.apache.org At: 06/27/17 07:30:47 To: dev@lucene.apache.org Subject: Re: Release planning for 7.0 Erick, sure. If you think

(how) do folks use the Cloud Graph (Radial) in the Solr Admin UI?

Any thoughts on potentially removing the radial cloud graph? https://issues.apache.org/jira/browse/SOLR-5405 is the background for the question and further input and views would be very welcome. Thanks, Christine - To

SolrMetricReporter init/validate logic

Hi Everyone, If anyone has a few minutes, I'd appreciate further input and/or code reviews for https://issues.apache.org/jira/browse/SOLR-10671 logic tweaks. Thanks, Christine

Re: [DISCUSS] Sandbox module dependencies

lucene-queryparser has an existing dependency on lucene-sandbox and it puzzled/confused me when first coming across is. Nothing depending on sandbox would seem clearer i.e. it's sandboxed, isolated, contained, etc. Instead of comments/statements (in caps or otherwise) in the ivy.xml files,

Re:Release planning for 7.0

Hi Everyone, Just to say that https://issues.apache.org/jira/browse/SOLR-8668 for removal should complete later this week, hopefully. And on an unrelated note, does anyone have any history or experience with the NOTICE.txt files? Including https://issues.apache.org/jira/browse/LUCENE-7852 in

Re: Strange Solr JIRA versions (Lucene too!)

Hi Everyone, Perhaps a little more context would help get us all on the same page re: the "to 6.x or to not 6.x" tag question. === "to 6.x" tag === So, some of us (myself included) for SOLR issues used to tag FixVersion 6.x since the commit was to branch_6x and (at least myself) assumed that

Re: Strange Solr JIRA versions (Lucene too!)

Thanks for flagging this up! I've gone and tidied up a few (but not all) using a very unsophisticated git grep approach to determine the fix version. what=LUCENE- for version in 0 1 2 3 4 5 6 ; do echo branch_6_$version git log --decorate --oneline --graph origin/branch_6_$version |

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

The "javadocs want to fail" output sounds like https://issues.apache.org/jira/browse/SOLR-10004 ticket. From: dev@lucene.apache.org At: 05/17/17 18:44:36 To: dev@lucene.apache.org Subject: Re: [VOTE] Release Lucene/Solr 6.6.0 RC1 The smoke tester ended with: SUCCESS! [0:59:34.797969]

HttpShardHandlerFactory.loadBalancerRequests(MinimumAbsolute|MaximumFraction)

Hi Everyone, If anyone has a few moments this week, I'd appreciate further feedback and/or code reviews for https://issues.apache.org/jira/browse/SOLR-10479 new feature. Thanks, Christine

Re:Welcome Mike Drob as Lucene/Solr committer

Welcome Mike! From: dev@lucene.apache.org At: 05/08/17 16:42:41 To: dev@lucene.apache.org, md...@apache.org Subject: Re:Welcome Mike Drob as Lucene/Solr committer I'm pleased to announce that Mike Drob has accepted the PMC's invitation to become a committer. Mike, it's tradition that you

Re: Requires subscription

Hi Adeppa, Thanks for your interest and welcome! As Dorian mentioned https://wiki.apache.org/solr/HowToContribute has lots of information on how to get involved. I saw Learning-to-Rank on your profile and so perhaps https://issues.apache.org/jira/browse/SOLR-10174 might be of interest as a

Re: Release 6.6

I'd appreciate feedback on https://issues.apache.org/jira/browse/SOLR-10479 with a view towards making it into the 6.6 release. Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 04/25/17 19:13:39 I’d like to get SOLR-1485, at least the numeric

Re: [VOTE] Release Lucene/Solr 6.5.1 RC1

I've held back from porting to 6.5.1 on the assumption that 6.5.1 would be mostly to fix bugs introduced in 6.5.0 but not necessarily bugs that existed before then, unless the fixes are small and/or the bug serious e.g. security issues. Not quite sure how that assumption came about.

Re: Strange Solr JIRA versions

Joining the conversation late here. I've been using fixVersion 6.x in the honest belief that: * that was the done thing (and now i know that it isn't, oops) * what is displayed as 6.x now will in future become 6.6 (when 6.6 is released) or it will stay 6.x (if there is no 6.6 release) * if a

Resolved --> Closed transition for 6.4 release issues

Hi Everyone, Does anyone recall how the 'Resolved' to 'Closed' status transition for JIRA issues works? I just noticed that some 6.4 tickets are still marked 'Resolved' rather than 'Closed' which surprised me. This JQL finds them: "status = Resolved and project in (LUCENE,SOLR) and

Re: 6.5.1 release?

I'd also like to include fix for https://issues.apache.org/jira/browse/SOLR-10421 which should be just four lines of actual fix, plus ideally a test for it which will be more than four lines ... - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 04/04/17

Re:code comment out of date: Note that newly flushed segments will remain unsorted

Thanks for noticing and reporting this. I committed a fix under https://issues.apache.org/jira/browse/LUCENE-7763 ticket. Christine From: dev@lucene.apache.org At: 03/31/17 14:27:33 To: dev@lucene.apache.org Subject: Re:code comment out of date: Note that newly flushed segments will remain

Re: 6.5.1 release?

I'd like to include https://issues.apache.org/jira/browse/SOLR-10383 too (on Monday) if there are no objections or concerns. From: dev@lucene.apache.org At: 03/31/17 15:08:12 To: Christine Poerschke (BLOOMBERG/ LONDON), dev@lucene.apache.org Subject: Re: 6.5.1 release? Joel, I'd like to include

Re: 6.5.1 release?

Correct, release 6.5.1 will be off branch_6_5 branch and there will be a 6.5.1 tag (but not branch) e.g. for the 6.4.2 release we have tag https://github.com/apache/lucene-solr/tree/releases/lucene-solr/6.4.2 branch_6_6 will (in future) be branched off the branch_6x branch. branch_7x will (in

Re:JIRA non-logged-in filters issue (infra?) - GSOC2017 impact

Hi Alex, Thanks for noticing and diagnosing and following up on this. You asked if somebody could confirm what you found. Jonny Marks and I were able to confirm what you describe though we used not label=gsoc2017 but reporter=jm100 as the JQL search criteria: *

Re: Dealing with issues reported by Findbugs

Hi Shawn, I'm also interested in how IDE warning logic could be used more. https://issues.apache.org/jira/browse/LUCENE-7746 is in that direction, indirectly i.e. it would guard against re-introduction of warnings/errors previously dealt with. Thanks, Christine - Original Message -

Re:[JENKINS-EA] Lucene-Solr-6.x-Linux (64bit/jdk-9-ea+160) - Build # 3057 - Unstable!

Taking a look. - Original Message - From: dev@lucene.apache.org To: a...@apache.org, cpoersc...@apache.org, dev@lucene.apache.org, markrmil...@apache.org At: 03/14/17 12:56:37 Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/3057/ Java: 64bit/jdk-9-ea+160

Re: Developer's Guide

Somewhat related, any thoughts on combining the two 'How to Contribute to ...' wiki pages into a unified 'How to Contribute' under lucene.apache.org itself? https://wiki.apache.org/lucene-java/HowToContribute https://wiki.apache.org/solr/HowToContribute - Original Message - From:

Re: 6.4.2 release?

as the 5.5.4 backward indices when we cut the first RC. I will let you know when I am done. Le mer. 15 févr. 2017 à 15:53, Christine Poerschke (BLOOMBERG/ LONDON) <cpoersc...@bloomberg.net> a écrit : Hi, These two could be minor candidates for inclusion: * https://issues.apache.org/jira

Re: 6.4.2 release?

is to have it in the 6.4.2 section from the outset (if it goes into the 6.4.2 release that is). Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 02/22/17 13:42:54 Hi Christine, > On Feb 22, 2017, at 5:10 AM, Christine Poerschke (BLOOMBERG/ LON

Re: 6.4.2 release?

ng with a >> new release now. >> >> Le mer. 15 févr. 2017 à 16:13, Adrien Grand <jpou...@gmail.com >> <mailto:jpou...@gmail.com>> a écrit : >> >> +1 >> >> One ask I have is t

Re: solr info

Two related links, non-generic links :) http://lucene.apache.org/solr/resources.html http://lucene.apache.org/solr/community.html#mailing-lists-irc - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 02/15/17 23:43:40 On 16 February 2017 at 04:34,

Re:6.4.2 release?

Hi, These two could be minor candidates for inclusion: * https://issues.apache.org/jira/browse/SOLR-10083 Fix instanceof check in ConstDoubleSource.equals * https://issues.apache.org/jira/browse/LUCENE-7676 FilterCodecReader to override more super-class methods The former had narrowly

Re:Welcome Toke Eskildsen as a Lucene/Solr committer

Welcome Toke! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 02/14/17 12:09:32 I'm pleased to announce that Toke Eskildsen has accepted the Lucene PMC's invitation to become a committer. Toke, it's tradition that you introduce yourself with a brief bio.

Re: [JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_121) - Build # 6385 - Still Failing!

Oops, my mistake. Thanks for fixing Adrian! From: dev@lucene.apache.org At: 02/10/17 08:41:09 To: cpoersc...@apache.org, dev@lucene.apache.org, markrmil...@apache.org Subject: Re: [JENKINS] Lucene-Solr-master-Windows (64bit/jdk1.8.0_121) - Build # 6385 - Still Failing! I removed the unused

Re: [VOTE] Release Lucene/Solr 6.4.1 RC1

If there were to be a respin (and I understand that is an 'if' at this point) then I'd like to propose for the small (unrelated) https://issues.apache.org/jira/browse/SOLR-10083 fix to be included. Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At:

RE: Disable HTML mails

+1 for text. From: dev@lucene.apache.org At: 01/31/17 14:56:51 To: dev@lucene.apache.org Subject: RE: Disable HTML mails Yes, that was meant as a majority vote, or not? Vetoing makes no sense here! Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail:

Re: mirrors-solr-latest-redir.html vs. mirrors-solr-latest-redir.html?

Downloads landing page (automatically from /doap.rdf, including links to RefGuide) and instead of the redirect we display a download button which links to closer.lua with latest version. -- Jan Høydahl Den 23. jan. 2017 kl. 17.07 skrev Christine Poerschke (BLOOMBERG/ LONDON) <cpoe

Re: Lucene/Solr 7

+1 for May. I'd like to see https://issues.apache.org/jira/browse/SOLR-8668 in the 7.0 release (and have tagged/updated the ticket to indicate so). Christine From: dev@lucene.apache.org At: 01/24/17 17:17:27 To: dev@lucene.apache.org Subject: Re: Lucene/Solr 7 I would love to see SOLR-5944,

Re: mirrors-solr-latest-redir.html vs. mirrors-solr-latest-redir.html?

Problem solved for me (thanks Diego!) - the trick is to do a 'refresh' in the browser in the few seconds _before_ the mirrors-solr-latest-redir page redirects to the download page. From: dev@lucene.apache.org At: 01/23/17 15:14:43 To: Christine Poerschke (BLOOMBERG/ LONDON), dev

Re: mirrors-solr-latest-redir.html vs. mirrors-solr-latest-redir.html?

Thanks Ishan for quick reply. The second link should have had the ? included in the clickable link and with that ? as part of the link then for me it redirects to 6.4.0 as expected. From: dev@lucene.apache.org At: 01/23/17 14:58:04 To: Christine Poerschke (BLOOMBERG/ LONDON), dev

mirrors-solr-latest-redir.html vs. mirrors-solr-latest-redir.html?

Hello. Is anyone else able to reproduce: http://lucene.apache.org/solr/mirrors-solr-latest-redir.html vs. http://lucene.apache.org/solr/mirrors-solr-latest-redir.html? The former is the Download image on http://lucene.apache.org/solr/ (for me and a colleague going to 6.3.0 still) and also

ContributorsGroup Wiki (https://wiki.apache.org/solr)

Please add my username to the ContributorsGroup: ChristinePoerschke Thank you. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 6.4 release

I'm looking into https://issues.apache.org/jira/browse/SOLR-9972 which just came in. From: dev@lucene.apache.org At: 01/16/17 15:05:45 To: dev@lucene.apache.org Subject: Re: 6.4 release You can still push bug fixes Alan, I'll create the first RC tomorrow if the all the builds are green.This

Re:[jira] [Commented] (SOLR-8542) Integrate Learning to Rank into Solr

Hi Cassandra, JIRA looks to be down with ETA for it being back beyond the end of my day here in London but I just wanted to let you know about the draft umbrella page https://cwiki.apache.org/confluence/display/solr/Machine+Learning+and+Solr that I just started. Also cc/fyi including Joel

Re: Welcome Cao Manh Dat as a Lucene/Solr committer

Congrats and welcome! From: dev@lucene.apache.org At: 01/10/17 11:29:42 To: dev@lucene.apache.org Subject: Re: Welcome Cao Manh Dat as a Lucene/Solr committer Congrats Đạt. Very well deserved! On Tue, Jan 10, 2017 at 10:02 AM, Shalin Shekhar Mangar wrote:

Re: 6.4 release

Hi Jim, there's some permissions group to which your wiki handle probably still needs to be added, I recall running into this myself w.r.t. editing pages. This thread sounds related: http://apache.markmail.org/thread/5ldcbqa5tirofplc Going forward, could we make wiki and cwiki permission setup

Re: 6.4 release

All done, thanks for checking. Have a good weekend. From: dev@lucene.apache.org At: 01/06/17 18:23:06 To: dev@lucene.apache.org Subject: Re: 6.4 release Thanks all for your answers. Are we still good to build the first RC on Monday ? Christine maybe do you need more time ? 2017-01-05 5:47

Re: 6.4 release

I'd like to finalise the name of the Learning-To-Rank (SOLR-8542) Solr Ref Guide page before the first RC is cut. Details: The Solr Reference Guide content for SOLR-8542 (Integrate Learning to Rank into Solr) is currently on the tentatively named

Re:Welcome Jim Ferenczi as a Lucene/Solr committer

Welcome Jim! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 01/01/17 10:05:18 I'm pleased to announce that Jim Ferenczi has accepted the Lucene PMC's invitation to become a committer. Jim, it's tradition that you introduce yourself with a brief bio. Your

Re: Welcome Ishan Chattopadhyaya as Lucene/Solr committer

Welcome Ishan! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 11/29/16 18:29:43 Welcome Ishan! On Tue, Nov 29, 2016 at 10:25 AM, Dawid Weiss wrote: > Welcome Ishan and congratulations! > > Dawid > > On Tue, Nov 29, 2016 at 7:21 PM,

Re:[GitHub] lucene-solr pull request #116: fixed NPEs

Hi Roman, thanks for your pull request. I have created https://issues.apache.org/jira/browse/SOLR-9775 to correspond to it. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 11/15/16 21:43:05 GitHub user kagan770 opened a pull request:

Re: VOTE: Apache Solr Reference Guide for Solr 6.3

I'm done too, having fixed a typo and added two javadocs links on https://cwiki.apache.org/confluence/display/solr/Query+Re-Ranking page. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 11/08/16 13:56:47 I’m done. I fixed a few other minor things I

Re: [JENKINS] Lucene-Solr-SmokeRelease-master - Build # 610 - Failure

Thanks Steve! Adding maven config had been on our radar as a 'before branch_6x cherry-pick' item but I had forgotten about this Jenkins job here, oops, sorry. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 11/02/16 14:05:30 I committed a fix (hopefully) -

Re: Lucene/Solr 6.2.0 release

It would be good to include these two minor bug fixes i think: https://issues.apache.org/jira/browse/SOLR-9413 (actually really LUCENE-) https://issues.apache.org/jira/browse/SOLR-9391 (for solr/client/solrj) Patches available for both. Reviews and comments welcome as usual. Thanks,

Re: Welcome Alexandre Rafalovitch as a Lucene/Solr committer!

Welcome Alex! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 08/07/16 06:15:24 Thank you everybody. I can confirm that I can add myself the whoweare page. I am looking forward to gaining similar privileges to the JIRA and the Reference Guide. I can say

RE: [JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_92) - Build # 17331 - Failure!

SQLHandler.java fix committed. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 07/22/16 15:06:57 This is caused by this additional failure (build is not only unstable, it failed): [ecj-lint] 11. ERROR in

Re:[JENKINS-EA] Lucene-Solr-master-Linux (64bit/jdk-9-ea+127) - Build # 17298 - Still Unstable!

I broke this in SOLR-9275, fix committed. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: 07/19/16 10:30:42 Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17298/ Java: 64bit/jdk-9-ea+127 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests

Re:[JENKINS-MAVEN] Lucene-Solr-Maven-6.x #113: POMs out of sync

Hello. "POMs out of sync" - will it get synced up automatically somehow or is some sort of human intervention needed? In SOLR-9298 and SOLR-9300 I made some small maven/pom related changes today but am quite new to maven. Thanks, Christine - Original Message - From:

Re: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3351 - Failure!

Thanks Adrien! Looks like the same eclipse vs. precommit difference also exists for org.eclipse.jdt.core.compiler.problem.comparingIdentical=error org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error categories. I'll go ahead and add those two for the eclipse configuration. From:

Re:[JENKINS] Lucene-Solr-master-Linux (64bit/jdk1.8.0_92) - Build # 16766 - Still Failing!

Created https://issues.apache.org/jira/browse/SOLR-9121 with a rough patch fix. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: May 17 2016 10:46:42 Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/16766/ Java: 64bit/jdk1.8.0_92

Re:[JENKINS] Lucene-Solr-master-Linux (32bit/jdk1.8.0_92) - Build # 16693 - Failure!

Have created https://issues.apache.org/jira/browse/SOLR-9093 for this. Though as yet undecided on minimalistic vs. wider scope fix. Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: May 9 2016 10:40:31 Build:

Re: org.apache.solr.schema.TestManagedSchemaAPI.test

ed the test and retry > logic. This was a couple of months back when I had initially worked on the > patch so I don't remember everything. -- Steve www.lucidworks.com > On May 6, 2016, at 9:43 AM, Christine Poerschke (BLOOMBERG/ LONDON) > <cpoersc...@bloomberg.net> wrote: >

Re: solr.common.util.Pair --> commons.lang3.tuple.Pair

Thanks everyone for your input! I have created https://issues.apache.org/jira/browse/SOLR-9079 as a future 'wish' item. Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: May 5 2016 19:53:58 On 5/5/2016 11:07 AM, Erick Erickson wrote: > Or

org.apache.solr.schema.TestManagedSchemaAPI.test

Hello. Just wondering if anyone is looking into these? I took a little look and am unclear on the difference between the testReloadAndAddSimple and testAddFieldAndDocument methods. Happy to @BadApple annotate and create a JIRA ticket for follow-up if that would help? Christine -

solr.common.util.Pair --> commons.lang3.tuple.Pair

Steve Davids wrote on another email thread: Though, out of curiosity why not just use the Pair class in Apache Commons-Lang? http://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/tuple/Pair.html I'd be +1 to switching over to org.apache.commons.lang3.tuple.Pair - it

Re: Welcome Scott Blum as a Lucene/Solr committer!

Welcome Scott! From: dev@lucene.apache.org At: Apr 19 2016 19:05:29 To: dev@lucene.apache.org Subject: Re: Welcome Scott Blum as a Lucene/Solr committer! Thanks everyone! I'm currently an engineer at FullStory, where search is one of the foundational aspects of what we do. Among other things,

Re:[JENKINS-EA] Lucene-Solr-master-Linux (32bit/jdk-9-ea+113) - Build # 16505 - Still Failing!

Probably correlated to my LUCENE-7210 change. Looking into. - Original Message - From: jenk...@thetaphi.de To: cpoersc...@apache.org, dev@lucene.apache.org, mikemcc...@apache.org At: Apr 14 2016 17:53:51 Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/16505/ Java:

Re:[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 520 - Failure!

Probably correlated to my LUCENE-7210 change. Looking into. - Original Message - From: jenk...@thetaphi.de To: cpoersc...@apache.org, dev@lucene.apache.org, mikemcc...@apache.org At: Apr 14 2016 17:36:36 Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/520/ Java:

Re: Welcome Karl Wright as a Lucene/Solr committer!

Welcome Karl! From: dev@lucene.apache.org At: Apr 5 2016 07:49:10 To: dev@lucene.apache.org Subject: Re: Welcome Karl Wright as a Lucene/Solr committer! Welcome! On 5 April 2016 at 01:35, Karl Wright wrote: Thanks to all for the warm welcome!! I am honored to be a part

Re: git email format customizability: add branch to subject?

+1 for keeping the repo name but perhaps we could drop the "git: " prefix? Without the prefix the subject would still be fairly distinguishable from the "svn commit" emails such as "svn commit: r1731559 - /lucene/cms/trunk/content/extpaths.txt" (assuming the svn commit emails keep their

Re:git email format customizability: add branch to subject?

https://git-wip-us.apache.org/docs/switching-to-git.html seems to suggest there is per project flexibility. Branch not one of the (currently) available variables though, no? +1 for "the branch be included in the subject" Christine - Original Message - From: dev@lucene.apache.org To:

RE: [JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 3082 - Still Failing!

Thanks Uwe! - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: Feb 13 2016 12:56:45 I committed a fix. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Uwe Schindler

Re:[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+104) - Build # 15867 - Failure!

This is me. Taking a look and will remedy. - Original Message - From: dev@lucene.apache.org To: cpoersc...@apache.org, dev@lucene.apache.org At: Feb 12 2016 21:08:48 Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15867/ Java: 64bit/jdk-9-ea+104 -XX:-UseCompressedOops

Re: Lucene/Solr 6.0.0 release

+1 for 5.5.0 release. Am about to mark SOLR-8621 as a blocker, it's basically 'done' (with collaboration and help from Shai) but a signature change for MergePolicyFactory will be needed to support SOLR-5730 (which ideally would also be included in 5.5.0 and which hopefully can be wrapped up

Re:[JENKINS] Lucene-Solr-5.x-MacOSX (64bit/jdk1.8.0) - Build # 2999 - Failure!

This is due to my LUCENE-7006 change adding this test. Able to reproduce (3 out of 3 times) with given seed and args. Will look into further (though not today). Christine - Original Message - From: dev@lucene.apache.org To: cpoersc...@apache.org, dev@lucene.apache.org, sar...@gmail.com

Re: reviews.apache.org / GIT migration

Yes, thanks for the input everyone. https://issues.apache.org/jira/browse/INFRA-11152 created for a lucene-solr.git project on ReviewBoard. From: dev@lucene.apache.org At: Jan 26 2016 19:55:44 To: dev@lucene.apache.org Cc: Christine Poerschke (BLOOMBERG/ LONDON) Subject: Re: reviews.apache.org

reviews.apache.org / GIT migration

Hello. Having not used it before, I'd like to try out reviews.apache.org (even though it's only been used a few times for the project in the past based on the https://reviews.apache.org/groups/lucene/ listing). The review board seems so far unware of the svn-to-git migration. Other projects

Re:reviews.apache.org / GIT migration

Looks like https://issues.apache.org/jira/browse/INFRA-7630 set up the original/existing review board. If there are no objections or existing ticket then I will raise a similar ticket towards the end of this week. Christine - Original Message - From: dev@lucene.apache.org To:

Re:[jira] [Updated] (LUCENE-6962) Add per-dimension min/max to dimensional values

Apologies, meant to reply to the commits mailing list. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: Jan 8 2016 13:19:51 Hello. Might there be a min-versus-max copy/paste mistake in getMaxPackedValue? I will try next to see if that fixes recent

Re:[jira] [Updated] (LUCENE-6962) Add per-dimension min/max to dimensional values

Hello. Might there be a min-versus-max copy/paste mistake in getMaxPackedValue? I will try next to see if that fixes recent org.apache.lucene.index.TestDuelingCodecs test failures. Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: Jan 6 2016

Re:svn commit: r1723682 - in /lucene/dev/trunk/lucene: ./ codecs/src/java/org/apache/lucene/codecs/simpletext/ core/src/java/org/apache/lucene/codecs/ core/src/java/org/apache/lucene/codecs/lucene60/

Hello. Might there be a min-versus-max copy/paste mistake in getMaxPackedValue? I will try next to see if that fixes recent org.apache.lucene.index.TestDuelingCodecs test failures. Christine - Original Message - From: dev@lucene.apache.org To: comm...@lucene.apache.org At: Jan 8 2016

SOLR-5209 in time for 6.0.0 release?

Hello Folks, Would anyone have a little time to review and comment on the latest https://issues.apache.org/jira/browse/SOLR-5209 patch which perhaps went simply unnoticed towards the end of 2015? Thanks, Christine

Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

, feature freeze in place (was Re: A 5.4 release?) The patch seems innocuous enough. From the ticket though it isn't so clear to me what problem it solves. I'm open to the opinion of others. Upayavira On Mon, Nov 30, 2015, at 12:09 PM, Christine Poerschke (BLOOMBERG/ LONDON) wrote

Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

As suggested I have now patched https://issues.apache.org/jira/browse/SOLR-8340 fix to 5.4 branch. From: dev@lucene.apache.org At: Nov 25 2015 14:11:46 To: dev@lucene.apache.org Subject: Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?) I have created the

Re:5.4 branch created, feature freeze in place (was Re: A 5.4 release?)

Any thoughts on getting the https://issues.apache.org/jira/browse/LUCENE-6911 fix into 5.4 solr or not? Basically StandardQueryParser's existing getMultiFields method is a no-op. From: dev@lucene.apache.org At: Nov 25 2015 14:11:46 To: dev@lucene.apache.org Subject: Re:5.4 branch created,

Re: Welcome Dennis Gove as Lucene/Solr committer

Welcome Dennis! From: dev@lucene.apache.org At: Nov 6 2015 16:26:52 To: joels...@gmail.com Cc: dev@lucene.apache.org Subject: Re: Welcome Dennis Gove as Lucene/Solr committer Wow! Thank you for the invite and all the well wishes! Customary Intro Bio: In a galaxy far far away But

Re: Welcome Nick Knize as Lucene/Solr committer

Welcome Nick! From: dev@lucene.apache.org At: Oct 20 2015 18:40:25 To: luc...@mikemccandless.com Cc: dev@lucene.apache.org Subject: Re: Welcome Nick Knize as Lucene/Solr committer Thanks for the honor to join such a talented group! Brief Bio: I started as a Meteorology major in undergrad.

Re: [JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b60) - Build # 13744 - Still Failing!

Fix committed. Thank you Steve and Adrien for helping me reproduce and fix this. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: Aug 5 2015 21:32:49 This seed reproduces 100% (3/3 trials) for me on OS X, Java8. [junit4] 2 NOTE: reproduce with: ant

Re: 5.3 release

I have merged/committed SOLR-7877 and SOLR-7766 to lucene_solr_5_3 branch. cwiki.apache.org also updated now w.r.t. SOLR-7766. --Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org Cc: sar...@gmail.com, u...@thetaphi.de At: Aug 5 2015 16:10:09 I have

Re: [JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b60)

); } else if (random().nextBoolean()) { - Original Message - From: dev@lucene.apache.org To: Christine Poerschke (BLOOMBERG/ LONDON), dev@lucene.apache.org At: Aug 6 2015 10:27:38 Hi Christine, On Wed, Aug 5, 2015 at 11:42 PM, Christine Poerschke (BLOOMBERG/ LONDON) cpoersc

[Live]IndexWriterConfig.(get|set)IndexingChain

Hello. Just added a note to LUCENE-6571 (which concerns Javadoc errors/warnings). Any thoughts on removing/relocating (get|set)IndexingChain from derived to base class and changing indexingChain's visibility to private? Thanks, Christine

<    1   2   3   >