GIT migration complete

2016-01-23 Thread Dawid Weiss
Ok, folks. Seems like code migration is complete, with both gh mirrors
and Apache repos up.

1. Please read the docs at: https://git-wip-us.apache.org/

2. I didn't realize Apache's repositories are over https, which makes
authorization rather painful for Linux users (requires password typing
on every push). I think I'll stick with gh for this reason and only
push my changes when they're fully baked.

3. The master branch (former trunk) passes ant precommit for me, but I
didn't apply build patches to branch_5x yet.

If there are any problems or concerns, let me know (perhaps I'll be
able to help).

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_66) - Build # 15619 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15619/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseSerialGC

1 tests failed.
FAILED:  org.apache.lucene.search.TestLatLonPointQueries.testRandomMedium

Error Message:
Captured an uncaught exception in thread: Thread[id=29, name=T4, 
state=RUNNABLE, group=TGRP-TestLatLonPointQueries]

Stack Trace:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=29, name=T4, state=RUNNABLE, 
group=TGRP-TestLatLonPointQueries]
Caused by: java.lang.AssertionError: some hits were wrong
at __randomizedtesting.SeedInfo.seed([2E7EF3BA6177F210]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)




Build Log:
[...truncated 7522 lines...]
   [junit4] Suite: org.apache.lucene.search.TestLatLonPointQueries
   [junit4]   1> T4: id=34041 should match but did not
   [junit4]   1>   small=true query=PointInRectQuery:field=point: Lower Left: 
[123.61905064691,68.20807387179073] Upper Right: 
[123.81376413066033,69.0928232700069] docID=33807
   [junit4]   1>   lat=68.63869828002365 lon=123.6190506578548
   [junit4]   1>   deleted?=false
   [junit4]   2> ?? 23, 2016 11:20:09 ?? 
com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler
 uncaughtException
   [junit4]   2> WARNING: Uncaught exception in thread: 
Thread[T4,5,TGRP-TestLatLonPointQueries]
   [junit4]   2> java.lang.AssertionError: some hits were wrong
   [junit4]   2>at 
__randomizedtesting.SeedInfo.seed([2E7EF3BA6177F210]:0)
   [junit4]   2>at org.junit.Assert.fail(Assert.java:93)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)
   [junit4]   2> 
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=TestLatLonPointQueries -Dtests.method=testRandomMedium 
-Dtests.seed=2E7EF3BA6177F210 -Dtests.multiplier=3 -Dtests.slow=true 
-Dtests.locale=zh -Dtests.timezone=Europe/Brussels -Dtests.asserts=true 
-Dtests.file.encoding=US-ASCII
   [junit4] ERROR   2.09s J0 | TestLatLonPointQueries.testRandomMedium <<<
   [junit4]> Throwable #1: java.lang.AssertionError
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.verify(BaseGeoPointTestCase.java:770)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.doTestRandom(BaseGeoPointTestCase.java:411)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.testRandomMedium(BaseGeoPointTestCase.java:335)
   [junit4]>at java.lang.Thread.run(Thread.java:745)Throwable #2: 
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=29, name=T4, state=RUNNABLE, 
group=TGRP-TestLatLonPointQueries]
   [junit4]> Caused by: java.lang.AssertionError: some hits were wrong
   [junit4]>at 
__randomizedtesting.SeedInfo.seed([2E7EF3BA6177F210]:0)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)
   [junit4] IGNOR/A 0.01s J0 | TestLatLonPointQueries.testRandomBig
   [junit4]> Assumption #1: 'nightly' test group is disabled (@Nightly())
   [junit4]   2> NOTE: test params are: codec=Asserting(Lucene60): 
{id=PostingsFormat(name=LuceneFixedGap)}, 
docValues:{id=DocValuesFormat(name=Direct)}, sim=ClassicSimilarity, locale=zh, 
timezone=Europe/Brussels
   [junit4]   2> NOTE: Linux 3.19.0-42-generic i386/Oracle Corporation 1.8.0_66 
(32-bit)/cpus=12,threads=1,free=43559384,total=64946176
   [junit4]   2> NOTE: All tests run in this JVM: [TestLatLonPointQueries]
   [junit4] Completed [1/13 (1!)] on J0 in 21.15s, 8 tests, 1 error, 1 skipped 
<<< FAILURES!

[...truncated 57 lines...]
BUILD FAILED
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:784: The following 
error occurred while executing this line:
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:728: The following 
error occurred while executing this line:
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:59: The following 
error occurred while executing this line:
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/lucene/build.xml:472: The 
following error occurred while executing this line:

[jira] [Updated] (LUCENE-6922) Improve svn to git workaround script

2016-01-23 Thread Paul Elschot (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Elschot updated LUCENE-6922:
-
Attachment: svnBranchToGit.py

svnBranchToGit.py script of 23 Jan 2015.

After the migration to git the tag for the 5.3.2 release seems to be missing, 
for the rest the new git repo is looking very good.

This script creates a local git branch lucene_solr_5_3.svn from the 
lucene_solr_5_3 branch.
The 5.3.2 release is easy to locate there as a commit of 16 Jan for SOLR-8496.

This also contains some general improvements since the previous patch.



> Improve svn to git workaround script
> 
>
> Key: LUCENE-6922
> URL: https://issues.apache.org/jira/browse/LUCENE-6922
> Project: Lucene - Core
>  Issue Type: Improvement
>  Components: -tools
>Reporter: Paul Elschot
>Priority: Minor
> Attachments: LUCENE-6922.patch, svnBranchToGit.py, svnBranchToGit.py, 
> svnBranchToGit.py
>
>
> As the git-svn mirror for Lucene/Solr will be turned off near the end of 
> 2015, try and improve the workaround script to become more usable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 395 - Failure

2016-01-23 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/395/

No tests ran.

Build Log:
[...truncated 35912 lines...]
prepare-release-no-sign:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist
 [copy] Copying 461 files to 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/lucene
 [copy] Copying 245 files to 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/solr
   [smoker] Java 1.8 
JAVA_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
   [smoker] NOTE: output encoding is UTF-8
   [smoker] 
   [smoker] Load release URL 
"file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/"...
   [smoker] 
   [smoker] Test Lucene...
   [smoker]   test basics...
   [smoker]   get KEYS
   [smoker] 0.2 MB in 0.04 sec (3.9 MB/sec)
   [smoker]   check changes HTML...
   [smoker]   download lucene-6.0.0-src.tgz...
   [smoker] 28.2 MB in 0.04 sec (796.6 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   download lucene-6.0.0.tgz...
   [smoker] 62.6 MB in 0.08 sec (786.0 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   download lucene-6.0.0.zip...
   [smoker] 73.1 MB in 0.09 sec (818.2 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   unpack lucene-6.0.0.tgz...
   [smoker] verify JAR metadata/identity/no javax.* or java.* classes...
   [smoker] test demo with 1.8...
   [smoker]   got 5973 hits for query "lucene"
   [smoker] checkindex with 1.8...
   [smoker] check Lucene's javadoc JAR
   [smoker]   unpack lucene-6.0.0.zip...
   [smoker] verify JAR metadata/identity/no javax.* or java.* classes...
   [smoker] test demo with 1.8...
   [smoker]   got 5973 hits for query "lucene"
   [smoker] checkindex with 1.8...
   [smoker] check Lucene's javadoc JAR
   [smoker]   unpack lucene-6.0.0-src.tgz...
   [smoker] Traceback (most recent call last):
   [smoker]   File 
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py",
 line 1427, in 
   [smoker] main()
   [smoker]   File 
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py",
 line 1372, in main
   [smoker] smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, 
c.is_signed, ' '.join(c.test_args))
   [smoker]   File 
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py",
 line 1410, in smokeTest
   [smoker] unpackAndVerify(java, 'lucene', tmpDir, 'lucene-%s-src.tgz' % 
version, svnRevision, version, testArgs, baseURL)
   [smoker]   File 
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py",
 line 588, in unpackAndVerify
   [smoker] verifyUnpacked(java, project, artifact, unpackPath, 
svnRevision, version, testArgs, tmpDir, baseURL)
   [smoker]   File 
"/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py",
 line 614, in verifyUnpacked
   [smoker] raise RuntimeError('file "%s" is missing from artifact %s' % 
(fileName, artifact))
   [smoker] RuntimeError: file "LICENSE.txt" is missing from artifact 
lucene-6.0.0-src.tgz

BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/build.xml:536:
 exec returned: 1

Total time: 10 minutes 34 seconds
Build step 'Invoke Ant' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.8.0_66) - Build # 5561 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5561/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseG1GC

1 tests failed.
FAILED:  org.apache.solr.update.AutoCommitTest.testCommitWithin

Error Message:
Exception during query

Stack Trace:
java.lang.RuntimeException: Exception during query
at 
__randomizedtesting.SeedInfo.seed([492941F0730FC0F2:F3FB2E88F0212EE7]:0)
at org.apache.solr.SolrTestCaseJ4.assertQ(SolrTestCaseJ4.java:755)
at 
org.apache.solr.update.AutoCommitTest.testCommitWithin(AutoCommitTest.java:326)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: REQUEST FAILED: 
xpath=//result[@numFound=1]
xml response was: 

00


request was:q=id:529=standard=0=20=2.2
at org.apache.solr.SolrTestCaseJ4.assertQ(SolrTestCaseJ4.java:748)
... 40 more




Build Log:
[...truncated 9510 lines...]
   [junit4] Suite: org.apache.solr.update.AutoCommitTest
   [junit4] 

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

2016-01-23 Thread Shalin Shekhar Mangar
Got it, thanks! I'll try your suggestion, Dawid.

On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
> If you're using github then yes, you will need to fork again and
> rebase any changes you may have. This can be done by having two
> origins locally (two "sources" of commits) -- one from the old clone,
> the second one from the new clone. Then you can rebase the branches or
> commits you wish and push them to the new clone.
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>>> Thanks Dawid and Daniel for all the work!
>>>
>>> One strange thing that I noticed is that my fork of apache/lucene-solr
>>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>>> that guy is. What can we do to fix this?
>>
>> Nothing. This is GitHub's fallback method when the original repository
>> goes away as it did here (replaced with a new repo with a new history).
>> Since referring to the old repo which doesn't exist anymore would break
>> your copy, they have fallen back to another copy of it.
>>
>> Please re-fork.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
 1. The content of the lucene-solr.git repository looks good!

 2) PROBLEM. I can't push my own branch:

 $ git co master -b git-check
 $ [... committed a dummy commit ]
 $ git push origin HEAD -u
 fatal: remote error: access denied or repository not exported: 
 /lucene-solr.git

 3) Solr repo is still available for some reason, both as real git repo 
 here:

 git://git.apache.org/solr.git

 and listed here:

 https://git.apache.org/

 Could I be seeing a mirror or something?

 Dawid


 On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
> Checking everything now -- that was fast Daniel!
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
> wrote:
>> Just a heads up: Everything is working now and GitHub has caught up with
>> the new repository. You should be good to go :)
>>
>> With regards,
>> Daniel.
>>
>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
 Hello Daniel,

 I've prepared everything for the migration and I hand it off to you (I
 will be available in the morning, if you need assistance). I can also
 log on to hipchat, but send me an e-mail if you wish me to.

 Here are the steps we kindly ask you to perform (I allowed myself to
 uppercase certain things, apologies if it looks like shouting):

 1) Permanently REMOVE the following git mirrors of SVN (reason: they
 are obsolete and incorrect syncs, consolidated git repo contains full
 history):

 git://git.apache.org/solr.git
>>> DONE
>>>
 git://git.apache.org/lucene.git
>>> DONE

 2) Notify (somehow) GitHub that these two repos have been removed
 (they should not be available or visible on GitHub as well):

 https://github.com/apache/lucene
>>> DONE
 https://github.com/apache/solr
>>> DONE
>>>

 3) DISABLE svn syncing for the following git mirror:

 git://git.apache.org/lucene-solr.git
>>> DONE
>>>

 and then REPLACE it (wipe it clean) with the content of the following
 consolidated repository:

 g...@github.com:dweiss/lucene-solr-svn2git.git

 I don't know how it looks from the backend's side, but this should
 also work, if there are sufficient permissions:

 git clone g...@github.com:dweiss/lucene-solr-svn2git.git
 git remote add apache git://git.apache.org/lucene-solr.git
 git push --mirror apache
>>> We have our own methods, but nonetheless DONE. Please check that you
>>> have write-access to the new repo.

 4) I don't know if we need to make GitHub aware of the replaced
 content of the lucene-solr repo or if their syncing will handle this
 automatically. It would be nice if they could catch up as quickly as
 possible.
>>>
>>> As explained on the JIRA ticket, if we're lucky, this should happen
>>> automagically in about 20 minutes from now. If not, we'll have to wait
>>> 24 hours. Time will tell :)
>>>
>>> With regards,
>>> Daniel.
>>>

 In case of questions, problems or a successful import, please drop me
 an e-mail. Oh, thank you for being so nice and helping us on your day
 off -- much appreciated.

 Dawid


[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

2016-01-23 Thread Paul Elschot (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113697#comment-15113697
 ] 

Paul Elschot commented on LUCENE-6922:
--

I put the latest result on github:
git fetch https://github.com/PaulElschot/lucene-solr.git lucene_solr_5_3.svn


> Improve svn to git workaround script
> 
>
> Key: LUCENE-6922
> URL: https://issues.apache.org/jira/browse/LUCENE-6922
> Project: Lucene - Core
>  Issue Type: Improvement
>  Components: -tools
>Reporter: Paul Elschot
>Priority: Minor
> Attachments: LUCENE-6922.patch, svnBranchToGit.py, svnBranchToGit.py, 
> svnBranchToGit.py
>
>
> As the git-svn mirror for Lucene/Solr will be turned off near the end of 
> 2015, try and improve the workaround script to become more usable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113696#comment-15113696
 ] 

Uwe Schindler commented on LUCENE-6938:
---

In trunk, the smoke tester on Jenkins did not pass: 
https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/395/console

To me it looks like some magic we do with the src-export folder did not fully 
work, so missing some files:
{noformat}
package-tgz-src:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/src-export/docs/changes
  [get] Getting: https://issues.apache.org/jira/rest/api/2/project/LUCENE
  [get] To: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/src-export/docs/changes/jiraVersionList.json
 [exec] Failed to open 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/src-export/CHANGES.txt
 [exec] Use of uninitialized value $first_relid_regex in substitution 
(s///) at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 223.
 [exec] Use of uninitialized value $second_relid_regex in substitution 
(s///) at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 225.
 [exec] Use of uninitialized value $first_relid_regex in concatenation (.) 
or string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 226.
 [exec] Use of uninitialized value $second_relid_regex in concatenation (.) 
or string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 226.
 [exec] Use of uninitialized value $title in concatenation (.) or string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
 [exec] Use of uninitialized value $first_relid in concatenation (.) or 
string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
 [exec] Use of uninitialized value $second_relid in concatenation (.) or 
string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
 [exec] Use of uninitialized value $first_relid in concatenation (.) or 
string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
 [exec] Use of uninitialized value $second_relid in concatenation (.) or 
string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
 [exec] Use of uninitialized value $title in concatenation (.) or string at 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/site/changes/changes2html.pl
 line 231.
   [delete] Deleting: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/src-export/docs/changes/jiraVersionList.json
 [copy] Copying 3 files to 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/src-export/docs/changes
  [tar] Building tar: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/dist/lucene-6.0.0-src.tgz
 [echo] Building checksums for 
'/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/dist/lucene-6.0.0-src.tgz'
{noformat}

Not sure what is broken there.

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Dawid Weiss
1. The content of the lucene-solr.git repository looks good!

2) PROBLEM. I can't push my own branch:

$ git co master -b git-check
$ [... committed a dummy commit ]
$ git push origin HEAD -u
fatal: remote error: access denied or repository not exported: /lucene-solr.git

3) Solr repo is still available for some reason, both as real git repo here:

git://git.apache.org/solr.git

and listed here:

https://git.apache.org/

Could I be seeing a mirror or something?

Dawid


On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
> Checking everything now -- that was fast Daniel!
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
>> Just a heads up: Everything is working now and GitHub has caught up with
>> the new repository. You should be good to go :)
>>
>> With regards,
>> Daniel.
>>
>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
 Hello Daniel,

 I've prepared everything for the migration and I hand it off to you (I
 will be available in the morning, if you need assistance). I can also
 log on to hipchat, but send me an e-mail if you wish me to.

 Here are the steps we kindly ask you to perform (I allowed myself to
 uppercase certain things, apologies if it looks like shouting):

 1) Permanently REMOVE the following git mirrors of SVN (reason: they
 are obsolete and incorrect syncs, consolidated git repo contains full
 history):

 git://git.apache.org/solr.git
>>> DONE
>>>
 git://git.apache.org/lucene.git
>>> DONE

 2) Notify (somehow) GitHub that these two repos have been removed
 (they should not be available or visible on GitHub as well):

 https://github.com/apache/lucene
>>> DONE
 https://github.com/apache/solr
>>> DONE
>>>

 3) DISABLE svn syncing for the following git mirror:

 git://git.apache.org/lucene-solr.git
>>> DONE
>>>

 and then REPLACE it (wipe it clean) with the content of the following
 consolidated repository:

 g...@github.com:dweiss/lucene-solr-svn2git.git

 I don't know how it looks from the backend's side, but this should
 also work, if there are sufficient permissions:

 git clone g...@github.com:dweiss/lucene-solr-svn2git.git
 git remote add apache git://git.apache.org/lucene-solr.git
 git push --mirror apache
>>> We have our own methods, but nonetheless DONE. Please check that you
>>> have write-access to the new repo.

 4) I don't know if we need to make GitHub aware of the replaced
 content of the lucene-solr repo or if their syncing will handle this
 automatically. It would be nice if they could catch up as quickly as
 possible.
>>>
>>> As explained on the JIRA ticket, if we're lucky, this should happen
>>> automagically in about 20 minutes from now. If not, we'll have to wait
>>> 24 hours. Time will tell :)
>>>
>>> With regards,
>>> Daniel.
>>>

 In case of questions, problems or a successful import, please drop me
 an e-mail. Oh, thank you for being so nice and helping us on your day
 off -- much appreciated.

 Dawid

>>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Ramkumar R. Aiyengar
https://git-scm.com/docs/git-credential-cache

Should help with the constant password typing..
On 23 Jan 2016 09:13, "Dawid Weiss"  wrote:

> Ok, folks. Seems like code migration is complete, with both gh mirrors
> and Apache repos up.
>
> 1. Please read the docs at: https://git-wip-us.apache.org/
>
> 2. I didn't realize Apache's repositories are over https, which makes
> authorization rather painful for Linux users (requires password typing
> on every push). I think I'll stick with gh for this reason and only
> push my changes when they're fully baked.
>
> 3. The master branch (former trunk) passes ant precommit for me, but I
> didn't apply build patches to branch_5x yet.
>
> If there are any problems or concerns, let me know (perhaps I'll be
> able to help).
>
> Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-1

Here is the patch to fix the Lucene src.tgz. The reason was simple.

src.export.dir contains now root folder, but previously it was only the lucene/ 
subfolder. The logic in the macro and git's behaviour did not reflect this. Te 
quick workaround is to define additional property for Lucene's build.xml and 
append this while tarring and running scripts.

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-1.patch

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: (was: LUCENE-6938-1)

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-1.patch

Final version, previous one was not as effective as current one.

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: (was: LUCENE-6938-1.patch)

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 396 - Still Failing

2016-01-23 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/396/

No tests ran.

Build Log:
[...truncated 35897 lines...]
prepare-release-no-sign:
[mkdir] Created dir: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist
 [copy] Copying 461 files to 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/lucene
 [copy] Copying 245 files to 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/solr
   [smoker] Java 1.8 
JAVA_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
   [smoker] NOTE: output encoding is UTF-8
   [smoker] 
   [smoker] Load release URL 
"file:/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist/"...
   [smoker] 
   [smoker] Test Lucene...
   [smoker]   test basics...
   [smoker]   get KEYS
   [smoker] 0.2 MB in 0.01 sec (11.0 MB/sec)
   [smoker]   check changes HTML...
   [smoker]   download lucene-6.0.0-src.tgz...
   [smoker] 28.3 MB in 0.04 sec (794.6 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   download lucene-6.0.0.tgz...
   [smoker] 62.6 MB in 0.08 sec (766.9 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   download lucene-6.0.0.zip...
   [smoker] 73.1 MB in 0.10 sec (739.1 MB/sec)
   [smoker] verify md5/sha1 digests
   [smoker]   unpack lucene-6.0.0.tgz...
   [smoker] verify JAR metadata/identity/no javax.* or java.* classes...
   [smoker] test demo with 1.8...
   [smoker]   got 5973 hits for query "lucene"
   [smoker] checkindex with 1.8...
   [smoker] check Lucene's javadoc JAR
   [smoker]   unpack lucene-6.0.0.zip...
   [smoker] verify JAR metadata/identity/no javax.* or java.* classes...
   [smoker] test demo with 1.8...
   [smoker]   got 5973 hits for query "lucene"
   [smoker] checkindex with 1.8...
   [smoker] check Lucene's javadoc JAR
   [smoker]   unpack lucene-6.0.0-src.tgz...
   [smoker] make sure no JARs/WARs in src dist...
   [smoker] run "ant validate"
   [smoker] run tests w/ Java 8 and testArgs='-Dtests.slow=false'...
   [smoker] 
   [smoker] command "export 
JAVA_HOME="/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8" 
PATH="/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/bin:$PATH" 
JAVACMD="/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/bin/java";
 ant clean test -Dtests.slow=false" failed:
   [smoker] Buildfile: 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/tmp/unpack/lucene-6.0.0/build.xml
   [smoker] 
   [smoker] clean:
   [smoker][delete] Deleting directory 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/tmp/unpack/lucene-6.0.0/build
   [smoker] 
   [smoker] ivy-availability-check:
   [smoker] 
   [smoker] ivy-fail:
   [smoker] 
   [smoker] ivy-configure:
   [smoker] [ivy:configure] :: Apache Ivy 2.3.0 - 20130110142753 :: 
http://ant.apache.org/ivy/ ::
   [smoker] [ivy:configure] :: loading settings :: file = 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/tmp/unpack/lucene-6.0.0/ivy-settings.xml
   [smoker] 
   [smoker] -clover.load:
   [smoker] 
   [smoker] resolve-groovy:
   [smoker] [ivy:cachepath] :: resolving dependencies :: 
org.codehaus.groovy#groovy-all-caller;working
   [smoker] [ivy:cachepath] confs: [default]
   [smoker] [ivy:cachepath] found org.codehaus.groovy#groovy-all;2.4.4 in 
public
   [smoker] [ivy:cachepath] :: resolution report :: resolve 233ms :: artifacts 
dl 3ms
   [smoker] 
-
   [smoker] |  |modules||   
artifacts   |
   [smoker] |   conf   | number| search|dwnlded|evicted|| 
number|dwnlded|
   [smoker] 
-
   [smoker] |  default |   1   |   0   |   0   |   0   ||   1   |   
0   |
   [smoker] 
-
   [smoker] 
   [smoker] -init-totals:
   [smoker] 
   [smoker] test-core:
   [smoker] 
   [smoker] -clover.disable:
   [smoker] 
   [smoker] ivy-availability-check:
   [smoker] 
   [smoker] ivy-fail:
   [smoker] 
   [smoker] ivy-configure:
   [smoker] [ivy:configure] :: loading settings :: file = 
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/tmp/unpack/lucene-6.0.0/ivy-settings.xml
   [smoker] 
   [smoker] -clover.load:
   [smoker] 
   [smoker] -clover.classpath:
   [smoker] 
   [smoker] -clover.setup:
   [smoker] 
   [smoker] clover:
   [smoker] 
   [smoker] resolve:
   [smoker] 
   [smoker] init:
   [smoker] 
   [smoker] compile-core:
   [smoker] [mkdir] Created dir: 

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

2016-01-23 Thread Daniel Gruno
Just a heads up: Everything is working now and GitHub has caught up with
the new repository. You should be good to go :)

With regards,
Daniel.

On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
> 
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
> 
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
> 
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo or if their syncing will handle this
>> automatically. It would be nice if they could catch up as quickly as
>> possible.
> 
> As explained on the JIRA ticket, if we're lucky, this should happen
> automagically in about 20 minutes from now. If not, we'll have to wait
> 24 hours. Time will tell :)
> 
> With regards,
> Daniel.
> 
>>
>> In case of questions, problems or a successful import, please drop me
>> an e-mail. Oh, thank you for being so nice and helping us on your day
>> off -- much appreciated.
>>
>> Dawid
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Dawid Weiss
Checking everything now -- that was fast Daniel!
Dawid


On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
> Just a heads up: Everything is working now and GitHub has caught up with
> the new repository. You should be good to go :)
>
> With regards,
> Daniel.
>
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>>
>>> I've prepared everything for the migration and I hand it off to you (I
>>> will be available in the morning, if you need assistance). I can also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>>
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>>
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains full
>>> history):
>>>
>>> git://git.apache.org/solr.git
>> DONE
>>
>>> git://git.apache.org/lucene.git
>> DONE
>>>
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>>
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>>
>>>
>>> 3) DISABLE svn syncing for the following git mirror:
>>>
>>> git://git.apache.org/lucene-solr.git
>> DONE
>>
>>>
>>> and then REPLACE it (wipe it clean) with the content of the following
>>> consolidated repository:
>>>
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>>
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>>
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>>> git remote add apache git://git.apache.org/lucene-solr.git
>>> git push --mirror apache
>> We have our own methods, but nonetheless DONE. Please check that you
>> have write-access to the new repo.
>>>
>>> 4) I don't know if we need to make GitHub aware of the replaced
>>> content of the lucene-solr repo or if their syncing will handle this
>>> automatically. It would be nice if they could catch up as quickly as
>>> possible.
>>
>> As explained on the JIRA ticket, if we're lucky, this should happen
>> automagically in about 20 minutes from now. If not, we'll have to wait
>> 24 hours. Time will tell :)
>>
>> With regards,
>> Daniel.
>>
>>>
>>> In case of questions, problems or a successful import, please drop me
>>> an e-mail. Oh, thank you for being so nice and helping us on your day
>>> off -- much appreciated.
>>>
>>> Dawid
>>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113753#comment-15113753
 ] 

Uwe Schindler commented on LUCENE-6938:
---

I cherry-picked the 3 commit (Mark/Dawids and 2 of mine). Worked like a charm 
with the GUI of Tortoise. The conflicts Dawid found was just java8 vs. java7 
strings.

I'll now reenable 5.x builds on jenkins

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-1.patch

Updated patch also disabling svnkit stuff in root.

Will commit in a moment to make smoker work

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938-1.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113728#comment-15113728
 ] 

Uwe Schindler commented on LUCENE-6938:
---

It looks like JIRA does not yet reports GIT commits, we should fix that.

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Dawid Weiss
Thanks Ramkumar. Also thank you for saving that list of PRs, that was
very thoughtful of you.

Dawid

On Sat, Jan 23, 2016 at 10:26 AM, Ramkumar R. Aiyengar
 wrote:
> https://git-scm.com/docs/git-credential-cache
>
> Should help with the constant password typing..
>
> On 23 Jan 2016 09:13, "Dawid Weiss"  wrote:
>>
>> Ok, folks. Seems like code migration is complete, with both gh mirrors
>> and Apache repos up.
>>
>> 1. Please read the docs at: https://git-wip-us.apache.org/
>>
>> 2. I didn't realize Apache's repositories are over https, which makes
>> authorization rather painful for Linux users (requires password typing
>> on every push). I think I'll stick with gh for this reason and only
>> push my changes when they're fully baked.
>>
>> 3. The master branch (former trunk) passes ant precommit for me, but I
>> didn't apply build patches to branch_5x yet.
>>
>> If there are any problems or concerns, let me know (perhaps I'll be
>> able to help).
>>
>> Dawid
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15621 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15621/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC

1 tests failed.
FAILED:  org.apache.lucene.search.grouping.TestGrouping.testBasic

Error Message:


Stack Trace:
java.lang.AssertionError
at 
__randomizedtesting.SeedInfo.seed([E3AE5C3FEE8E32AC:4854412A3152B482]:0)
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.lucene.search.grouping.TestGrouping.testBasic(TestGrouping.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)




Build Log:
[...truncated 6204 lines...]
   [junit4] Suite: org.apache.lucene.search.grouping.TestGrouping
   [junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=TestGrouping 
-Dtests.method=testBasic -Dtests.seed=E3AE5C3FEE8E32AC -Dtests.multiplier=3 
-Dtests.slow=true -Dtests.locale=es-CU -Dtests.timezone=America/Rio_Branco 
-Dtests.asserts=true -Dtests.file.encoding=ISO-8859-1
   [junit4] FAILURE 0.01s J0 | TestGrouping.testBasic <<<
   [junit4]> Throwable #1: java.lang.AssertionError
   [junit4]>at 
__randomizedtesting.SeedInfo.seed([E3AE5C3FEE8E32AC:4854412A3152B482]:0)
   [junit4]>at 

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

2016-01-23 Thread Daniel Gruno
On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
> 
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

Nothing. This is GitHub's fallback method when the original repository
goes away as it did here (replaced with a new repo with a new history).
Since referring to the old repo which doesn't exist anymore would break
your copy, they have fallen back to another copy of it.

Please re-fork.

With regards,
Daniel.

> 
> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
>> 1. The content of the lucene-solr.git repository looks good!
>>
>> 2) PROBLEM. I can't push my own branch:
>>
>> $ git co master -b git-check
>> $ [... committed a dummy commit ]
>> $ git push origin HEAD -u
>> fatal: remote error: access denied or repository not exported: 
>> /lucene-solr.git
>>
>> 3) Solr repo is still available for some reason, both as real git repo here:
>>
>> git://git.apache.org/solr.git
>>
>> and listed here:
>>
>> https://git.apache.org/
>>
>> Could I be seeing a mirror or something?
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
>>> Checking everything now -- that was fast Daniel!
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
 Just a heads up: Everything is working now and GitHub has caught up with
 the new repository. You should be good to go :)

 With regards,
 Daniel.

 On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
>
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
>
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
>
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo or if their syncing will handle this
>> automatically. It would be nice if they could catch up as quickly as
>> possible.
>
> As explained on the JIRA ticket, if we're lucky, this should happen
> automagically in about 20 minutes from now. If not, we'll have to wait
> 24 hours. Time will tell :)
>
> With regards,
> Daniel.
>
>>
>> In case of questions, problems or a successful import, please drop me
>> an e-mail. Oh, thank you for being so nice and helping us on your day
>> off -- much appreciated.
>>
>> Dawid
>>
>

>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
> 
> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Shalin Shekhar Mangar
Thanks Dawid and Daniel for all the work!

One strange thing that I noticed is that my fork of apache/lucene-solr
at https://github.com/shalinmangar/lucene-solr is now shown to be a
fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
that guy is. What can we do to fix this?

On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
> 1. The content of the lucene-solr.git repository looks good!
>
> 2) PROBLEM. I can't push my own branch:
>
> $ git co master -b git-check
> $ [... committed a dummy commit ]
> $ git push origin HEAD -u
> fatal: remote error: access denied or repository not exported: 
> /lucene-solr.git
>
> 3) Solr repo is still available for some reason, both as real git repo here:
>
> git://git.apache.org/solr.git
>
> and listed here:
>
> https://git.apache.org/
>
> Could I be seeing a mirror or something?
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
>> Checking everything now -- that was fast Daniel!
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
>>> Just a heads up: Everything is working now and GitHub has caught up with
>>> the new repository. You should be good to go :)
>>>
>>> With regards,
>>> Daniel.
>>>
>>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
 On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
>
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
>
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
>
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
>
> git://git.apache.org/solr.git
 DONE

> git://git.apache.org/lucene.git
 DONE
>
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
>
> https://github.com/apache/lucene
 DONE
> https://github.com/apache/solr
 DONE

>
> 3) DISABLE svn syncing for the following git mirror:
>
> git://git.apache.org/lucene-solr.git
 DONE

>
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
>
> g...@github.com:dweiss/lucene-solr-svn2git.git
>
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
>
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
 We have our own methods, but nonetheless DONE. Please check that you
 have write-access to the new repo.
>
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

 As explained on the JIRA ticket, if we're lucky, this should happen
 automagically in about 20 minutes from now. If not, we'll have to wait
 24 hours. Time will tell :)

 With regards,
 Daniel.

>
> In case of questions, problems or a successful import, please drop me
> an e-mail. Oh, thank you for being so nice and helping us on your day
> off -- much appreciated.
>
> Dawid
>

>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>



-- 
Regards,
Shalin Shekhar Mangar.

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Dawid Weiss
If you're using github then yes, you will need to fork again and
rebase any changes you may have. This can be done by having two
origins locally (two "sources" of commits) -- one from the old clone,
the second one from the new clone. Then you can rebase the branches or
commits you wish and push them to the new clone.

Dawid


On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>> Thanks Dawid and Daniel for all the work!
>>
>> One strange thing that I noticed is that my fork of apache/lucene-solr
>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>> that guy is. What can we do to fix this?
>
> Nothing. This is GitHub's fallback method when the original repository
> goes away as it did here (replaced with a new repo with a new history).
> Since referring to the old repo which doesn't exist anymore would break
> your copy, they have fallen back to another copy of it.
>
> Please re-fork.
>
> With regards,
> Daniel.
>
>>
>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
>>> 1. The content of the lucene-solr.git repository looks good!
>>>
>>> 2) PROBLEM. I can't push my own branch:
>>>
>>> $ git co master -b git-check
>>> $ [... committed a dummy commit ]
>>> $ git push origin HEAD -u
>>> fatal: remote error: access denied or repository not exported: 
>>> /lucene-solr.git
>>>
>>> 3) Solr repo is still available for some reason, both as real git repo here:
>>>
>>> git://git.apache.org/solr.git
>>>
>>> and listed here:
>>>
>>> https://git.apache.org/
>>>
>>> Could I be seeing a mirror or something?
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
 Checking everything now -- that was fast Daniel!
 Dawid


 On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
> Just a heads up: Everything is working now and GitHub has caught up with
> the new repository. You should be good to go :)
>
> With regards,
> Daniel.
>
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>>
>>> I've prepared everything for the migration and I hand it off to you (I
>>> will be available in the morning, if you need assistance). I can also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>>
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>>
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains full
>>> history):
>>>
>>> git://git.apache.org/solr.git
>> DONE
>>
>>> git://git.apache.org/lucene.git
>> DONE
>>>
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>>
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>>
>>>
>>> 3) DISABLE svn syncing for the following git mirror:
>>>
>>> git://git.apache.org/lucene-solr.git
>> DONE
>>
>>>
>>> and then REPLACE it (wipe it clean) with the content of the following
>>> consolidated repository:
>>>
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>>
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>>
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>>> git remote add apache git://git.apache.org/lucene-solr.git
>>> git push --mirror apache
>> We have our own methods, but nonetheless DONE. Please check that you
>> have write-access to the new repo.
>>>
>>> 4) I don't know if we need to make GitHub aware of the replaced
>>> content of the lucene-solr repo or if their syncing will handle this
>>> automatically. It would be nice if they could catch up as quickly as
>>> possible.
>>
>> As explained on the JIRA ticket, if we're lucky, this should happen
>> automagically in about 20 minutes from now. If not, we'll have to wait
>> 24 hours. Time will tell :)
>>
>> With regards,
>> Daniel.
>>
>>>
>>> In case of questions, problems or a successful import, please drop me
>>> an e-mail. Oh, thank you for being so nice and helping us on your day
>>> off -- much appreciated.
>>>
>>> Dawid
>>>
>>
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>
>>
>>
>
>
> 

RE: GIT migration complete

2016-01-23 Thread Uwe Schindler
Hi,

Thanks! I am talking care of Jenkins at the moment. 

First Policeman one is working: 
http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15619/console

The Changes I do for jenkins is:
- Deleted *all* workspaces to have clean start
- Change all Jobs (is a bit of work as manually, especially for ASF) to use Git 
checkouts of corresponding branch
- Add the following "additional behaviour" config: Clean before checkout: Clean 
up the workspace before every checkout by deleting all untracked files and 
directories, including those which are specified in .gitignore. It also resets 
all tracked files to their versioned state. This ensures that the workspace is 
in the same state as if you cloned and checked out in a brand-new empty 
directory, and ensures that your build is not affected by the files generated 
by the previous build.

Uwe

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de

> From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> Sent: Saturday, January 23, 2016 10:13 AM
> To: dev@lucene.apache.org
> Subject: GIT migration complete
> 
> Ok, folks. Seems like code migration is complete, with both gh mirrors
> and Apache repos up.
> 
> 1. Please read the docs at: https://git-wip-us.apache.org/
> 
> 2. I didn't realize Apache's repositories are over https, which makes
> authorization rather painful for Linux users (requires password typing
> on every push). I think I'll stick with gh for this reason and only
> push my changes when they're fully baked.
> 
> 3. The master branch (former trunk) passes ant precommit for me, but I
> didn't apply build patches to branch_5x yet.
> 
> If there are any problems or concerns, let me know (perhaps I'll be
> able to help).
> 
> Dawid
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Ramkumar R. Aiyengar
You're welcome! :)
On 23 Jan 2016 09:31, "Dawid Weiss"  wrote:

> Thanks Ramkumar. Also thank you for saving that list of PRs, that was
> very thoughtful of you.
>
> Dawid
>
> On Sat, Jan 23, 2016 at 10:26 AM, Ramkumar R. Aiyengar
>  wrote:
> > https://git-scm.com/docs/git-credential-cache
> >
> > Should help with the constant password typing..
> >
> > On 23 Jan 2016 09:13, "Dawid Weiss"  wrote:
> >>
> >> Ok, folks. Seems like code migration is complete, with both gh mirrors
> >> and Apache repos up.
> >>
> >> 1. Please read the docs at: https://git-wip-us.apache.org/
> >>
> >> 2. I didn't realize Apache's repositories are over https, which makes
> >> authorization rather painful for Linux users (requires password typing
> >> on every push). I think I'll stick with gh for this reason and only
> >> push my changes when they're fully baked.
> >>
> >> 3. The master branch (former trunk) passes ant precommit for me, but I
> >> didn't apply build patches to branch_5x yet.
> >>
> >> If there are any problems or concerns, let me know (perhaps I'll be
> >> able to help).
> >>
> >> Dawid
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: (was: LUCENE-6938-1.patch)

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: (was: LUCENE-6938-1.patch)

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uwe Schindler updated LUCENE-6938:
--
Attachment: LUCENE-6938-1.patch

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938-1.patch, 
> LUCENE-6938-1.patch, LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15622 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15622/
Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseSerialGC

1 tests failed.
FAILED:  
org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication

Error Message:
Index: 0, Size: 0

Stack Trace:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at 
__randomizedtesting.SeedInfo.seed([10AC58808C579824:E7DFB6D84ABF37C2]:0)
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at 
org.apache.solr.handler.TestReplicationHandler.doTestIndexAndConfigAliasReplication(TestReplicationHandler.java:1241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)




Build Log:
[...truncated 10255 lines...]
   [junit4] Suite: org.apache.solr.handler.TestReplicationHandler
   [junit4]   2> Creating dataDir: 

[jira] [Commented] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113724#comment-15113724
 ] 

Uwe Schindler commented on LUCENE-6938:
---

I committed everything. [~dawid.weiss], can you merge my recent commit to 5.x, 
too?

The Jenkins Jobs for 5.x are not yet enabled, I am waiting for backport.

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Michael McCandless
Thank you Dawid and Daniel for all the hard work here!!

Mike McCandless

http://blog.mikemccandless.com


On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
 wrote:
> Got it, thanks! I'll try your suggestion, Dawid.
>
> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
>> If you're using github then yes, you will need to fork again and
>> rebase any changes you may have. This can be done by having two
>> origins locally (two "sources" of commits) -- one from the old clone,
>> the second one from the new clone. Then you can rebase the branches or
>> commits you wish and push them to the new clone.
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
>>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
 Thanks Dawid and Daniel for all the work!

 One strange thing that I noticed is that my fork of apache/lucene-solr
 at https://github.com/shalinmangar/lucene-solr is now shown to be a
 fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
 that guy is. What can we do to fix this?
>>>
>>> Nothing. This is GitHub's fallback method when the original repository
>>> goes away as it did here (replaced with a new repo with a new history).
>>> Since referring to the old repo which doesn't exist anymore would break
>>> your copy, they have fallen back to another copy of it.
>>>
>>> Please re-fork.
>>>
>>> With regards,
>>> Daniel.
>>>

 On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
> 1. The content of the lucene-solr.git repository looks good!
>
> 2) PROBLEM. I can't push my own branch:
>
> $ git co master -b git-check
> $ [... committed a dummy commit ]
> $ git push origin HEAD -u
> fatal: remote error: access denied or repository not exported: 
> /lucene-solr.git
>
> 3) Solr repo is still available for some reason, both as real git repo 
> here:
>
> git://git.apache.org/solr.git
>
> and listed here:
>
> https://git.apache.org/
>
> Could I be seeing a mirror or something?
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
> wrote:
>> Checking everything now -- that was fast Daniel!
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
>> wrote:
>>> Just a heads up: Everything is working now and GitHub has caught up with
>>> the new repository. You should be good to go :)
>>>
>>> With regards,
>>> Daniel.
>>>
>>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
 On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
>
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
>
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
>
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
>
> git://git.apache.org/solr.git
 DONE

> git://git.apache.org/lucene.git
 DONE
>
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
>
> https://github.com/apache/lucene
 DONE
> https://github.com/apache/solr
 DONE

>
> 3) DISABLE svn syncing for the following git mirror:
>
> git://git.apache.org/lucene-solr.git
 DONE

>
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
>
> g...@github.com:dweiss/lucene-solr-svn2git.git
>
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
>
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
 We have our own methods, but nonetheless DONE. Please check that you
 have write-access to the new repo.
>
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

 As explained on the JIRA ticket, if we're lucky, this should happen
 automagically in about 20 minutes from now. If not, we'll have to wait

Post git transition

2016-01-23 Thread Dawid Weiss
Thanks to everyone for early feedback. I have a pretty busy day today
after a short night, but I'll try to kick in and apply the patches/
missing bits you requested. You can also try to play around -- clone
the project on github and use your own clone of the repository to file
a pull request if you don't feed comfortable with git yet.

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15623 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15623/
Java: 32bit/jdk-9-ea+95 -server -XX:+UseG1GC -XX:-CompactStrings

2 tests failed.
FAILED:  org.apache.lucene.search.TestLatLonPointQueries.testAllLatEqual

Error Message:
Captured an uncaught exception in thread: Thread[id=38, name=T2, 
state=RUNNABLE, group=TGRP-TestLatLonPointQueries]

Stack Trace:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=38, name=T2, state=RUNNABLE, 
group=TGRP-TestLatLonPointQueries]
Caused by: java.lang.AssertionError: some hits were wrong
at __randomizedtesting.SeedInfo.seed([43A6134EAE421688]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)


FAILED:  org.apache.lucene.search.TestLatLonPointQueries.testMultiValued

Error Message:
some hits were wrong

Stack Trace:
java.lang.AssertionError: some hits were wrong
at 
__randomizedtesting.SeedInfo.seed([43A6134EAE421688:9786777C608056C0]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.lucene.util.BaseGeoPointTestCase.testMultiValued(BaseGeoPointTestCase.java:322)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 

[jira] [Updated] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Heisey updated SOLR-8589:
---
Attachment: solr-8589-new-list-details-aliases.png

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch, solr-8589-new-list-details-aliases.png
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

2016-01-23 Thread Shalin Shekhar Mangar (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shalin Shekhar Mangar updated SOLR-8582:

 Assignee: Noble Paul
Affects Version/s: 5.4.1
   5.3.2

> /update/json/docs is 4x slower than /update for indexing a list of json docs
> 
>
> Key: SOLR-8582
> URL: https://issues.apache.org/jira/browse/SOLR-8582
> Project: Solr
>  Issue Type: Bug
>  Components: update
>Affects Versions: 5.3.2, 5.4.1
>Reporter: Shalin Shekhar Mangar
>Assignee: Noble Paul
> Fix For: 5.5, Trunk
>
> Attachments: SOLR-8582.patch, SOLR-8582.patch
>
>
> Indexing a ~650 MB json file containing a list of 2.2 million json documents, 
> I found that bin/post had become 4x slower after SOLR-7042. Memory 
> consumption has also gone up and I can no longer index this file with a 512mb 
> heap.
> The difference is because we now default to /update/json/docs instead of 
> /update. This can be verified on trunk:
> {code}
> time curl 'http://localhost:8983/solr/gettingstarted/update' --data-binary 
> @/hdd/solr-data/imdb.json 
> {"responseHeader":{"status":0,"QTime":161869}}
> ​
> real  2m42.044s
> user  0m0.292s
> sys   0m0.493s
> ​
> time curl 'http://localhost:8983/solr/gettingstarted/update/json/docs' 
> --data-binary @/hdd/solr-data/imdb.json 
> {"responseHeader":{"status":0,"QTime":686264}}
> ​
> real  11m26.478s
> user  0m0.324s
> sys   0m0.552s
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-8587) Add segments file information to core admin status

2016-01-23 Thread Shai Erera (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shai Erera updated SOLR-8587:
-
Attachment: SOLR-8587.patch

Patch updated to the GIT clone.

> Add segments file information to core admin status
> --
>
> Key: SOLR-8587
> URL: https://issues.apache.org/jira/browse/SOLR-8587
> Project: Solr
>  Issue Type: Improvement
>Reporter: Shai Erera
>Assignee: Shai Erera
> Attachments: SOLR-8587.patch, SOLR-8587.patch
>
>
> Having the index's segments file name returned by CoreAdminHandler STATUS can 
> be useful. The info I'm thinking about is the segments file name and its 
> size. If you record that from time to time, in a case of crisis, when u need 
> to restore the index and may not be sure which copy you need to restore, this 
> tiny piece of info can be very useful, as the segmentsN file records the 
> commit point, and therefore what you core reported and what you see at hand 
> can help you make a safer decision.
> I also think it's useful info in general, e.g. probably even more than 
> 'version', and it doesn't add much complexity to the handler or the response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Resolved] (SOLR-8582) /update/json/docs is 4x slower than /update for indexing a list of json docs

2016-01-23 Thread Shalin Shekhar Mangar (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shalin Shekhar Mangar resolved SOLR-8582.
-
Resolution: Fixed

Thanks Noble!

> /update/json/docs is 4x slower than /update for indexing a list of json docs
> 
>
> Key: SOLR-8582
> URL: https://issues.apache.org/jira/browse/SOLR-8582
> Project: Solr
>  Issue Type: Bug
>  Components: update
>Affects Versions: 5.3.2, 5.4.1
>Reporter: Shalin Shekhar Mangar
>Assignee: Noble Paul
> Fix For: 5.5, Trunk
>
> Attachments: SOLR-8582.patch, SOLR-8582.patch
>
>
> Indexing a ~650 MB json file containing a list of 2.2 million json documents, 
> I found that bin/post had become 4x slower after SOLR-7042. Memory 
> consumption has also gone up and I can no longer index this file with a 512mb 
> heap.
> The difference is because we now default to /update/json/docs instead of 
> /update. This can be verified on trunk:
> {code}
> time curl 'http://localhost:8983/solr/gettingstarted/update' --data-binary 
> @/hdd/solr-data/imdb.json 
> {"responseHeader":{"status":0,"QTime":161869}}
> ​
> real  2m42.044s
> user  0m0.292s
> sys   0m0.493s
> ​
> time curl 'http://localhost:8983/solr/gettingstarted/update/json/docs' 
> --data-binary @/hdd/solr-data/imdb.json 
> {"responseHeader":{"status":0,"QTime":686264}}
> ​
> real  11m26.478s
> user  0m0.324s
> sys   0m0.552s
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: lucene-solr git commit: make this test less anal about scores so the new DFI sim won't cause false failures

2016-01-23 Thread Michael McCandless
Woops, thanks Uwe!

Mike McCandless

http://blog.mikemccandless.com


On Sat, Jan 23, 2016 at 9:51 AM, Uwe Schindler  wrote:
> Hi Mike,
>
> the GIT Howto page at apache says, that your commits should use the 
> @apache.org address. If you don't want to change this globally, you can set 
> the e-mail address for a working-copy only, see second one:
>
> https://git-wip-us.apache.org/#committers-getting-started
>
> Your current commit makes it look like you (mikemcc...@apache.org) pushed a 
> commit from somebody else (m...@mikemccandless.com).
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>> -Original Message-
>> From: mikemcc...@apache.org [mailto:mikemcc...@apache.org]
>> Sent: Saturday, January 23, 2016 3:32 PM
>> To: comm...@lucene.apache.org
>> Subject: lucene-solr git commit: make this test less anal about scores so the
>> new DFI sim won't cause false failures
>>
>> Repository: lucene-solr
>> Updated Branches:
>>   refs/heads/master 657b3e617 -> 1199bbe1b
>>
>>
>> make this test less anal about scores so the new DFI sim won't cause false
>> failures
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/lucene-
>> solr/commit/1199bbe1
>> Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/1199bbe1
>> Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/1199bbe1
>>
>> Branch: refs/heads/master
>> Commit: 1199bbe1b39e73c6e78ec570eae2ae62a5ccc361
>> Parents: 657b3e6
>> Author: Michael McCandless 
>> Authored: Sat Jan 23 09:31:39 2016 -0500
>> Committer: Mike McCandless 
>> Committed: Sat Jan 23 09:31:39 2016 -0500
>>
>> --
>>  .../src/test/org/apache/lucene/search/grouping/TestGrouping.java | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/lucene-
>> solr/blob/1199bbe1/lucene/grouping/src/test/org/apache/lucene/search/gr
>> ouping/TestGrouping.java
>> --
>> diff --git
>> a/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroupi
>> ng.java
>> b/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroup
>> ing.java
>> index a8711c5..2842528 100644
>> ---
>> a/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroupi
>> ng.java
>> +++
>> b/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroup
>> ing.java
>> @@ -176,8 +176,8 @@ public class TestGrouping extends LuceneTestCase {
>>  assertEquals(0, group.scoreDocs[0].doc);
>>  assertEquals(1, group.scoreDocs[1].doc);
>>  assertEquals(2, group.scoreDocs[2].doc);
>> -assertTrue(group.scoreDocs[0].score > group.scoreDocs[1].score);
>> -assertTrue(group.scoreDocs[1].score > group.scoreDocs[2].score);
>> +assertTrue(group.scoreDocs[0].score >= group.scoreDocs[1].score);
>> +assertTrue(group.scoreDocs[1].score >= group.scoreDocs[2].score);
>>
>>  group = groups.groups[2];
>>  compareGroupValue("author2", group);
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-trunk-Solaris (64bit/jdk1.8.0) - Build # 349 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/349/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC

2 tests failed.
FAILED:  org.apache.solr.handler.TestReplicationHandler.doTestStressReplication

Error Message:
[index.20160124023732261, index.properties, replication.properties, 
index.20160124023717240] expected:<1> but was:<2>

Stack Trace:
java.lang.AssertionError: [index.20160124023732261, index.properties, 
replication.properties, index.20160124023717240] expected:<1> but was:<2>
at 
__randomizedtesting.SeedInfo.seed([5C84E66530510DC6:872FE6A335796475]:0)
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.failNotEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:128)
at org.junit.Assert.assertEquals(Assert.java:472)
at 
org.apache.solr.handler.TestReplicationHandler.checkForSingleIndex(TestReplicationHandler.java:820)
at 
org.apache.solr.handler.TestReplicationHandler.doTestStressReplication(TestReplicationHandler.java:787)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 

Re: Post git transition

2016-01-23 Thread Joel Bernstein
Just forked and cloned. The clone was fast! I'll play around some this
weekend. Thanks for taking this on!

Joel Bernstein
http://joelsolr.blogspot.com/

On Sat, Jan 23, 2016 at 8:21 AM, Dawid Weiss  wrote:

> Thanks to everyone for early feedback. I have a pretty busy day today
> after a short night, but I'll try to kick in and apply the patches/
> missing bits you requested. You can also try to play around -- clone
> the project on github and use your own clone of the repository to file
> a pull request if you don't feed comfortable with git yet.
>
> Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113774#comment-15113774
 ] 

Shawn Heisey commented on SOLR-8589:


This was requested by [~yriveiro] in the #solr IRC channel.

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15625 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15625/
Java: 32bit/jdk-9-ea+95 -client -XX:+UseSerialGC -XX:-CompactStrings

1 tests failed.
FAILED:  org.apache.solr.handler.TestReplicationHandler.doTestStressReplication

Error Message:
timed out waiting for collection1 startAt time to exceed: Sun Jan 24 00:15:12 
CST 2016

Stack Trace:
java.lang.AssertionError: timed out waiting for collection1 startAt time to 
exceed: Sun Jan 24 00:15:12 CST 2016
at 
__randomizedtesting.SeedInfo.seed([E30AF1751E14C28A:38A1F1B31B3CAB39]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.solr.handler.TestReplicationHandler.watchCoreStartAt(TestReplicationHandler.java:1419)
at 
org.apache.solr.handler.TestReplicationHandler.doTestStressReplication(TestReplicationHandler.java:771)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:747)




Build Log:
[...truncated 10306 lines...]
   [junit4] Suite: 

[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Yago Riveiro (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113817#comment-15113817
 ] 

Yago Riveiro commented on SOLR-8589:


Aliases are related with collections, if I need to do a HTTP call to get the 
aliases from clusterstatus API I will need to parse a huge structure (with 
thousand of collections) with a lot of noise only to know the aliases ...

IMHO the collection API should return this info if requested on a command LIST. 
Something like aliases=true

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (LUCENE-6985) Create some (simple) guides on how to use git to perform common dev tasks

2016-01-23 Thread Dawid Weiss (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Weiss updated LUCENE-6985:

Description: 
Some simple guides that demonstrate basic git principles and routine tasks 
(below). The guides are here:

https://github.com/dweiss/lucene-git-guides

Core concepts

1. how to clone and setup lucene/solr git repo for local work
2. basic git concepts: branches, remote branches, references, staging area.

Simple tasks:

1. Checkout branch X, create local branch Y, modify something, create a diff 
for Jira.
2. Checkout branch X, create local branch Y, modify something, catch-up with 
changes on X, create a diff for Jira.
3. Checkout branch X, create local branch Y, modify something, catch-up with 
changes on X, apply aggregate changes from Y on X (as a single commit).
4. Backport feature/ commit C from branch X to Y via cherry picking.

More advanced:

1. Create a feature branch off branch X, develop the feature, then apply it as 
a series of commits to X.
2. Create a feature branch off branch X, develop the feature, then apply it as 
a series of commits to X and Y (different branch).

  was:
I'll prepare some simple github repos that demonstrate how to (from command 
line, GUI users can find their buttons I'm sure) perform:

Simple tasks:

1. Checkout branch X, create local branch Y, modify something, create a diff 
for Jira.
2. Checkout branch X, create local branch Y, modify something, catch-up with 
changes on X, create a diff for Jira.
3. Checkout branch X, create local branch Y, modify something, catch-up with 
changes on X, apply aggregate changes from Y on X (as a single commit).
4. Backport feature/ commit C from branch X to Y via cherry picking.

More advanced:

1. Create a feature branch off branch X, develop the feature, then apply it as 
a series of commits to X.
2. Create a feature branch off branch X, develop the feature, then apply it as 
a series of commits to X and Y (different branch).


> Create some (simple) guides on how to use git to perform common dev tasks
> -
>
> Key: LUCENE-6985
> URL: https://issues.apache.org/jira/browse/LUCENE-6985
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
>
> Some simple guides that demonstrate basic git principles and routine tasks 
> (below). The guides are here:
> https://github.com/dweiss/lucene-git-guides
> Core concepts
> 1. how to clone and setup lucene/solr git repo for local work
> 2. basic git concepts: branches, remote branches, references, staging area.
> Simple tasks:
> 1. Checkout branch X, create local branch Y, modify something, create a diff 
> for Jira.
> 2. Checkout branch X, create local branch Y, modify something, catch-up with 
> changes on X, create a diff for Jira.
> 3. Checkout branch X, create local branch Y, modify something, catch-up with 
> changes on X, apply aggregate changes from Y on X (as a single commit).
> 4. Backport feature/ commit C from branch X to Y via cherry picking.
> More advanced:
> 1. Create a feature branch off branch X, develop the feature, then apply it 
> as a series of commits to X.
> 2. Create a feature branch off branch X, develop the feature, then apply it 
> as a series of commits to X and Y (different branch).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Yonik Seeley
Here's a useful thing you can add to your .profile , it conditionally
displays the branch you are on in your shell prompt:
https://gist.github.com/yonik/04b2e759eecf5ef96383

Example:

/opt/code$ cd lusolr
[master] /opt/code/lusolr$

-Yonik


On Sat, Jan 23, 2016 at 12:55 PM, Ramkumar R. Aiyengar
 wrote:
> Not a big deal, but guys, do check if your mail is set properly in
> ~/.gitconfig, otherwise commits would show your personal mail as the author.
> Committer still shows up as your apache mail address, but many UIs hide it
> by default, and might not be apparent to those new to the project/git..
>
> Example .gitconfig snippet allowing you to keep your existing name/mail but
> override for apache.org..
>
> [user "https://git-wip-us.apache.org;]
> name = Ramkumar Aiyengar
> mail = andyetitmo...@apache.org
>
>
> On Sat, Jan 23, 2016 at 3:41 PM, Uwe Schindler  wrote:
>>
>> Hi,
>>
>> I migrated all Policeman and ASF Jenkins Jobs to Git. Everything should be
>> set up now.
>> The Jobs for 5.3 and 5.4 were deleted.
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>> > -Original Message-
>> > From: Uwe Schindler [mailto:u...@thetaphi.de]
>> > Sent: Saturday, January 23, 2016 11:05 AM
>> > To: dev@lucene.apache.org
>> > Subject: RE: GIT migration complete
>> >
>> > Hi,
>> >
>> > Thanks! I am talking care of Jenkins at the moment.
>> >
>> > First Policeman one is working:
>> > http://jenkins.thetaphi.de/job/Lucene-Solr-
>> > trunk-Linux/15619/console
>> >
>> > The Changes I do for jenkins is:
>> > - Deleted *all* workspaces to have clean start
>> > - Change all Jobs (is a bit of work as manually, especially for ASF) to
>> > use Git
>> > checkouts of corresponding branch
>> > - Add the following "additional behaviour" config: Clean before
>> > checkout:
>> > Clean up the workspace before every checkout by deleting all untracked
>> > files
>> > and directories, including those which are specified in .gitignore. It
>> > also resets
>> > all tracked files to their versioned state. This ensures that the
>> > workspace is in
>> > the same state as if you cloned and checked out in a brand-new empty
>> > directory, and ensures that your build is not affected by the files
>> > generated
>> > by the previous build.
>> >
>> > Uwe
>> >
>> > -
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: u...@thetaphi.de
>> >
>> > > From: Dawid Weiss [mailto:dawid.we...@gmail.com]
>> > > Sent: Saturday, January 23, 2016 10:13 AM
>> > > To: dev@lucene.apache.org
>> > > Subject: GIT migration complete
>> > >
>> > > Ok, folks. Seems like code migration is complete, with both gh mirrors
>> > > and Apache repos up.
>> > >
>> > > 1. Please read the docs at: https://git-wip-us.apache.org/
>> > >
>> > > 2. I didn't realize Apache's repositories are over https, which makes
>> > > authorization rather painful for Linux users (requires password typing
>> > > on every push). I think I'll stick with gh for this reason and only
>> > > push my changes when they're fully baked.
>> > >
>> > > 3. The master branch (former trunk) passes ant precommit for me, but I
>> > > didn't apply build patches to branch_5x yet.
>> > >
>> > > If there are any problems or concerns, let me know (perhaps I'll be
>> > > able to help).
>> > >
>> > > Dawid
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> > > For additional commands, e-mail: dev-h...@lucene.apache.org
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> > For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>
>
>
> --
> Not sent from my iPhone or my Blackberry or anyone else's

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[ANNOUNCE] Apache Solr 5.4.1 released

2016-01-23 Thread Adrien Grand
23 January 2016, Apache Solr™ 5.4.1 available

The Lucene PMC is pleased to announce the release of Apache Solr 5.4.1

Solr is the popular, blazing fast, open source NoSQL search platform
from the Apache Lucene project. Its major features include powerful
full-text search, hit highlighting, faceted search, dynamic
clustering, database integration, rich document (e.g., Word, PDF)
handling, and geospatial search. Solr is highly scalable, providing
fault tolerant distributed search and indexing, and powers the search
and navigation features of many of the world's largest internet sites.

This release contains various bug fixes and optimizations since the 5.4.0
release. The release is available for immediate download at:

  http://lucene.apache.org/solr/mirrors-solr-latest-redir.html

Please read CHANGES.txt for a full list of new features and changes:

  https://lucene.apache.org/solr/5_4_1/changes/Changes.html

This release especially contains a fix for a faceting bug that could
cause facet counts to include deleted documents and a fix for a
corruption bug that was introduced in version 5.4.0. If you are on
5.4.0 and using BINARY, SORTED_NUMERIC or SORTED_SET doc values,
upgrading to 5.4.1 is strongly recommended.

See the CHANGES.txt file included with the release for a full list of
changes and further details.

Please report any feedback to the mailing lists (
http://lucene.apache.org/solr/discussion.html)

Note: The Apache Software Foundation uses an extensive mirroring network
for distributing releases. It is possible that the mirror you are using may
not have replicated the release yet. If that is the case, please try
another mirror. This also goes for Maven access.


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

2016-01-23 Thread Michael McCandless
I *pushed* a fix ;)

Mike McCandless

http://blog.mikemccandless.com


On Sat, Jan 23, 2016 at 9:27 AM, Michael McCandless
 wrote:
> I'll fix.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 6:50 AM, Policeman Jenkins Server
>  wrote:
>> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15621/
>> Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
>>
>> 1 tests failed.
>> FAILED:  org.apache.lucene.search.grouping.TestGrouping.testBasic
>>
>> Error Message:
>>
>>
>> Stack Trace:
>> java.lang.AssertionError
>> at 
>> __randomizedtesting.SeedInfo.seed([E3AE5C3FEE8E32AC:4854412A3152B482]:0)
>> at org.junit.Assert.fail(Assert.java:92)
>> at org.junit.Assert.assertTrue(Assert.java:43)
>> at org.junit.Assert.assertTrue(Assert.java:54)
>> at 
>> org.apache.lucene.search.grouping.TestGrouping.testBasic(TestGrouping.java:180)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
>> at 
>> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
>> at 
>> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
>> at 
>> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
>> at 
>> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
>> at 
>> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
>> at 
>> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
>> at 
>> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
>> at 
>> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
>> at 
>> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
>> at 
>> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>> at 
>> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
>> at 
>> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
>> at 
>> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
>> at 
>> org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
>> at 
>> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>> at 
>> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>>
>> Build Log:
>> [...truncated 6204 lines...]
>>[junit4] Suite: 

[jira] [Created] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)
Shawn Heisey created SOLR-8589:
--

 Summary: Add aliases to the LIST action results in the Collections 
API
 Key: SOLR-8589
 URL: https://issues.apache.org/jira/browse/SOLR-8589
 Project: Solr
  Issue Type: Improvement
  Components: SolrCloud
Affects Versions: 5.4.1
Reporter: Shawn Heisey
Assignee: Shawn Heisey
Priority: Minor


Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
is not available as a typical query response, I believe it is only available 
via the http API for zookeeper.

The results from the LIST action in the Collections API is well-situated to 
handle this. The current results are contained in a "collections" node, we can 
simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

2016-01-23 Thread Dawid Weiss (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113786#comment-15113786
 ] 

Dawid Weiss commented on LUCENE-6922:
-

Indeed, I overlooked this, thanks for confirming. I'll fix.

> Improve svn to git workaround script
> 
>
> Key: LUCENE-6922
> URL: https://issues.apache.org/jira/browse/LUCENE-6922
> Project: Lucene - Core
>  Issue Type: Improvement
>  Components: -tools
>Reporter: Paul Elschot
>Priority: Minor
> Attachments: LUCENE-6922.patch, svnBranchToGit.py, svnBranchToGit.py, 
> svnBranchToGit.py
>
>
> As the git-svn mirror for Lucene/Solr will be turned off near the end of 
> 2015, try and improve the workaround script to become more usable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Heisey updated SOLR-8589:
---
Attachment: SOLR-8589.patch

Patch.

Was the aliasMap implemented as a nested map with the idea that we might 
someday support some other kind of alias besides a collection alias?  Currently 
this code only gets the "collection" node from the outer map.  Is this OK?

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-6937) Migrate Lucene project from SVN to Git.

2016-01-23 Thread Dawid Weiss (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113806#comment-15113806
 ] 

Dawid Weiss commented on LUCENE-6937:
-

I overlooked one release tag/ commit during migration. Here is the fixup log 
(already pushed to the repo):

{code}
# Locate the release tag's version in SVN

$ svn log -v --stop-on-copy 
https://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_5_3_2

r1726288 | anshum | 2016-01-22 19:57:58 +0100 (Fri, 22 Jan 2016) | 1 line
Changed paths:
   A /lucene/dev/tags/lucene_solr_5_3_2 (from 
/lucene/dev/branches/lucene_solr_5_3:1725196)

Lucene/Solr release 5.3.2


$ git log --all --grep="@1726288"

# nothing, we lost this commit during pruning because it wasn't reachable by 
any ref.
# let's locate the *last* change that occurred on 
/lucene/dev/branches/lucene_solr_5_3
# prior to r1725196:

$ svn info 
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_3@1725196

Path: lucene_solr_5_3
URL: https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_3
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1725196
Node Kind: directory
Last Changed Author: yonik
Last Changed Rev: 1725012
Last Changed Date: 2016-01-16 19:07:46 +0100 (Sat, 16 Jan 2016)

# So the last change was r1725012, locate it in git:

$ git log --all --grep="@1725012"

commit d57d7b14883a4b27990ee88419ac89dbed8f34bf
Author: Yonik Seeley 
Date:   Sat Jan 16 18:07:46 2016 +

SOLR-8496: multi-select faceting and getDocSet(List) can match 
deleted docs

git-svn-id: 
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_3@1725012 
13f79535-47bb-0310-9956-ffa450edef68

# Tag this commit as the release commit (no further changes occurred on the tag 
path in SVN):

git tag releases/lucene-solr/5.3.2 d57d7b14883a4b27
git push origin releases/lucene-solr/5.3.2
{code}

> Migrate Lucene project from SVN to Git.
> ---
>
> Key: LUCENE-6937
> URL: https://issues.apache.org/jira/browse/LUCENE-6937
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
>
> See mailing list discussion: 
> http://mail-archives.apache.org/mod_mbox/lucene-dev/201512.mbox/%3CCAL8PwkbFVT83ZbCZm0y-x-MDeTH6HYC_xYEjRev9fzzk5YXYmQ%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



(LUCENE-6985) for those learning git

2016-01-23 Thread Dawid Weiss
Hey. I've tried to share some of the basic git concepts and knowledge
(the way I see it). The web is full of excellent git tutorials, but
perhaps somebody will find this useful.

https://github.com/dweiss/lucene-git-guides

I didn't finish everything LUCENE-6985 lists; I'll try to add the
remaining points during the week. Like I said previously -- the
understanding of the underlying git concepts (commit tree, reference)
helps a lot, whether you use command line or some gui tool is of
secondary nature.

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



RE: lucene-solr git commit: make this test less anal about scores so the new DFI sim won't cause false failures

2016-01-23 Thread Uwe Schindler
Hi Mike,

the GIT Howto page at apache says, that your commits should use the @apache.org 
address. If you don't want to change this globally, you can set the e-mail 
address for a working-copy only, see second one:

https://git-wip-us.apache.org/#committers-getting-started

Your current commit makes it look like you (mikemcc...@apache.org) pushed a 
commit from somebody else (m...@mikemccandless.com).

Uwe

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: mikemcc...@apache.org [mailto:mikemcc...@apache.org]
> Sent: Saturday, January 23, 2016 3:32 PM
> To: comm...@lucene.apache.org
> Subject: lucene-solr git commit: make this test less anal about scores so the
> new DFI sim won't cause false failures
> 
> Repository: lucene-solr
> Updated Branches:
>   refs/heads/master 657b3e617 -> 1199bbe1b
> 
> 
> make this test less anal about scores so the new DFI sim won't cause false
> failures
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
> Commit: http://git-wip-us.apache.org/repos/asf/lucene-
> solr/commit/1199bbe1
> Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/1199bbe1
> Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/1199bbe1
> 
> Branch: refs/heads/master
> Commit: 1199bbe1b39e73c6e78ec570eae2ae62a5ccc361
> Parents: 657b3e6
> Author: Michael McCandless 
> Authored: Sat Jan 23 09:31:39 2016 -0500
> Committer: Mike McCandless 
> Committed: Sat Jan 23 09:31:39 2016 -0500
> 
> --
>  .../src/test/org/apache/lucene/search/grouping/TestGrouping.java | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/lucene-
> solr/blob/1199bbe1/lucene/grouping/src/test/org/apache/lucene/search/gr
> ouping/TestGrouping.java
> --
> diff --git
> a/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroupi
> ng.java
> b/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroup
> ing.java
> index a8711c5..2842528 100644
> ---
> a/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroupi
> ng.java
> +++
> b/lucene/grouping/src/test/org/apache/lucene/search/grouping/TestGroup
> ing.java
> @@ -176,8 +176,8 @@ public class TestGrouping extends LuceneTestCase {
>  assertEquals(0, group.scoreDocs[0].doc);
>  assertEquals(1, group.scoreDocs[1].doc);
>  assertEquals(2, group.scoreDocs[2].doc);
> -assertTrue(group.scoreDocs[0].score > group.scoreDocs[1].score);
> -assertTrue(group.scoreDocs[1].score > group.scoreDocs[2].score);
> +assertTrue(group.scoreDocs[0].score >= group.scoreDocs[1].score);
> +assertTrue(group.scoreDocs[1].score >= group.scoreDocs[2].score);
> 
>  group = groups.groups[2];
>  compareGroupValue("author2", group);


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Michael McCandless
I'll fix.

Mike McCandless

http://blog.mikemccandless.com


On Sat, Jan 23, 2016 at 6:50 AM, Policeman Jenkins Server
 wrote:
> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15621/
> Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
>
> 1 tests failed.
> FAILED:  org.apache.lucene.search.grouping.TestGrouping.testBasic
>
> Error Message:
>
>
> Stack Trace:
> java.lang.AssertionError
> at 
> __randomizedtesting.SeedInfo.seed([E3AE5C3FEE8E32AC:4854412A3152B482]:0)
> at org.junit.Assert.fail(Assert.java:92)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertTrue(Assert.java:54)
> at 
> org.apache.lucene.search.grouping.TestGrouping.testBasic(TestGrouping.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
> at 
> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
> at 
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
> at 
> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
> at 
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
> at 
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
> at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
> at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
> at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
> at 
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
> at 
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at 
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
> at 
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
> at 
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
> at 
> org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
> at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
>
> Build Log:
> [...truncated 6204 lines...]
>[junit4] Suite: org.apache.lucene.search.grouping.TestGrouping
>[junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=TestGrouping 
> -Dtests.method=testBasic -Dtests.seed=E3AE5C3FEE8E32AC -Dtests.multiplier=3 
> -Dtests.slow=true -Dtests.locale=es-CU -Dtests.timezone=America/Rio_Branco 
> 

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

2016-01-23 Thread Adrien Grand
Woohoo!

Le sam. 23 janv. 2016 15:35, Michael McCandless 
a écrit :

> I *pushed* a fix ;)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 9:27 AM, Michael McCandless
>  wrote:
> > I'll fix.
> >
> > Mike McCandless
> >
> > http://blog.mikemccandless.com
> >
> >
> > On Sat, Jan 23, 2016 at 6:50 AM, Policeman Jenkins Server
> >  wrote:
> >> Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15621/
> >> Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC
> >>
> >> 1 tests failed.
> >> FAILED:  org.apache.lucene.search.grouping.TestGrouping.testBasic
> >>
> >> Error Message:
> >>
> >>
> >> Stack Trace:
> >> java.lang.AssertionError
> >> at
> __randomizedtesting.SeedInfo.seed([E3AE5C3FEE8E32AC:4854412A3152B482]:0)
> >> at org.junit.Assert.fail(Assert.java:92)
> >> at org.junit.Assert.assertTrue(Assert.java:43)
> >> at org.junit.Assert.assertTrue(Assert.java:54)
> >> at
> org.apache.lucene.search.grouping.TestGrouping.testBasic(TestGrouping.java:180)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:497)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
> >> at
> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
> >> at
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
> >> at
> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
> >> at
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
> >> at
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
> >> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
> >> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
> >> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
> >> at
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
> >> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> >> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
> >> at
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
> >> at
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
> >> at
> org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
> >> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> >> at
> 

RE: GIT migration complete

2016-01-23 Thread Uwe Schindler
Hi,

I migrated all Policeman and ASF Jenkins Jobs to Git. Everything should be set 
up now.
The Jobs for 5.3 and 5.4 were deleted.

Uwe

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Saturday, January 23, 2016 11:05 AM
> To: dev@lucene.apache.org
> Subject: RE: GIT migration complete
> 
> Hi,
> 
> Thanks! I am talking care of Jenkins at the moment.
> 
> First Policeman one is working: http://jenkins.thetaphi.de/job/Lucene-Solr-
> trunk-Linux/15619/console
> 
> The Changes I do for jenkins is:
> - Deleted *all* workspaces to have clean start
> - Change all Jobs (is a bit of work as manually, especially for ASF) to use 
> Git
> checkouts of corresponding branch
> - Add the following "additional behaviour" config: Clean before checkout:
> Clean up the workspace before every checkout by deleting all untracked files
> and directories, including those which are specified in .gitignore. It also 
> resets
> all tracked files to their versioned state. This ensures that the workspace 
> is in
> the same state as if you cloned and checked out in a brand-new empty
> directory, and ensures that your build is not affected by the files generated
> by the previous build.
> 
> Uwe
> 
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
> 
> > From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> > Sent: Saturday, January 23, 2016 10:13 AM
> > To: dev@lucene.apache.org
> > Subject: GIT migration complete
> >
> > Ok, folks. Seems like code migration is complete, with both gh mirrors
> > and Apache repos up.
> >
> > 1. Please read the docs at: https://git-wip-us.apache.org/
> >
> > 2. I didn't realize Apache's repositories are over https, which makes
> > authorization rather painful for Linux users (requires password typing
> > on every push). I think I'll stick with gh for this reason and only
> > push my changes when they're fully baked.
> >
> > 3. The master branch (former trunk) passes ant precommit for me, but I
> > didn't apply build patches to branch_5x yet.
> >
> > If there are any problems or concerns, let me know (perhaps I'll be
> > able to help).
> >
> > Dawid
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shalin Shekhar Mangar (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113805#comment-15113805
 ] 

Shalin Shekhar Mangar commented on SOLR-8589:
-

Aliases are returned by the clusterstatus API

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113866#comment-15113866
 ] 

Shawn Heisey commented on SOLR-8589:


I built the branch_5x server with my patch.  Then I started the cloud example, 
added some collections and some aliases.  WIth the CLUSTERSTATUS action, the 
information about which aliases are present and what collections are used is 
scattered all over the output.

I will attach a screenshot showing what you get with my patch on the LIST 
action.  The change will not affect most programs that consume the LIST output, 
unless they are coded poorly.


> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Ramkumar R. Aiyengar
Not a big deal, but guys, do check if your mail is set properly in
~/.gitconfig, otherwise commits would show your personal mail as the
author. Committer still shows up as your apache mail address, but many UIs
hide it by default, and might not be apparent to those new to the
project/git..

Example .gitconfig snippet allowing you to keep your existing name/mail but
override for apache.org..

[user "https://git-wip-us.apache.org;]
name = Ramkumar Aiyengar
mail = andyetitmo...@apache.org


On Sat, Jan 23, 2016 at 3:41 PM, Uwe Schindler  wrote:

> Hi,
>
> I migrated all Policeman and ASF Jenkins Jobs to Git. Everything should be
> set up now.
> The Jobs for 5.3 and 5.4 were deleted.
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Uwe Schindler [mailto:u...@thetaphi.de]
> > Sent: Saturday, January 23, 2016 11:05 AM
> > To: dev@lucene.apache.org
> > Subject: RE: GIT migration complete
> >
> > Hi,
> >
> > Thanks! I am talking care of Jenkins at the moment.
> >
> > First Policeman one is working:
> http://jenkins.thetaphi.de/job/Lucene-Solr-
> > trunk-Linux/15619/console
> >
> > The Changes I do for jenkins is:
> > - Deleted *all* workspaces to have clean start
> > - Change all Jobs (is a bit of work as manually, especially for ASF) to
> use Git
> > checkouts of corresponding branch
> > - Add the following "additional behaviour" config: Clean before checkout:
> > Clean up the workspace before every checkout by deleting all untracked
> files
> > and directories, including those which are specified in .gitignore. It
> also resets
> > all tracked files to their versioned state. This ensures that the
> workspace is in
> > the same state as if you cloned and checked out in a brand-new empty
> > directory, and ensures that your build is not affected by the files
> generated
> > by the previous build.
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
> > > From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> > > Sent: Saturday, January 23, 2016 10:13 AM
> > > To: dev@lucene.apache.org
> > > Subject: GIT migration complete
> > >
> > > Ok, folks. Seems like code migration is complete, with both gh mirrors
> > > and Apache repos up.
> > >
> > > 1. Please read the docs at: https://git-wip-us.apache.org/
> > >
> > > 2. I didn't realize Apache's repositories are over https, which makes
> > > authorization rather painful for Linux users (requires password typing
> > > on every push). I think I'll stick with gh for this reason and only
> > > push my changes when they're fully baked.
> > >
> > > 3. The master branch (former trunk) passes ant precommit for me, but I
> > > didn't apply build patches to branch_5x yet.
> > >
> > > If there are any problems or concerns, let me know (perhaps I'll be
> > > able to help).
> > >
> > > Dawid
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


-- 
Not sent from my iPhone or my Blackberry or anyone else's


[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_66) - Build # 15627 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15627/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseSerialGC

1 tests failed.
FAILED:  org.apache.lucene.search.TestLatLonPointQueries.testRandomMedium

Error Message:
Captured an uncaught exception in thread: Thread[id=66, name=T1, 
state=RUNNABLE, group=TGRP-TestLatLonPointQueries]

Stack Trace:
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=66, name=T1, state=RUNNABLE, 
group=TGRP-TestLatLonPointQueries]
Caused by: java.lang.AssertionError: some hits were wrong
at __randomizedtesting.SeedInfo.seed([31974FDE0D2B59DF]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)




Build Log:
[...truncated 7527 lines...]
   [junit4] Suite: org.apache.lucene.search.TestLatLonPointQueries
   [junit4] IGNOR/A 0.01s J0 | TestLatLonPointQueries.testRandomBig
   [junit4]> Assumption #1: 'nightly' test group is disabled (@Nightly())
   [junit4]   1> T1: id=10013 should match but did not
   [junit4]   1>   small=true query=PointInRectQuery:field=point: Lower Left: 
[-141.43780203780085,70.86664532168423] Upper Right: 
[-141.40930016546494,71.5516812238477] docID=9918
   [junit4]   1>   lat=71.4017852898268 lon=-141.40930016162181
   [junit4]   1>   deleted?=false
   [junit4]   2> Led 24, 2016 4:55:03 DOP. 
com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler
 uncaughtException
   [junit4]   2> WARNING: Uncaught exception in thread: 
Thread[T1,5,TGRP-TestLatLonPointQueries]
   [junit4]   2> java.lang.AssertionError: some hits were wrong
   [junit4]   2>at 
__randomizedtesting.SeedInfo.seed([31974FDE0D2B59DF]:0)
   [junit4]   2>at org.junit.Assert.fail(Assert.java:93)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
   [junit4]   2>at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)
   [junit4]   2> 
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=TestLatLonPointQueries -Dtests.method=testRandomMedium 
-Dtests.seed=31974FDE0D2B59DF -Dtests.multiplier=3 -Dtests.slow=true 
-Dtests.locale=cs-CZ -Dtests.timezone=Australia/Tasmania -Dtests.asserts=true 
-Dtests.file.encoding=US-ASCII
   [junit4] ERROR   1.37s J0 | TestLatLonPointQueries.testRandomMedium <<<
   [junit4]> Throwable #1: java.lang.AssertionError
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.verify(BaseGeoPointTestCase.java:770)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.doTestRandom(BaseGeoPointTestCase.java:411)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase.testRandomMedium(BaseGeoPointTestCase.java:335)
   [junit4]>at java.lang.Thread.run(Thread.java:745)Throwable #2: 
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught 
exception in thread: Thread[id=66, name=T1, state=RUNNABLE, 
group=TGRP-TestLatLonPointQueries]
   [junit4]> Caused by: java.lang.AssertionError: some hits were wrong
   [junit4]>at 
__randomizedtesting.SeedInfo.seed([31974FDE0D2B59DF]:0)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$VerifyHits.test(BaseGeoPointTestCase.java:552)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$2._run(BaseGeoPointTestCase.java:756)
   [junit4]>at 
org.apache.lucene.util.BaseGeoPointTestCase$2.run(BaseGeoPointTestCase.java:623)
   [junit4]   2> NOTE: test params are: codec=Asserting(Lucene60): 
{id=PostingsFormat(name=LuceneVarGapDocFreqInterval)}, 
docValues:{id=DocValuesFormat(name=Direct)}, 
sim=RandomSimilarity(queryNorm=false,coord=crazy): {}, locale=cs-CZ, 
timezone=Australia/Tasmania
   [junit4]   2> NOTE: Linux 3.19.0-47-generic i386/Oracle Corporation 1.8.0_66 
(32-bit)/cpus=12,threads=1,free=37802256,total=64946176
   [junit4]   2> NOTE: All tests run in this JVM: [TestIDVersionPostingsFormat, 
TestLatLonPointQueries]
   [junit4] Completed [4/13 (1!)] on J0 in 14.00s, 8 tests, 1 error, 1 skipped 
<<< FAILURES!

[...truncated 48 lines...]
BUILD FAILED
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:675: The following 
error occurred while executing this line:
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:619: The following 
error occurred while executing this line:
/home/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:57: The following 
error occurred while executing this line:

[ANNOUNCE] Apache Lucene 5.4.1 released

2016-01-23 Thread Adrien Grand
23 January 2016, Apache Lucene™ 5.4.1 available

The Lucene PMC is pleased to announce the release of Apache Lucene 5.4.1

Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for nearly
any application that requires full-text search, especially cross-platform.

This release contains an important fix for a corruption bug that was
introduced in version 5.4.0. If you are on 5.4.0 and using BINARY,
SORTED_NUMERIC or SORTED_SET doc values, upgrading to 5.4.1 is strongly
recommended. The release is available for immediate download at:

  http://lucene.apache.org/core/mirrors-core-latest-redir.html

Please read CHANGES.txt for a full list of new features and changes:

  https://lucene.apache.org/core/5_4_1/changes/Changes.html

Please report any feedback to the mailing lists
(http://lucene.apache.org/core/discussion.html)

Note: The Apache Software Foundation uses an extensive mirroring network
for distributing releases.  It is possible that the mirror you are using
may not have replicated the release yet.  If that is the case, please
try another mirror.  This also goes for Maven access.


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

2016-01-23 Thread Steve Rowe
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 McCandless
>> 
>> http://blog.mikemccandless.com
>> 
>> 
>> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
>>  wrote:
>>> Got it, thanks! I'll try your suggestion, Dawid.
>>> 
>>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
 If you're using github then yes, you will need to fork again and
 rebase any changes you may have. This can be done by having two
 origins locally (two "sources" of commits) -- one from the old clone,
 the second one from the new clone. Then you can rebase the branches or
 commits you wish and push them to the new clone.
 
 Dawid
 
 
 On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>> Thanks Dawid and Daniel for all the work!
>> 
>> One strange thing that I noticed is that my fork of apache/lucene-solr
>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>> that guy is. What can we do to fix this?
> 
> Nothing. This is GitHub's fallback method when the original repository
> goes away as it did here (replaced with a new repo with a new history).
> Since referring to the old repo which doesn't exist anymore would break
> your copy, they have fallen back to another copy of it.
> 
> Please re-fork.
> 
> With regards,
> Daniel.
> 
>> 
>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  
>> wrote:
>>> 1. The content of the lucene-solr.git repository looks good!
>>> 
>>> 2) PROBLEM. I can't push my own branch:
>>> 
>>> $ git co master -b git-check
>>> $ [... committed a dummy commit ]
>>> $ git push origin HEAD -u
>>> fatal: remote error: access denied or repository not exported: 
>>> /lucene-solr.git
>>> 
>>> 3) Solr repo is still available for some reason, both as real git repo 
>>> here:
>>> 
>>> git://git.apache.org/solr.git
>>> 
>>> and listed here:
>>> 
>>> https://git.apache.org/
>>> 
>>> Could I be seeing a mirror or something?
>>> 
>>> Dawid
>>> 
>>> 
>>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
>>> wrote:
 Checking everything now -- that was fast Daniel!
 Dawid
 
 
 On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
 wrote:
> Just a heads up: Everything is working now and GitHub has caught up 
> with
> the new repository. You should be good to go :)
> 
> With regards,
> Daniel.
> 
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>> 
>>> I've prepared everything for the migration and I hand it off to you 
>>> (I
>>> will be available in the morning, if you need assistance). I can 
>>> also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>> 
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>> 
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains 
>>> full
>>> history):
>>> 
>>> git://git.apache.org/solr.git
>> DONE
>> 
>>> git://git.apache.org/lucene.git
>> DONE
>>> 
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>> 
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>> 
>>> 
>>> 3) DISABLE svn syncing for the following git mirror:
>>> 
>>> git://git.apache.org/lucene-solr.git
>> DONE
>> 
>>> 
>>> and then REPLACE it (wipe it clean) with the content of the 
>>> following
>>> consolidated repository:
>>> 
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>> 
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>> 
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git

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

2016-01-23 Thread Uwe Schindler
Hi,

 

Github is just a mirror, as before. We don’t do our development on Github, but 
people can do it there in forks of Githubs mirror. New code changes must always 
be pushed by committers to the git-wip-us.apache.org server with their 
apache.org user name.

 

The official read-only GIT URL is: git://git.apache.org/lucene-solr.git

The Jenkins servers are configured to use this URL.

 

Uwe

 

-

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

  http://www.thetaphi.de

eMail: u...@thetaphi.de

 

From: Jack Krupansky [mailto:jack.krupan...@gmail.com] 
Sent: Saturday, January 23, 2016 10:38 PM
To: Lucene-dev 
Subject: Re: Apache Lucene/Solr GIT migration, requesting infra help

 

The tiniest of nits: Could somebody update the Lucene and Solr web pages for 
the location of source code:

https://lucene.apache.org/core/developer.html

http://lucene.apache.org/solr/resources.html

 

Just to confirm, this really is the primary copy of the Lucene/Solr source code 
now, right?

https://github.com/apache/lucene-solr

 

Well, technically that seems to still be a mirror of whatever the actually repo 
really is... is this the absolute primary copy, here?

https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git

 

I'm just wondering exactly which URL should be used to view the (definitive) 
current source, especially since I know in the past there were issues with the 
github mirror being behind svn. But is this new "mirror" truly only a mirror or 
is it now the real repo? I do see that if I click on the links in the git 
commit notifications they have some funky old format, not the more modern 
github formatting.

 

As an example, if I want to view the definitive source for the tagged release 
for 5.4.1, is the official repo here:

https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1

or

https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0

(That's the page I get if I click on the releases/lucene-solr/5.4.1 link on the 
ASF Cananonical Repository icon for Lucene-Solr.)

 

And finally, is the old commit notifications mailing list relevant anymore, or 
should people be encouraged to enable watching of the github repository? I 
noticed that (of course) I am not currently watching the new github repo 
(mirror), but am getting notifications - is there some magic involved or are 
github commit notifications automatically sent to the dev list? (ahh... I do 
see that the sender of the github commit info actually is still 
comm...@lucene.apache.org  , so clearly the 
commit notification list is being used.) Is that intentional for the long run 
or just an expedient for the transition until people get familiar with github?

 

I am reasonably familiar with github, but git behind the Apache firewall is 
still somewhat a mystery. A few more clues about what is really going on would 
be helpful. Or at least stuff average contributors might care about, not the 
hard-core Infra stuff.

 

Thanks.




-- Jack Krupansky

 

On Sat, 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 McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
>  > wrote:
>> Got it, thanks! I'll try your suggestion, Dawid.
>>
>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss >  > wrote:
>>> If you're using github then yes, you will need to fork again and
>>> rebase any changes you may have. This can be done by having two
>>> origins locally (two "sources" of commits) -- one from the old clone,
>>> the second one from the new clone. Then you can rebase the branches or
>>> commits you wish and push them to the new clone.
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno >>  > wrote:
 On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
>
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

 Nothing. This is GitHub's fallback method when the original repository
 goes away as it did here (replaced with a new repo with a new history).
 Since referring to the old repo which doesn't exist anymore would break
 your copy, they have fallen back to another copy of it.


intellij git history

2016-01-23 Thread Yonik Seeley
Everything looks fine from the command line, but Intellij  IDEA 14
doesn't seem to be able to see the history:

If I right click on a file and do "GIT->Show History" I only see a single entry:

* 2c97a68 2016-01-23 | Revert "LUCENE-6937: moving trunk from SVN to
GIT." Welcome to GIT world. [Dawid Weiss]

Anyone else see this?

-Yonik

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Jack Krupansky
The tiniest of nits: Could somebody update the Lucene and Solr web pages
for the location of source code:
https://lucene.apache.org/core/developer.html
http://lucene.apache.org/solr/resources.html

Just to confirm, this really is the primary copy of the Lucene/Solr source
code now, right?
https://github.com/apache/lucene-solr

Well, technically that seems to still be a mirror of whatever the actually
repo really is... is this the absolute primary copy, here?
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git

I'm just wondering exactly which URL should be used to view the
(definitive) current source, especially since I know in the past there were
issues with the github mirror being behind svn. But is this new "mirror"
truly only a mirror or is it now the real repo? I do see that if I click on
the links in the git commit notifications they have some funky old format,
not the more modern github formatting.

As an example, if I want to view the definitive source for the tagged
release for 5.4.1, is the official repo here:
https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
or
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0
(That's the page I get if I click on the releases/lucene-solr/5.4.1 link on
the ASF Cananonical Repository icon for Lucene-Solr.)

And finally, is the old commit notifications mailing list relevant anymore,
or should people be encouraged to enable watching of the github repository?
I noticed that (of course) I am not currently watching the new github repo
(mirror), but am getting notifications - is there some magic involved or
are github commit notifications automatically sent to the dev list? (ahh...
I do see that the sender of the github commit info actually is still
comm...@lucene.apache.org, so clearly the commit notification list is being
used.) Is that intentional for the long run or just an expedient for the
transition until people get familiar with github?

I am reasonably familiar with github, but git behind the Apache firewall is
still somewhat a mystery. A few more clues about what is really going on
would be helpful. Or at least stuff average contributors might care about,
not the hard-core Infra stuff.

Thanks.

-- Jack Krupansky

On Sat, 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 McCandless
> >
> > http://blog.mikemccandless.com
> >
> >
> > On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
> >  wrote:
> >> Got it, thanks! I'll try your suggestion, Dawid.
> >>
> >> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss 
> wrote:
> >>> If you're using github then yes, you will need to fork again and
> >>> rebase any changes you may have. This can be done by having two
> >>> origins locally (two "sources" of commits) -- one from the old clone,
> >>> the second one from the new clone. Then you can rebase the branches or
> >>> commits you wish and push them to the new clone.
> >>>
> >>> Dawid
> >>>
> >>>
> >>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno 
> wrote:
>  On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> > Thanks Dawid and Daniel for all the work!
> >
> > One strange thing that I noticed is that my fork of
> apache/lucene-solr
> > at https://github.com/shalinmangar/lucene-solr is now shown to be a
> > fork of https://github.com/mdodsworth/lucene-solr. I have no idea
> who
> > that guy is. What can we do to fix this?
> 
>  Nothing. This is GitHub's fallback method when the original repository
>  goes away as it did here (replaced with a new repo with a new
> history).
>  Since referring to the old repo which doesn't exist anymore would
> break
>  your copy, they have fallen back to another copy of it.
> 
>  Please re-fork.
> 
>  With regards,
>  Daniel.
> 
> >
> > On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss 
> wrote:
> >> 1. The content of the lucene-solr.git repository looks good!
> >>
> >> 2) PROBLEM. I can't push my own branch:
> >>
> >> $ git co master -b git-check
> >> $ [... committed a dummy commit ]
> >> $ git push origin HEAD -u
> >> fatal: remote error: access denied or repository not exported:
> /lucene-solr.git
> >>
> >> 3) Solr repo is still available for some reason, both as real git
> repo here:
> >>
> >> git://git.apache.org/solr.git
> >>
> >> and listed here:
> >>
> >> https://git.apache.org/
> >>
> >> Could I be seeing a mirror or something?
> >>
> >> Dawid
> >>
> >>
> >> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss 
> wrote:
> >>> 

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

2016-01-23 Thread Dawid Weiss
> It is a bit stupid that the last commit in SVN was just reverted and not made 
> completely hidden. I would have synced up the converted repo only up to the 
> revision before the final *delete all* commit instead of reverting it.

I did this intentionally. This way SVN history and git history don't
have any gaps -- they're a seamless transition from one to the other.

The two commits... well, yes - true, they could be avoided. The
repository can stay as it is, no need to rewrite anything. You could
just change the position of references (branch_5x and master) and
branch them off before the wipeout commit, then force-push them. At
this point this would mean people's local master/branch_5x branches
would be diverged from history, so they'd have to update.

I don't think it's worth the hassle, to be honest.

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Releasing 5.3.2

2016-01-23 Thread Anshum Gupta
Hi,

I am about to work on the website changes and add news etc. for the 5.3.2
release but that would also mean that the default download link changes to
5.3.2 from 5.4.1. I'm not sure if that's a good idea.

We haven't really run into this issue before so I'm thinking about not
changing that link as part of the release process in such cases. What do
you guys think?

-- 
Anshum Gupta


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

2016-01-23 Thread Anshum Gupta
Thanks Dawid and Daniel for all the effort!

On Sat, Jan 23, 2016 at 2:40 PM, Dawid Weiss  wrote:

> > is the official repo here:
> > https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
> > or
> >
> https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0
>
> With git it does not technically matter which the "official" repo is
> -- all the commits should have identical hashes. You could fetch
> commits from one source and then change the source to another, they'd
> still be the same commits. So if you're looking at a particular commit
> hash (or tag) it will be identical in ALL mirrors.
>
> The write-access repository is this:
> https://git-wip-us.apache.org/repos/asf/lucene-solr.git
>
> The read-only view is:
> git://git.apache.org/lucene-solr.git
>
> The same applies to github's mirror (which may be a few commits
> behind, but will still contain identical commits, hashes, etc.)
>
> Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


-- 
Anshum Gupta


[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+95) - Build # 15631 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15631/
Java: 64bit/jdk-9-ea+95 -XX:+UseCompressedOops -XX:+UseParallelGC 
-XX:-CompactStrings

1 tests failed.
FAILED:  
org.apache.lucene.index.TestMixedDocValuesUpdates.testManyReopensAndFields

Error Message:
this IndexWriter is closed

Stack Trace:
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:714)
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:728)
at 
org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1459)
at 
org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1242)
at 
org.apache.lucene.index.TestMixedDocValuesUpdates.testManyReopensAndFields(TestMixedDocValuesUpdates.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:747)
Caused by: java.io.EOFException: read past EOF: pos=3135 vs length=3135: 
RAMInputStream(name=_2r_3_Direct_0.dvdd)
at 
org.apache.lucene.store.RAMInputStream.nextBuffer(RAMInputStream.java:116)
at 
org.apache.lucene.store.RAMInputStream.readBytes(RAMInputStream.java:77)
at 
org.apache.lucene.store.MockIndexInputWrapper.readBytes(MockIndexInputWrapper.java:138)
at 

[ANNOUNCE] Apache Solr 5.3.2 released

2016-01-23 Thread Anshum Gupta
23 January 2016, Apache Solr™ 5.3.2 available

The Lucene PMC is pleased to announce the release of Apache Solr 5.3.2

Solr is the popular, blazing fast, open source NoSQL search platform
from the Apache Lucene project. Its major features include powerful
full-text search, hit highlighting, faceted search, dynamic
clustering, database integration, rich document (e.g., Word, PDF)
handling, and geospatial search. Solr is highly scalable, providing
fault tolerant distributed search and indexing, and powers the search
and navigation features of many of the world's largest internet sites.

This release contains various bug fixes and optimizations since the 5.3.1
release. The release is available for immediate download at:

  http://www.apache.org/dyn/closer.lua/lucene/solr/5.3.2

Please read CHANGES.txt for a full list of new features and changes:

  https://lucene.apache.org/solr/5_3_2/changes/Changes.html

Solr 5.3.2 includes 11 bug fixes and added support for configuring TTL
PKIAuthenticationPlugin's tokens.

See the CHANGES.txt file included with the release for a full list of
changes and further details.

Please report any feedback to the mailing lists (
http://lucene.apache.org/solr/discussion.html)

Note: The Apache Software Foundation uses an extensive mirroring network
for distributing releases. It is possible that the mirror you are using may
not have replicated the release yet. If that is the case, please try
another mirror. This also goes for Maven access.

-- 
Anshum Gupta


[ANNOUNCE] Apache Lucene 5.3.2 released

2016-01-23 Thread Anshum Gupta
23 January 2016, Apache Lucene™ 5.3.2 available

The Lucene PMC is pleased to announce the release of Apache Lucene 5.3.2

Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for nearly
any application that requires full-text search, especially cross-platform.

This release contains one bug fix since the 5.3.1 release. The release
is available for immediate download at:

  http://www.apache.org/dyn/closer.lua/lucene/java/5.3.2

Please read CHANGES.txt for a full list of new features and changes:

  https://lucene.apache.org/core/5_3_2/changes/Changes.html

Please report any feedback to the mailing lists
(http://lucene.apache.org/core/discussion.html)

Note: The Apache Software Foundation uses an extensive mirroring network
for distributing releases.  It is possible that the mirror you are using
may not have replicated the release yet.  If that is the case, please
try another mirror.  This also goes for Maven access.

-- 
Anshum Gupta


Re: GIT migration date (SVN freeze)

2016-01-23 Thread Mark Miller
That's just you ignoring what I've written.

- Mark
On Wed, Jan 20, 2016 at 12:21 PM Robert Muir  wrote:

> But this is your personal opinion.
>
> Feel free to do what you like, but don't try to dictate how other
> folks use their computers.
> This religious nature of git users is extremely frustrating.
>
> There is really nothing wrong with using merge, personally that is
> what I will be using. it is easy to understand.
>
> On Tue, Jan 19, 2016 at 5:48 PM, Mark Miller 
> wrote:
> > bq. Especially having a rule that everyone *must* rebase doesn't seem
> right.
> >
> > We don't really have many rules, just agreed upon guidelines. There is no
> > "rule" that you have to commit LUCENE-XXX: message, but we do it because
> it
> > would be a mess if everyone used their own format. That doesn't mean when
> > someone commits "this little test fix" someone says, wtf, you broke the
> > 'rule'. Don't get too caught up in the language, you have to take it in
> the
> > spirit of how the project operates.
> >
> > Merge commits either offer no information or add all the patch
> information
> > to the history tree. It really just muddles things up for everyone.
> >
> > No one seems to have any actual arguments for merge?
> >
> > bq.  Rebasing just makes development more complicated
> >
> > Do you have any statements to back that up? I find rebasing extremely
> > simple.
> >
> > Git is simple when used simply. It's a nightmare when used fully.
> >
> > - Mark
> >
> > On Tue, Jan 19, 2016 at 5:25 PM Ryan Ernst  wrote:
> >>
> >> I agree merges are better to use than rebasing. Rebasing just makes
> >> development more complicated, and if you want to squash, you can always
> do
> >> so with merge --squash (as Dawid pointed out on this thread). Especially
> >> having a rule that everyone *must* rebase doesn't seem right.
> >>
> >> On Tue, Jan 19, 2016 at 2:09 PM, Robert Muir  wrote:
> >>>
> >>> yeah, rebasing is garbage. That is what merge is for.
> >>>
> >>> If apache adds a merge button like github, even better.
> >>>
> >>> On Tue, Jan 19, 2016 at 4:11 PM, Gus Heck  wrote:
> >>> > I'm not very fond of rebasing every commit. I don't like the
> >>> > destruction of
> >>> > merge history, but I'm not a committer here
> >>> >
> >>> > The following link may help any folks not familiar with git and
> >>> > rebasing
> >>> > from getting themselves (and possibly the project) into a snafu:
> >>> >
> >>> >
> >>> >
> https://www.atlassian.com/git/tutorials/merging-vs-rebasing/the-golden-rule-of-rebasing
> >>> >
> >>> > On Tue, Jan 19, 2016 at 2:55 PM, Ramkumar R. Aiyengar
> >>> >  wrote:
> >>> >>
> >>> >> +1. There might be ways to enforce it on the remote side..
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> http://stackoverflow.com/questions/2039773/have-remote-git-repository-refuse-merge-commits-on-push
> >>> >>
> >>> >> But I am not a git expert enough to tell you exactly what the
> solution
> >>> >> there is trying to do..
> >>> >>
> >>> >> On 19 Jan 2016 19:00, "Mark Miller"  wrote:
> >>> >>>
> >>> >>> I think for everyone's sanity we want to mostly ban merge commits
> and
> >>> >>> insist people use rebase and a linear history. I think we want to
> >>> >>> keep the
> >>> >>> history nice and clean just like it is now.
> >>> >>>
> >>> >>> You can change the pull command so that it does rebase rather than
> >>> >>> merge
> >>> >>> via git config --global pull.rebase true
> >>> >>>
> >>> >>> Even if everyone does not agree with that, we need some discussion
> >>> >>> and
> >>> >>> guidelines. Everyone going crazy in Git with merge commits makes an
> >>> >>> ungodly
> >>> >>> mess.
> >>> >>>
> >>> >>> - Mark
> >>> >>>
> >>> >>> On Tue, Jan 19, 2016 at 1:49 PM Dawid Weiss  >
> >>> >>> wrote:
> >>> 
> >>>  > So I'm clear, this also means that from Saturday morning (call
> it
> >>>  > 6:00
> >>>  > UTC)
> >>>  > until you give the OK (assuming the original schedule) I
> shouldn't
> >>>  > count
> >>>  > on having access to any of the source code, right?
> >>> 
> >>>  You will have access to the source code -- the SVN remains
> >>>  functional,
> >>>  but it'll be an empty folder on the branches I mentioned.
> >>> 
> >>>  > And when you do give the OK, I should plan on rebasing whatever
> >>>  > I'm
> >>>  > working on to the new Git repo. There, did I use at least one
> Git
> >>>  > term
> >>>  > correctly?
> >>> 
> >>>  Well, the workflow is up to you. One possible way to work is like
> >>>  this
> >>>  (I assume command line, because that's what I use).
> >>> 
> >>>  1) git clone 
> >>>  cd lucene_solr
> >>> 
> >>>  2) git checkout master -b mybranch
> >>> 
> >>>  3) while (not done) {
> >>>    // work on mybranch's files.
> >>>    git add -A . 

Re: intellij git history

2016-01-23 Thread Mark Miller
Just a guess, but perhaps the follow option will help?
On Sat, Jan 23, 2016 at 9:56 PM Yonik Seeley  wrote:

> Everything looks fine from the command line, but Intellij  IDEA 14
> doesn't seem to be able to see the history:
>
> If I right click on a file and do "GIT->Show History" I only see a single
> entry:
>
> * 2c97a68 2016-01-23 | Revert "LUCENE-6937: moving trunk from SVN to
> GIT." Welcome to GIT world. [Dawid Weiss]
>
> Anyone else see this?
>
> -Yonik
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
> --
- Mark
about.me/markrmiller


[JENKINS] Lucene-Solr-5.x-Solaris (multiarch/jdk1.7.0) - Build # 344 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/344/
Java: multiarch/jdk1.7.0 -d32 -server -XX:+UseG1GC

1 tests failed.
FAILED:  org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test

Error Message:
Server refused connection at: 
http://127.0.0.1:51386/lt/c8n_1x3_commits_shard1_replica3

Stack Trace:
org.apache.solr.client.solrj.SolrServerException: Server refused connection at: 
http://127.0.0.1:51386/lt/c8n_1x3_commits_shard1_replica3
at 
__randomizedtesting.SeedInfo.seed([E3C2EEC15F8F73FD:6B96D11BF1731E05]:0)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:582)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:240)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:229)
at 
org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:150)
at org.apache.solr.client.solrj.SolrClient.commit(SolrClient.java:483)
at org.apache.solr.client.solrj.SolrClient.commit(SolrClient.java:464)
at 
org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.sendCommitWithRetry(LeaderInitiatedRecoveryOnCommitTest.java:169)
at 
org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.oneShardTest(LeaderInitiatedRecoveryOnCommitTest.java:129)
at 
org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test(LeaderInitiatedRecoveryOnCommitTest.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
org.apache.solr.BaseDistributedSearchTestCase$ShardsRepeatRule$ShardsFixedStatement.callStatement(BaseDistributedSearchTestCase.java:965)
at 
org.apache.solr.BaseDistributedSearchTestCase$ShardsRepeatRule$ShardsStatement.evaluate(BaseDistributedSearchTestCase.java:940)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 

[jira] [Commented] (SOLR-8587) Add segments file information to core admin status

2016-01-23 Thread Anshum Gupta (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113961#comment-15113961
 ] 

Anshum Gupta commented on SOLR-8587:


+1
I think this makes sense, specially until we have backup/restore for SolrCloud 
in place.

> Add segments file information to core admin status
> --
>
> Key: SOLR-8587
> URL: https://issues.apache.org/jira/browse/SOLR-8587
> Project: Solr
>  Issue Type: Improvement
>Reporter: Shai Erera
>Assignee: Shai Erera
> Attachments: SOLR-8587.patch, SOLR-8587.patch
>
>
> Having the index's segments file name returned by CoreAdminHandler STATUS can 
> be useful. The info I'm thinking about is the segments file name and its 
> size. If you record that from time to time, in a case of crisis, when u need 
> to restore the index and may not be sure which copy you need to restore, this 
> tiny piece of info can be very useful, as the segmentsN file records the 
> commit point, and therefore what you core reported and what you see at hand 
> can help you make a safer decision.
> I also think it's useful info in general, e.g. probably even more than 
> 'version', and it doesn't add much complexity to the handler or the response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2016-01-23 Thread Erick Erickson
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 McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
>  wrote:
>> Got it, thanks! I'll try your suggestion, Dawid.
>>
>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
>>> If you're using github then yes, you will need to fork again and
>>> rebase any changes you may have. This can be done by having two
>>> origins locally (two "sources" of commits) -- one from the old clone,
>>> the second one from the new clone. Then you can rebase the branches or
>>> commits you wish and push them to the new clone.
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
 On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
>
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

 Nothing. This is GitHub's fallback method when the original repository
 goes away as it did here (replaced with a new repo with a new history).
 Since referring to the old repo which doesn't exist anymore would break
 your copy, they have fallen back to another copy of it.

 Please re-fork.

 With regards,
 Daniel.

>
> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  
> wrote:
>> 1. The content of the lucene-solr.git repository looks good!
>>
>> 2) PROBLEM. I can't push my own branch:
>>
>> $ git co master -b git-check
>> $ [... committed a dummy commit ]
>> $ git push origin HEAD -u
>> fatal: remote error: access denied or repository not exported: 
>> /lucene-solr.git
>>
>> 3) Solr repo is still available for some reason, both as real git repo 
>> here:
>>
>> git://git.apache.org/solr.git
>>
>> and listed here:
>>
>> https://git.apache.org/
>>
>> Could I be seeing a mirror or something?
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
>> wrote:
>>> Checking everything now -- that was fast Daniel!
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
>>> wrote:
 Just a heads up: Everything is working now and GitHub has caught up 
 with
 the new repository. You should be good to go :)

 With regards,
 Daniel.

 On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you 
>> (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
>
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
>
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
>
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo 

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

2016-01-23 Thread Dawid Weiss
> is the official repo here:
> https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
> or
> https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0

With git it does not technically matter which the "official" repo is
-- all the commits should have identical hashes. You could fetch
commits from one source and then change the source to another, they'd
still be the same commits. So if you're looking at a particular commit
hash (or tag) it will be identical in ALL mirrors.

The write-access repository is this:
https://git-wip-us.apache.org/repos/asf/lucene-solr.git

The read-only view is:
git://git.apache.org/lucene-solr.git

The same applies to github's mirror (which may be a few commits
behind, but will still contain identical commits, hashes, etc.)

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-NightlyTests-5.x - Build # 1081 - Still Failing

2016-01-23 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1081/

2 tests failed.
FAILED:  org.apache.solr.hadoop.MorphlineBasicMiniMRTest.mrRun

Error Message:
Failed on local exception: java.io.IOException: Connection reset by peer; Host 
Details : local host is: "lucene1-us-west/10.41.0.5"; destination host is: 
"lucene1-us-west.apache.org":59512; 

Stack Trace:
java.io.IOException: Failed on local exception: java.io.IOException: Connection 
reset by peer; Host Details : local host is: "lucene1-us-west/10.41.0.5"; 
destination host is: "lucene1-us-west.apache.org":59512; 
at 
__randomizedtesting.SeedInfo.seed([33287850551375AA:3D7ACC5E548547A5]:0)
at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:772)
at org.apache.hadoop.ipc.Client.call(Client.java:1472)
at org.apache.hadoop.ipc.Client.call(Client.java:1399)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:232)
at com.sun.proxy.$Proxy46.getClusterMetrics(Unknown Source)
at 
org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getClusterMetrics(ApplicationClientProtocolPBClientImpl.java:202)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
at com.sun.proxy.$Proxy47.getClusterMetrics(Unknown Source)
at 
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getYarnClusterMetrics(YarnClientImpl.java:461)
at 
org.apache.hadoop.mapred.ResourceMgrDelegate.getClusterMetrics(ResourceMgrDelegate.java:151)
at 
org.apache.hadoop.mapred.YARNRunner.getClusterMetrics(YARNRunner.java:179)
at 
org.apache.hadoop.mapreduce.Cluster.getClusterStatus(Cluster.java:246)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:719)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:717)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at 
org.apache.hadoop.mapred.JobClient.getClusterStatus(JobClient.java:717)
at 
org.apache.solr.hadoop.MapReduceIndexerTool.run(MapReduceIndexerTool.java:645)
at 
org.apache.solr.hadoop.MapReduceIndexerTool.run(MapReduceIndexerTool.java:608)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at 
org.apache.solr.hadoop.MorphlineBasicMiniMRTest.mrRun(MorphlineBasicMiniMRTest.java:363)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.8.0_66) - Build # 15326 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/15326/
Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseSerialGC

1 tests failed.
FAILED:  org.apache.solr.handler.TestReplicationHandler.doTestStressReplication

Error Message:
timed out waiting for collection1 startAt time to exceed: Sun Jan 24 07:30:36 
PONT 2016

Stack Trace:
java.lang.AssertionError: timed out waiting for collection1 startAt time to 
exceed: Sun Jan 24 07:30:36 PONT 2016
at 
__randomizedtesting.SeedInfo.seed([69FE43E94C15EB20:B255432F493D8293]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.solr.handler.TestReplicationHandler.watchCoreStartAt(TestReplicationHandler.java:1419)
at 
org.apache.solr.handler.TestReplicationHandler.doTestStressReplication(TestReplicationHandler.java:771)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)




Build Log:
[...truncated 10273 lines...]
   [junit4] Suite: 

[jira] [Commented] (LUCENE-6985) Create some (simple) guides on how to use git to perform common dev tasks

2016-01-23 Thread Paul Elschot (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114007#comment-15114007
 ] 

Paul Elschot commented on LUCENE-6985:
--

I have some long running branches against trunk that I needed to move onto 
master.
These branches regularly get trunk merged into them, so rebasing will not work.

This command sequence takes a local branch brn from trunk to master.
Except for the merge and the cherry-pick, these steps can be easily done in 
gitk, normally with a right click:

git checkout brn
git merge trunk # produce a merge commit, possibly resolve any conflicts.

git tag brn.20160123 # tag the merge commit
git branch -D prefilltokenstream # delete the branch

git checkout master
git branch brn # recreate the branch starting on master
git checkout brn 
git cherry-pick brn.20160123 -m 2 # add a commit with the diff to trunk as 
merged above



> Create some (simple) guides on how to use git to perform common dev tasks
> -
>
> Key: LUCENE-6985
> URL: https://issues.apache.org/jira/browse/LUCENE-6985
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Dawid Weiss
>Assignee: Dawid Weiss
>
> Some simple guides that demonstrate basic git principles and routine tasks 
> (below). The guides are here:
> https://github.com/dweiss/lucene-git-guides
> Core concepts
> 1. how to clone and setup lucene/solr git repo for local work
> 2. basic git concepts: branches, remote branches, references, staging area.
> Simple tasks:
> 1. Checkout branch X, create local branch Y, modify something, create a diff 
> for Jira.
> 2. Checkout branch X, create local branch Y, modify something, catch-up with 
> changes on X, create a diff for Jira.
> 3. Checkout branch X, create local branch Y, modify something, catch-up with 
> changes on X, apply aggregate changes from Y on X (as a single commit).
> 4. Backport feature/ commit C from branch X to Y via cherry picking.
> More advanced:
> 1. Create a feature branch off branch X, develop the feature, then apply it 
> as a series of commits to X.
> 2. Create a feature branch off branch X, develop the feature, then apply it 
> as a series of commits to X and Y (different branch).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_66) - Build # 15630 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15630/
Java: 64bit/jdk1.8.0_66 -XX:-UseCompressedOops -XX:+UseSerialGC

3 tests failed.
FAILED:  
junit.framework.TestSuite.org.apache.solr.cloud.CollectionsAPIDistributedZkTest

Error Message:
5 threads leaked from SUITE scope at 
org.apache.solr.cloud.CollectionsAPIDistributedZkTest: 1) Thread[id=6522, 
name=zkCallback-885-thread-3, state=TIMED_WAITING, 
group=TGRP-CollectionsAPIDistributedZkTest] at 
sun.misc.Unsafe.park(Native Method) at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) 
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
 at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
 at 
java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941) 
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)   
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at java.lang.Thread.run(Thread.java:745)2) Thread[id=6057, 
name=TEST-CollectionsAPIDistributedZkTest.test-seed#[997BA144AABCAB13]-EventThread,
 state=WAITING, group=TGRP-CollectionsAPIDistributedZkTest] at 
sun.misc.Unsafe.park(Native Method) at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) 
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:494)
3) Thread[id=6056, 
name=TEST-CollectionsAPIDistributedZkTest.test-seed#[997BA144AABCAB13]-SendThread(127.0.0.1:55625),
 state=TIMED_WAITING, group=TGRP-CollectionsAPIDistributedZkTest] at 
java.lang.Thread.sleep(Native Method) at 
org.apache.zookeeper.ClientCnxnSocketNIO.cleanup(ClientCnxnSocketNIO.java:230)  
   at 
org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:1185)
 at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1110)4) 
Thread[id=6521, name=zkCallback-885-thread-2, state=TIMED_WAITING, 
group=TGRP-CollectionsAPIDistributedZkTest] at 
sun.misc.Unsafe.park(Native Method) at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) 
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
 at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
 at 
java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941) 
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)   
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at java.lang.Thread.run(Thread.java:745)5) Thread[id=6058, 
name=zkCallback-885-thread-1, state=TIMED_WAITING, 
group=TGRP-CollectionsAPIDistributedZkTest] at 
sun.misc.Unsafe.park(Native Method) at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) 
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
 at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
 at 
java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941) 
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)   
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at java.lang.Thread.run(Thread.java:745)

Stack Trace:
com.carrotsearch.randomizedtesting.ThreadLeakError: 5 threads leaked from SUITE 
scope at org.apache.solr.cloud.CollectionsAPIDistributedZkTest: 
   1) Thread[id=6522, name=zkCallback-885-thread-3, state=TIMED_WAITING, 
group=TGRP-CollectionsAPIDistributedZkTest]
at sun.misc.Unsafe.park(Native Method)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at 

[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.8.0_66) - Build # 5564 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5564/
Java: 32bit/jdk1.8.0_66 -client -XX:+UseParallelGC

1 tests failed.
FAILED:  
junit.framework.TestSuite.org.apache.solr.handler.TestSolrConfigHandlerCloud

Error Message:
ObjectTracker found 2 object(s) that were not released!!! 
[MockDirectoryWrapper, MockDirectoryWrapper]

Stack Trace:
java.lang.AssertionError: ObjectTracker found 2 object(s) that were not 
released!!! [MockDirectoryWrapper, MockDirectoryWrapper]
at __randomizedtesting.SeedInfo.seed([88C36B8E45EB62C2]:0)
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertNull(Assert.java:551)
at org.apache.solr.SolrTestCaseJ4.afterClass(SolrTestCaseJ4.java:229)
at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:834)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)




Build Log:
[...truncated 10890 lines...]
   [junit4] Suite: org.apache.solr.handler.TestSolrConfigHandlerCloud
   [junit4]   2> Creating dataDir: 
C:\Users\JenkinsSlave\workspace\Lucene-Solr-trunk-Windows\solr\build\solr-core\test\J1\temp\solr.handler.TestSolrConfigHandlerCloud_88C36B8E45EB62C2-001\init-core-data-001
   [junit4]   2> 2662712 INFO  
(SUITE-TestSolrConfigHandlerCloud-seed#[88C36B8E45EB62C2]-worker) [] 
o.a.s.SolrTestCaseJ4 Randomized ssl (false) and clientAuth (false)
   [junit4]   2> 2662712 INFO  
(SUITE-TestSolrConfigHandlerCloud-seed#[88C36B8E45EB62C2]-worker) [] 
o.a.s.BaseDistributedSearchTestCase Setting hostContext system property: 
/fd_tt/tb
   [junit4]   2> 2662715 INFO  
(TEST-TestSolrConfigHandlerCloud.test-seed#[88C36B8E45EB62C2]) [] 
o.a.s.c.ZkTestServer STARTING ZK TEST SERVER
   [junit4]   2> 2662715 INFO  (Thread-7062) [] o.a.s.c.ZkTestServer client 
port:0.0.0.0/0.0.0.0:0
   [junit4]   2> 2662715 INFO  (Thread-7062) [] o.a.s.c.ZkTestServer 
Starting server
   [junit4]   2> 2662826 INFO  
(TEST-TestSolrConfigHandlerCloud.test-seed#[88C36B8E45EB62C2]) [] 
o.a.s.c.ZkTestServer start zk server on port:63008
   [junit4]   2> 2662826 INFO  
(TEST-TestSolrConfigHandlerCloud.test-seed#[88C36B8E45EB62C2]) [] 
o.a.s.c.c.SolrZkClient Using default ZkCredentialsProvider
   [junit4]   2> 2662827 INFO  
(TEST-TestSolrConfigHandlerCloud.test-seed#[88C36B8E45EB62C2]) [] 
o.a.s.c.c.ConnectionManager Waiting for client to connect to ZooKeeper
   [junit4]   2> 2662831 INFO  (zkCallback-2348-thread-1) [] 
o.a.s.c.c.ConnectionManager Watcher 
org.apache.solr.common.cloud.ConnectionManager@1db20d4 name:ZooKeeperConnection 
Watcher:127.0.0.1:63008 got event WatchedEvent state:SyncConnected type:None 
path:null path:null type:None
   [junit4]   2> 2662832 INFO  
(TEST-TestSolrConfigHandlerCloud.test-seed#[88C36B8E45EB62C2]) [] 

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

2016-01-23 Thread Uwe Schindler
Thanks Dawid and Daniel,

I am happy with the migration, only one small thing (but its too late to fix 
this):

It is a bit stupid that the last commit in SVN was just reverted and not made 
completely hidden. I would have synced up the converted repo only up to the 
revision before the final *delete all* commit instead of reverting it. Now we 
have a change on every file, which shows 2 useless commits on every file when 
browsing through history. I think we can only remove that 2 commits by 
rewriting history, so not sure. In any case, I am happy.

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: Saturday, January 23, 2016 10:11 PM
> To: dev@lucene.apache.org
> Cc: Dawid Weiss ; Daniel Gruno
> 
> Subject: 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 McCandless
> >>
> >> http://blog.mikemccandless.com
> >>
> >>
> >> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
> >>  wrote:
> >>> Got it, thanks! I'll try your suggestion, Dawid.
> >>>
> >>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss 
> wrote:
>  If you're using github then yes, you will need to fork again and
>  rebase any changes you may have. This can be done by having two
>  origins locally (two "sources" of commits) -- one from the old clone,
>  the second one from the new clone. Then you can rebase the branches
> or
>  commits you wish and push them to the new clone.
> 
>  Dawid
> 
> 
>  On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno
>  wrote:
> > On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> >> Thanks Dawid and Daniel for all the work!
> >>
> >> One strange thing that I noticed is that my fork of apache/lucene-
> solr
> >> at https://github.com/shalinmangar/lucene-solr is now shown to be
> a
> >> fork of https://github.com/mdodsworth/lucene-solr. I have no idea
> who
> >> that guy is. What can we do to fix this?
> >
> > Nothing. This is GitHub's fallback method when the original repository
> > goes away as it did here (replaced with a new repo with a new
> history).
> > Since referring to the old repo which doesn't exist anymore would
> break
> > your copy, they have fallen back to another copy of it.
> >
> > Please re-fork.
> >
> > With regards,
> > Daniel.
> >
> >>
> >> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss
>  wrote:
> >>> 1. The content of the lucene-solr.git repository looks good!
> >>>
> >>> 2) PROBLEM. I can't push my own branch:
> >>>
> >>> $ git co master -b git-check
> >>> $ [... committed a dummy commit ]
> >>> $ git push origin HEAD -u
> >>> fatal: remote error: access denied or repository not exported:
> /lucene-solr.git
> >>>
> >>> 3) Solr repo is still available for some reason, both as real git repo
> here:
> >>>
> >>> git://git.apache.org/solr.git
> >>>
> >>> and listed here:
> >>>
> >>> https://git.apache.org/
> >>>
> >>> Could I be seeing a mirror or something?
> >>>
> >>> Dawid
> >>>
> >>>
> >>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss
>  wrote:
>  Checking everything now -- that was fast Daniel!
>  Dawid
> 
> 
>  On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno
>  wrote:
> > Just a heads up: Everything is working now and GitHub has
> caught up with
> > the new repository. You should be good to go :)
> >
> > With regards,
> > Daniel.
> >
> > On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> >> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> >>> Hello Daniel,
> >>>
> >>> I've prepared everything for the migration and I hand it off to
> you (I
> >>> will be available in the morning, if you need assistance). I can
> also
> >>> log on to hipchat, but send me an e-mail if you wish me to.
> >>>
> >>> Here are the steps we kindly ask you to perform (I allowed
> myself to
> >>> uppercase certain things, apologies if it looks like shouting):
> >>>
> >>> 1) Permanently REMOVE the following git mirrors of SVN
> (reason: they
> >>> are obsolete and incorrect syncs, consolidated git repo
> contains full
> >>> 

[jira] [Commented] (LUCENE-6938) Convert build to work with Git rather than SVN.

2016-01-23 Thread Uwe Schindler (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114024#comment-15114024
 ] 

Uwe Schindler commented on LUCENE-6938:
---

As we currently have no auto-comments from the Git Bot:
- I improved the Git hash behaviour for non-Git checkouts or if Git executable 
is missing (like SVN did before)
- [~steve_rowe] added Git to the Maven build

> Convert build to work with Git rather than SVN.
> ---
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Mark Miller
>Assignee: Mark Miller
> Attachments: LUCENE-6938-1.patch, LUCENE-6938.patch, 
> LUCENE-6938.patch, LUCENE-6938.patch, LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to 
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from 
> LUCENE-6933.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-8589) Add aliases to the LIST action results in the Collections API

2016-01-23 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114037#comment-15114037
 ] 

Shawn Heisey commented on SOLR-8589:


I've discovered that the CREATEALIAS action does not validate whether the 
target collections actually exist.

I can understand a need to create an alias before the collection exists ... 
what I propose is that the action should normally validate, but have an option 
to toggle the validation.  Because of the potential for a backward 
compatibility break with existing user code, changing the default behavior 
would need to happen in 6.0.

> Add aliases to the LIST action results in the Collections API
> -
>
> Key: SOLR-8589
> URL: https://issues.apache.org/jira/browse/SOLR-8589
> Project: Solr
>  Issue Type: Improvement
>  Components: SolrCloud
>Affects Versions: 5.4.1
>Reporter: Shawn Heisey
>Assignee: Shawn Heisey
>Priority: Minor
> Attachments: SOLR-8589.patch, solr-8589-new-list-details-aliases.png
>
>
> Although it is possible to get a list of SolrCloud aliases vi an HTTP API, it 
> is not available as a typical query response, I believe it is only available 
> via the http API for zookeeper.
> The results from the LIST action in the Collections API is well-situated to 
> handle this. The current results are contained in a "collections" node, we 
> can simply add an "aliases" node if there are any aliases defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[JENKINS-EA] Lucene-Solr-trunk-Linux (32bit/jdk-9-ea+95) - Build # 15629 - Failure!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15629/
Java: 32bit/jdk-9-ea+95 -server -XX:+UseConcMarkSweepGC -XX:-CompactStrings

1 tests failed.
FAILED:  org.apache.lucene.search.TestLatLonPointQueries.testMultiValued

Error Message:
some hits were wrong

Stack Trace:
java.lang.AssertionError: some hits were wrong
at 
__randomizedtesting.SeedInfo.seed([923AA3F9FC1CEAC1:461AC7CB32DEAA89]:0)
at org.junit.Assert.fail(Assert.java:93)
at 
org.apache.lucene.util.BaseGeoPointTestCase.testMultiValued(BaseGeoPointTestCase.java:322)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:747)




Build Log:
[...truncated 7538 lines...]
   [junit4] Suite: org.apache.lucene.search.TestLatLonPointQueries
   [junit4]   1> 
TEST-TestLatLonPointQueries.testMultiValued-seed#[923AA3F9FC1CEAC1]: id=4015 
docID=4015 should match but did not
   [junit4]   1>   rect=GeoRect(lon=-6.510150580122516 TO -5.067347279310519 
lat=-56.95136302061232 TO -55.6007372269333)
   [junit4]   1>   lat=-55.76429421922066 lon=-5.035505435552694
   [junit4]   1>   lat=-56.84061597766225 lon=-5.06734725242745
   [junit4]   1>   result1=false result2=true
   [junit4]   2> NOTE: reproduce with: ant test  
-Dtestcase=TestLatLonPointQueries -Dtests.method=testMultiValued 
-Dtests.seed=923AA3F9FC1CEAC1 -Dtests.multiplier=3 

[jira] [Commented] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

2016-01-23 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114185#comment-15114185
 ] 

Joel Bernstein commented on SOLR-8573:
--

Just committed this to the new github repo. I don't believe it's connected to 
jira yet so here is the link to the commit:

https://github.com/apache/lucene-solr/commit/a3064d36bba0c613ca099aeda5af156fcf39ba76

> Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and 
> getWarnings
> --
>
> Key: SOLR-8573
> URL: https://issues.apache.org/jira/browse/SOLR-8573
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: Trunk
>Reporter: Kevin Risden
> Fix For: Trunk
>
> Attachments: SOLR-8573.patch, SOLR-8573.patch
>
>
> 2016-01-20 10:20:30.877 WARN   685 [ExecutorRunner-pool-2-thread-2 - C.ᅣチ] 
> Internal error while executing: select fielda, count(fieldc) from test group 
> by fielda
> java.lang.UnsupportedOperationException
>   at 
> org.apache.solr.client.solrj.io.sql.StatementImpl.clearWarnings(StatementImpl.java:186)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.onseven.dbvis.h.B.B.ᅣチ(Z:194)
>   at com.onseven.dbvis.h.B.F$A.call(Z:1369)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

2016-01-23 Thread Joel Bernstein (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joel Bernstein updated SOLR-8573:
-
Affects Version/s: (was: Trunk)
   6.0

> Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and 
> getWarnings
> --
>
> Key: SOLR-8573
> URL: https://issues.apache.org/jira/browse/SOLR-8573
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: 6.0
>Reporter: Kevin Risden
> Fix For: 6.0
>
> Attachments: SOLR-8573.patch, SOLR-8573.patch
>
>
> 2016-01-20 10:20:30.877 WARN   685 [ExecutorRunner-pool-2-thread-2 - C.ᅣチ] 
> Internal error while executing: select fielda, count(fieldc) from test group 
> by fielda
> java.lang.UnsupportedOperationException
>   at 
> org.apache.solr.client.solrj.io.sql.StatementImpl.clearWarnings(StatementImpl.java:186)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.onseven.dbvis.h.B.B.ᅣチ(Z:194)
>   at com.onseven.dbvis.h.B.F$A.call(Z:1369)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

2016-01-23 Thread Joel Bernstein (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joel Bernstein updated SOLR-8573:
-
Fix Version/s: (was: Trunk)
   6.0

> Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and 
> getWarnings
> --
>
> Key: SOLR-8573
> URL: https://issues.apache.org/jira/browse/SOLR-8573
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: 6.0
>Reporter: Kevin Risden
> Fix For: 6.0
>
> Attachments: SOLR-8573.patch, SOLR-8573.patch
>
>
> 2016-01-20 10:20:30.877 WARN   685 [ExecutorRunner-pool-2-thread-2 - C.ᅣチ] 
> Internal error while executing: select fielda, count(fieldc) from test group 
> by fielda
> java.lang.UnsupportedOperationException
>   at 
> org.apache.solr.client.solrj.io.sql.StatementImpl.clearWarnings(StatementImpl.java:186)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.onseven.dbvis.h.B.B.ᅣチ(Z:194)
>   at com.onseven.dbvis.h.B.F$A.call(Z:1369)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Resolved] (SOLR-8573) Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and getWarnings

2016-01-23 Thread Joel Bernstein (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joel Bernstein resolved SOLR-8573.
--
Resolution: Implemented

> Implement ConnectionImpl,StatementImpl,ResultSetImpl clearWarnings and 
> getWarnings
> --
>
> Key: SOLR-8573
> URL: https://issues.apache.org/jira/browse/SOLR-8573
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: 6.0
>Reporter: Kevin Risden
> Fix For: Trunk
>
> Attachments: SOLR-8573.patch, SOLR-8573.patch
>
>
> 2016-01-20 10:20:30.877 WARN   685 [ExecutorRunner-pool-2-thread-2 - C.ᅣチ] 
> Internal error while executing: select fielda, count(fieldc) from test group 
> by fielda
> java.lang.UnsupportedOperationException
>   at 
> org.apache.solr.client.solrj.io.sql.StatementImpl.clearWarnings(StatementImpl.java:186)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.onseven.dbvis.h.B.B.ᅣチ(Z:194)
>   at com.onseven.dbvis.h.B.F$A.call(Z:1369)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-8581) Integration tests for rolling upgrades

2016-01-23 Thread Mark Miller (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114160#comment-15114160
 ] 

Mark Miller commented on SOLR-8581:
---

+1. If we want to support this for real, requires tests. 

>  Integration tests for rolling upgrades
> ---
>
> Key: SOLR-8581
> URL: https://issues.apache.org/jira/browse/SOLR-8581
> Project: Solr
>  Issue Type: Test
>Reporter: Vivek Narang
>
> I intend to work on an integration test suite for Solr, to test for issues to 
> deal with back compat, rolling upgrades etc.
> The interface for the test suite, as I'm planning, would be to have it accept 
> two versions of Solr (either released versions or trunk/branch).
> I work on SolrCloud, and we need something like this to enable us to upgrade 
> more frequently. I had a conversation with @Ishan Chattopadhyaya, who 
> emphasised to me the need to have something like this.
> If there's already any ongoing effort in doing this, I can help out there. 
> Please let me know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: GIT migration complete

2016-01-23 Thread Joel Bernstein
I had no problem pushing my first commit. But I didn't seem to have
permission to merge a pull-request from Github. Is there another layer of
permissions that need to be setup for this?

Joel Bernstein
http://joelsolr.blogspot.com/

On Sat, Jan 23, 2016 at 1:23 PM, Yonik Seeley  wrote:

> Here's a useful thing you can add to your .profile , it conditionally
> displays the branch you are on in your shell prompt:
> https://gist.github.com/yonik/04b2e759eecf5ef96383
>
> Example:
>
> /opt/code$ cd lusolr
> [master] /opt/code/lusolr$
>
> -Yonik
>
>
> On Sat, Jan 23, 2016 at 12:55 PM, Ramkumar R. Aiyengar
>  wrote:
> > Not a big deal, but guys, do check if your mail is set properly in
> > ~/.gitconfig, otherwise commits would show your personal mail as the
> author.
> > Committer still shows up as your apache mail address, but many UIs hide
> it
> > by default, and might not be apparent to those new to the project/git..
> >
> > Example .gitconfig snippet allowing you to keep your existing name/mail
> but
> > override for apache.org..
> >
> > [user "https://git-wip-us.apache.org;]
> > name = Ramkumar Aiyengar
> > mail = andyetitmo...@apache.org
> >
> >
> > On Sat, Jan 23, 2016 at 3:41 PM, Uwe Schindler  wrote:
> >>
> >> Hi,
> >>
> >> I migrated all Policeman and ASF Jenkins Jobs to Git. Everything should
> be
> >> set up now.
> >> The Jobs for 5.3 and 5.4 were deleted.
> >>
> >> Uwe
> >>
> >> -
> >> Uwe Schindler
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >>
> >> > -Original Message-
> >> > From: Uwe Schindler [mailto:u...@thetaphi.de]
> >> > Sent: Saturday, January 23, 2016 11:05 AM
> >> > To: dev@lucene.apache.org
> >> > Subject: RE: GIT migration complete
> >> >
> >> > Hi,
> >> >
> >> > Thanks! I am talking care of Jenkins at the moment.
> >> >
> >> > First Policeman one is working:
> >> > http://jenkins.thetaphi.de/job/Lucene-Solr-
> >> > trunk-Linux/15619/console
> >> >
> >> > The Changes I do for jenkins is:
> >> > - Deleted *all* workspaces to have clean start
> >> > - Change all Jobs (is a bit of work as manually, especially for ASF)
> to
> >> > use Git
> >> > checkouts of corresponding branch
> >> > - Add the following "additional behaviour" config: Clean before
> >> > checkout:
> >> > Clean up the workspace before every checkout by deleting all untracked
> >> > files
> >> > and directories, including those which are specified in .gitignore. It
> >> > also resets
> >> > all tracked files to their versioned state. This ensures that the
> >> > workspace is in
> >> > the same state as if you cloned and checked out in a brand-new empty
> >> > directory, and ensures that your build is not affected by the files
> >> > generated
> >> > by the previous build.
> >> >
> >> > Uwe
> >> >
> >> > -
> >> > Uwe Schindler
> >> > H.-H.-Meier-Allee 63, D-28213 Bremen
> >> > http://www.thetaphi.de
> >> > eMail: u...@thetaphi.de
> >> >
> >> > > From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> >> > > Sent: Saturday, January 23, 2016 10:13 AM
> >> > > To: dev@lucene.apache.org
> >> > > Subject: GIT migration complete
> >> > >
> >> > > Ok, folks. Seems like code migration is complete, with both gh
> mirrors
> >> > > and Apache repos up.
> >> > >
> >> > > 1. Please read the docs at: https://git-wip-us.apache.org/
> >> > >
> >> > > 2. I didn't realize Apache's repositories are over https, which
> makes
> >> > > authorization rather painful for Linux users (requires password
> typing
> >> > > on every push). I think I'll stick with gh for this reason and only
> >> > > push my changes when they're fully baked.
> >> > >
> >> > > 3. The master branch (former trunk) passes ant precommit for me,
> but I
> >> > > didn't apply build patches to branch_5x yet.
> >> > >
> >> > > If there are any problems or concerns, let me know (perhaps I'll be
> >> > > able to help).
> >> > >
> >> > > Dawid
> >> > >
> >> > >
> -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> > > For additional commands, e-mail: dev-h...@lucene.apache.org
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> >
> >
> > --
> > Not sent from my iPhone or my Blackberry or anyone else's
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


Re: Releasing 5.3.2

2016-01-23 Thread Steve Rowe
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
> release but that would also mean that the default download link changes to
> 5.3.2 from 5.4.1. I'm not sure if that's a good idea.
>
> We haven't really run into this issue before so I'm thinking about not
> changing that link as part of the release process in such cases. What do
> you guys think?
>
> --
> Anshum Gupta
>


[JENKINS] Lucene-Solr-trunk-Windows (32bit/jdk1.8.0_66) - Build # 5565 - Still Failing!

2016-01-23 Thread Policeman Jenkins Server
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5565/
Java: 32bit/jdk1.8.0_66 -server -XX:+UseSerialGC

1 tests failed.
FAILED:  org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir

Error Message:
Exception during query

Stack Trace:
java.lang.RuntimeException: Exception during query
at 
__randomizedtesting.SeedInfo.seed([7AF68A38CE54D66B:93AC310050CD46C3]:0)
at org.apache.solr.SolrTestCaseJ4.assertQ(SolrTestCaseJ4.java:755)
at 
org.apache.solr.core.TestArbitraryIndexDir.testLoadNewIndexDir(TestArbitraryIndexDir.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1764)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:871)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:907)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:921)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:50)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:49)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:809)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:460)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:880)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:781)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:816)
at 
com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:827)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
at 
org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:46)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:42)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:54)
at 
org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:48)
at 
org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:65)
at 
org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:55)
at 
com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at 
com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:367)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: REQUEST FAILED: xpath=*[count(//doc)=1]
xml response was: 

00


request was:q=id:2=standard=0=20=2.2
at 

[jira] [Comment Edited] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

2016-01-23 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114204#comment-15114204
 ] 

Joel Bernstein edited comment on SOLR-8519 at 1/24/16 5:10 AM:
---

I was thinking about about having the SQLHandler populate the meta-data in the 
first tuple. The approach would be to wrap a MetaDataStream around the 
TupleStream compiled from the SQL statement. The MetaDataStream would then 
inject the meta-data into the first tuple in the read() method, and simply pass 
through all the other tuples. This would also allow us to pass an ordered list 
of fields in the meta-data.


was (Author: joel.bernstein):
I was thinking about about having the SQLHandler populate the meta-data in the 
first tuple. The approach would be to wrap a MetaDataStream around the 
TupleStream compiled from the SQL statement. The MetaDataStream would then 
inject the meta-data into the first tuple in the read() method, and simply pass 
through all the other tuples. This would also allow us it pass an ordered list 
of fields in the meta-data.

> Implement ResultSetMetaDataImpl.getColumnCount()
> 
>
> Key: SOLR-8519
> URL: https://issues.apache.org/jira/browse/SOLR-8519
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: Trunk
>Reporter: Kevin Risden
> Attachments: SOLR-8519.patch, SOLR-8519.patch
>
>
> DBVisualizer uses getColumnCount to determine how many columns to try to 
> display from the result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Comment Edited] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

2016-01-23 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114204#comment-15114204
 ] 

Joel Bernstein edited comment on SOLR-8519 at 1/24/16 5:08 AM:
---

I was thinking about about having the SQLHandler populate the meta-data in the 
first tuple. The approach would be to wrap a MetaDataStream around the 
TupleStream compiled from the SQL statement. The MetaDataStream would then 
inject the meta-data into the first tuple in the read() method, and simply pass 
through all the other tuples. This would also allow us it pass an ordered list 
of fields in the meta-data.


was (Author: joel.bernstein):
I was thinking about about having the SQLHandler populate the meta-data in the 
first tuple. The approach would be to wrap a MetaDataStream around the 
TupleStream compiled from SQL statement. The MetaDataStream would then inject 
the meta-data into the first tuple in the read() method, and simply pass 
through all the other tuples. This would also allow us it pass an ordered list 
of fields in the meta-data.

> Implement ResultSetMetaDataImpl.getColumnCount()
> 
>
> Key: SOLR-8519
> URL: https://issues.apache.org/jira/browse/SOLR-8519
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: Trunk
>Reporter: Kevin Risden
> Attachments: SOLR-8519.patch, SOLR-8519.patch
>
>
> DBVisualizer uses getColumnCount to determine how many columns to try to 
> display from the result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-8519) Implement ResultSetMetaDataImpl.getColumnCount()

2016-01-23 Thread Joel Bernstein (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114204#comment-15114204
 ] 

Joel Bernstein commented on SOLR-8519:
--

I was thinking about about having the SQLHandler populate the meta-data in the 
first tuple. The approach would be to wrap a MetaDataStream around the 
TupleStream compiled from SQL statement. The MetaDataStream would then inject 
the meta-data into the first tuple in the read() method, and simply pass 
through all the other tuples. This would also allow us it pass an ordered list 
of fields in the meta-data.

> Implement ResultSetMetaDataImpl.getColumnCount()
> 
>
> Key: SOLR-8519
> URL: https://issues.apache.org/jira/browse/SOLR-8519
> Project: Solr
>  Issue Type: Sub-task
>  Components: SolrJ
>Affects Versions: Trunk
>Reporter: Kevin Risden
> Attachments: SOLR-8519.patch, SOLR-8519.patch
>
>
> DBVisualizer uses getColumnCount to determine how many columns to try to 
> display from the result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



  1   2   >