Re: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 - Failure

al in chat on January 2nd :-) > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > >> -Original Message- >> From: Steve Rowe [mailto:sar...@gmail.com] >> Sent: Thursday, D

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

+1 Docs, changes and javadocs look good. Smoke tester with Java7 & Java8: SUCCESS! [0:47:55.140380] -- Steve www.lucidworks.com > On Jan 19, 2016, at 2:39 AM, Noble Paul wrote: > > +1 > > SUCCESS! [1:32:46.196214] > > using java 7 > > On Tue, Jan 19, 2016 at 12:53 PM, Shalin Shekhar Manga

Re: [VOTE] Release Lucene/Solr 5.4.1 RC2

+1 Docs, changes and javadocs look good. Smoke tester with Java7 and Java8: SUCCESS! [0:48:02.638363] -- Steve www.lucidworks.com > On Jan 18, 2016, at 3:14 PM, Ramkumar R. Aiyengar > wrote: > > +1 > > SUCCESS! [0:56:50.593184] > > On Mon, Jan 18, 2016 at 7:19 PM, Erick Erickson > wrote

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

Another possibly related failure from my Jenkins, reproduces for me: —— [junit4] Suite: org.apache.lucene.search.TestDimensionalQueries [junit4] 1> T1: id=61212 should match but did not [junit4] 1> small=true query=DimensionalPointInRectQuery:field=point: Lower Left: [22.8696195255

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Not true - you can fix it in SVN. From : svn propset -r N --revprop svn:log "new log message” URL -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:13 PM, Dawid Weiss wrote: > > No way to do it in SVN. You can revert your commit and comm

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

uot; >>> >>> I admit I didn't check, but I'd be surprised if these were allowed as >>> this permits historical changes to the content of the repository. If >>> you do have admin privileges you can rewrite the repository entirely >>> and do wh

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties (of which svn:log is one) cause the property's previous value to be permanently discarded” Digging… -- Steve www.lucidworks.com > On Jan 22, 2016, at 2:30 PM, Steve Rowe wrote: > > Again, not tru

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

On Jan 22, 2016, at 2:41 PM, Dawid Weiss wrote: > >> Hmm, re-reading the FAQ, I think I’m wrong: "changes to revision properties >> (of which svn:log is one) cause the property's previous value to be >> permanently discarded” > > Hmm... They're not versioned in the SVN dumps I looked at? Righ

Re: [VOTE] Release Lucene/Solr 5.3.2-RC2

> On Jan 22, 2016, at 2:28 PM, Dawid Weiss wrote: > > 1) I'd notify infra because this permits any committer to destroy the > log history without a trace ;) For Lucene anyway (and I suspect most/all ASF projects?), there is an (out-of-band) trace: the archive of log messages emailed to comm..

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1662: POMs out of sync

I’ve opened an INFRA issue to explore why none of our Maven snapshot deployment jobs has fully succeeded in the last 10 days: https://issues.apache.org/jira/browse/INFRA-3 -- Steve www.lucidworks.com > On Jan 21, 2016, at 9:11 PM, Apache Jenkins Server > wrote: > > Build: https://builds.

Re: Apache Lucene/Solr GIT migration, requesting infra help

Thanks Dawid and Daniel! -- Steve www.lucidworks.com > On Jan 23, 2016, at 3:45 PM, Erick Erickson wrote: > > Indeed, thanks for your work Dawid and Daniel!! > > On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless > wrote: >> Thank you Dawid and Daniel for all the hard work here!! >> >> Mike

Re: Releasing 5.3.2

The download link should always be the latest point release from the latest major/minor release, so +1 to keep it at 5.4.1. -- Steve www.lucidworks.com On Saturday, January 23, 2016, Anshum Gupta wrote: > Hi, > > I am about to work on the website changes and add news etc. for the 5.3.2 > releas

Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1074 - Failure

This is pretty strange - I looked on lucene1-us-west.apache.org, and the lucene/build/lucene.tgz.unpacked/ directory does not exist. The trunk version of this job has succeeded twice on ASF Jenkins. I just locally ran ‘ant prepare-release-no-sign’ on branch_5x under lucene/ and it built success

Re: lucene-solr git commit: fix false failures from test bugs

Hi Mike, My Jenkins's nightly monster trunk job failed on both these tests last night, and the seeds no longer reproduce after your fix. However, a third test failed in the same run, and it still reproduces for me - not sure if it’s related though: —— [junit4] Suite: org.apache.lucene.index.T

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

+1 Smoke tester says: SUCCESS! [1:03:14.565590] Changes, docs and javadocs look good. Steve On Jan 17, 2014, at 9:13 AM, Mark Miller wrote: > Please vote to release the following artifacts: > > http://people.apache.org/~markrmiller/lucene_solr_4_6_1r1559132/ > > Here is my +1. > > -- > - M

Re: [VOTE] Release Lucene/Solr 4.6.1 RC2

When running the smoke tester against RC2, I ran into the same test problem that Simon fixed a week ago on branch_4x, but not on lucene_solr_4_6: [ http://svn.apache.org/r1557503]. My log is below. Not worth a respin IMHO. Running smoke tester again. - [junit4] Suite: org.apache.lucene.s

Re: [VOTE] Release Lucene/Solr 4.6.1 RC2

+1 Smoke tester passed the second time for me; changes, docs and javadocs look good. Steve On Sun, Jan 19, 2014 at 9:29 PM, Mark Miller wrote: > Please vote to release the following artifacts: > > http://people.apache.org/~markrmiller/lucene_solr_4_6_1r1559610/ > > Here is my +1. > > SUCCESS!

Re: Welcome Areek Zillur as Lucene/Solr committer!

Congrats and welcome, Areek! Steve On Jan 21, 2014 2:26 PM, "Robert Muir" wrote: > I'm pleased to announce that Areek Zillur has accepted to join our ranks > as a committer. > > Areek has been improving suggester support in Lucene and Solr, including a > revamped Solr component slated for the 4.

Re: [VOTE] Release Lucene/Solr 4.6.1 RC4

+1 for http://people.apache.org/~markrmiller/lucene_solr_4_6_1r1560866/ SUCCESS! [0:51:01.553003] Docs, changes and javadocs look good. Steve On Jan 23, 2014, at 9:57 PM, Mark Miller wrote: > Here we go, hopefully for that last time now…thanks everyone for bearing with > us. > > Please vot

Re: [JENKINS] Lucene-Solr-4.x-Linux (64bit/jdk1.7.0_60-ea-b03) - Build # 9122 - Still Failing!

check-licenses: [echo] License check under: /mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/lucene [licenses] CHECKSUM FAILED for /mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/lucene/benchmark/lib/spatial4j-0.4.jar (expected: "28b666145773098aeeadd033f3dd6c5b2871c208" was: "3fb96c751e

Re: Welcome Benson Margulies as Lucene/Solr committer!

Welcome Benson! > would some kind soul please point me to the explanation of how the > web site is maintained so I can add myself? Is it just the ASF CMS? It is the ASF CMS - see the "how to update the website" link from < http://wiki.apache.org/lucene-java/CommittersResources>. Steve On Sat,

Re: maven build issues with non-numeric custom version

Ryan, I'll take a look today. - Steve On Jan 28, 2014 2:39 PM, "Ryan McKinley" wrote: > The real version number i was trying was: > -Dversion=4.7.r1562172M > > essentially a standard lucene build with a few chances. Having the > non-numbers in the version make it fail > > This used to work -- an

Re: maven build issues with non-numeric custom version

See https://issues.apache.org/jira/browse/LUCENE-5420 - I put up a patch that fixes the issue for me. - Steve On Jan 28, 2014, at 3:10 PM, Steve Rowe wrote: > Ryan, I'll take a look today. - Steve > > On Jan 28, 2014 2:39 PM, "Ryan McKinley" wrote: > The real vers

Re: maven build issues with non-numeric custom version

-poms ant -Ddev.version.suffix=36433c00c4e02003c2c3bc702a0f65891a373244 get-maven-poms Steve On Jan 29, 2014, at 10:07 AM, Steve Rowe wrote: > See https://issues.apache.org/jira/browse/LUCENE-5420 - I put up a patch that > fixes the issue for me. - Steve > > On Jan 28, 2014, at 3:

Re: Welcome Anshum Gupta as Lucene/Solr Committer!

Welcome Anshum! On Sun, Feb 16, 2014 at 5:55 PM, Christian Moen wrote: > Congrats! > > On Feb 17, 2014, at 7:33 AM, Mark Miller wrote: > > Hey everybody! > > The Lucene PMC is happy to welcome Anshum Gupta as a committer on the > Lucene / Solr project. Anshum has contributed to a number of is

Re: [CONF] Apache Solr Reference Guide > Other Parsers

Hi Joel, On Feb 19, 2014, at 11:37 AM, Joel Bernstein (Confluence) wrote: > Happy to make the changes here as well if I have access. I just added you to the solr-committers group on Confluence (more info here: ), so you

Re: [VOTE] Lucene / Solr 4.7.0 RC1

I’d like to respin for LUCENE-5447 - I screwed up the StandardTokenizerImpl.jflex patch, and didn’t have tests that triggered the problem. I’ve attached a patch that adds tests illustrating the problem, along with the fix, and I plan on committing to trunk, branch_4x and lucene_solr_4_7. Sorry

Re: [CONF] Apache Solr Reference Guide > Other Parsers

to gain access? I hate seeing out of date > documentation…. > > Eric > > On Feb 19, 2014, at 11:47 AM, Steve Rowe wrote: > >> Hi Joel, >> >> On Feb 19, 2014, at 11:37 AM, Joel Bernstein (Confluence) >> wrote: >> >>> Happy to make the

Re: [VOTE] Lucene / Solr 4.7.0 RC1

a respin to pull back a few low risk bug fixes for >>> the experimental map reduce / morphlines contribs. >>> >>> - Mark >>> >>> http://about.me/markrmiller >>> >>> On Feb 19, 2014, at 12:06 PM, Steve Rowe wrote: >>> &g

Re: [VOTE] Lucene / Solr 4.7.0 RC3

I volunteer to be 4.7.1 RM. I’d prefer to delay the 4.7.0 release to include all known bugfixes, though. Simon, if you’re okay with it, I could take over as 4.7.0 RM and handle any respins. If not, it’s your prerogative to continue with the current RC vote; others can express their opinions

Re: [VOTE] Lucene / Solr 4.7.0 RC3

+1, I like it :) Probably should only check the changes in the first release section though - I know I don’t want to go back and fix up thousands of issues. Steve On Feb 21, 2014, at 10:05 AM, Robert Muir wrote: > > On Fri, Feb 21, 2014 at 6:31 AM, Martijn v Groningen > wrote: > > Only sp

4.7 CHANGES.txt and editing schema.xml and solrconfig.xml [was: Re: [VOTE] Lucene / Solr 4.7.0 RC1]

Hi Cassandra, On Feb 19, 2014, at 12:00 PM, Cassandra Targett wrote: > I'm starting to look at what needs to be updated in the ref guide, and I > noticed a number of references in changes.txt to the issues for being able to > update solrconfig.xml and schema.xml (SOLR-5287, 5446, 5456, maybe o

Re: 4.7 CHANGES.txt and editing schema.xml and solrconfig.xml [was: Re: [VOTE] Lucene / Solr 4.7.0 RC1]

On Feb 21, 2014, at 3:56 PM, Steve Rowe wrote: > Hi Cassandra, > > On Feb 19, 2014, at 12:00 PM, Cassandra Targett wrote: > >> I'm starting to look at what needs to be updated in the ref guide, and I >> noticed a number of references in changes.txt to the issues

Re: svn commit: r1570951 - in /lucene/dev/trunk: lucene/ivy-versions.properties solr/CHANGES.txt

Mark, In your SOLR-5765 commits, you reverted my CHANGES.txt cleanup for the Admin UI stuff (editing vs browsing conf dir) - I assume this was inadvertent? Steve On Feb 22, 2014, at 9:08 PM, markrmil...@apache.org wrote: > Author: markrmiller > Date: Sun Feb 23 02:08:52 2014 > New Revision: 1

Re: Solr Reference Guide pages; turn off comments?

I think deletion after addressing comments is too soon - I really like how doc contributors get a response to their contributions the way it’s done now. Maybe delete comments that have been addressed after each release? Steve On Feb 23, 2014, at 12:38 PM, Shalin Shekhar Mangar wrote: > I th

Re: [VOTE] Lucene / Solr 4.7.0 RC4

+1 Smoke tester was happy, and docs, changes and javadocs look good. Steve On Feb 22, 2014, at 5:46 AM, Simon Willnauer wrote: > Please vote for the forth Release Candidate for Lucene/Solr 4.7.0 > > you can download it here: > http://people.apache.org/~simonw/staging_area/lucene-solr-4.7.0-RC

Solr 4.7 release notes

I’ve taken a stab: https://wiki.apache.org/solr/ReleaseNote47 Mostly just trimmed down the New Features from CHANGES.txt. I’d appreciate review and improvement. Steve - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.or

Lucene 4.7 release notes

First pass here: https://wiki.apache.org/lucene-java/ReleaseNote47 I trimmed down and rearranged New Features from CHANGES.txt, trying to group together same-module features, and added a few links to blog posts I knew about. Please review and improve. Thanks, Steve --

Re: VOTE: Release apache-solr-ref-guide-4.7.pdf (RC1)

I regularized the preformatted blocks, so that none now have an extra blank line at the top - for some reason, all of the boxes on about half of the cwiki pages had this issue, but the other half didn’t. (I had to edit the source format to achieve this, and even there I couldn’t see a differenc

Re: VOTE: Release apache-solr-ref-guide-4.7.pdf (RC1)

27, 2014, at 12:06 PM, Cassandra Targett wrote: > > On Thu, Feb 27, 2014 at 4:11 AM, Steve Rowe wrote: > > I noticed that a couple of “Topics covered in this section” boxes are too > narrow to allow their content to be legible - the ones on pages 251 and 300 > look really ba

Re: VOTE: RC1 Release apache-solr-ref-guide-5.4.pdf

+1, thanks Cassandra. - Steve > On Dec 8, 2015, at 10:53 AM, Cassandra Targett wrote: > > Please VOTE to release the Apache Solr Ref Guide for Solr 5.4: > > https://dist.apache.org/repos/dist/dev/lucene/solr/ref-guide/apache-solr-ref-guide-5.4-RC1/ > > $ cat apache-solr-ref-guide-5.4.pdf.sha1

Re: 5.3.2 bug fix release

Historical aside: I was thinking we’d never produced a bugfix release on a previous minor branch, but I went looking and found that 4.9.1, released 9/21/14, was just such a one: 4.10.0 was released on 9/4/14. AFAICT Mike McCandless initially proposed a 4.9.1 release on 9/16/14 here:

Re: [CI] Lucene 5x Linux 64 Test Only - Build # 64501 - Failure!

This email was never delivered to me for moderation either. In fact, the last MODERATE email I received for email from Elastic’s CI server was on Sept. 8th for Build URL http://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/62794/. > On Sep 22, 2015, at 12:27 PM, Michael McCandless

Re: Please vote for the 3rd release candidate for Lucene/Solr 5.3.1

Also, the download link on the Solr News page is , but for every other release we’ve used the redirect-to-latest link - I think we should do the same for 5.3.1. > On Sep 24, 2

Re: Please vote for the 3rd release candidate for Lucene/Solr 5.3.1

I fixed the Solr news item to not mention Lucene - I had to fix before making the shortened s.apache.org/solr-5.3.1 link to update the Freenode #solr IRC channel topic, since the URL fragment id is autogenerated from the text of the header. - Steve > On Sep 24, 2015, at 11:39 AM, Anshum Gupta

Re: Welcome Nick Knize as Lucene/Solr committer

Welcome Nick! Steve > On Oct 20, 2015, at 12:50 PM, Michael McCandless > wrote: > > I'm pleased to announce that Nick Knize has accepted the PMC's > invitation to become a committer. > > Nick, it's tradition that you introduce yourself with a brief bio / > origin story, explaining how you arr

Re: Repository Publishing

Hi Gus, Check out the section “C. How to deploy Maven artifacts to a repository” in dev-tools/maven/README.maven in the Lucene/Solr source. I recommend reading the rest of that file too, especially the part about specifying custom artifact versions, in item 3 under section “D. How to use Maven

Re: [JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_60) - Build # 14711 - Failure!

Hi Martin, You should start another thread to discuss this topic; replying to a jenkins build failure message means lots of people will never look at your email. Do you know about the Maven build that already is included with the project? If not, start here:

Re: Welcome Tomás Fernández Löbbe to the PMC

Welcome Tomás! Steve On Friday, November 6, 2015, Anshum Gupta wrote: > I'm pleased to announce that Tomás Fernández Löbbe has accepted the PMC’s > invitation to join. > > Welcome Tomás! > > -- > Anshum Gupta >

Re: Welcome Joel Bernstein to the PMC

Welcome Joel! Steve > On Nov 6, 2015, at 9:26 AM, Yonik Seeley wrote: > > I'm pleased to announce that Joel as accepted the PMC's invitation to join. > > Welcome Joel! > > -Yonik > > - > To unsubscribe, e-mail: dev-unsubscr.

Re: Welcome Dennis Gove as Lucene/Solr committer

Welcome Dennis! Steve > On Nov 6, 2015, at 10:19 AM, Joel Bernstein wrote: > > I'm pleased to announce that Dennis Gove has accepted the PMC's > invitation to become a committer. > > Dennis, it's tradition that you introduce yourself with a brief bio. > > Your account is not entirely ready ye

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 430 - Still Failing

Looks like ASF Jenkins's lucene slave is running out of disk space (again): > [smoker][junit4] java.io.IOException: No space left on device Uwe, opinions on what to do? Should we ask Infra for more disk space (again)? > On Jan 7, 2016, at 12:54 PM, Apache Jenkins Server > wrote: > > Buil

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 11 - Still Failing

I committed a fix: LUCENE-6955. - Steve > On Jan 9, 2016, at 3:29 PM, Apache Jenkins Server > wrote: > > Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.3/11/ > > No tests ran. > > Build Log: > [...truncated 53068 lines...] > prepare-release-no-sign: >[mkdir] Created dir:

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 430 - Still Failing

o manually delete it. > >> -Original Message- >> From: Steve Rowe [mailto:sar...@gmail.com] >> Sent: Thursday, January 07, 2016 7:23 PM >> >> Looks like ASF Jenkins's lucene slave is running out of disk space (again): >> >>> [smoker][jun

Re: [VOTE] Release Lucene/Solr 5.3.2-RC1

+1 Docs, changes and javadocs look good. I ran the smoke tester with Java7 and Java8: SUCCESS! [0:48:53.667806] -- Steve www.lucidworks.com > On Jan 12, 2016, at 9:01 AM, david.w.smi...@gmail.com wrote: > > +1 > SUCCESS! [0:49:17.877825] > > > On Tue, Jan 12, 2016 at 8:21 AM Anshum Gupta w

Re: 5.4.1 release

Thanks Adrien! -- Steve www.lucidworks.com > On Jan 12, 2016, at 5:39 AM, Adrien Grand wrote: > > Le mar. 12 janv. 2016 à 09:30, Adrien Grand a écrit : > I'll go through commits that have been merged to the 5.3 branch and make sure > they are on the 5.4 branch as well. > > This should be goo

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.4 - Build # 14 - Failure

Uwe, want me to do this for the 5.4 jobs, or will you? -- Steve www.lucidworks.com > On Jan 13, 2016, at 9:56 AM, Uwe Schindler wrote: > > This is an issue of the current Jenkins setup. The problem is that command > line subversion is different from Jenkin’s internal SVN client. Because of >

Re: Welcome Areek Zillur to the Lucene / Solr PMC

Welcome Areek! Steve > On Nov 11, 2015, at 3:48 PM, Simon Willnauer > wrote: > > I'm pleased to announce that Areek has accepted the PMC's invitation to join. > > Welcome Areek! > > Simon - To unsubscribe, e-mail: dev-unsu

Re: [JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 629 - Failure

Reproduces for me - I created . > On Nov 16, 2015, at 10:05 AM, Apache Jenkins Server > wrote: > > Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/629/ > > 1 tests failed. > FAILED: > org.apache.solr.search.TestRandomCollaps

Lucene's ASF Jenkins slave was stuck for over 5 days on a single job

I just killed this job: Just before I killed it, the job's status was: Started 5 days 10 hr ago Build has been executing for 5 days 10 hr on lucene and the last line of the console was: [junit4] HEARTBEAT J1 PID(1824@lu

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

I can’t reproduce on 64-bit Linux (Debian 8.3). I installed the 32-bit JDK 9 build 104[1], then ran this cmdline: ant test -Dargs="-server -XX:+UseG1GC -XX:-CompactStrings -XX:-UseSuperWord" -Dtestcase=TestLookaheadTokenFilter -Dtests.method=testRandomStrings -Dtests.seed=51FD7B60247BBA86 -Dtes

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1676: POMs out of sync

I committed a Maven build fix for the compilation errors (LUCENE-6997). -- Steve www.lucidworks.com > On Feb 11, 2016, at 2:25 AM, Apache Jenkins Server > wrote: > > Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1676/ > > No tests ran. > > Build Log: > [...truncated 42801 line

Re: [01/31] lucene-solr git commit: current patch

Mike, It looks like you committed this work to master without the JIRA number in the log? Seems like a mistake? Or maybe I’m misinterpreting this push. The switch to git has increased the commit list volume many fold... -- Steve www.lucidworks.com > On Feb 11, 2016, at 8:42 AM, mikemcc...@a

Re: [VOTE] Release Lucene/Solr 5.5.0 RC1

Mike, how did the smoke tester’s maven checks succeed? > On Feb 12, 2016, at 12:42 PM, Michael McCandless > wrote: > > Please vote for the RC1 release candidate for Lucene/Solr 5.5.0, the > last feature release before Lucene 6.0.0 and the first Lucene/Solr > release since we switched from Subve

Re: [VOTE] Release Lucene/Solr 5.5.0 RC1

> On Fri, Feb 12, 2016 at 3:44 PM, Steve Rowe wrote: >> Mike, how did the smoke tester’s maven checks succeed? > On Feb 12, 2016, at 12:57 PM, Michael McCandless > wrote: > > I was wondering the same thing, but somehow it did? Maybe it pulled > from my local .m2? Th

Re: [VOTE] Release Lucene/Solr 5.5.0 RC1

> On Feb 12, 2016, at 3:32 PM, Steve Rowe wrote: > >> On Fri, Feb 12, 2016 at 3:44 PM, Steve Rowe wrote: >>> Mike, how did the smoke tester’s maven checks succeed? > >> On Feb 12, 2016, at 12:57 PM, Michael McCandless >> wrote: >> >> I

Re: Should schema API allow deleting uniqueKey?

I don't think we should allow deleting the uniqueKey field. I'm surprised it even works - I would have thought that there would be a schema validity check: you shouldn't be able to specify a non-existent field as the uniqueKey. Note that the replace-field operation should be fine in this case. S

Re: [VOTE] Release Lucene/Solr 5.4.0-RC1

+1 Docs, javadocs, and changes look good. Smoke tester was happy with Java7 and Java8: SUCCESS! [1:53:58.550314] Steve > On Dec 7, 2015, at 5:31 AM, Upayavira wrote: > > Yes, Shalin, you are right. My fix was still required, but I clearly > manually entered the SVN commit command wrong. Seei

Re: VOTE: RC0 Release apache-solr-ref-guide-5.4.pdf

There’s a table with a truncated right-hand column on page 221 (De-Duplication | Configuration Options | SignatureUpdateProcessorFactory properties). I think this is worthy of respin. I scanned through the rest of the ref guide and couldn’t find any more examples of right-truncated tables. I’

Re: VOTE: RC0 Release apache-solr-ref-guide-5.4.pdf

I added chunk a couple places within the long terms in the affected table, and the single-page PDF export looks fixed now: no extra whitespace, wrapping is performed, all content is visible. Steve > On Dec 8, 2015, at 8:52 AM, Steve Rowe wrote: > > There’s a table with a trunca

Re: [JENKINS] Lucene-Solr-NightlyTests-6.x - Build # 14 - Still Failing

These tests failed with connection reset while using Turkish locales. The commit sha is just before I committed the upgrade to Jetty 9.3.8.v20160314, which includes a fix for the Turkish locale problem, so hopefully this is the last time we see this failure. -- Steve www.lucidworks.com > On Ma

Re: [JENKINS] Lucene-Solr-5.5-Linux (64bit/jdk1.7.0_80) - Build # 9 - Still Failing!

This reproduces for me on branch_5_5, branch_5x and master. -- Steve www.lucidworks.com > On Feb 14, 2016, at 8:20 PM, Policeman Jenkins Server > wrote: > > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.5-Linux/9/ > Java: 64bit/jdk1.7.0_80 -XX:+UseCompressedOops -XX:+UseSerialGC > > 1 t

Re: [JENKINS] Lucene-Solr-NightlyTests-5.x - Build # 1098 - Still Failing

I’ve seen this same failure on my Jenkins, but neither seed reproduces for me. -- Steve www.lucidworks.com > On Feb 15, 2016, at 4:36 AM, Apache Jenkins Server > wrote: > > Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1098/ > > 1 tests failed. > FAILED: > org.apache.luc

Re: [JENKINS] Lucene-Solr-NightlyTests-5.x - Build # 1098 - Still Failing

:) yeah, no coffee yet, thanks Mike. -- Steve www.lucidworks.com > On Feb 15, 2016, at 9:04 AM, Michael McCandless > wrote: > > I committed a fix for this a few hours ago... > > Mike McCandless > > http://blog.mikemccandless.com > > > On Mon, Feb 15, 2

Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure

Aha, thanks for figuring the Jenkins thing out Uwe. -- Steve www.lucidworks.com > On Feb 17, 2016, at 1:25 PM, Uwe Schindler wrote: > > Hehe, > > for this checkout the "Clean Before Checkout" option was missing in Jenkins > (5.x). Steve cloned this for 5.5, too. This is why every 2nd build f

Re: [VOTE] Release Lucene/Solr 5.5.0 RC3

+1 Docs, changes and javadocs look good. I ran the smoke tester with —test-java8: SUCCESS! [0:40:02.457972] -- Steve www.lucidworks.com > On Feb 16, 2016, at 4:07 PM, Michael McCandless > wrote: > > Please vote for the RC3 release candidate for Lucene/Solr 5.5.0, the > last feature release b

Re: VOTE: RC1 Release apache-solr-ref-guide-5.5.pdf

+1 -- Steve www.lucidworks.com > On Feb 19, 2016, at 6:05 PM, Chris Hostetter wrote: > > > Please VOTE to release the following artifacts as > apache-solr-ref-guide-5.5.pdf ... > > https://dist.apache.org/repos/dist/dev/lucene/solr/ref-guide/apache-solr-ref-guide-5.5-RC1/ > > -Hoss > http:/

Re: VOTE: RC1 Release apache-solr-ref-guide-5.5.pdf

Hoss, looks like Mike didn’t see your email, and sent out an earlier version of the Solr announcement. We should send a separate ref guide announcement. -- Steve www.lucidworks.com > On Feb 23, 2016, at 12:48 AM, Chris Hostetter > wrote: > > > Mike: since the ref guide is now up 2 80% of th

Welcome Upayavira as Lucene/Solr committer

I'm pleased to announce that Upayavira has accepted the PMC's invitation to become a committer. Upayavira, it's tradition that you introduce yourself with a brief bio. Mike McCandless, the Lucene PMC chair, has already added your “upayavira" account to the “lucene" LDAP group, so you now have c

Re: [Solr Wiki] Trivial Update of "SolrCaching" by KonstantinGribov

You’re right, Konstantin. I’ve created a JIRA issue: Steve But for some > On Jul 7, 2015, at 12:20 PM, Konstantin Gribov wrote: > > Currently API docs for Lucene can be found in 2 clicks from lucene.apache.org > ("lucene core" link, then 5.2.1

Re: 5.5.1 - addVersion.py

Anshum, For the 5.5.1 release, addVersion.py should be run on branch_6_0 and branch_6x. On master, where 6.0 is the oldest supported version, addVersion.py shouldn’t be run for any version less than 6.0. This is by design - see Mike’s commit removing the 5.x constants on master after LATEST be

JIRA version cleanup

I was looking at the published 5.5.1 Changes.html and noticed that there was no release date associated with the 5.3.2 release, and so I went and looked at the JIRA version management pages, which is where this information is drawn from when Changes.html is built:

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

Hi Christine, This test was added in SOLR-8662. Varun did the work and I reviewed. I asked a similar question about testReloadAndAddSimple - from

Re: [JENKINS] Lucene-Solr-SmokeRelease-master - Build # 485 - Still Failing

Looks like we should add functionality to addVersion.py to add unsupported versions on master, and then run it on master even when the release version is no longer supported on master. I’ll work on a patch. > On May 7, 2016, at 3:48 AM, Apache Jenkins Server > wrote: > > Build: https://build

Lucene/Solr 6.0.1

I’d like to make a 6.0.1 release, and I volunteer to be RM. I propose to cut the first RC in one week: next Friday. -- Steve www.lucidworks.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

Re: Lucene/Solr 6.0.1

> > Le ven. 13 mai 2016 à 18:06, Steve Rowe a écrit : > I’d like to make a 6.0.1 release, and I volunteer to be RM. > > I propose to cut the first RC in one week: next Friday. > > -- > Steve > www.lucidworks.com >

Re: Lucene/Solr 6.0.1

n change date" bugs/issues (2 > Solr, 1 Lucene). > > On Fri, May 13, 2016 at 12:06 PM Steve Rowe wrote: > I’d like to make a 6.0.1 release, and I volunteer to be RM. > > I propose to cut the first RC in one week: next Fr

Re: Lucene/Solr 6.0.1

? Thanks. -- Steve www.lucidworks.com > On May 13, 2016, at 12:05 PM, Steve Rowe wrote: > > I’d like to make a 6.0.1 release, and I volunteer to be RM. > > I propose to cut the first RC in one week: next Friday. > > -- > St

Re: Lucene/Solr 6.0.1

r each > cherry picked commit. It's too bad this conundrum/annoyance exists. > > ~ David > > On Fri, May 13, 2016 at 8:11 PM Steve Rowe wrote: > David, > > Since it’s a bugfix release, the branch is already cut: branch_6_0. > > Please go ahead and start backporti

Re: [VOTE] Release Lucene/Solr 6.0.0 RC1

Nick, I see Mike has committed a fix for LUCENE-7158 to the 6.0 branch after your RC was cut, and the issue is marked as fixed in 6.0. Does that mean you will be creating another RC? I’m going to hold off testing RC1 until you address this. -- Steve www.lucidworks.com > On Apr 1, 2016, at 11

Re: [VOTE] Release Lucene/Solr 6.0.0 RC2

I got a dependency checksum failure when I ran the smoke tester, which is weird, since others have already succeeded, and I would think that the test is deterministic… I’m looking into it: —— check-licenses: [echo] License check under: /tmp/smoke_lucene_6.0.0_48c80f91b8e5cd9b3a9b48e6184bd5

Re: [VOTE] Release Lucene/Solr 6.0.0 RC2

> On Apr 4, 2016, at 10:32 AM, Steve Rowe wrote: > > I got a dependency checksum failure when I ran the smoke tester, which is > weird, since others have already succeeded, and I would think that the test > is deterministic… I’m looking into it: > > —— > check-licens

Re: [VOTE] Release Lucene/Solr 6.0.0 RC2

FYI there is a reproducing failure in lucene/spatial on branch_6_0: https://issues.apache.org/jira/browse/LUCENE-7172 -- Steve www.lucidworks.com > On Apr 1, 2016, at 4:44 PM, Nicholas Knize wrote: > > Please vote for the RC2 release candidate for Lucene/Solr 6.0.0. > > Artifacts: > > > h

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

Welcome Karl! -- Steve www.lucidworks.com > On Apr 4, 2016, at 10:28 AM, Michael McCandless > wrote: > > I'm pleased to announce that Karl Wright has accepted the Lucene PMC's > invitation to become a committer. > > Karl, it's tradition that you introduce yourself with a brief bio. > > Karma

Fwd: [JENKINS] Lucene-Solr-tests-master - Build # 6234 - Still Failing!

Master is failing to compile in lucene/spatial-extras/ - see my Jenkins' failure email below. Git bisect says: —— 0843e95f0c6661eaa8db372deb06318da1cfe9d2 is the first bad commit commit 0843e95f0c6661eaa8db372deb06318da1cfe9d2 Author: Karl Wright Date: Sun Apr 3 09:43:11 2016 -0400 —— -- St

Re: 6.0 Jenkins builds

Yup, I did, and I sent an email to the dev list saying about a week ago: -- Steve www.lucidworks.com > On Apr 4, 2016, at 2:00 PM, Michael McCandless > wrote: > > Did anyone

Re: [VOTE] Release Lucene/Solr 6.0.0 RC2

+1 Docs, changes and javadocs look good, except that there is a 5.5.1 section in Solr’s CHANGES.txt, but there shouldn’t be (shouldn’t block release, IMO). Smoke tester: SUCCESS! [0:24:05.242799] -- Steve www.lucidworks.com > On Apr 1, 2016, at 4:44 PM, Nicholas Knize wrote: > > Please vote

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

Caused by SOLR-9109, which didn’t exhibit this problem for me on OS X - looking into it. -- Steve www.lucidworks.com > On May 16, 2016, at 6:10 PM, Policeman Jenkins Server > wrote: > > Build: http://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/5847/ > Java: 64bit/jdk1.8.0_92 -XX:-UseCo

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

Also works on my Linux box, so this is apparently a Windows-only problem. -- Steve www.lucidworks.com > On May 16, 2016, at 6:13 PM, Steve Rowe wrote: > > Caused by SOLR-9109, which didn’t exhibit this problem for me on OS X - > looking into it. > > -- > Steve > www

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

Maybe its caused by not using an URL correctly. I'll > fix with a commit. > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > >> -----Original Message- >> From: Steve Rowe [mailto:sar.

<    2   3   4   5   6   7   8   9   10   11   >