Shingo Sasaki created SOLR-7335:
---
Summary: Multivalue field that is boosted on indexing time has
wrong norm.
Key: SOLR-7335
URL: https://issues.apache.org/jira/browse/SOLR-7335
Project: Solr
I
> [...] since we're being all formal and such ;-)
I support Robert here -- diminutive forms are tricky, especially the
English ones and especially for non-native speakers of the language. I
clearly remember the jaw-dropping moment I found out Bob is actually
Robert and Ted stands for Edward...
An
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390032#comment-14390032
]
Ishan Chattopadhyaya commented on SOLR-7274:
Even the basic auth implementation
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389336#comment-14389336
]
Ishan Chattopadhyaya edited comment on SOLR-7274 at 4/1/15 5:44 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390016#comment-14390016
]
ASF subversion and git services commented on SOLR-7325:
---
Commit 16705
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.1-Linux/181/
Java: 64bit/jdk1.7.0_76 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.RecoveryAfterSoftCommitTest.test
Error Message:
Didn't see all replicas for shard shard1 in collection1 come up within 3
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2869/
3 tests failed.
FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test
Error Message:
IOException occured when talking to server at:
http://127.0.0.1:43024/c8n_1x3_commits_shard1_replica3
Stack Trace:
org.ap
I opened https://issues.apache.org/jira/browse/LUCENE-6383 as a
followup. The fix should work for this test at least, i beasted the
test over 100 times and it seems ok now.
On Wed, Apr 1, 2015 at 12:02 AM, Robert Muir wrote:
> I committed a fix. But I think memoryPF can get really wasteful here.
[
https://issues.apache.org/jira/browse/LUCENE-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389982#comment-14389982
]
Robert Muir commented on LUCENE-6383:
-
We should also look into why [~jpountz]'s test
[
https://issues.apache.org/jira/browse/LUCENE-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved LUCENE-6378.
---
Resolution: Fixed
Fix Version/s: (was: 5.1)
5.2
Thanks Mike and
[
https://issues.apache.org/jira/browse/LUCENE-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389977#comment-14389977
]
ASF subversion and git services commented on LUCENE-6378:
-
Commit
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/4622/
Java: 32bit/jdk1.8.0_40 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestSolrConfigHandler
Error Message:
Could not remove the following files (in the order of attempts
Robert Muir created LUCENE-6383:
---
Summary: MemoryPostings fst encoding can be surprisingly
inefficient (especially in tests, with payloads)
Key: LUCENE-6383
URL: https://issues.apache.org/jira/browse/LUCENE-6383
I committed a fix. But I think memoryPF can get really wasteful here.
This is ultimately the same problem as the TestDuelingCodecs OOM.
On Tue, Mar 31, 2015 at 11:08 PM, Robert Muir wrote:
> This reproduces. I'm digging.
>
> On Mon, Mar 2, 2015 at 9:52 AM, Apache Jenkins Server
> wrote:
>> Buil
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389945#comment-14389945
]
Noble Paul edited comment on SOLR-7274 at 4/1/15 3:55 AM:
--
Let me
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389945#comment-14389945
]
Noble Paul commented on SOLR-7274:
--
Let me give a thread dump of my thought process
* We
[
https://issues.apache.org/jira/browse/SOLR-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389939#comment-14389939
]
Erick Erickson commented on SOLR-7334:
--
Hmm, somehow I can't assign it to Upayavira, s
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389935#comment-14389935
]
Ishan Chattopadhyaya edited comment on SOLR-7274 at 4/1/15 3:37 AM:
-
Erick Erickson created SOLR-7334:
Summary: Admin UI does not show "Num Docs" and "Deleted Docs", and
"Heap Memory Usage is -1"
Key: SOLR-7334
URL: https://issues.apache.org/jira/browse/SOLR-7334
Proje
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389336#comment-14389336
]
Ishan Chattopadhyaya edited comment on SOLR-7274 at 4/1/15 3:36 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389935#comment-14389935
]
Ishan Chattopadhyaya commented on SOLR-7274:
Sure, sounds good. We could do the
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389933#comment-14389933
]
Anshum Gupta commented on SOLR-7274:
+1 on what Noble says.
Can we use what Cloudera d
[
https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389924#comment-14389924
]
Shawn Heisey commented on SOLR-7319:
Devolving into a general discussion about garbage
This reproduces. I'm digging.
On Mon, Mar 2, 2015 at 9:52 AM, Apache Jenkins Server
wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/774/
>
> 1 tests failed.
> REGRESSION:
> org.apache.lucene.index.TestIndexWriterForceMerge.testForceMergeTempSpaceUsage
>
> Error Messag
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/12008/
Java: 32bit/jdk1.8.0_40 -server -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.DistributedIntervalFacetingTest.test
Error Message:
Timeout occured while waiting response from server at:
https://127.0.0.1:47256/_bf/v/co
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389921#comment-14389921
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389918#comment-14389918
]
Noble Paul commented on SOLR-7274:
--
bq.I would think this one time editing would be perfor
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389915#comment-14389915
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
The problem is with NIGHTLY we generate many more documents, if we get
unlucky and get something like MemoryPostings also are indexing stuff
like payloads, we get huge FSTs (the outputs have big postings lists)
I don't want to lose coverage for Nightly/Direct so I removed the
NIGHTLY conditional l
Sounds good Mr. Muir (since we're being all formal and such ;-),
thanks for the heads up.
Cheers,
Tim
On Tue, Mar 31, 2015 at 6:02 PM, Robert Muir wrote:
> Hi Timothy,
>
> As a start I'd like to merge
> http://svn.apache.org/viewvc?view=revision&revision=1670530 to the 5.1
> branch.
>
> These ar
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389904#comment-14389904
]
Ishan Chattopadhyaya commented on SOLR-7274:
I would think this one time editin
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12174/
Java: 32bit/jdk1.8.0_60-ea-b06 -client -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test
Error Message:
There were too many update fails (25 > 20) - we expect it can happen, but
I can reproduce it with current 5.x, it hits OOME after about 15 minutes.
On Sat, Mar 14, 2015 at 11:01 AM, Apache Jenkins Server
wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/786/
>
> 1 tests failed.
> REGRESSION: org.apache.lucene.index.TestDuelingCodecs.testEquals
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389888#comment-14389888
]
Noble Paul commented on SOLR-7274:
--
Users editing web.xml is not an option
> Pluggable au
I picked same JVM version and args and revision number, and tried
beasting the seed and master seed. I cannot make this one fail. I
don't see a leak in OrdsBlockTreeTermsReader at a glance.
The test itself is provoking random low level exceptions and
assertHandlerRevision is masking some of them,
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2121/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.cloud.BasicDistributedZkTest.test
Error Message:
commitWithin did not work on node: http://127.0.0.1:51154/collection1
expect
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2868/
3 tests failed.
FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test
Error Message:
IOException occured when talking to server at:
http://127.0.0.1:48214/c8n_1x3_commits_shard1_replica1
Stack Trace:
org.ap
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389811#comment-14389811
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
Hi Timothy,
As a start I'd like to merge
http://svn.apache.org/viewvc?view=revision&revision=1670530 to the 5.1
branch.
These are the most frequent failures during nightly tests in lucene.
Changes are test-only.
-
To unsubscribe
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389800#comment-14389800
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389795#comment-14389795
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
I'm looking into this one next.
On Tue, Mar 31, 2015 at 1:06 PM, Apache Jenkins Server
wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/803/
>
> 1 tests failed.
> FAILED:
> junit.framework.TestSuite.org.apache.lucene.replicator.IndexAndTaxonomyReplicationClientTest
>
>
[
https://issues.apache.org/jira/browse/SOLR-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389775#comment-14389775
]
ASF subversion and git services commented on SOLR-7331:
---
Commit 16705
[
https://issues.apache.org/jira/browse/SOLR-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389771#comment-14389771
]
ASF subversion and git services commented on SOLR-7331:
---
Commit 16705
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4504/
Java: 64bit/jdk1.8.0_40 -XX:+UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestSolrConfigHandler
Error Message:
Could not remove the following files (in the order of
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389756#comment-14389756
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389750#comment-14389750
]
ASF subversion and git services commented on SOLR-7331:
---
Commit 16705
[
https://issues.apache.org/jira/browse/SOLR-7329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389748#comment-14389748
]
ASF subversion and git services commented on SOLR-7329:
---
Commit 16705
[
https://issues.apache.org/jira/browse/SOLR-7329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389738#comment-14389738
]
ASF subversion and git services commented on SOLR-7329:
---
Commit 16705
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12173/
Java: 32bit/jdk1.8.0_40 -client -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test
Error Message:
Error from server at
http://127.0.0.1:60061/s/compositeid_collection_with_router
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/4621/
Java: 64bit/jdk1.8.0_40 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.core.TestSolrConfigHandler
Error Message:
Could not remove the following files (in the or
Hi,
I have opened a pull request for
https://issues.apache.org/jira/browse/SOLR-7121
at https://github.com/apache/lucene-solr/pull/132
This PR allows clients to specify some threshold values beyond which the
targeted core can declare itself unhealthy and proactively go down to
recover.
When the
[
https://issues.apache.org/jira/browse/SOLR-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389659#comment-14389659
]
Timothy Potter commented on SOLR-6816:
--
[~yo...@apache.org] I opened SOLR-7332 for the
[
https://issues.apache.org/jira/browse/SOLR-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389653#comment-14389653
]
Timothy Potter commented on SOLR-7333:
--
Here's the original comment I made about this
Timothy Potter created SOLR-7333:
Summary: Make the poll queue time configurable and use knowledge
that a batch is being processed to poll efficiently
Key: SOLR-7333
URL: https://issues.apache.org/jira/browse/SOLR
[
https://issues.apache.org/jira/browse/SOLR-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389615#comment-14389615
]
Timothy Potter commented on SOLR-6820:
--
jfyi - my patch for SOLR-7332 includes the fix
[
https://issues.apache.org/jira/browse/SOLR-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter reassigned SOLR-6820:
Assignee: Timothy Potter
> The sync on the VersionInfo bucket in DistributedUpdateProcesser#
[
https://issues.apache.org/jira/browse/SOLR-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-7332:
-
Attachment: SOLR-7332.patch
First pass at a patch that seeds the version buckets with the max value
[
https://issues.apache.org/jira/browse/LUCENE-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6382:
---
Attachment: LUCENE-6382.patch
Another iteration: I dropped the limit to Integer.MAX_V
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389569#comment-14389569
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
link: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/
On Tue, Mar 31, 2015 at 6:53 PM, Robert Muir wrote:
> Nightly tests have only been executing in jenkins the last 14 days,
> and only on 5.x
>
> All 14 executions have failed.
>
> Before that, the last nightly test run was Dec 27, 2
Nightly tests have only been executing in jenkins the last 14 days,
and only on 5.x
All 14 executions have failed.
Before that, the last nightly test run was Dec 27, 2014.
I'm finding a lot of failures when beasting nightly tests. It would be
good for us to try to run and fix nightly tests to ge
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389556#comment-14389556
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389521#comment-14389521
]
Timothy Potter commented on SOLR-7240:
--
Marking this as a blocker for 5.1. Although bi
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter reopened SOLR-7240:
--
Assignee: Timothy Potter (was: Hoss Man)
> redirect / to /solr
>
>
>
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-7240:
-
Priority: Blocker (was: Major)
> redirect / to /solr
>
>
> K
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389505#comment-14389505
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2867/
3 tests failed.
FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test
Error Message:
IOException occured when talking to server at:
http://127.0.0.1:10211/c8n_1x3_commits_shard1_replica3
Stack Trace:
org.ap
Timothy Potter created SOLR-7332:
Summary: Seed version buckets with max version from index
Key: SOLR-7332
URL: https://issues.apache.org/jira/browse/SOLR-7332
Project: Solr
Issue Type: Sub-t
+1 for blocker based on the admin UI issues.
Joel Bernstein
http://joelsolr.blogspot.com/
On Tue, Mar 31, 2015 at 4:41 PM, Erick Erickson
wrote:
> Do we care that the admin UI doesn't show max Docs and deleted docs?
> At least when I try it in Chrome or Safari. And Heap Memory is
> displayed as
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389428#comment-14389428
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389423#comment-14389423
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389416#comment-14389416
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389408#comment-14389408
]
Anshum Gupta commented on SOLR-7275:
Jan, I am working on what I've described above as
Do we care that the admin UI doesn't show max Docs and deleted docs?
At least when I try it in Chrome or Safari. And Heap Memory is
displayed as -1.
I'll raise a JIRA if others see this same thing, blocker for 5.1 or not?
Erick
On Tue, Mar 31, 2015 at 9:45 AM, Noble Paul wrote:
> I've committed
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389336#comment-14389336
]
Ishan Chattopadhyaya edited comment on SOLR-7274 at 3/31/15 8:32 PM:
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389336#comment-14389336
]
Ishan Chattopadhyaya edited comment on SOLR-7274 at 3/31/15 8:29 PM:
[
https://issues.apache.org/jira/browse/SOLR-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389336#comment-14389336
]
Ishan Chattopadhyaya commented on SOLR-7274:
I am working on implementing plugg
And I almost always do it exactly the opposite, I develop on trunk
then backport via svn merge Shawn's comments are well taken though
assuming 5x is closest to what you're actually using.
But it doesn't matter that much to you because you can't commit anyway
so pick whichever one is most conve
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-6271:
---
Attachment: LUCENE-6271.patch
Here is a patch against trunk based on the issue branch. All nocommits
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389274#comment-14389274
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389273#comment-14389273
]
ASF subversion and git services commented on LUCENE-6378:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389272#comment-14389272
]
Timothy Potter commented on SOLR-7240:
--
Solr won't start if using: java -jar start.jar
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389256#comment-14389256
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389208#comment-14389208
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389202#comment-14389202
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389195#comment-14389195
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389187#comment-14389187
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389132#comment-14389132
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389129#comment-14389129
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker closed SOLR-7324.
---
Resolution: Fixed
Fix Version/s: 5.2
Trunk
Thanks Stephan!
> No need to call
[
https://issues.apache.org/jira/browse/SOLR-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389122#comment-14389122
]
ASF subversion and git services commented on SOLR-7324:
---
Commit 16704
Thank you Shawn for your suggestion.
Regards
On Tue, Mar 31, 2015 at 11:28 PM, Shawn Heisey wrote:
> On 3/31/2015 11:48 AM, luqman ulkhair wrote:
> > Thanks Gora,Can you please tell me should I checkout trunk or
> > branch?How does the development process work in asf?
>
> In terms of commits, we
[
https://issues.apache.org/jira/browse/SOLR-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389121#comment-14389121
]
Shai Erera commented on SOLR-7325:
--
[~shalinmangar] (or anyone else), if there are no obje
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389113#comment-14389113
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389107#comment-14389107
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
On 3/31/2015 11:48 AM, luqman ulkhair wrote:
> Thanks Gora,Can you please tell me should I checkout trunk or
> branch?How does the development process work in asf?
In terms of commits, we almost always commit first to trunk, then
backport to any branches that will also receive the change.
I perso
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2866/
4 tests failed.
REGRESSION: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
Didn't see all replicas for shard shard1 in c8n_1x2 come up within 3 ms!
ClusterState: { "control_collection":{ "replicationFa
[
https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389091#comment-14389091
]
ASF subversion and git services commented on LUCENE-6271:
-
Commit
On 31 March 2015 at 23:18, luqman ulkhair wrote:
> Thanks Gora,Can you please tell me should I checkout trunk or branch?How
> does the development process work in asf?
Sadly, I am not yet actively involved in Solr development, except as a
bystander. Hopefully, others can correct me if I mis-state
1 - 100 of 208 matches
Mail list logo